{"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-2018-18893 in the wild and no public exploit code.","fix":"Upgrade com.hubspot.jinjava:jinjava to 2.4.6 or later.","what":"CVE-2018-18893 is a medium-severity code injection vulnerability in n/a, published on 3 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-18893 and fix it if it is affected.\n\nWhat it is: CVE-2018-18893 is a medium-severity code injection vulnerability in n/a, published on 3 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-18893 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.4.6\n- com.hubspot.jinjava:jinjava (Maven): affected all versions; fixed in 2.4.6\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-18893/ (Markdown: https://insights.sbomify.com/CVE-2018-18893/index.md)","id":"CVE-2018-18893","markdown":"https://insights.sbomify.com/CVE-2018-18893/index.md","name":"CVE-2018-18893","record":{"aliases":["GHSA-45r8-3495-x6rm"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Java template engine","requires_auth":"none","summary":"Attackers can execute arbitrary code via the getClass method in the Jinjava template engine due to insufficient input validation.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jinjava","vendor":"hubspot"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[],"description":"Jinjava before 2.4.6 does not block the getClass method, related to com/hubspot/jinjava/el/ext/JinjavaBeanELResolver.java.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2023-02-17","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-02-17T09:48:14Z","kind":"github_poc","ref":"https://github.com/LycsHub/CVE-2018-18893","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":true,"headline":"Jinjava calls getClass","id":"CVE-2018-18893","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2018"},"n_packages":2,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2018-18894"},"packages":[{"ecosystem":"Maven","fixed":["2.4.6"],"introduced":["0"],"last_affected":[],"package":"com.hubspot.jinjava:jinjava","purl":null,"source":"GHSA-45r8-3495-x6rm"},{"ecosystem":"Maven","fixed":["2.4.6"],"introduced":["0"],"last_affected":[],"package":"com.hubspot.jinjava:jinjava","purl":"pkg:maven/com.hubspot.jinjava/jinjava","source":"GHSA-45r8-3495-x6rm"}],"prev":{"headline":"Code injection in n/a","id":"CVE-2018-18892"},"products":["n/a"],"published":"2019-01-03","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":6.5,"headline":"Unauthorized access to Class instance in Jinjava","id":"CVE-2020-12668","kev_date_added":null,"published":"2021-02-19"}],"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":"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-08-05","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code via the getClass method in the Jinjava template engine due to insufficient input validation.","url":"https://insights.sbomify.com/CVE-2018-18893/"}