{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-29815 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-29815 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-29815 is a medium-severity code injection vulnerability in Jetbrains Intellij Idea, published on 28 Apr 2022. 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-2022-29815 and fix it if it is affected.\n\nWhat it is: CVE-2022-29815 is a medium-severity code injection vulnerability in Jetbrains Intellij Idea, published on 28 Apr 2022. 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-2022-29815 in the wild and no public exploit code.\n\nAffected product: Jetbrains Intellij Idea. 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-2022-29815/ (Markdown: https://insights.sbomify.com/CVE-2022-29815/index.md)","id":"CVE-2022-29815","markdown":"https://insights.sbomify.com/CVE-2022-29815/index.md","name":"CVE-2022-29815","record":{"aliases":["GHSA-96xh-h4gh-f43m"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IntelliJ IDEA IDE","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary code locally by tricking users into opening malicious workspace settings in IntelliJ IDEA.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"JetBrains","cpe":[{"product":"intellij_idea","vendor":"jetbrains"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"In JetBrains IntelliJ IDEA before 2022.1 local code execution via workspace settings was possible","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":"Code injection in IntelliJ IDEA","id":"CVE-2022-29815","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"jetbrains:intellij_idea","products":["jetbrains:intellij_idea"],"type":"code_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in IntelliJ IDEA","id":"CVE-2022-29816"},"packages":[],"prev":{"headline":"Code injection in IntelliJ IDEA","id":"CVE-2022-29814"},"products":["IntelliJ IDEA"],"published":"2022-04-28","related":[{"cvss_score":10,"headline":"Missing authorization in IntelliJ IDEA","id":"CVE-2026-64812","kev_date_added":null,"published":"2026-07-23"},{"cvss_score":10,"headline":"Missing authorization in IntelliJ IDEA","id":"CVE-2026-64813","kev_date_added":null,"published":"2026-07-23"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2020-11690","kev_date_added":null,"published":"2020-04-22"},{"cvss_score":9.8,"headline":"Misconfiguration in n/a","id":"CVE-2019-10104","kev_date_added":null,"published":"2019-07-03"},{"cvss_score":9.8,"headline":"Misconfiguration in n/a","id":"CVE-2019-9186","kev_date_added":null,"published":"2019-07-03"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2019-9823","kev_date_added":null,"published":"2019-07-03"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2019-9873","kev_date_added":null,"published":"2019-07-03"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["JetBrains"]},"summary":"Attackers can execute arbitrary code locally by tricking users into opening malicious workspace settings in IntelliJ IDEA.","url":"https://insights.sbomify.com/CVE-2022-29815/"}