VictoriaMetrics Snappy Decoder DoS Vulnerability is Causing OOM
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.110.23, 1.122.8, 1.129.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
VictoriaMetrics is a scalable solution for monitoring and managing time series data. In versions from 1.0.0 to before 1.110.23, from 1.111.0 to before 1.122.8, and from 1.123.0 to before 1.129.1, affected versions are vulnerable to DoS attacks because the snappy decoder ignored VictoriaMetrics request size limits allowing malformed blocks to trigger excessive memory use. This could lead to OOM errors and service instability. The fix enforces block-size checks based on MaxRequest limits. This issue has been patched in versions 1.110.23, 1.122.8, and 1.129.1.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- VictoriaMetrics VictoriaMetrics
From 1.0.0 · fixed in 1.110.23; From 1.111.0 · fixed in 1.122.8; From 1.123.0 · fixed in 1.129.1
- github.com/VictoriaMetrics/VictoriaMetricsGo
From 1.123.0 · fixed in 1.129.1
- github.com/VictoriaMetrics/VictoriaMetricsGo
From 1.111.0 · fixed in 1.122.8
- github.com/VictoriaMetrics/VictoriaMetricsGo
From 1.0.0 · fixed in 1.110.23
- github.com/VictoriaMetrics/VictoriaMetricsGo
fixed in 1.110.23; From 1.111.0 · fixed in 1.122.8; From 1.123.0 · fixed in 1.129.1