{"answers":{"affected":"2 open source packages ship an affected version, including rendertron. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-18355 in the wild and no public exploit code.","fix":"Upgrade rendertron to 1.1.0 or later.","what":"CVE-2017-18355 is a high-severity vulnerability in n/a, published on 17 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-18355 and fix it if it is affected.\n\nWhat it is: CVE-2017-18355 is a high-severity vulnerability in n/a, published on 17 Dec 2018. 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-2017-18355 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rendertron (npm): affected all versions; fixed in 1.1.0\n- rendertron (npm): affected all versions; fixed in 1.1.0\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-2017-18355/ (Markdown: https://insights.sbomify.com/CVE-2017-18355/index.md)","id":"CVE-2017-18355","markdown":"https://insights.sbomify.com/CVE-2017-18355/index.md","name":"CVE-2017-18355","record":{"aliases":["GHSA-vqmr-957g-r7w3"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Rendertron headless browser","requires_auth":"none","summary":"Remote attackers can read server absolute paths by accessing exposed package.json files in Rendertron's node_modules directory.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rendertron","vendor":"google"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Installed packages are exposed by node_modules in Rendertron 1.0.0, allowing remote attackers to read absolute paths on the server by examining the \"_where\" attribute of package.json files.","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":"Rendertron discloses absolute paths of files","id":"CVE-2017-18355","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":2,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2017-18356"},"packages":[{"ecosystem":"npm","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"rendertron","purl":null,"source":"GHSA-vqmr-957g-r7w3"},{"ecosystem":"npm","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"rendertron","purl":"pkg:npm/rendertron","source":"GHSA-vqmr-957g-r7w3"}],"prev":{"headline":"rendertron LFI vulnerability","id":"CVE-2017-18354"},"products":["n/a"],"published":"2018-12-17","related":[{"cvss_score":7.5,"headline":"rendertron can remotely shut down Chrome instance","id":"CVE-2017-18353","kev_date_added":null,"published":"2018-12-17"},{"cvss_score":7.5,"headline":"rendertron LFI vulnerability","id":"CVE-2017-18354","kev_date_added":null,"published":"2018-12-17"},{"cvss_score":6.1,"headline":"rendertron XSS vulnerability","id":"CVE-2017-18352","kev_date_added":null,"published":"2018-12-17"},{"cvss_score":3.5,"headline":"SSRF in Rendertron","id":"CVE-2020-8902","kev_date_added":null,"published":"2021-02-23"}],"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":"Remote attackers can read server absolute paths by accessing exposed package.json files in Rendertron's node_modules directory.","url":"https://insights.sbomify.com/CVE-2017-18355/"}