Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
khronosgroup/glslang
main @ ce138e2
5
Fixes
1
CVEs
HIGH
Peak severity
Highlights
Memory Corruption: 3 prior fixes. Scrutinize any change in this area.
glslang/MachineIndependent/preprocessor: most-fixed (2 issues). Treat as high-risk during review.
3 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: Flawed buffer size calculations during memset initializations within the TGlslIoMapper constructor can cause critical heap or stack-based out-of-bounds memory corruption. This represents a recurring pattern in the mapping components.
Memory Safety: The preprocessor is highly vulnerable to stack-based buffer overflows due to hardcoded, narrow buffers. Enforcing uniform token length constraints is vital to prevent malformed or oversized input tokens from exceeding allocated memory.
Memory Corruption: Custom memory pool allocators (mem_Alloc) and legacy hash tables inside the preprocessor engine are prone to state desynchronization and corruption, necessitating their replacement with safer standard containers.