dbcve.org
PHPApplication

CVE-2024-8932

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-22
Fix available
A fix is available. Upgrade to 8.1.31 / 8.2.26 or later.
See remediation →
100/100
Remediation priority · Urgent
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
In PHP versions 8.1.* before 8.1.31, 8.2.* before 8.2.26, 8.3.* before 8.3.14, uncontrolled long string inputs to ldap_escape() function on 32-bit systems can cause an integer overflow, resulting in an out-of-bounds write.

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

PHP's ldap_escape() function in versions 8.1 before 8.1.31, 8.2 before 8.2.26, and 8.3 before 8.3.14 has an integer overflow vulnerability when processing long string inputs on 32-bit systems, allowing attackers to write data beyond allocated buffer boundaries.

MitigationUpgrade PHP to version 8.1.31, 8.2.26, or 8.3.14 or later. Until patches are applied, avoid using ldap_escape() with untrusted long strings on 32-bit systems.

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
PHPApplication
Affected:>= 8.1.0, < 8.1.31>= 8.2.0, < 8.2.26>= 8.3.0, < 8.3.14
OntapApplication
Affected:= 9

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Identify PHP version
    Run 'php -v' or 'phpinfo()' to see the installed PHP version number
    Affected if Version is 8.1.0-8.1.30, 8.2.0-8.2.25, or 8.3.0-8.3.13
  2. Determine system architecture
    Run 'uname -m' or check system documentation to confirm if the OS and PHP are 32-bit (x86) or 64-bit (x86_64)
    Affected if Running on a 32-bit system (i386, i686, or similar)
  3. Locate ldap_escape usage
    Search PHP source code files for 'ldap_escape' function calls using grep or similar tooling
    Affected if Codebase uses the ldap_escape() function
  4. Assess input handling
    Review the ldap_escape() calls to determine if they process external or untrusted string input and estimate maximum input length
    Affected if ldap_escape() processes long strings from untrusted sources

You are affected if you run any PHP version 8.1.0-8.1.30, 8.2.0-8.2.25, or 8.3.0-8.3.13 on a 32-bit system AND use ldap_escape() with long external strings.

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.

dbcve · scoped
Upgrade available Upgrade to 8.1.31 / 8.2.26 / 8.3.14 or later
Fixed in 8.1.318.2.268.3.14
Interim mitigation

Upgrade PHP to version 8.1.31, 8.2.26, or 8.3.14 or later. Until patches are applied, avoid using ldap_escape() with untrusted long strings on 32-bit systems.

Recommended fix High confidence

Upgrade to PHP 8.1.31, 8.2.26, or 8.3.14 (or later in respective branch)

  1. Identify the currently installed PHP version using 'php -v' or 'php --version'
  2. Determine which PHP branch is in use (8.1.x, 8.2.x, or 8.3.x)
  3. For Debian/Ubuntu systems: Run 'sudo apt update' followed by 'sudo apt upgrade php' or 'sudo apt install php8.x' (replace 8.x with desired version)
  4. For RHEL/CentOS/Fedora: Run 'sudo dnf update php' or 'sudo yum update php'
  5. For Alpine: Run 'apk update' followed by 'apk upgrade php'
  6. Verify the upgrade was successful by running 'php -v' and confirming the version is 8.1.31+, 8.2.26+, or 8.3.14+
  7. If using PHP-FPM, restart the service: 'sudo systemctl restart php-fpm' or 'sudo service php-fpm restart'
  8. Test that LDAP functionality still works correctly after the upgrade
Caveat Minor point releases typically contain only bug/security fixes; however, review the PHP migration guides (php.net/manual/en/migration81.php, migration82.php, migration83.php) for any changes affecting custom code

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in PHP Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8932 — 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-2024-8932 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