{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24569 exists.","fix":"No fix has been published for CVE-2024-24569 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-24569 is a medium-severity path traversal vulnerability in pixee java-security-toolkit, published on 1 Feb 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-24569 and fix it if it is affected.\n\nWhat it is: CVE-2024-24569 is a medium-severity path traversal vulnerability in pixee java-security-toolkit, published on 1 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24569 exists.\n\nAffected product: pixee java-security-toolkit. 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-24569/ (Markdown: https://insights.sbomify.com/CVE-2024-24569/index.md)","id":"CVE-2024-24569","markdown":"https://insights.sbomify.com/CVE-2024-24569/index.md","name":"CVE-2024-24569","record":{"aliases":["GHSA-qh4g-4m4w-jgv2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Java security toolkit","requires_auth":"none","summary":"Attackers can traverse to sibling directories, bypassing path restrictions in the Pixee Java security toolkit.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"java_code_security_toolkit","vendor":"pixee"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"The Pixee Java Code Security Toolkit is a set of security APIs meant to help secure Java code. `ZipSecurity#isBelowCurrentDirectory` is vulnerable to a partial-path traversal bypass. To be vulnerable to the bypass, the application must use toolkit version \u003c=1.1.1, use ZipSecurity as a guard against path traversal, and have an exploit path. Although the control still protects attackers from escaping the application path into higher level directories (e.g., /etc/), it will allow \"escaping\" into sibling paths. For example, if your running path is /my/app/path you an attacker could navigate into /my/app/path-something-else. This vulnerability is patched in 1.1.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"`ZipSecurity#isBelowCurrentDirectory` is vulnerable to partial-path traversal vulnerability","id":"CVE-2024-24569","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":"Statamic account takeover via XSS and password reset link","id":"CVE-2024-24570"},"packages":[],"prev":{"headline":"Suricata http2: header handling evasion","id":"CVE-2024-24568"},"products":["java-security-toolkit"],"published":"2024-02-01","related":[],"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":"partial"},"state":"PUBLISHED","updated":"2025-06-17","vendors":["pixee"]},"summary":"Attackers can traverse to sibling directories, bypassing path restrictions in the Pixee Java security toolkit.","url":"https://insights.sbomify.com/CVE-2024-24569/"}