gsd-2018-7160
Vulnerability from gsd
Modified
2023-12-13 01:22
Details
The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution. An attack is possible from malicious websites open in a web browser on the same computer, or another computer with network access to the computer running the Node.js process. A malicious website could use a DNS rebinding attack to trick the web browser to bypass same-origin-policy checks and to allow HTTP connections to localhost or to hosts on the local network. If a Node.js process with the debug port active is running on localhost or on a host on the local network, the malicious website could connect to it as a debugger, and get full code execution access.
Aliases
Aliases
{ GSD: { alias: "CVE-2018-7160", description: "The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution. An attack is possible from malicious websites open in a web browser on the same computer, or another computer with network access to the computer running the Node.js process. A malicious website could use a DNS rebinding attack to trick the web browser to bypass same-origin-policy checks and to allow HTTP connections to localhost or to hosts on the local network. If a Node.js process with the debug port active is running on localhost or on a host on the local network, the malicious website could connect to it as a debugger, and get full code execution access.", id: "GSD-2018-7160", references: [ "https://www.suse.com/security/cve/CVE-2018-7160.html", "https://access.redhat.com/errata/RHSA-2018:2949", "https://advisories.mageia.org/CVE-2018-7160.html", "https://ubuntu.com/security/CVE-2018-7160", ], }, gsd: { metadata: { exploitCode: "unknown", remediation: "unknown", reportConfidence: "confirmed", type: "vulnerability", }, osvSchema: { aliases: [ "CVE-2018-7160", ], details: "The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution. An attack is possible from malicious websites open in a web browser on the same computer, or another computer with network access to the computer running the Node.js process. A malicious website could use a DNS rebinding attack to trick the web browser to bypass same-origin-policy checks and to allow HTTP connections to localhost or to hosts on the local network. If a Node.js process with the debug port active is running on localhost or on a host on the local network, the malicious website could connect to it as a debugger, and get full code execution access.", id: "GSD-2018-7160", modified: "2023-12-13T01:22:32.850680Z", schema_version: "1.4.0", }, }, namespaces: { "cve.org": { CVE_data_meta: { ASSIGNER: "cve-request@iojs.org", DATE_PUBLIC: "2018-03-21T00:00:00", ID: "CVE-2018-7160", STATE: "PUBLIC", }, affects: { vendor: { vendor_data: [ { product: { product_data: [ { product_name: "Node.js", version: { version_data: [ { version_value: "^6.0.0 || ^8.0.0 || ^9.0.0", }, ], }, }, ], }, vendor_name: "The Node.js Project", }, ], }, }, data_format: "MITRE", data_type: "CVE", data_version: "4.0", description: { description_data: [ { lang: "eng", value: "The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution. An attack is possible from malicious websites open in a web browser on the same computer, or another computer with network access to the computer running the Node.js process. A malicious website could use a DNS rebinding attack to trick the web browser to bypass same-origin-policy checks and to allow HTTP connections to localhost or to hosts on the local network. If a Node.js process with the debug port active is running on localhost or on a host on the local network, the malicious website could connect to it as a debugger, and get full code execution access.", }, ], }, problemtype: { problemtype_data: [ { description: [ { lang: "eng", value: "CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action", }, ], }, ], }, references: { reference_data: [ { name: "https://www.oracle.com//security-alerts/cpujul2021.html", refsource: "MISC", url: "https://www.oracle.com//security-alerts/cpujul2021.html", }, { name: "https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/", refsource: "CONFIRM", url: "https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/", }, { name: "https://support.f5.com/csp/article/K63025104?utm_source=f5support&utm_medium=RSS", refsource: "CONFIRM", url: "https://support.f5.com/csp/article/K63025104?utm_source=f5support&utm_medium=RSS", }, ], }, }, "gitlab.com": { advisories: [ { affected_range: ">=6.0", affected_versions: "All versions starting from 6.0", cvss_v2: "AV:N/AC:M/Au:N/C:P/I:P/A:P", cvss_v3: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", cwe_ids: [ "CWE-1035", "CWE-290", "CWE-78", "CWE-937", ], date: "2023-07-20", description: "The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution. An attack is possible from malicious websites open in a web browser on the same computer, or another computer with network access to the computer running the Node.js process. A malicious website could use a DNS rebinding attack to trick the web browser to bypass same-origin-policy checks and to allow HTTP connections to localhost or to hosts on the local network. If a Node.js process with the debug port active is running on localhost or on a host on the local network, the malicious website could connect to it as a debugger, and get full code execution access.", fixed_versions: [], identifier: "CVE-2018-7160", identifiers: [ "GHSA-wq4c-wm6x-jw44", "CVE-2018-7160", ], not_impacted: "All versions before 6.0", package_slug: "npm/node-inspector", pubdate: "2022-05-13", solution: "Unfortunately, there is no solution available yet.", title: "Authentication Bypass by Spoofing", urls: [ "https://nvd.nist.gov/vuln/detail/CVE-2018-7160", "https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/", "https://support.f5.com/csp/article/K63025104?utm_source=f5support&utm_medium=RSS", "https://www.oracle.com//security-alerts/cpujul2021.html", "https://github.com/advisories/GHSA-wq4c-wm6x-jw44", ], uuid: "e977e281-dfe0-4468-bcf1-fc4a9ef295eb", }, ], }, "nvd.nist.gov": { configurations: { CVE_data_version: "4.0", nodes: [ { children: [], cpe_match: [ { cpe23Uri: "cpe:2.3:a:nodejs:node.js:*:*:*:*:lts:*:*:*", cpe_name: [], versionEndExcluding: "6.14.0", versionStartIncluding: "6.9.0", vulnerable: true, }, { cpe23Uri: "cpe:2.3:a:nodejs:node.js:*:*:*:*:lts:*:*:*", cpe_name: [], versionEndExcluding: "8.11.0", versionStartIncluding: "8.9.0", vulnerable: true, }, { cpe23Uri: "cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*", cpe_name: [], versionEndIncluding: "6.8.1", versionStartIncluding: "6.0.0", vulnerable: true, }, { cpe23Uri: "cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*", cpe_name: [], versionEndIncluding: "8.8.1", versionStartIncluding: "8.0.0", vulnerable: true, }, { cpe23Uri: "cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*", cpe_name: [], versionEndExcluding: "9.10.0", versionStartIncluding: "9.0.0", vulnerable: true, }, ], operator: "OR", }, ], }, cve: { CVE_data_meta: { ASSIGNER: "cve-request@iojs.org", ID: "CVE-2018-7160", }, data_format: "MITRE", data_type: "CVE", data_version: "4.0", description: { description_data: [ { lang: "en", value: "The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution. An attack is possible from malicious websites open in a web browser on the same computer, or another computer with network access to the computer running the Node.js process. A malicious website could use a DNS rebinding attack to trick the web browser to bypass same-origin-policy checks and to allow HTTP connections to localhost or to hosts on the local network. If a Node.js process with the debug port active is running on localhost or on a host on the local network, the malicious website could connect to it as a debugger, and get full code execution access.", }, ], }, problemtype: { problemtype_data: [ { description: [ { lang: "en", value: "CWE-290", }, ], }, ], }, references: { reference_data: [ { name: "https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/", refsource: "CONFIRM", tags: [ "Vendor Advisory", ], url: "https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/", }, { name: "https://support.f5.com/csp/article/K63025104?utm_source=f5support&utm_medium=RSS", refsource: "CONFIRM", tags: [ "Third Party Advisory", ], url: "https://support.f5.com/csp/article/K63025104?utm_source=f5support&utm_medium=RSS", }, { name: "N/A", refsource: "N/A", tags: [ "Third Party Advisory", ], url: "https://www.oracle.com//security-alerts/cpujul2021.html", }, ], }, }, impact: { baseMetricV2: { cvssV2: { accessComplexity: "MEDIUM", accessVector: "NETWORK", authentication: "NONE", availabilityImpact: "PARTIAL", baseScore: 6.8, confidentialityImpact: "PARTIAL", integrityImpact: "PARTIAL", vectorString: "AV:N/AC:M/Au:N/C:P/I:P/A:P", version: "2.0", }, exploitabilityScore: 8.6, impactScore: 6.4, obtainAllPrivilege: false, obtainOtherPrivilege: false, obtainUserPrivilege: false, severity: "MEDIUM", userInteractionRequired: true, }, baseMetricV3: { cvssV3: { attackComplexity: "LOW", attackVector: "NETWORK", availabilityImpact: "HIGH", baseScore: 8.8, baseSeverity: "HIGH", confidentialityImpact: "HIGH", integrityImpact: "HIGH", privilegesRequired: "NONE", scope: "UNCHANGED", userInteraction: "REQUIRED", vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", version: "3.1", }, exploitabilityScore: 2.8, impactScore: 5.9, }, }, lastModifiedDate: "2022-08-16T13:01Z", publishedDate: "2018-05-17T14:29Z", }, }, }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…