Loading vulnerability…
In EVerest (EV charging software stack) versions prior to 2025.10.0, an integer overflow in SdpPacket::parse_header() can corrupt internal length tracking such that after a full 8-byte header is read, the current buffer length is set to 7. Subsequent computation of the remaining length to read (current length minus header length) yields a negative value, which is then passed/converted to a size_t and interpreted as SIZE_MAX (or slightly less). Depending on whether the server is operating over plain TCP or TLS, this results in either an infinite loop (unreachable exit condition) or a stack buffer overflow.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
SdpPacket::parse_header().No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.