CVE-2019-11831

CVE-2019-11831 is a critical-severity path traversal vulnerability in typo3/phar-stream-wrapper (composer), affecting versions >= 2.0.0, < 2.1.1. It is fixed in 2.1.1, 3.1.1, 7.67.0, 8.6.16, 8.7.1.

Summary

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.

Impact

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2019-11831 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.1.1, 3.1.1, 7.67.0, 8.6.16, 8.7.1); upgrading removes the vulnerable code path.

Affected versions

typo3/phar-stream-wrapper (>= 2.0.0, < 2.1.1) typo3/phar-stream-wrapper (>= 3.0.0, < 3.1.1) drupal/core (>= 7.0.0, < 7.67.0) drupal/core (>= 8.0.0, < 8.6.16) drupal/core (>= 8.7.0, < 8.7.1) drupal/drupal (>= 7.0.0, < 7.67.0) drupal/drupal (>= 8.0.0, < 8.6.16) drupal/drupal (>= 8.7.0, < 8.7.1)

Security releases

typo3/phar-stream-wrapper → 2.1.1 (composer) typo3/phar-stream-wrapper → 3.1.1 (composer) drupal/core → 7.67.0 (composer) drupal/core → 8.6.16 (composer) drupal/core → 8.7.1 (composer) drupal/drupal → 7.67.0 (composer) drupal/drupal → 8.6.16 (composer) drupal/drupal → 8.7.1 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

typo3/phar-stream-wrapper to 2.1.1 or later; typo3/phar-stream-wrapper to 3.1.1 or later; drupal/core to 7.67.0 or later; drupal/core to 8.6.16 or later; drupal/core to 8.7.1 or later; drupal/drupal to 7.67.0 or later; drupal/drupal to 8.6.16 or later; drupal/drupal to 8.7.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2019-11831? CVE-2019-11831 is a critical-severity path traversal vulnerability in typo3/phar-stream-wrapper (composer), affecting versions >= 2.0.0, < 2.1.1. It is fixed in 2.1.1, 3.1.1, 7.67.0, 8.6.16, 8.7.1. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
  2. How severe is CVE-2019-11831? CVE-2019-11831 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which packages are affected by CVE-2019-11831?
    • typo3/phar-stream-wrapper (composer) (versions >= 2.0.0, < 2.1.1)
    • drupal/core (composer) (versions >= 7.0.0, < 7.67.0)
    • drupal/drupal (composer) (versions >= 7.0.0, < 7.67.0)
  4. Is there a fix for CVE-2019-11831? Yes. CVE-2019-11831 is fixed in 2.1.1, 3.1.1, 7.67.0, 8.6.16, 8.7.1. Upgrade to this version or later.
  5. Is CVE-2019-11831 exploitable, and should I be worried? Whether CVE-2019-11831 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2019-11831 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2019-11831?
    • Upgrade typo3/phar-stream-wrapper to 2.1.1 or later
    • Upgrade typo3/phar-stream-wrapper to 3.1.1 or later
    • Upgrade drupal/core to 7.67.0 or later
    • Upgrade drupal/core to 8.6.16 or later
    • Upgrade drupal/core to 8.7.1 or later
    • Upgrade drupal/drupal to 7.67.0 or later
    • Upgrade drupal/drupal to 8.6.16 or later
    • Upgrade drupal/drupal to 8.7.1 or later

Other vulnerabilities in typo3/phar-stream-wrapper

CVE-2019-11830CVE-2019-11831

Stop the waste.
Protect your environment with Kodem.