dbcve.org
PharstreamwrapperApplication · TYPO3

CVE-2019-11831

CRITICAL · 9.8 CVSS v3.1 Published 2019-05-09
Fix available
A fix is available. Upgrade to 2.1.1 / 3.1.1 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
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.

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 PharStreamWrapper (phar-stream-wrapper) package used by TYPO3 fails to properly sanitize directory traversal sequences in phar:// URLs. Attackers can use paths like 'phar:///path/bad.phar/../good.phar' to bypass deserialization protection mechanisms that rely on blocking phar:// streams, potentially leading to remote code execution.

MitigationUpgrade PharStreamWrapper to version 2.1.1 or later for the 2.x branch, or 3.1.1 or later for the 3.x branch to obtain the directory traversal protection fix.

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
Affected:>= 2.0.0, < 2.1.1>= 3.0.0, < 3.1.1
Debian LinuxOperating system
Affected:= 8.0= 9.0
FedoraOperating system
Affected:= 28= 29= 30
DrupalCMS
Affected:>= 7.0, < 7.67>= 8.6.0, < 8.6.16>= 8.7.0, < 8.7.1
Joomla\!Application
Affected:>= 3.9.3, <= 3.9.5

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. Check PharStreamWrapper version in vendor directory
    If using Composer, run 'composer show phar-io/pharstreamwrapper' or inspect vendor/phar-io/pharstreamwrapper/composer.json for the version field
    Affected if version is >= 2.0.0 and < 2.1.1, or >= 3.0.0 and < 3.1.1
  2. Check TYPO3 CMS version
    In TYPO3, check typo3/sysext/core/Classes/Utility/GeneralUtility.php for version constant, or check typo3/sysext/core/composer.json
    Affected if TYPO3 CMS is installed and uses PharStreamWrapper with the vulnerable version range from step 1
  3. Check Drupal version
    Inspect core/lib/Drupal.php for the VERSION constant, or check composer.json if using Composer-based install
    Affected if Drupal version is 7.0-7.66, 8.6.0-8.6.15, or 8.7.0 and uses the vulnerable PharStreamWrapper
  4. Check Joomla version
    Inspect libraries/vendor/phar-io/pharstreamwrapper/composer.json or check the Joomla administrator about box for version number
    Affected if Joomla version is 3.9.3 through 3.9.5 and includes the vulnerable PharStreamWrapper package
  5. Verify phar:// stream handling is active
    Search codebase for usage of 'phar://' in file operations or unserialize() calls that process user-supplied data
    Affected if phar:// stream handling is enabled and processes untrusted input, allowing the directory traversal bypass to be exploited

Your environment is affected if any of the identified products (TYPO3, Drupal, Joomla) are using PharStreamWrapper versions 2.0.0-2.1.0 or 3.0.0-3.1.0 AND the application processes phar:// streams from untrusted sources.

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 2.1.1 / 3.1.1 / 7.67 or later
Fixed in 2.1.13.1.17.67
Interim mitigation

Upgrade PharStreamWrapper to version 2.1.1 or later for the 2.x branch, or 3.1.1 or later for the 3.x branch to obtain the directory traversal protection fix.

Recommended fix High confidence

PharStreamWrapper: 2.1.1 or 3.1.1 | Drupal: 7.67, 8.6.16, or 8.7.1 | Joomla!: 3.9.6+

  1. Identify the affected product in your environment: PharStreamWrapper, Drupal, or Joomla!
  2. For PharStreamWrapper: Check the currently installed version (composer show pharstream/phar-stream-wrapper or similar)
  3. For Drupal: Check core version (drush status or composer show drupal/core)
  4. For Joomla!: Check the Joomla! version in the admin dashboard
  5. For PharStreamWrapper 2.x: Upgrade to version 2.1.1 or later using: composer require pharstream/phar-stream-wrapper:^2.1
  6. For PharStreamWrapper 3.x: Upgrade to version 3.1.1 or later using: composer require pharstream/phar-stream-wrapper:^3.1
  7. For Drupal 7.x: Upgrade to 7.67 or later (composer require drupal/core:^7.67)
  8. For Drupal 8.6.x: Upgrade to 8.6.16 or later (composer require drupal/core:^8.6.16)
Caveat Drupal major version upgrades may have breaking changes; test thoroughly before production deployment

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

Fix this in Pharstreamwrapper Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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