Page History

...

Reading previously dynamically allocated memory after it has been deallocated can lead to abnormal program termination and denial-of-service attacks. Writing memory that has been deallocated can lead to the execution of arbitrary code with the permissions of the vulnerable process.

Rule	Severity	Likelihood	Detectable	RepairableRemediation Cost	Priority	Level
MEM50-CPP	High	Likely	No	MediumNo	P18P9	L1L2

Automated Detection

Helix QAC

Tool

Version

Checker

Description

Astrée

Include Page

	Astrée_V
	Astrée_V

dangling_pointer_use

Axivion Bauhaus Suite

Include Page

	Axivion Bauhaus Suite_V
	Axivion Bauhaus Suite_V

CertC++-MEM50

Clang

Include Page

	Clang_V
	Clang_V

clang-analyzer-cplusplus.NewDelete
clang-analyzer-alpha.security.ArrayBoundV2

Checked by clang-tidy, but does not catch all violations of this rule.

CodeSonar

Include Page

	CodeSonar_V
	CodeSonar_V

ALLOC.UAF

Use after free

Compass/ROSE

Coverity

Include Page

	Coverity_V
	Coverity_V

USE_AFTER_FREE

Can detect the specific instances where memory is deallocated more than once or read/written to the target of a freed pointer

Helix QAC

Include Page

	Helix QAC_V
	Helix QAC_V

C++4303, C++4304

Klocwork

Include Page

	Klocwork_V
	Klocwork_V

UFM.DEREF.MIGHT
UFM.DEREF.MUST
UFM.FFM.MIGHT
UFM.FFM.MUST
UFM.RETURN.MIGHT
UFM.RETURN.MUST
UFM.USE.MIGHT
UFM.USE.MUSTMUST

LDRA tool suite

Include Page