CVE-2019-15606: HTTP header values do not have trailing OWS trimmed

Published Feb 6, 2020
·
Updated

HTTP header values do not have trailing OWS trimmed

Other sources

Including trailing white space in HTTP header values in Nodejs 10, 12, and 13 causes bypass of authorization based on header value comparisons

— Launchpad

Optional whitespace should be trimmed from HTTP header values. Its presence may allow attackers to bypass security checks based on HTTP header values.

— Red Hat

Affected Software

48 affected componentsFixes available
debian/nodejs
12.22.12~dfsg-1~deb11u412.22.12~dfsg-1~deb11u518.19.0+dfsg-6~deb12u218.19.0+dfsg-6~deb12u120.17.0+dfsg-2
Nodejs Node.js>=10.0.0<10.19.0
Nodejs Node.js>=12.0.0<12.15.0
Nodejs Node.js>=13.0.0<13.8.0
Oracle Communications Cloud Native Core Network Function Cloud Native Environment=1.4.0
Oracle GraalVM=19.3.1
Oracle GraalVM=20.0.0
Debian Debian Linux=10.0
redhat Enterprise Linux=8.0
redhat Enterprise Linux Eus=8.1
openSUSE Leap=15.1
Nodejs Node.js>=13.0.0<13.8.0
redhat/nodejs<10.19.0
10.19.0
redhat/nodejs<12.15.0
12.15.0
redhat/nodejs<13.8.0
13.8.0
Node.js Node.js>=10.0.0<10.19.0, >=12.0.0<12.15.0, >=13.0.0<13.8.0
10.19.012.15.013.8.0
Node.js Node.js>=10.0.0<10.19.0
10.19.0
Node.js Node.js>=12.0.0<12.15.0
12.15.0
Node.js Node.js>=13.0.0<13.8.0
13.8.0
alpine/nodejs<10.19.0-r0
10.19.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<12.15.0-r0
12.15.0-r0
alpine/nodejs<10.19.0-r0
10.19.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0
alpine/nodejs-current<13.11.0-r0
13.11.0-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/nodejs to a version that resolves this vulnerability.

    Fixed in 12.22.12~dfsg-1~deb11u4Fixed in 12.22.12~dfsg-1~deb11u5Fixed in 18.19.0+dfsg-6~deb12u2Fixed in 18.19.0+dfsg-6~deb12u1Fixed in 20.17.0+dfsg-2
  2. Upgrade

    Upgrade redhat/nodejs to a version that resolves this vulnerability.

    Fixed in 10.19.0
  3. Upgrade

    Upgrade redhat/nodejs to a version that resolves this vulnerability.

    Fixed in 12.15.0
  4. Upgrade

    Upgrade redhat/nodejs to a version that resolves this vulnerability.

    Fixed in 13.8.0
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.19.0Fixed in 12.15.0Fixed in 13.8.0
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.19.0
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 12.15.0
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 13.8.0
  9. Upgrade

    Upgrade alpine/nodejs to a version that resolves this vulnerability.

    Fixed in 10.19.0-r0
  10. Upgrade

    Upgrade alpine/nodejs to a version that resolves this vulnerability.

    Fixed in 12.15.0-r0
  11. Upgrade

    Upgrade alpine/nodejs-current to a version that resolves this vulnerability.

    Fixed in 13.11.0-r0

Event History

Feb 6, 2020
CVE Published
via Node.js·03:11 AM
Data Sourced
via Node.js·03:11 AM
SeverityAffected Software
Data Sourced
via Node.js·12:00 PM
Description
Feb 7, 2020
Data Sourced
via Red Hat·12:21 AM
DescriptionSeverityAffected Software
CVE Published
via MITRE·02:58 PM
Data Sourced
via MITRE·02:58 PM
DescriptionWeakness
Data Sourced
via NVD·03:15 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·03:15 PM
DescriptionSeverityAffected Software
Jun 1, 2020
Data Sourced
via IBM·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is CVE-2019-15606?

CVE-2019-15606 is a vulnerability in Nodejs 10, 12, and 13 that allows bypass of authorization based on header value comparisons by including trailing white space in HTTP header values.

2

What is the severity of CVE-2019-15606?

The severity of CVE-2019-15606 is medium, with a severity value of 4.

3

How does CVE-2019-15606 affect Nodejs?

CVE-2019-15606 affects Nodejs versions 10, 12, and 13.

4

How can the CVE-2019-15606 vulnerability be fixed?

To fix the CVE-2019-15606 vulnerability, update Nodejs to the recommended versions: 10.24.0~dfsg-1~deb10u1, 10.24.0~dfsg-1~deb10u3, 12.22.12~dfsg-1~deb11u3, 12.22.12~dfsg-1~deb11u4, or 18.13.0+dfsg1-1.

5

Where can I find more information about CVE-2019-15606?

You can find more information about CVE-2019-15606 at the following references: [1] HackerOne report: https://hackerone.com/reports/730779 [2] Nodejs commit: https://github.com/nodejs/node/commit/2eee90e959ca4abaf53caf238d063c396f2ea17c [3] Debian Security Tracker: https://security-tracker.debian.org/tracker/CVE-2019-15606

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203