Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

getfirefly/firefly

              develop @ c672f3a
            

Fixes

CVEs

HIGH

Peak severity

100.0%

Coverage

Highlights

Memory Corruption: 3 prior fixes. Scrutinize any change in this area.

.github/workflows: most-fixed (1 issue). Treat as high-risk during review.

4 high-severity fixes in this history; regressions here are high-impact.

Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Memory Corruption: Incorrect tuple pointer alignment allows metadata to be overwritten with arbitrary term values, causing severe memory corruption within the runtime. Developers must ensure correct layout adjustments and alignment restrictions during compiler optimization or struct layout definitions.

Memory Corruption: Cons cell heap cloning lacked proper validation, allowing non-heap pointers to escape into the process heap and corrupt the Garbage Collector. Validating pointer ownership prior to heap operations is critical.

Memory Corruption: Manual and redundant memory deallocation inside ProcessHeap's Drop implementation caused double-free vulnerabilities, which can lead to unstable system states or remote code execution. Manual deallocation should be avoided in favor of safe RAII wrappers.