{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-41282 exists.","fix":"No fix has been published for CVE-2021-41282 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41282 is a high-severity code injection vulnerability in n/a, published on 1 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-41282 and fix it if it is affected.\n\nWhat it is: CVE-2021-41282 is a high-severity code injection vulnerability in n/a, published on 1 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-41282 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2021-41282/ (Markdown: https://insights.sbomify.com/CVE-2021-41282/index.md)","id":"CVE-2021-41282","markdown":"https://insights.sbomify.com/CVE-2021-41282/index.md","name":"CVE-2021-41282","record":{"aliases":["GHSA-px3p-5c29-4jxr"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"pfSense firewall","requires_auth":"low_privilege","summary":"Authenticated attackers can inject sed commands to write arbitrary files, potentially leading to code execution or privilege escalation on pfSense firewalls.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pfsense","vendor":"pfsense"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"diag_routes.php in pfSense 2.5.2 allows sed data injection. Authenticated users are intended to be able to view data about the routes set in the firewall. The data is retrieved by executing the netstat utility, and then its output is parsed via the sed utility. Although the common protection mechanisms against command injection (i.e., the usage of the escapeshellarg function for the arguments) are used, it is still possible to inject sed-specific code and write an arbitrary file in an arbitrary location.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2022-02-23","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":1,"refs":[{"date":"2022-02-23","kind":"metasploit","ref":"exploit/unix/http/pfsense_diag_routes_webshell","stars":null,"title":"pfSense Diag Routes Web Shell Upload"},{"date":null,"kind":"nuclei","ref":"http/cves/2021/CVE-2021-41282.yaml","stars":null,"title":"pfSense - Arbitrary File Write"}],"tier":"weaponised"},"has_fix":false,"headline":"Code injection in n/a","id":"CVE-2021-41282","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2021"},"n_packages":0,"n_references":4,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2021-41285"},"packages":[],"prev":{"headline":"Path traversal in Matrix Synapse","id":"CVE-2021-41281"},"products":["n/a"],"published":"2022-03-01","related":[{"cvss_score":9.9,"headline":"Code injection in n/a","id":"CVE-2025-69691","kev_date_added":null,"published":"2026-05-08"},{"cvss_score":9.8,"headline":"Weak cryptography in n/a","id":"CVE-2023-29974","kev_date_added":null,"published":"2023-11-08"},{"cvss_score":9.1,"headline":"Deserialization in n/a","id":"CVE-2025-69690","kev_date_added":null,"published":"2026-05-08"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2016-10709","kev_date_added":null,"published":"2018-01-22"},{"cvss_score":8.6,"headline":"Netgate pfSense CE 2.7.0 through 2.9.0 OS Command Injection via interfaces_qinq_edit.php","id":"CVE-2026-111214","kev_date_added":null,"published":"2026-10-15"},{"cvss_score":8.6,"headline":"Netgate pfSense CE through 2.9.0 OS Command Injection via Wireless Parent Interface","id":"CVE-2026-111215","kev_date_added":null,"published":"2026-10-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Authenticated attackers can inject sed commands to write arbitrary files, potentially leading to code execution or privilege escalation on pfSense firewalls.","url":"https://insights.sbomify.com/CVE-2021-41282/"}