Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') Affecting nodejs-full-i18n package, versions <1:14.21.1-2.module+el8.7.0+20895+79a25710
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-ORACLE8-NODEJSFULLI18N-3227836
- published 11 Jan 2023
- disclosed 26 Nov 2022
Introduced: 26 Nov 2022
CVE-2022-24999 Open this link in a new tabHow to fix?
Upgrade Oracle:8 nodejs-full-i18n to version 1:14.21.1-2.module+el8.7.0+20895+79a25710 or higher.
This issue was patched in ELSA-2023-0050.
NVD Description
Note: Versions mentioned in the description apply only to the upstream nodejs-full-i18n package and not the nodejs-full-i18n package as distributed by Oracle.
See How to fix? for Oracle:8 relevant fixed versions and status.
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[proto]=b&a[proto]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
References
- https://linux.oracle.com/cve/CVE-2022-24999.html
- https://linux.oracle.com/errata/ELSA-2023-0050.html
- https://github.com/expressjs/express/releases/tag/4.17.3
- https://github.com/ljharb/qs/pull/428
- https://github.com/n8tz/CVE-2022-24999
- https://lists.debian.org/debian-lts-announce/2023/01/msg00039.html
- https://security.netapp.com/advisory/ntap-20230908-0005/