dbcve.org
PcreApplication

CVE-2007-4767

MEDIUM · 5.0 CVSS v2.0 Published 2007-11-07
Fix available
A fix is available. Upgrade to after 7.3 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Perl-Compatible Regular Expression (PCRE) library before 7.3 does not properly compute the length of (1) a \p sequence, (2) a \P sequence, or (3) a \P{x} sequence, which allows context-dependent attackers to cause a denial of service (infinite loop or crash) or execute arbitrary code.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The PCRE library before 7.3 contains a flaw in how it calculates the length of Unicode property escapes (\p, \P, and \P{x} sequences). This improper length computation can cause the regex engine to enter an infinite loop, crash, or potentially execute arbitrary code when processing maliciously crafted regex patterns.

MitigationUpgrade PCRE library to version 7.3 or later. For systems using PCRE as an embedded library, rebuild and redeploy any applications statically linked against the vulnerable PCRE version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PcreApplication
Affected:<= 6.0<= 6.1<= 7.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed PCRE library version
    Run 'pcre-config --version' or 'pcregrep --version' or check the library file directly with 'ldd' on binaries or check /usr/lib/libpcre* files
    Affected if Version is 7.3 or lower (6.0, 6.1, or any version <= 7.3)
  2. Identify applications using PCRE
    Use 'ldd <binary>' or 'ldconfig -p | grep pcre' to list binaries linked against PCRE, or check package manager for installed packages containing 'pcre'
    Affected if Any application is dynamically linked to a vulnerable PCRE version
  3. Check for static PCRE linking in custom binaries
    If using custom-built software, review build documentation or use 'strings <binary> | grep pcre' to identify embedded PCRE versions
    Affected if Custom applications are statically linked to PCRE version 7.3 or lower
  4. Verify regex patterns use Unicode property escapes
    Search source code or configuration files for \p, \P, or \P{ patterns in regex definitions used by PCRE-dependent applications
    Affected if Any application processes regex patterns containing Unicode property escapes (\p{}, \P{}, or \P{x})

You are affected if your system has PCRE library version 7.3 or lower AND any application processes regex patterns using Unicode property escapes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 7.3
Interim mitigation

Upgrade PCRE library to version 7.3 or later. For systems using PCRE as an embedded library, rebuild and redeploy any applications statically linked against the vulnerable PCRE version.

Fix this in Pcre Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-4767 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-4767 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data