CVE-2015-8389

9.8 CRITICAL

📋 TL;DR

This vulnerability in PCRE (Perl Compatible Regular Expressions) library allows remote attackers to cause denial of service through infinite recursion by crafting specific regular expression patterns. It affects any software using vulnerable PCRE versions, including web browsers like Konqueror and various server applications.

💻 Affected Systems

Products:
  • PCRE library
  • Konqueror browser
  • Any software using PCRE for regex processing
Versions: PCRE versions before 8.38
Operating Systems: Linux, Unix-like systems, Any OS running affected software
Default Config Vulnerable: ⚠️ Yes
Notes: Applications must use PCRE for regex processing to be vulnerable. JavaScript engines using PCRE (like Konqueror's) are particularly exposed.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete system compromise, though this is theoretical and not demonstrated in public disclosures.

🟠

Likely Case

Denial of service through application crashes or resource exhaustion when processing malicious regex patterns.

🟢

If Mitigated

Limited impact with proper input validation and updated libraries, potentially causing only temporary service disruption.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Proof-of-concept demonstrates the infinite recursion pattern. Weaponization likely for DoS attacks but RCE not confirmed.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: PCRE 8.38 and later

Vendor Advisory: http://vcs.pcre.org/pcre/code/trunk/ChangeLog?view=markup

Restart Required: Yes

Instructions:

1. Update PCRE library to version 8.38 or later. 2. Recompile any applications statically linked to PCRE. 3. Restart affected services.

🔧 Temporary Workarounds

Input validation for regex patterns

all

Validate and sanitize regular expression inputs before processing

Limit regex complexity

all

Configure applications to limit recursion depth or timeout regex processing

🧯 If You Can't Patch

  • Implement WAF rules to block known malicious regex patterns
  • Isolate vulnerable systems from untrusted networks

🔍 How to Verify

Check if Vulnerable:

Check PCRE version with: pcretest -C

Check Version:

pcretest -C

Verify Fix Applied:

Verify PCRE version is 8.38 or higher: pcretest -C | grep 'PCRE version'

📡 Detection & Monitoring

Log Indicators:

  • Application crashes
  • High CPU usage from regex processing
  • Stack overflow errors

Network Indicators:

  • HTTP requests containing crafted regex patterns
  • Unusual traffic to regex processing endpoints

SIEM Query:

source="application.log" AND ("stack overflow" OR "recursion depth" OR "PCRE")

🔗 References

📤 Share & Export