{"answers":{"affected":"2 open source packages ship an affected version, including com.hubspot.jinjava:jinjava. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-12668 in the wild and no public exploit code.","fix":"Upgrade com.hubspot.jinjava:jinjava to 2.5.4 or later.","what":"CVE-2020-12668 is a medium-severity code injection vulnerability in n/a, published on 19 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-12668 and fix it if it is affected.\n\nWhat it is: CVE-2020-12668 is a medium-severity code injection vulnerability in n/a, published on 19 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-12668 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.hubspot.jinjava:jinjava (Maven): affected all versions; fixed in 2.5.4\n- com.hubspot.jinjava:jinjava (Maven): affected all versions; fixed in 2.5.4\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-2020-12668/ (Markdown: https://insights.sbomify.com/CVE-2020-12668/index.md)","id":"CVE-2020-12668","markdown":"https://insights.sbomify.com/CVE-2020-12668/index.md","name":"CVE-2020-12668","record":{"aliases":["GHSA-2hjr-fg6c-v2h6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Java template engine","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary Java methods via Jinjava templates, leading to arbitrary file disclosure and potential code execution.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jinjava","vendor":"hubspot"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Jinjava before 2.5.4 allow access to arbitrary classes by calling Java methods on objects passed into a Jinjava context. This could allow for abuse of the application class loader, including Arbitrary File Disclosure.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Unauthorized access to Class instance in Jinjava","id":"CVE-2020-12668","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":2,"n_references":5,"next":{"headline":"Incorrect Authorization in Dolibarr","id":"CVE-2020-12669"},"packages":[{"ecosystem":"Maven","fixed":["2.5.4"],"introduced":["0"],"last_affected":[],"package":"com.hubspot.jinjava:jinjava","purl":null,"source":"GHSA-2hjr-fg6c-v2h6"},{"ecosystem":"Maven","fixed":["2.5.4"],"introduced":["0"],"last_affected":[],"package":"com.hubspot.jinjava:jinjava","purl":"pkg:maven/com.hubspot.jinjava/jinjava","source":"GHSA-2hjr-fg6c-v2h6"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2020-12667"},"products":["n/a"],"published":"2021-02-19","related":[{"cvss_score":9.8,"headline":"JinJava Bypass through ForTag leads to Arbitrary Java Execution","id":"CVE-2026-25526","kev_date_added":null,"published":"2026-02-04"},{"cvss_score":9.8,"headline":"jinjava Sandbox Bypass via JavaType-Based Deserialization","id":"CVE-2025-59340","kev_date_added":null,"published":"2025-09-17"},{"cvss_score":5.3,"headline":"Jinjava calls getClass","id":"CVE-2018-18893","kev_date_added":null,"published":"2019-01-03"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary Java methods via Jinjava templates, leading to arbitrary file disclosure and potential code execution.","url":"https://insights.sbomify.com/CVE-2020-12668/"}