{"answers":{"affected":"2 open source packages ship an affected version, including com.browserup:browserup-proxy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26282 in the wild and no public exploit code.","fix":"Upgrade com.browserup:browserup-proxy to 2.1.2 or later.","what":"CVE-2020-26282 is a critical code injection vulnerability in browserup-proxy, published on 24 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-26282 and fix it if it is affected.\n\nWhat it is: CVE-2020-26282 is a critical code injection vulnerability in browserup-proxy, published on 24 Dec 2020. 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-2020-26282 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.browserup:browserup-proxy (Maven): affected all versions; fixed in 2.1.2\n- com.browserup:browserup-proxy (Maven): affected all versions; fixed in 2.1.2\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-26282/ (Markdown: https://insights.sbomify.com/CVE-2020-26282/index.md)","id":"CVE-2020-26282","markdown":"https://insights.sbomify.com/CVE-2020-26282/index.md","name":"CVE-2020-26282","record":{"aliases":["GHSA-wmfg-55f9-j8hq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Java proxy library","requires_auth":"none","summary":"Unauthenticated attackers can achieve remote code execution by injecting Java EL expressions into BrowserUp Proxy.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"browserup_proxy","vendor":"browserup"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"BrowserUp Proxy allows you to manipulate HTTP requests and responses, capture HTTP content, and export performance data as a HAR file. BrowserUp Proxy works well as a standalone proxy server, but it is especially useful when embedded in Selenium tests. A Server-Side Template Injection was identified in BrowserUp Proxy enabling attackers to inject arbitrary Java EL expressions, leading to unauthenticated Remote Code Execution (RCE) vulnerability. This has been patched in version 2.1.2.","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":"Template Injection in BrowserUp Proxy","id":"CVE-2020-26282","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":2,"n_references":4,"next":{"headline":"Control character injection in console output","id":"CVE-2020-26283"},"packages":[{"ecosystem":"Maven","fixed":["2.1.2"],"introduced":["0"],"last_affected":[],"package":"com.browserup:browserup-proxy","purl":null,"source":"GHSA-wmfg-55f9-j8hq"},{"ecosystem":"Maven","fixed":["2.1.2"],"introduced":["0"],"last_affected":[],"package":"com.browserup:browserup-proxy","purl":"pkg:maven/com.browserup/browserup-proxy","source":"GHSA-wmfg-55f9-j8hq"}],"prev":{"headline":"request smuggling in async-h1","id":"CVE-2020-26281"},"products":["browserup-proxy"],"published":"2020-12-24","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["browserup"]},"summary":"Unauthenticated attackers can achieve remote code execution by injecting Java EL expressions into BrowserUp Proxy.","url":"https://insights.sbomify.com/CVE-2020-26282/"}