CVE-2019-11831 — typo3/phar-stream-wrapper
CRITICALCVE-2019-11831 is a critical-severity (CVSS 9.8) Path Traversal vulnerability in typo3/phar-stream-wrapper. A fix is available for typo3/phar-stream-wrapper — see the affected versions and patch details below.
Directory Traversal in typo3/phar-stream-wrapper
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2019-11831 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,238 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
typo3/phar-stream-wrapper🐘typo3/phar-stream-wrapper🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/drupal🐘drupal/drupal🐘drupal/drupalReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
The PharStreamWrapper (aka phar-stream-wrapper) package 2.x before 2.1.1 and 3.x before 3.1.1 for TYPO3 does not prevent directory traversal, which allows attackers to bypass a deserialization protection mechanism, as demonstrated by a phar:///path/bad.phar/../good.phar URL.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/phar-stream-wrapper | ≥ 2.0.0&&< 2.1.1 | 2.1.1composer require typo3/phar-stream-wrapper:^2.1.1 |
| 🐘Packagist | typo3/phar-stream-wrapper | ≥ 3.0.0&&< 3.1.1 | 3.1.1composer require typo3/phar-stream-wrapper:^3.1.1 |
| 🐘Packagist | drupal/core | ≥ 7.0.0&&< 7.67.0 | 7.67.0composer require drupal/core:^7.67.0 |
| 🐘Packagist | drupal/core | ≥ 8.0.0&&< 8.6.16 | 8.6.16composer require drupal/core:^8.6.16 |
| 🐘Packagist | drupal/core | ≥ 8.7.0&&< 8.7.1 | 8.7.1composer require drupal/core:^8.7.1 |
| 🐘Packagist | drupal/drupal | ≥ 7.0.0&&< 7.67.0 | 7.67.0composer require drupal/drupal:^7.67.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/phar-stream-wrapper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/phar-stream-wrapper to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-11831 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2019-11831 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2019-11831. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2019-11831 in your dependencies?
O3 Security finds CVE-2019-11831 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.