{"answers":{"affected":"2 open source packages ship an affected version, including io.pebbletemplates:pebble-project. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19899 in the wild and no public exploit code.","fix":"Upgrade io.pebbletemplates:pebble-project to 3.1.4 or later.","what":"CVE-2019-19899 is a critical vulnerability in n/a, published on 18 Dec 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-2019-19899 and fix it if it is affected.\n\nWhat it is: CVE-2019-19899 is a critical vulnerability in n/a, published on 18 Dec 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-2019-19899 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.pebbletemplates:pebble-project (Maven): affected all versions; fixed in 3.1.4\n- io.pebbletemplates:pebble-project (Maven): affected all versions; fixed in 3.1.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-2019-19899/ (Markdown: https://insights.sbomify.com/CVE-2019-19899/index.md)","id":"CVE-2019-19899","markdown":"https://insights.sbomify.com/CVE-2019-19899/index.md","name":"CVE-2019-19899","record":{"aliases":["GHSA-83m8-7hj8-ff5w"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Java template engine","requires_auth":"none","summary":"Attackers can bypass Class access restrictions in Pebble Templates by exploiting the forName method, potentially leading to further exploitation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pebble_templates","vendor":"pebbletemplates"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Pebble Templates 3.1.2 allows attackers to bypass a protection mechanism (intended to block access to instances of java.lang.Class) because getClass is accessible via the public static java.lang.Class java.lang.Class.forName(java.lang.Module,java.lang.String) signature.","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":"Pebble Templates Improper Input Validation vulnerability","id":"CVE-2019-19899","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-19900"},"packages":[{"ecosystem":"Maven","fixed":["3.1.4"],"introduced":["0"],"last_affected":[],"package":"io.pebbletemplates:pebble-project","purl":null,"source":"GHSA-83m8-7hj8-ff5w"},{"ecosystem":"Maven","fixed":["3.1.4"],"introduced":["0"],"last_affected":[],"package":"io.pebbletemplates:pebble-project","purl":"pkg:maven/io.pebbletemplates/pebble-project","source":"GHSA-83m8-7hj8-ff5w"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2019-19898"},"products":["n/a"],"published":"2019-12-18","related":[{"cvss_score":9.8,"headline":"Pebble Templates protection mechanism bypass can lead to arbitrary code execution","id":"CVE-2022-37767","kev_date_added":null,"published":"2022-09-12"},{"cvss_score":6.1,"headline":"Pebble has Arbitrary Local File Inclusion (LFI) Vulnerability via `include` macro","id":"CVE-2025-1686","kev_date_added":null,"published":"2025-02-27"}],"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-05","vendors":["n/a"]},"summary":"Attackers can bypass Class access restrictions in Pebble Templates by exploiting the forName method, potentially leading to further exploitation.","url":"https://insights.sbomify.com/CVE-2019-19899/"}