LiveActive security incident?Get immediate response
CVE Record

CVE-2005-2491: Integer overflow in pcre_compile.c in Perl Compatible Regular Expressions (PCRE) before 6.2, as used in mul...

Integer overflow in pcre_compile.c in Perl Compatible Regular Expressions (PCRE) before 6.2, as used in multiple products such as Python, Ethereal, and PHP, allows attackers to execute arbitrary code via quantifier values in regular expressions, which leads to a heap-based buffer overflow.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2005-2491 is an old PCRE flaw where specially crafted regular expression quantifiers can corrupt heap memory. Software that lets untrusted users supply regex patterns may face arbitrary code execution risk. The source bundle names PCRE before 6.2 and examples including Python, Ethereal, and PHP. Exposure is most likely in legacy systems or products embedding PCRE before 6.2, especially services accepting user-controlled regular expressions. The CVE record’s affected product metadata is incomplete, so confirm exposure through vendor packages, embedded libraries, and advisories. Treat as high priority for legacy environments and externally exposed services. This is unlikely to affect modern patched stacks, but the arbitrary-code-execution impact justifies targeted inventory and remediation where old PCRE or bundled copies remain. Mitigation focus: Upgrade PCRE to 6.2 or a vendor-supported fixed version.; Apply vendor advisories for products bundling or statically linking PCRE.; Inventory legacy Python, Ethereal, PHP, and appliance packages using PCRE..

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2005-2491 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.