Loading vulnerability…
dataSIMS Avionics ARINC 664-1 version 4.5.3 contains a local buffer overflow condition triggered by processing a manipulated milstd1553result.txt file. A maliciously crafted file (with carefully constructed payload and alignment sections) can cause memory corruption/overwrite during parsing/handling, which may be leveraged to achieve arbitrary code execution on the affected Windows system.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains an archival proof-of-concept for CVE-2021-47881, a local stack-based buffer overflow in Data Device Corporation dataSIMS Avionics ARINC 664-1 version 4.5.3 on Windows. Structure is small and straightforward: two exploit-related Python files under poc/ and three documentation files (README plus English and Turkish writeups). The original exploit file, poc/49577.py, is the verbatim Python 2 Exploit-DB submission; poc/poc_py3.py is a Python 3 port that preserves byte-identical output and adds argument parsing plus a layout display mode. Core capability: both scripts generate a malicious file named milstd1553result.txt. The payload is 1040 bytes long and is built from several filler segments followed by a 4-byte overwrite field. The documented saved return address/EIP overwrite occurs at offset 1007, with EIP set to 0x42424242 ('BBBB') when the vulnerable application reads the file. This demonstrates reliable control of the instruction pointer for crash/DoS and exploitability research, but not code execution. Important exploit limitations are explicit in the repository: this is a local file-based PoC only, not a remote exploit; it requires the target software to open/process the crafted result file; and the trailing 29-byte msfvenom shikata_ga_nai stub is non-functional. The included documentation explains that the stub decodes only a single 4-byte block and lacks the expected loop terminator, so execution would fall through into still-encoded bytes. As a result, the repository should be classified as a proof of concept demonstrating memory corruption and EIP control rather than an operational weaponized exploit. No network communication, C2, callback, or scanning behavior is present. The only meaningful fingerprintable target artifact in the code is the filename milstd1553result.txt, which is both the output of the PoC and the file the vulnerable application is expected to read back. The Python 3 port also supports --layout to print field offsets and -o/--out to choose an alternate output path.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.