{"answers":{"affected":"2 open source packages ship an affected version, including io.pebbletemplates:pebble. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-37767 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-37767 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-37767 is a critical code injection vulnerability in n/a, published on 12 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-37767 and fix it if it is affected.\n\nWhat it is: CVE-2022-37767 is a critical code injection vulnerability in n/a, published on 12 Sep 2022. 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-2022-37767 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.pebbletemplates:pebble (Maven): affected all versions up to 3.1.5; no fix listed\n- io.pebbletemplates:pebble (Maven): affected all versions up to 3.1.5; no fix listed\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-37767/ (Markdown: https://insights.sbomify.com/CVE-2022-37767/index.md)","id":"CVE-2022-37767","markdown":"https://insights.sbomify.com/CVE-2022-37767/index.md","name":"CVE-2022-37767","record":{"aliases":["GHSA-wxx5-w9jc-48wx"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Java templating library","requires_auth":"none","summary":"Attackers can execute arbitrary code via Pebble Templates if untrusted input is passed to the engine without application-level restrictions.","user_interaction":"not_required","vuln_class":"code_injection"},"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-863","name":"Incorrect Authorization"}],"description":"Pebble Templates 3.1.5 allows attackers to bypass a protection mechanism and implement arbitrary code execution with springbok. NOTE: the vendor disputes this because input to the Pebble templating engine is intended to include arbitrary Java code, and thus either the input should not arrive from an untrusted source, or else the application using the engine should apply restrictions to the input. The engine is not responsible for validating the input.","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":false,"headline":"Pebble Templates protection mechanism bypass can lead to arbitrary code execution","id":"CVE-2022-37767","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2022-37768"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["3.1.5"],"package":"io.pebbletemplates:pebble","purl":null,"source":"GHSA-wxx5-w9jc-48wx"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["3.1.5"],"package":"io.pebbletemplates:pebble","purl":"pkg:maven/io.pebbletemplates/pebble","source":"GHSA-wxx5-w9jc-48wx"}],"prev":{"headline":"graphql-java vulnerable to Denial of Service via GraphQL query that consumes CPU resources","id":"CVE-2022-37734"},"products":["n/a"],"published":"2022-09-12","related":[{"cvss_score":9.8,"headline":"Pebble Templates Improper Input Validation vulnerability","id":"CVE-2019-19899","kev_date_added":null,"published":"2019-12-18"},{"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-03","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code via Pebble Templates if untrusted input is passed to the engine without application-level restrictions.","url":"https://insights.sbomify.com/CVE-2022-37767/"}