Skip to content
Fencer Intel
medium 5.3

CVE-2024-32664 json

Suricata's base64 contains an out of bounds write

published 2y ago modified 4mo ago also EUVD-2024-30455

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known

Summary

Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to 7.0.5 and 6.0.19, specially crafted traffic or datasets can cause a limited buffer overflow. This vulnerability is fixed in 7.0.5 and 6.0.19. Workarounds include not use rules with `base64_decode` keyword with `bytes` option with value 1, 2 or 5 and for 7.0.x, setting `app-layer.protocols.smtp.mime.body-md5` to false.

Patch / fix

  • oisf suricata 6.0.19, 7.0.5
  • openinfosecfoundation suricata 6.0.19, 7.0.5
  • suricata-ids suricata 6.0.19, 7.0.5
  • suricata Debian 14, Debian 13 1:7.0.5-1

debian advisories DEBIAN-CVE-2024-32664

  • suricata openSUSE Tumbleweed 8.0.0-1.1

opensuse advisories openSUSE-SU-2025:15394-1

  • suricata Alpine 3.24, Alpine 3.23, Alpine 3.22 +2 more 7.0.6-r0

alpine advisories ALPINE-CVE-2024-32664

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2024-32664 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.87% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 3.1 7.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected products

  • OISF suricata

Classification

Weakness
  • CWE-122 Heap-based Buffer Overflow
  • CWE-120 Buffer Copy without Checking Size of Input

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.