CVE-2022-43548: DNS rebinding in --inspect via invalid octal IP address

Published Nov 3, 2022
·
Updated

A flaw was found in NodeJS. The issue occurs in the Node.js rebinding protector for --inspect that still allows invalid IP addresses, specifically, the octal format. This flaw allows an attacker to perform DNS rebinding and execute arbitrary code.

Other sources

A OS Command Injection vulnerability exists in Node.js versions <14.21.1, <16.18.1, <18.12.1, <19.0.1 due to an insufficient IsAllowedHost check that can easily be bypassed because IsIPAddress does not properly check if an IP address is invalid before making DBS requests allowing rebinding attacks.The fix for this issue in https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32212 was incomplete and this new CVE is to complete the fix.

Hi upstream just released nodejs 14.21.1 to fix CVE-2022-43548 https://github.com/nodejs/node/releases/tag/v14.21.1 https://nodejs.org/en/blog/release/v18.12.1/ https://nodejs.org/en/blog/release/v16.18.1/

— Red Hat

The Node.js rebinding protector for --inspect still allows invalid IP address, specifically, the octal format.

— Node.Js

Affected Software

30 affected componentsFixes available
redhat/nodejs<18-9010020221118120946.rhel9
18-9010020221118120946.rhel9
redhat/nodejs<1:16.18.1-3.el9_1
1:16.18.1-3.el9_1
redhat/rh-nodejs14-nodejs<0:14.21.1-3.el7
0:14.21.1-3.el7
redhat/rh-nodejs14-nodejs-nodemon<0:2.0.20-2.el7
0:2.0.20-2.el7
Nodejs Node.js>=14.0.0<=14.14.0
Nodejs Node.js>=14.15.0<14.21.1
Nodejs Node.js>=16.0.0<=16.12.0
Nodejs Node.js>=16.13.0<16.18.1
Nodejs Node.js>=18.0.0<=18.11.0
Nodejs Node.js=18.12.0
Nodejs Node.js=19.0.0
Debian Debian Linux=10.0
Debian Debian Linux=11.0
Node.js Node.js>=14.0.0<14.21.1, >=16.0.0<16.18.1, >=18.0.0<18.12.1, >=19.0.0<19.0.1
14.21.116.18.118.12.119.0.1
Node.js Node.js>=14.0.0<14.21.1
14.21.1
Node.js Node.js>=16.0.0<16.18.1
16.18.1
Node.js Node.js>=18.0.0<18.12.1
18.12.1
Node.js Node.js>=19.0.0<19.0.1
19.0.1
debian/nodejs<18.12.1+dfsg-1
18.12.1+dfsg-1
debian/nodejs<18.12.1+dfsg-1
18.12.1+dfsg-1
debian/nodejs<18.12.1+dfsg-1
18.12.1+dfsg-1
debian/nodejs
18.20.4+dfsg-1~deb12u218.20.4+dfsg-1~deb12u320.19.2+dfsg-1+deb13u220.19.2+dfsg-1+deb13u324.21.0+dfsg+~cs24.13.4-124.22.2+dfsg+~cs24.19.2-1
alpine/nodejs<18.12.1-r0
18.12.1-r0
alpine/nodejs<18.12.1-r0
18.12.1-r0
alpine/nodejs<18.12.1-r0
18.12.1-r0
alpine/nodejs<18.12.1-r0
18.12.1-r0
alpine/nodejs<18.12.1-r0
18.12.1-r0
alpine/nodejs<18.12.1-r0
18.12.1-r0
alpine/nodejs<18.12.1-r0
18.12.1-r0
alpine/nodejs<18.12.1-r0
18.12.1-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 18-9010020221118120946.rhel9
  2. Upgrade

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

    Fixed in 1:16.18.1-3.el9_1
  3. Upgrade

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

    Fixed in 0:14.21.1-3.el7
  4. Upgrade

    Upgrade redhat/rh-nodejs14-nodejs-nodemon to a version that resolves this vulnerability.

    Fixed in 0:2.0.20-2.el7
  5. Upgrade

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

    Fixed in 14.21.1Fixed in 16.18.1Fixed in 18.12.1Fixed in 19.0.1
  6. Upgrade

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

    Fixed in 14.21.1
  7. Upgrade

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

    Fixed in 16.18.1
  8. Upgrade

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

    Fixed in 18.12.1
  9. Upgrade

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

    Fixed in 19.0.1
  10. Upgrade

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

    Fixed in 18.20.4+dfsg-1~deb12u2Fixed in 18.20.4+dfsg-1~deb12u3Fixed in 20.19.2+dfsg-1+deb13u2Fixed in 20.19.2+dfsg-1+deb13u3Fixed in 24.21.0+dfsg+~cs24.13.4-1Fixed in 24.22.2+dfsg+~cs24.19.2-1
  11. Upgrade

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

    Fixed in 18.12.1-r0
  12. Upgrade

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

    Fixed in 18.12.1+dfsg-1
  13. Upgrade

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

    Fixed in 14.21.1
  14. Upgrade

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

    Fixed in 16.18.1
  15. Upgrade

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

    Fixed in 18.12.1
  16. Upgrade

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

    Fixed in 19.0.1

Event History

Nov 3, 2022
CVE Published
via Node.js·12:00 AM
Data Sourced
via Node.js·12:00 AM
DescriptionSeverity
Nov 4, 2022
Data Sourced
via Node.js·05:51 PM
Affected Software
Nov 8, 2022
Data Sourced
via Red Hat·07:50 AM
DescriptionSeverityAffected Software
Dec 5, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Data Sourced
via NVD·10:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·10:15 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is CVE-2022-43548?

CVE-2022-43548 is a OS Command Injection vulnerability in Node.js versions <14.21.1, <16.18.1, <18.12.1, <19.0.1 that allows for rebinding attacks.

2

What is the severity of CVE-2022-43548?

The severity of CVE-2022-43548 is high with a CVSS score of 7.5.

3

How does CVE-2022-43548 occur?

CVE-2022-43548 occurs due to an insufficient IsAllowedHost check in Node.js that can be bypassed, allowing for rebinding attacks.

4

Which versions of Node.js are affected by CVE-2022-43548?

Node.js versions <14.21.1, <16.18.1, <18.12.1, <19.0.1 are affected by CVE-2022-43548.

5

How can CVE-2022-43548 be fixed?

To fix CVE-2022-43548, it is recommended to upgrade to Node.js versions 14.21.1, 16.18.1, 18.12.1, or 19.0.1.

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