CVE-2014-3586 is a local information-disclosure vulnerability in the Command Line Interface of Red Hat JBoss Enterprise Application Platform and WildFly. The CLI creates its command-history file in the invoking user's home directory with insecure default permissions. Other local users may consequently read sensitive information retained in CLI command history.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
JBoss AS CLI insecure default permissions on its history file.
Insecure default permissions on the JBoss Application Server command-line interface history file (.jboss-cli-history), permitting local information disclosure.
An insecure default file-permissions flaw in the JBoss Enterprise Application Platform command-line interface history file.
An insecure default file-permissions flaw in the JBoss Enterprise Application Platform command-line interface history file that could let a local malicious user access otherwise unavailable information.
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.