STARM · SW-04 · SOFTWARE
Buffer Overflows
STARMCatalog entries from the DIPS Threat Inventory. The paper cites that dataset and does not use this name.
Overloading input buffers to execute unauthorized code.
Severity in the dataset8/10
Not the paper’s H/M/L.
- Target
- Program Logic
- Layer in the inventory
- Application / Backend
- Mitigation
- Using memory-safe languages (Rust) or static analysis.
- How the inventory says to fix it
- Rule-based: Stack canaries and NX bits. AI: Fuzzing during DevSecOps to find overflows before launch.
- Quick fix
- Limit input size
- ML approaches named
- RNN/LSTM for syscall sequences, Hidden Markov Models (HMM), Random Forest classifiers on runtime telemetry, eBPF-based ML anomaly models
- Methodology
- Abnormal memory access patterns, stack anomalies, unexpected crashes or reboots, unusual instruction flow
- Handler role
- Software Developer
- Stage
- Development
- Standard named
- ISO/IEC 27001
- Status in the inventory
- Fixed
STARMCatalog entries from the DIPS Threat Inventory. The paper cites that dataset and does not use this name.
Connection recorded in the inventory
Command Injection