{"answers":{"affected":"2 open source packages ship an affected version, including com.ibeetl:beetl-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-22533 in the wild and no public exploit code.","fix":"Upgrade com.ibeetl:beetl-core to 3.15.13.RELEASE or later.","what":"CVE-2024-22533 is a critical code injection vulnerability in n/a, published on 2 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-22533 and fix it if it is affected.\n\nWhat it is: CVE-2024-22533 is a critical code injection vulnerability in n/a, published on 2 Feb 2024. 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-2024-22533 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.ibeetl:beetl-core (Maven): affected all versions; fixed in 3.15.13.RELEASE\n- com.ibeetl:beetl-core (Maven): affected all versions; fixed in 3.15.13.RELEASE\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-2024-22533/ (Markdown: https://insights.sbomify.com/CVE-2024-22533/index.md)","id":"CVE-2024-22533","markdown":"https://insights.sbomify.com/CVE-2024-22533/index.md","name":"CVE-2024-22533","record":{"aliases":["GHSA-9gh8-877r-g477"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Beetl template engine","requires_auth":"none","summary":"Attackers can achieve arbitrary code execution by bypassing blacklist filters in the Beetl template engine when controlling input templates.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"beetl","vendor":"xiandafu"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","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-94","name":"Improper Control of Generation of Code"}],"description":"Before Beetl v3.15.12, the rendering template has a server-side template injection (SSTI) vulnerability. When the incoming template is controllable, it will be filtered by the DefaultNativeSecurityManager blacklist. Because blacklist filtering is not strict, the blacklist can be bypassed, leading to arbitrary code execution.","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":"Beetl Server-Side Template Injection vulnerability","id":"CVE-2024-22533","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2024"},"n_packages":2,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2024-22543"},"packages":[{"ecosystem":"Maven","fixed":["3.15.13.RELEASE"],"introduced":["0"],"last_affected":[],"package":"com.ibeetl:beetl-core","purl":null,"source":"GHSA-9gh8-877r-g477"},{"ecosystem":"Maven","fixed":["3.15.13.RELEASE"],"introduced":["0"],"last_affected":[],"package":"com.ibeetl:beetl-core","purl":"pkg:maven/com.ibeetl/beetl-core","source":"GHSA-9gh8-877r-g477"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2024-22532"},"products":["n/a"],"published":"2024-02-02","related":[],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-17","vendors":["n/a"]},"summary":"Attackers can achieve arbitrary code execution by bypassing blacklist filters in the Beetl template engine when controlling input templates.","url":"https://insights.sbomify.com/CVE-2024-22533/"}