Skip to main content
assistive.skiplink.to.breadcrumbs
assistive.skiplink.to.header.menu
assistive.skiplink.to.action.menu
assistive.skiplink.to.quick.search

Page History

Versions Compared

Key

This line was added.
This line was removed.
Formatting was changed.

...

Tool

Version

Checker

Description

Include Page

	CodeSonar_V
	CodeSonar_V

(customization)

Users can add a custom check for use of realloc().

Could detect possible violations of this rule by first flagging any usage of realloc(). Also, it could flag any usage of free that is not preceded by code to clear out the preceding memory, using memset. This heuristic is imperfect because it flags all possible data leaks, not just leaks of "sensitive" data, because ROSE cannot tell which data is sensitive

Include Page

	Helix QAC_V
	Helix QAC_V

C5010

LDRA tool suite

Include Page

	LDRA_V
	LDRA_V

44 S

Enhanced Enforcement

Parasoft C/C++test

Include Page

	Parasoft_V
	Parasoft_V

CERT_C-MEM03-a

Sensitive data should be cleared before being deallocated

Polyspace Bug Finder

Include Page

	Polyspace Bug Finder_V
	Polyspace Bug Finder_V

CERT C: Rec. MEM03-C

Checks for:

Sensitive heap memory not cleared before release
Uncleared sensitive data in stack

Sensitive data not cleared or released by memory routine

Variable in stack is not cleared and contains sensitive data

Rec. partially covered.

Include Page

	PVS-Studio_V
	PVS-Studio_V

V1072

Include Page

PRQA QA-C_v PRQA QA-C_v 5010 Partially implemented

Related Vulnerabilities

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

...