{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-38346 exists.","fix":"No fix has been published for CVE-2023-38346 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-38346 is a high-severity path traversal vulnerability in n/a, published on 22 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-38346 and fix it if it is affected.\n\nWhat it is: CVE-2023-38346 is a high-severity path traversal vulnerability in n/a, published on 22 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-38346 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2023-38346/ (Markdown: https://insights.sbomify.com/CVE-2023-38346/index.md)","id":"CVE-2023-38346","markdown":"https://insights.sbomify.com/CVE-2023-38346/index.md","name":"CVE-2023-38346","record":{"aliases":["GHSA-5pr5-788c-3f6c"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"VxWorks RTOS","requires_auth":"low_privilege","summary":"Attackers can exploit improper path handling in tarExtract to traverse directories and access or modify files outside the intended extraction path.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vxworks","vendor":"windriver"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"An issue was discovered in Wind River VxWorks 6.9 and 7. The function ``tarExtract`` implements TAR file extraction and thereby also processes files within an archive that have relative or absolute file paths. A developer using the \"tarExtract\" function may expect that the function will strip leading slashes from absolute paths or stop processing when encountering relative paths that are outside of the extraction path, unless otherwise forced. This could lead to unexpected and undocumented behavior, which in general could result in a directory traversal, and associated unexpected behavior.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Path traversal in n/a","id":"CVE-2023-38346","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2023-38347"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2023-38344"},"products":["n/a"],"published":"2023-09-22","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2013-0714","kev_date_added":null,"published":"2013-03-20"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-29999","kev_date_added":null,"published":"2021-04-13"},{"cvss_score":8.1,"headline":"Integer overflow in n/a","id":"CVE-2019-9865","kev_date_added":null,"published":"2019-05-29"},{"cvss_score":8.1,"headline":"Integer overflow in n/a","id":"CVE-2015-7599","kev_date_added":null,"published":"2017-02-07"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2013-0711","kev_date_added":null,"published":"2013-03-20"},{"cvss_score":7.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2010-2966","kev_date_added":null,"published":"2010-08-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-25","vendors":["n/a"]},"summary":"Attackers can exploit improper path handling in tarExtract to traverse directories and access or modify files outside the intended extraction path.","url":"https://insights.sbomify.com/CVE-2023-38346/"}