PHPApplication
CVE-2022-31628
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 · uneditedIn PHP versions before 7.4.31, 8.0.24 and 8.1.11, the phar uncompressor code would recursively uncompress "quines" gzip files, resulting in an infinite loop.
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 confidenceIn PHP versions before 7.4.31, 8.0.24, and 8.1.11, the phar uncompressor code contains a vulnerability where specially crafted 'quines' gzip files trigger recursive decompression, causing an infinite loop that results in denial of service.
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
< 7.4.31>= 8.0.0, < 8.0.24>= 8.1.0, < 8.1.11
FedoraOperating system
= 35= 36= 37
Debian LinuxOperating system
= 10.0= 11.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed PHP versionRun 'php -v' or 'php --version' to see the PHP interpreter versionAffected if Version is below 7.4.31, between 8.0.0 and 8.0.23, or between 8.1.0 and 8.1.10
-
Verify phar extension is enabledRun 'php -m' and look for 'phar' in the loaded modules listAffected if phar extension is loaded and PHP version is in the vulnerable range
-
Identify if PHP processes phar archivesReview application code and server configuration for usage of phar:// stream wrappers or phar functions like phar_open_read(), phar_extract_all(), or similarAffected if Applications or scripts process untrusted phar archives from external sources
If PHP version falls within the vulnerable ranges and the phar extension is enabled to process phar archives, the system is potentially affected by this infinite loop DoS vulnerability
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.4.318.0.248.1.11
Update PHP to version 7.4.31, 8.0.24, 8.1.11 or later to patch the vulnerable phar uncompressor code.
PHP 7.4.31, PHP 8.0.24, or PHP 8.1.11 (depending on your current major version branch)
- Identify current PHP version using 'php -v' or 'php --version'
- For PHP 7.4.x: Upgrade to 7.4.31 or later using system package manager (e.g., 'apt-get update && apt-get install php7.4' or 'yum update php74' or equivalent)
- For PHP 8.0.x: Upgrade to 8.0.24 or later
- For PHP 8.1.x: Upgrade to 8.1.11 or later
- Verify the fix by running 'php -v' and confirming the version number matches or exceeds the appropriate fixed release
- Restart any PHP-FPM or web server services to ensure the new version is active
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in PHP
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31628 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-31628 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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