{"answers":{"affected":"2 open source packages ship an affected version, including stringstream. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-21270 in the wild and no public exploit code.","fix":"Upgrade stringstream to 0.0.6 or later.","what":"CVE-2018-21270 is a medium-severity vulnerability in Nodejs Node.js, published on 3 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-21270 and fix it if it is affected.\n\nWhat it is: CVE-2018-21270 is a medium-severity vulnerability in Nodejs Node.js, published on 3 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-21270 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- stringstream (npm): affected all versions; fixed in 0.0.6\n- stringstream (npm): affected all versions; fixed in 0.0.6\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-21270/ (Markdown: https://insights.sbomify.com/CVE-2018-21270/index.md)","id":"CVE-2018-21270","markdown":"https://insights.sbomify.com/CVE-2018-21270/index.md","name":"CVE-2018-21270","record":{"aliases":["CLSA-2026-1772583200","CLSA-2026-1773274557","DEBIAN-CVE-2018-21270","GHSA-mf6x-7mm4-x2g7","UBUNTU-CVE-2018-21270"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js stringstream module","requires_auth":"none","summary":"An out-of-bounds read in the stringstream module allows attackers to read uninitialized memory when processing numeric input streams.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"node.js","vendor":"nodejs"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Out-of-bounds Read in stringstream","id":"CVE-2018-21270","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"nodejs:node.js","products":["nodejs:node.js"],"type":"information_disclosure","year":"2018"},"n_packages":2,"n_references":3,"next":{"headline":"Duplicate Advisory: Use after free in libpulse-binding","id":"CVE-2018-25001"},"packages":[{"ecosystem":"npm","fixed":["0.0.6"],"introduced":["0"],"last_affected":[],"package":"stringstream","purl":null,"source":"GHSA-mf6x-7mm4-x2g7"},{"ecosystem":"npm","fixed":["0.0.6"],"introduced":["0"],"last_affected":[],"package":"stringstream","purl":"pkg:npm/stringstream","source":"GHSA-mf6x-7mm4-x2g7"}],"prev":{"headline":"Path traversal in n/a","id":"CVE-2018-21269"},"products":["n/a"],"published":"2020-12-03","related":[{"cvss_score":9.8,"headline":"Security feature bypass in Node","id":"CVE-2023-32002","kev_date_added":null,"published":"2023-08-21"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2016-6303","kev_date_added":null,"published":"2016-09-16"},{"cvss_score":9.1,"headline":"Security feature bypass in Node.js","id":"CVE-2017-15896","kev_date_added":null,"published":"2017-12-11"},{"cvss_score":8.8,"headline":"Server-side request forgery in Node.js","id":"CVE-2018-7160","kev_date_added":null,"published":"2018-05-17"},{"cvss_score":8.1,"headline":"Misconfiguration in Node.js","id":"CVE-2018-12120","kev_date_added":null,"published":"2018-11-28"},{"cvss_score":7.9,"headline":"Path traversal in Node","id":"CVE-2024-21891","kev_date_added":null,"published":"2024-02-20"},{"cvss_score":7.9,"headline":"Path traversal in Node","id":"CVE-2024-21896","kev_date_added":null,"published":"2024-02-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An out-of-bounds read in the stringstream module allows attackers to read uninitialized memory when processing numeric input streams.","url":"https://insights.sbomify.com/CVE-2018-21270/"}