Authenticated command execution via unsanitized blacklist name
Published Oct 28, 2025 · Updated Oct 28, 2025
Command injection in IPFire before 2.29 allows remote authenticated users to execute commands as nobody through a crafted blacklist name. The urlfilter.cgi blacklist installer interpolates BE_NAME directly into a shell invocation without filtering shell metacharacters. Access to the authenticated blacklist editor is required, and injected commands run with the privileges of the nobody account.
Summary
What happened
Command injection in IPFire before 2.29 allows remote authenticated users to execute commands as nobody through a crafted blacklist name. The urlfilter.cgi blacklist installer interpolates BE_NAME directly into a shell invocation without filtering shell metacharacters. Access to the authenticated blacklist editor is required, and injected commands run with the privileges of the nobody account.
The record
- CVE
- CVE-2025-34312
- Published
- Oct 28, 2025
- Updated
- Oct 28, 2025
- Vendor
- IPFire Project
- Product
- IPFire
- Classifications
- CWE-78, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 28, 2025CVE publishedPublication date reported by the CVE source.
- Oct 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.29 (Core Update 198)
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Researcher Report proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo