{"answers":{"affected":"2 open source packages ship an affected version, including sync-exec. It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-16024 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-16024 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-16024 is a medium-severity vulnerability in Nodejs Node.js, published on 4 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-16024 and fix it if it is affected.\n\nWhat it is: CVE-2017-16024 is a medium-severity vulnerability in Nodejs Node.js, published on 4 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-16024 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sync-exec (npm): affected all versions up to 0.6.2; no fix listed\n- sync-exec (npm): affected all versions up to 0.6.2; no fix listed\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-16024/ (Markdown: https://insights.sbomify.com/CVE-2017-16024/index.md)","id":"CVE-2017-16024","markdown":"https://insights.sbomify.com/CVE-2017-16024/index.md","name":"CVE-2017-16024","record":{"aliases":["GHSA-38h8-x697-gh8q"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js sync-exec module","requires_auth":"low_privilege","summary":"Local attackers can read confidential data from temporary files created by the sync-exec module due to insecure permissions.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"node.js","vendor":"nodejs"},{"product":"sync-exec","vendor":"sync-exec_project"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/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"},{"id":"CWE-377","name":"DEPRECATED: Insecure Temporary File"}],"description":"The sync-exec module is used to simulate child_process.execSync in node versions \u003c0.11.9. Sync-exec uses tmp directories as a buffer before returning values. Other users on the server have read access to the tmp directory, possibly allowing an attacker on the server to obtain confidential information from the buffer/tmp file, while it exists.","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":false,"headline":"Tmp files readable by other users in sync-exec","id":"CVE-2017-16024","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"nodejs:node.js","products":["nodejs:node.js"],"type":"information_disclosure","year":"2017"},"n_packages":2,"n_references":4,"next":{"headline":"Denial of Service in nes","id":"CVE-2017-16025"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.6.2"],"package":"sync-exec","purl":null,"source":"GHSA-38h8-x697-gh8q"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.6.2"],"package":"sync-exec","purl":"pkg:npm/sync-exec","source":"GHSA-38h8-x697-gh8q"}],"prev":{"headline":"Regular Expression Denial of Service in decamelize","id":"CVE-2017-16023"},"products":["sync-exec node module"],"published":"2018-06-04","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-09-16","vendors":["HackerOne"]},"summary":"Local attackers can read confidential data from temporary files created by the sync-exec module due to insecure permissions.","url":"https://insights.sbomify.com/CVE-2017-16024/"}