PharstreamwrapperApplication · TYPO3
CVE-2019-11830
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 · uneditedPharMetaDataInterceptor in the PharStreamWrapper (aka phar-stream-wrapper) package 2.x before 2.1.1 and 3.x before 3.1.1 for TYPO3 mishandles Phar stub parsing, which allows attackers to bypass a deserialization protection mechanism.
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 confidenceThe PharMetaDataInterceptor in the phar-stream-wrapper library (versions 2.x before 2.1.1 and 3.x before 3.1.1) used by TYPO3 fails to properly handle Phar stub parsing, allowing attackers to circumvent the deserialization protection mechanism and potentially achieve remote code execution.
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
PharstreamwrapperApplication
>= 2.0.0, < 2.1.1>= 3.0.0, < 3.1.1CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify phar-stream-wrapper installationRun 'composer show phar-io/phar-stream-wrapper' in the TYPO3 project root to display the installed version, or inspect the composer.lock file for the 'phar-io/phar-stream-wrapper' package entry.Affected if The package is not installed or the version falls within the vulnerable ranges.
-
Verify vulnerable version rangeCompare the installed version number against the affected ranges: 2.0.0 <= version < 2.1.1 OR 3.0.0 <= version < 3.1.1.Affected if The installed version is 2.0.0 through 2.1.0, or 3.0.0 through 3.1.0.
-
Confirm TYPO3 usage of phar-stream-wrapperCheck if TYPO3 is using the phar-stream-wrapper for Phar file handling by examining the vendor directory at vendor/phar-io/phar-stream-wrapper/src/PharMetaDataInterceptor.php, or review TYPO3 configuration for phar handling.Affected if The PharMetaDataInterceptor class exists and is in use by the TYPO3 installation.
The environment is affected if the phar-stream-wrapper library is present with a version between 2.0.0 and 2.1.0, or between 3.0.0 and 3.1.0, and TYPO3 utilizes the PharMetaDataInterceptor for phar file processing.
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 · scoped2.1.13.1.1
Upgrade the phar-stream-wrapper package to version 2.1.1 or 3.1.1 (or higher) to patch the stub parsing vulnerability. In TYPO3, this is typically handled via Composer dependency update.
PharStreamWrapper 2.1.1 (for 2.x users) or 3.1.1 (for 3.x users)
- Identify which major version of PharStreamWrapper is currently installed (2.x or 3.x)
- For version 2.x: upgrade to PharStreamWrapper version 2.1.1 or later
- For version 3.x: upgrade to PharStreamWrapper version 3.1.1 or later
- Verify the upgrade was successful by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Pharstreamwrapper
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11830 — 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-2019-11830 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