CVE-2023-42282
Public on
Last Modified:
Description
A vulnerability was found in the NPM IP Package. This flaw allows an attacker to perform arbitrary code execution and obtain sensitive information via the isPublic() function by inducing a Server-Side Request Forgery (SSRF) attack and obtaining access to normally inaccessible resources.
Statement
It appears that npm does not utilize the bundled code therefore Red Hat Enterprise Linux is not affected by this vulnerability.
While the vulnerability in the NPM IP Package presents a significant security concern, it's categorized as important rather than critical due to several factors. Firstly, the misclassification of the private IP address 0x7f.1 as public by the isPublic() function does not directly lead to remote code execution or unauthorized access to critical systems. Instead, it facilitates SSRF attacks, which typically require additional conditions to fully exploit, such as the ability to influence server-side requests and responses. Additionally, the impact of SSRF attacks can vary depending on the specific environment and configuration of the affected system. While SSRF attacks can potentially lead to data exposure, service disruption, or lateral movement within a network, their severity is often mitigated by factors such as network segmentation, access controls, and the availability of sensitive resources.
Red Hat Developer Hub contains a fix in 1.1-91 version.
Mitigation
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Additional Information
- This content is not included.Bugzilla 2265161: nodejs-ip: arbitrary code execution via the isPublic() function
- Content from cwe.mitre.org is not included.CWE-918: Server-Side Request Forgery (SSRF)
- FAQ: Frequently asked questions about CVE-2023-42282
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.
External References
Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2023-42282
Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2023-42282
Affected Packages and Issued Red Hat Security Errata
| Products / Services | Components | State | Errata |
|---|---|---|---|
| HawtIO 4.0.0 for Red Hat build of Apache Camel 4 | Fixed | RHSA-2024:3550 | |
| Logging Subsystem for Red Hat OpenShift | openshift-logging/kibana6-rhel8 | Not affected | |
| Migration Toolkit for Virtualization 2.5 | migration-toolkit-virtualization/mtv-console-plugin-rhel9 | Fixed | RHBA-2024:1440 |
| NETWORK-OBSERVABILITY-1.6.0-RHEL-9 | network-observability/network-observability-cli-rhel9 | Fixed | RHSA-2024:3868 |
| NETWORK-OBSERVABILITY-1.6.0-RHEL-9 | network-observability/network-observability-console-plugin-rhel9 | Fixed | RHSA-2024:3868 |
| NETWORK-OBSERVABILITY-1.6.0-RHEL-9 | network-observability/network-observability-ebpf-agent-rhel9 | Fixed | RHSA-2024:3868 |
| NETWORK-OBSERVABILITY-1.6.0-RHEL-9 | network-observability/network-observability-flowlogs-pipeline-rhel9 | Fixed | RHSA-2024:3868 |
| NETWORK-OBSERVABILITY-1.6.0-RHEL-9 | network-observability/network-observability-operator-bundle | Fixed | RHSA-2024:3868 |
| NETWORK-OBSERVABILITY-1.6.0-RHEL-9 | network-observability/network-observability-rhel9-operator | Fixed | RHSA-2024:3868 |
| Node HealthCheck Operator | workload-availability/node-remediation-console-rhel8 | Affected | |
| RHDH-1.1-RHEL-9 | rhdh/rhdh-hub-rhel9 | Fixed | RHEA-2024:1366 |
| RHODF-4.15-RHEL-9 | odf4/mcg-core-rhel9 | Fixed | RHSA-2024:1383 |
| Red Hat Advanced Cluster Security 3 | advanced-cluster-security/rhacs-main-rhel8 | Out of support scope | |
| Red Hat Advanced Cluster Security 4 | advanced-cluster-security/rhacs-main-rhel8 | Not affected | |
| Red Hat Enterprise Linux 8 | nodejs:16/nodejs | Not affected | |
| Red Hat Enterprise Linux 8 | nodejs:18/nodejs | Not affected | |
| Red Hat Enterprise Linux 8 | nodejs:20/nodejs | Not affected | |
| Red Hat Enterprise Linux 9 | nodejs | Not affected | |
| Red Hat Enterprise Linux 9 | nodejs:18/nodejs | Not affected | |
| Red Hat Enterprise Linux 9 | nodejs:20/nodejs | Not affected | |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces/code-rhel8 | Fixed | RHSA-2024:10236 |
| Red Hat Software Collections | rh-nodejs14-nodejs | Not affected |
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).
| CVSS v3 Score Breakdown | Red Hat | NVD |
|---|---|---|
| CVSS v3 Base Score | 9.8 | 9.8 |
| Attack Vector | Network | Network |
| Attack Complexity | Low | Low |
| Privileges Required | None | None |
| User Interaction | None | None |
| Scope | Unchanged | Unchanged |
| Confidentiality Impact | High | High |
| Integrity Impact | High | High |
| Availability Impact | High | High |
CVSS v3 Vector
Red Hat CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
For more information, see https://access.redhat.com/solutions/762393.
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
- "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
- "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.
What can I do if my product is listed as "Will not fix"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
What can I do if my product is listed as "Fix deferred"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
- Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
My product is listed as "Out of Support Scope". What does this mean?
Not sure what something means? Check out our Security Glossary.