Loading vulnerability…
RTKLIB through version 2.4.3 contains an out-of-bounds write in the RTCM3 message parser, specifically in the decode_type1033 function. The vulnerable code fails to clamp attacker-influenced length counters to the size of fixed destination buffers, allowing writes beyond 64-byte descriptor fields. A crafted RTCM3 type-1033 message with a valid CRC can trigger up to a 191-byte overflow, corrupting adjacent members of the rtcm_t object. Because the vulnerable input can be delivered via an NTRIP correction stream or a serial RTCM3 correction stream, the flaw is remotely reachable in deployments that ingest untrusted correction data.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
5 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.