Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
yuin/gopher-lua
master @ 75f4976
2
Fixes
0
CVEs
HIGH
Peak severity
0.0%
Coverage
Highlights
Memory Corruption: 2 prior fixes. Scrutinize any change in this area.
alloc.go: most-fixed (1 issue). Treat as high-risk during review.
2 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: The custom memory allocator is highly sensitive to pointer arithmetic errors. Accessing slice memory via stale headers or manually computed offsets can result in Use-After-Free vulnerabilities. Developers must use direct slice index references rather than calculating offsets using raw pointer arithmetic.
Memory Corruption: Zero-copy casting optimizations (such as converting strings to read-only byte slices) bypass the Go compiler's escape analysis. Without explicit runtime keep-alive directives, the garbage collector may reclaim the underlying string data while the resulting byte slice is still actively referenced, leading to arbitrary memory corruption.