{"answers":{"affected":"2 open source packages ship an affected version, including net.lingala.zip4j:zip4j. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22899 exists.","fix":"Upgrade net.lingala.zip4j:zip4j to 2.11.3 or later.","what":"CVE-2023-22899 is a medium-severity vulnerability in n/a, published on 10 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-22899 and fix it if it is affected.\n\nWhat it is: CVE-2023-22899 is a medium-severity vulnerability in n/a, published on 10 Jan 2023. 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-2023-22899 exists.\n\nAffected packages and fixed versions:\n- net.lingala.zip4j:zip4j (Maven): affected all versions; fixed in 2.11.3\n- net.lingala.zip4j:zip4j (Maven): affected all versions; fixed in 2.11.3\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-22899/ (Markdown: https://insights.sbomify.com/CVE-2023-22899/index.md)","id":"CVE-2023-22899","markdown":"https://insights.sbomify.com/CVE-2023-22899/index.md","name":"CVE-2023-22899","record":{"aliases":["DEBIAN-CVE-2023-22899","GHSA-2pj2-gchf-wmw7","UBUNTU-CVE-2023-22899"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Java ZIP library","requires_auth":"none","summary":"Attackers can bypass integrity checks when decrypting ZIP archives using Zip4j, potentially allowing tampered data to be processed as valid.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"zip4j","vendor":"zip4j_project"}],"cvss":{"score":5.9,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"}],"description":"Zip4j through 2.11.2, as used in Threema and other products, does not always check the MAC when decrypting a ZIP archive.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Zip4j Origin Validation Error","id":"CVE-2023-22899","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":2,"n_references":6,"next":{"headline":"Thinking Software Technology Co., Ltd. Efence - SQL Injection","id":"CVE-2023-22900"},"packages":[{"ecosystem":"Maven","fixed":["2.11.3"],"introduced":["0"],"last_affected":[],"package":"net.lingala.zip4j:zip4j","purl":null,"source":"GHSA-2pj2-gchf-wmw7"},{"ecosystem":"Maven","fixed":["2.11.3"],"introduced":["0"],"last_affected":[],"package":"net.lingala.zip4j:zip4j","purl":"pkg:maven/net.lingala.zip4j/zip4j","source":"GHSA-2pj2-gchf-wmw7"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2023-22898"},"products":["n/a"],"published":"2023-01-10","related":[{"cvss_score":6.5,"headline":"Improper Limitation of a Pathname to a Restricted Directory in Zip4j","id":"CVE-2018-1002202","kev_date_added":null,"published":"2018-07-25"},{"cvss_score":5.5,"headline":"Uncaught Exception in zip4j","id":"CVE-2022-24615","kev_date_added":null,"published":"2022-02-24"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-09","vendors":["n/a"]},"summary":"Attackers can bypass integrity checks when decrypting ZIP archives using Zip4j, potentially allowing tampered data to be processed as valid.","url":"https://insights.sbomify.com/CVE-2023-22899/"}