Skip to content

Memory-safety analysis for C and C++ - #265

Merged
prabhu merged 2 commits into
mainfrom
feat/memsafe-part1
Sep 28, 2026
Merged

prabhu merged 2 commits into
mainfrom
feat/memsafe-part1

Conversation

@prabhu

@prabhu prabhu commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

Adds atom memory-safety, which runs chen's C/C++ memory-safety overlay and writes the findings as JSON.

  • --memory-api-config describes project allocator and copy APIs; --min-confidence filters findings.
  • --suggest-defines / --auto-defines: a census of the #if blocks hidden by undefined build macros, which suggests defines or applies the ones it can prove.
  • Scala 3.9.0 LTS; slicing semantics are built once per graph and scoped by language.

Results on the memory-safety corpus (baseline 0%): recall 62.77% / precision 98.33% at medium confidence, 75.53% / 95.95% at low, no findings on the negative controls. FFmpeg libavformat CVE litmus: 5/13 at medium and 7/13 at low (6 and 8 with --auto-defines), with no findings at the fixed sites.

Needs chen 4.0.0 (AppThreat/chen#188). Until it is published, CI builds chen from main in a temporary step (.github/actions/chen-from-main), so the checks pass once the chen PR is merged. Remove that step after the chen release.

…la 3.9.0, with a temporary CI step that builds chen from main
Signed-off-by: Prabhu Subramanian <prabhu@appthreat.com>
@prabhu
prabhu merged commit e9abb66 into main Sep 28, 2026
29 of 30 checks passed
@prabhu
prabhu deleted the feat/memsafe-part1 branch September 28, 2026 07:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant