Loading vulnerability…
HawtJNI versions before 1.8 contain an insecure temporary-file handling flaw in the Library class. When native libraries are bundled in an archive and no custom library path is configured, the class extracts them to predictably named files in the system temporary directory. A local attacker can win the interval between extraction and loading by replacing the extracted library with attacker-controlled content.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A local arbitrary native-library overwrite vulnerability in HawtJNI caused by predictable temporary filenames used when extracting bundled native libraries.
A local race-condition/library-hijacking vulnerability in HawtJNI caused by extracting native libraries to predictable filenames in /tmp.
A local race-condition and predictable temporary-file vulnerability in HawtJNI that can allow replacement of extracted native libraries with malicious code.
A local privilege/code-execution risk in HawtJNI caused by predictable temporary native-library filenames, enabling a race-condition overwrite by a local attacker.
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.