CVE-2015-8384 is a vulnerability in PCRE (Perl Compatible Regular Expressions) versions before 8.38, where the library mishandles certain recursive back references in regular expressions, such as the pattern /(?J)(?'d'(?'d'\g{d}))/ and similar constructs. This flaw can be triggered by a crafted regular expression, potentially leading to a buffer overflow. The vulnerability can be exploited remotely, for example, when a JavaScript RegExp object is processed by applications like Konqueror that use PCRE for regex evaluation. This issue is related to CVE-2015-8392 and CVE-2015-8395.
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.
1 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.