CVE-2019-12263 is a race-condition vulnerability in the Interpeak IPNET TCP/IP stack as used by Wind River VxWorks 6.9.4 and Vx7. The issue is described as TCP Urgent Pointer state confusion due to a race condition in the TCP component. According to the provided context, exploitation relies on concurrent access between the tNet0 network task and the receiving application, causing improper synchronization around TCP urgent-pointer handling and resulting in a buffer overflow condition in the TCP component. The flaw is part of the broader Ripple20/IPNET vulnerability set and affects supported VxWorks releases including 6.9.4.11, Vx7 SR540, and Vx7 SR610, as well as some older end-of-life versions; VxWorks 7 SR620 is reported as not affected.
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.