CVE-2023-23920: Node.js insecure loading of ICU data through ICU_DATA environment variable

Published Feb 16, 2023
·
Updated

An untrusted search path vulnerability exists in Node.js. <19.6.1, <18.14.1, <16.19.1, and <14.21.3 that could allow an attacker to search and potentially load ICU data when running with elevated privileges.

Other sources

Node.js could allow a remote authenticated attacker to bypass security restrictions, caused by improper access control. By sending a specially-crafted request using ICUDATA environment variable, an attacker could exploit this vulnerability to search and potentially load ICU data.

— IBM

Node.js would search and potentially load ICU data when running with elevated priviledges. Node.js was modified to build with ICUNOUSERDATAOVERRIDE to avoid this.

— Red Hat

Node.js would search and potentially load ICU data when running with elevated privileges. Node.js was modified to build with ICUNOUSERDATAOVERRIDE to avoid this.

All versions of the 19.x, 18.x, 16.x, and 14.x release lines.

— Node.Js

Affected Software

24 affected componentsFixes available
redhat/nodejs<18-9020020230327152102.rhel9
18-9020020230327152102.rhel9
redhat/nodejs<1:16.19.1-1.el9_2
1:16.19.1-1.el9_2
redhat/nodejs<1:16.20.2-1.el9_0
1:16.20.2-1.el9_0
redhat/rh-nodejs14<0:3.6-2.el7
0:3.6-2.el7
redhat/rh-nodejs14-nodejs<0:14.21.3-2.el7
0:14.21.3-2.el7
redhat/node.js<19.6.1
19.6.1
redhat/node.js<18.14.1
18.14.1
redhat/node.js<16.19.1
16.19.1
redhat/node.js<14.21.3
14.21.3
IBM Cognos Controller<=11.0.0 - 11.0.1
Nodejs Node.js>=14.0.0<=14.14.0
Nodejs Node.js>=14.0.0<14.21.3
Nodejs Node.js>=16.0.0<=16.12.0
Nodejs Node.js>=16.0.0<16.19.1
Nodejs Node.js>=18.0.0<=18.11.0
Nodejs Node.js>=18.0.0<18.14.1
Nodejs Node.js>=19.0.0<19.6.1
Debian Debian Linux=10.0
Node.js Node.js>=14.0.0<14.21.3, >=16.0.0<16.19.1, >=18.0.0<18.14.1, >=19.0.0<19.6.1
14.21.316.19.118.14.119.6.1
Node.js Node.js>=14.0.0<14.21.3
14.21.3
Node.js Node.js>=16.0.0<16.19.1
16.19.1
Node.js Node.js>=18.0.0<18.14.1
18.14.1
Node.js Node.js>=19.0.0<19.6.1
19.6.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

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-9020020230327152102.rhel9
  2. Upgrade

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

    Fixed in 1:16.19.1-1.el9_2
  3. Upgrade

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

    Fixed in 1:16.20.2-1.el9_0
  4. Upgrade

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

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

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

    Fixed in 0:14.21.3-2.el7
  6. Upgrade

    Upgrade redhat/Node.js to a version that resolves this vulnerability.

    Fixed in 19.6.1
  7. Upgrade

    Upgrade redhat/Node.js to a version that resolves this vulnerability.

    Fixed in 18.14.1
  8. Upgrade

    Upgrade redhat/Node.js to a version that resolves this vulnerability.

    Fixed in 16.19.1
  9. Upgrade

    Upgrade redhat/Node.js to a version that resolves this vulnerability.

    Fixed in 14.21.3
  10. Upgrade

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

    Fixed in 14.21.3Fixed in 16.19.1Fixed in 18.14.1Fixed in 19.6.1
  11. Upgrade

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

    Fixed in 14.21.3
  12. Upgrade

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

    Fixed in 16.19.1
  13. Upgrade

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

    Fixed in 18.14.1
  14. Upgrade

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

    Fixed in 19.6.1
  15. 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
  16. Upgrade

    Upgrade Node.js to a version that resolves this vulnerability.

    Fixed in 19.6.1
  17. Upgrade

    Upgrade Node.js to a version that resolves this vulnerability.

    Fixed in 18.14.1
  18. Upgrade

    Upgrade Node.js to a version that resolves this vulnerability.

    Fixed in 16.19.1
  19. Upgrade

    Upgrade Node.js to a version that resolves this vulnerability.

    Fixed in 14.21.3

Event History

Feb 16, 2023
CVE Published
12:00 AM
Data Sourced
via Node.js·09:00 PM
DescriptionSeverity
Data Sourced
via Node.js·10:08 PM
Affected Software
Feb 23, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Data Sourced
via NVD·08:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

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