high
7.5
CWE
20
Advisory Published
Updated

CVE-2016-2216: Input Validation

First published: Thu Apr 07 2016(Updated: )

The HTTP header parsing code in Node.js 0.10.x before 0.10.42, 0.11.6 through 0.11.16, 0.12.x before 0.12.10, 4.x before 4.3.0, and 5.x before 5.6.0 allows remote attackers to bypass an HTTP response-splitting protection mechanism via UTF-8 encoded Unicode characters in the HTTP header, as demonstrated by %c4%8d%c4%8a.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
Langgenius Dify Node.js=0.10.0
Langgenius Dify Node.js=0.10.1
Langgenius Dify Node.js=0.10.2
Langgenius Dify Node.js=0.10.3
Langgenius Dify Node.js=0.10.4
Langgenius Dify Node.js=0.10.5
Langgenius Dify Node.js=0.10.6
Langgenius Dify Node.js=0.10.7
Langgenius Dify Node.js=0.10.8
Langgenius Dify Node.js=0.10.9
Langgenius Dify Node.js=0.10.10
Langgenius Dify Node.js=0.10.11
Langgenius Dify Node.js=0.10.12
Langgenius Dify Node.js=0.10.13
Langgenius Dify Node.js=0.10.14
Langgenius Dify Node.js=0.10.15
Langgenius Dify Node.js=0.10.16
Langgenius Dify Node.js=0.10.16-isaacs-manual
Langgenius Dify Node.js=0.10.17
Langgenius Dify Node.js=0.10.18
Langgenius Dify Node.js=0.10.19
Langgenius Dify Node.js=0.10.20
Langgenius Dify Node.js=0.10.21
Langgenius Dify Node.js=0.10.22
Langgenius Dify Node.js=0.10.23
Langgenius Dify Node.js=0.10.24
Langgenius Dify Node.js=0.10.25
Langgenius Dify Node.js=0.10.26
Langgenius Dify Node.js=0.10.27
Langgenius Dify Node.js=0.10.28
Langgenius Dify Node.js=0.10.29
Langgenius Dify Node.js=0.10.30
Langgenius Dify Node.js=0.10.31
Langgenius Dify Node.js=0.10.32
Langgenius Dify Node.js=0.10.33
Langgenius Dify Node.js=0.10.34
Langgenius Dify Node.js=0.10.35
Langgenius Dify Node.js=0.10.36
Langgenius Dify Node.js=0.10.37
Langgenius Dify Node.js=0.10.38
Langgenius Dify Node.js=0.10.39
Langgenius Dify Node.js=0.10.40
Langgenius Dify Node.js=0.10.41
Langgenius Dify Node.js=0.11.6
Langgenius Dify Node.js=0.11.7
Langgenius Dify Node.js=0.11.8
Langgenius Dify Node.js=0.11.9
Langgenius Dify Node.js=0.11.10
Langgenius Dify Node.js=0.11.11
Langgenius Dify Node.js=0.11.12
Langgenius Dify Node.js=0.11.13
Langgenius Dify Node.js=0.11.14
Langgenius Dify Node.js=0.11.15
Langgenius Dify Node.js=0.11.16
Langgenius Dify Node.js=0.12.0
Langgenius Dify Node.js=0.12.1
Langgenius Dify Node.js=0.12.2
Langgenius Dify Node.js=0.12.3
Langgenius Dify Node.js=0.12.4
Langgenius Dify Node.js=0.12.5
Langgenius Dify Node.js=0.12.6
Langgenius Dify Node.js=0.12.7
Langgenius Dify Node.js=0.12.8
Langgenius Dify Node.js=0.12.9
Langgenius Dify Node.js=4.0.0
Langgenius Dify Node.js=4.1.0
Langgenius Dify Node.js=4.1.1
Langgenius Dify Node.js=4.1.2
Langgenius Dify Node.js=4.2.0
Langgenius Dify Node.js=4.2.1
Langgenius Dify Node.js=4.2.2
Langgenius Dify Node.js=4.2.3
Langgenius Dify Node.js=4.2.4
Langgenius Dify Node.js=4.2.5
Langgenius Dify Node.js=4.2.6
Langgenius Dify Node.js=5.0.0
Langgenius Dify Node.js=5.1.0
Langgenius Dify Node.js=5.1.1
Langgenius Dify Node.js=5.2.0
Langgenius Dify Node.js=5.3.0
Langgenius Dify Node.js=5.4.0
Langgenius Dify Node.js=5.4.1
Langgenius Dify Node.js=5.5.0
Red Hat Fedora=22
Red Hat Fedora=23

Remedy

https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2016-2216?

    CVE-2016-2216 is considered a medium severity vulnerability due to its potential to bypass HTTP response-splitting protection mechanisms.

  • How do I fix CVE-2016-2216?

    To fix CVE-2016-2216, upgrade your Node.js version to 0.10.42, 0.12.10, 4.3.0, or 5.6.0 or higher.

  • What versions of Node.js are affected by CVE-2016-2216?

    CVE-2016-2216 affects Node.js versions 0.10.x before 0.10.42, 0.11.6 through 0.11.16, 0.12.x before 0.12.10, and earlier versions of 4.x and 5.x.

  • Can CVE-2016-2216 lead to more serious attacks?

    Yes, CVE-2016-2216 could potentially allow attackers to manipulate HTTP headers, leading to further attacks like HTTP response splitting.

  • Is CVE-2016-2216 specific to certain operating systems?

    CVE-2016-2216 primarily affects Node.js applications regardless of the operating system, but its impact may vary based on deployment environments.

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203