LiveActive security incident?Get immediate response
CVE Record

CVE-2006-7230: Perl-Compatible Regular Expression (PCRE) library before 7.0 does not properly calculate the amount of memo...

Perl-Compatible Regular Expression (PCRE) library before 7.0 does not properly calculate the amount of memory needed for a compiled regular expression pattern when the (1) -x or (2) -i UTF-8 options change within the pattern, which allows context-dependent attackers to cause a denial of service (PCRE or glibc crash) via crafted regular expressions.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an old PCRE library flaw that can crash software when it compiles specially crafted regular expressions. The business impact is denial of service, not data theft, based on the supplied record. Exposure is most likely in legacy systems or embedded products still using PCRE before 7.0. Systems are exposed if they run PCRE before 7.0, including older Linux distribution packages or products embedding that library. Risk is highest where users, tenants, or integrations can supply regular expressions that applications compile. Treat as a legacy resilience issue. Prioritize internet-facing or multi-tenant services that accept user-defined regex. Broad emergency response is not supported by the supplied evidence, but outdated PCRE should be removed from supported environments. Mitigation focus: Inventory PCRE versions in operating systems, containers, appliances, and bundled application dependencies.; Apply vendor security updates from the relevant distribution or product advisory.; Upgrade affected PCRE deployments to a fixed, vendor-supported version not before 7.0..

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-2006-7230 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
3Source 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.