LiveActive security incident?Get immediate response
CVE Record

CVE-2005-4872: Perl-Compatible Regular Expression (PCRE) library before 6.2 does not properly count the number of named ca...

Perl-Compatible Regular Expression (PCRE) library before 6.2 does not properly count the number of named capturing subpatterns, which allows context-dependent attackers to cause a denial of service (crash) via a regular expression with a large number of named subpatterns, which triggers a buffer overflow. NOTE: this issue was originally subsumed by CVE-2006-7224, but that CVE has been REJECTED and split.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an old PCRE library flaw where specially crafted regular expressions can crash software using vulnerable PCRE versions before 6.2. The business risk is service interruption, not confirmed data theft or code execution. Exposure depends on whether any deployed product still embeds or links to that legacy PCRE code. Most modern systems should not be exposed unless they run legacy distributions, appliances, or applications bundling PCRE before 6.2. Vendor advisories indicate downstream impact existed across some Linux and appliance ecosystems, but the bundle does not identify specific current affected products. Treat this as a legacy availability risk. Prioritize it in environments with old appliances, unsupported servers, or applications that process user-supplied regular expressions. It is not KEV-listed and the supplied sources do not show active exploitation. Mitigation focus: Identify systems and applications using PCRE before 6.2.; Check vendor advisories for supported update packages or appliance guidance.; Upgrade PCRE or vendor packages where fixes are available..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2005-4872 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.