{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-34311 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-34311 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-34311 is a high-severity command injection vulnerability in IPFire.org IPFire, published on 28 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-34311 and fix it if it is affected.\n\nWhat it is: CVE-2025-34311 is a high-severity command injection vulnerability in IPFire.org IPFire, published on 28 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-34311 in the wild and no public exploit code.\n\nAffected product: IPFire.org IPFire. 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-2025-34311/ (Markdown: https://insights.sbomify.com/CVE-2025-34311/index.md)","id":"CVE-2025-34311","markdown":"https://insights.sbomify.com/CVE-2025-34311/index.md","name":"CVE-2025-34311","record":{"aliases":["GHSA-qxm8-6g78-524j"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"IPFire firewall OS","requires_auth":"low_privilege","summary":"Authenticated attackers can execute arbitrary commands as 'nobody' via unsanitized parameters in IPFire's Proxy report creation feature.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"ipfire","vendor":"ipfire"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"IPFire versions prior to 2.29 (Core Update 198) contain a command injection vulnerability that allows an authenticated attacker to execute arbitrary commands as the user 'nobody' via multiple parameters when creating a Proxy report. When a user creates a Proxy report the application issues an HTTP POST to /cgi-bin/logs.cgi/calamaris.dat and reads the values of DAY_BEGIN, MONTH_BEGIN, YEAR_BEGIN, DAY_END, MONTH_END, YEAR_END, NUM_DOMAINS, PERF_INTERVAL, NUM_CONTENT, HIST_LEVEL, NUM_HOSTS, NUM_URLS, and BYTE_UNIT, which are interpolated directly into the shell invocation of the mkreport helper. Because these parameters are never sanitized for improper characters or constructs, a crafted POST can inject shell metacharacters into one or more fields, causing arbitrary commands to run with the privileges of the 'nobody' user.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"IPFire \u003c v2.29 Command Injection via Proxy Report Creation","id":"CVE-2025-34311","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"IPFire \u003c v2.29 Command Injection via URL Filter Blacklist","id":"CVE-2025-34312"},"packages":[],"prev":{"headline":"IPFire \u003c v2.29 Stored XSS via Quality of Service (QoS) Settings","id":"CVE-2025-34310"},"products":["IPFire"],"published":"2025-10-28","related":[{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2021-33393","kev_date_added":null,"published":"2021-06-09"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2018-16232","kev_date_added":null,"published":"2018-10-17"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2017-9757","kev_date_added":null,"published":"2017-06-19"},{"cvss_score":8.7,"headline":"IPFire \u003c v2.29 Command Injection via URL Filter Blacklist","id":"CVE-2025-34312","kev_date_added":null,"published":"2025-10-28"},{"cvss_score":7.1,"headline":"IPFire \u003c v2.29 SQL Injection via OpenVPN Connection Logs","id":"CVE-2025-34304","kev_date_added":null,"published":"2025-10-28"},{"cvss_score":6.5,"headline":"Command injection in n/a","id":"CVE-2025-50974","kev_date_added":null,"published":"2025-08-26"}],"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-28","vendors":["IPFire.org"]},"summary":"Authenticated attackers can execute arbitrary commands as 'nobody' via unsanitized parameters in IPFire's Proxy report creation feature.","url":"https://insights.sbomify.com/CVE-2025-34311/"}