{"answers":{"affected":"2 open source packages ship an affected version, including com.github.junrar:junrar. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-12418 in the wild and no public exploit code.","fix":"Upgrade com.github.junrar:junrar to 1.0.1 or later.","what":"CVE-2018-12418 is a medium-severity denial of service vulnerability in n/a, published on 14 Jun 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-12418 and fix it if it is affected.\n\nWhat it is: CVE-2018-12418 is a medium-severity denial of service vulnerability in n/a, published on 14 Jun 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-12418 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.github.junrar:junrar (Maven): affected all versions; fixed in 1.0.1\n- com.github.junrar:junrar (Maven): affected all versions; fixed in 1.0.1\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-2018-12418/ (Markdown: https://insights.sbomify.com/CVE-2018-12418/index.md)","id":"CVE-2018-12418","markdown":"https://insights.sbomify.com/CVE-2018-12418/index.md","name":"CVE-2018-12418","record":{"aliases":["ECHO-dcdc-4fd6-a372","GHSA-5xqr-grq4-qwgx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Java RAR library","requires_auth":"none","summary":"An attacker can cause a denial of service via an infinite loop in the Junrar library when processing corrupt RAR files.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"junrar","vendor":"junrar_project"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-835","name":"Loop with Unreachable Exit Condition"}],"description":"Archive.java in Junrar before 1.0.1, as used in Apache Tika and other products, is affected by a denial of service vulnerability due to an infinite loop when handling corrupt RAR files.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2018-11-19","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-11-19T11:12:00Z","kind":"github_poc","ref":"https://github.com/tafamace/CVE-2018-12418","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":true,"headline":"Junrar vulnerable to Infinite Loop","id":"CVE-2018-12418","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"denial_of_service","year":"2018"},"n_packages":2,"n_references":2,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2018-12420"},"packages":[{"ecosystem":"Maven","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"com.github.junrar:junrar","purl":null,"source":"GHSA-5xqr-grq4-qwgx"},{"ecosystem":"Maven","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"com.github.junrar:junrar","purl":"pkg:maven/com.github.junrar/junrar","source":"GHSA-5xqr-grq4-qwgx"}],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2018-12417"},"products":["n/a"],"published":"2018-06-14","related":[{"cvss_score":7.5,"headline":"Infinite loop in junrar","id":"CVE-2022-23596","kev_date_added":null,"published":"2022-02-01"},{"cvss_score":5.9,"headline":"Junrar: Path Traversal (Zip-Slip) via Sibling Directory Name Prefix","id":"CVE-2026-41245","kev_date_added":null,"published":"2026-04-20"},{"cvss_score":5.9,"headline":"Junrar has arbitrary file write due to backslash path traversal bypass in LocalFolderExtractor on Linux/Unix","id":"CVE-2026-28208","kev_date_added":null,"published":"2026-02-26"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"An attacker can cause a denial of service via an infinite loop in the Junrar library when processing corrupt RAR files.","url":"https://insights.sbomify.com/CVE-2018-12418/"}