{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-31801 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-31801 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-31801 is a high-severity path traversal vulnerability in n/a, published on 29 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-31801 and fix it if it is affected.\n\nWhat it is: CVE-2024-31801 is a high-severity path traversal vulnerability in n/a, published on 29 Apr 2024. 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-2024-31801 in the wild and no public exploit code.\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-2024-31801/ (Markdown: https://insights.sbomify.com/CVE-2024-31801/index.md)","id":"CVE-2024-31801","markdown":"https://insights.sbomify.com/CVE-2024-31801/index.md","name":"CVE-2024-31801","record":{"aliases":["GHSA-p2m3-5whj-8vxq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"NEXSYS-ONE","requires_auth":"none","summary":"A remote attacker can obtain sensitive information via a crafted request due to a directory traversal vulnerability in NEXSYS-ONE.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Directory Traversal vulnerability in NEXSYS-ONE before v.Rev.15320 allows a remote attacker to obtain sensitive information via a crafted request.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Path traversal in n/a","id":"CVE-2024-31801","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Business logic in n/a","id":"CVE-2024-31802"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2024-31800"},"products":["n/a"],"published":"2024-04-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"A remote attacker can obtain sensitive information via a crafted request due to a directory traversal vulnerability in NEXSYS-ONE.","url":"https://insights.sbomify.com/CVE-2024-31801/"}