dbcve.org
IpfireApplication

CVE-2025-34311

HIGH · 8.8 CVSS v3.1 Published 2025-10-28
Fix available
A fix is available. Upgrade to 2.29 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

IPFire versions before 2.29 (Core Update 198) have a command injection vulnerability in the Proxy report creation feature (calamaris.dat). Multiple HTTP POST parameters (DAY_BEGIN, MONTH_BEGIN, YEAR_BEGIN, DAY_END, MONTH_END, YEAR_END, NUM_DOMAINS, PERF_INTERVAL, NUM_CONTENT, HIST_LEVEL, NUM_HOSTS, NUM_URLS, BYTE_UNIT) are directly interpolated into a shell command invoking the mkreport helper without any sanitization, allowing authenticated attackers to inject shell metacharacters and execute arbitrary commands as the unprivileged 'nobody' user.

MitigationUpgrade to IPFire 2.29 (Core Update 198) or later which implements proper input validation and sanitization of all proxy report parameters before shell invocation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IpfireApplication
Affected:< 2.29= 2.29

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check IPFire version
    Access the IPFire web UI and look at the System page, or run 'cat /etc/os-release' via SSH to determine the installed version. Look for the Core Update version number.
    Affected if The installed version is below 2.29 (Core Update 198) or exactly 2.29
  2. Verify logs.cgi interface is accessible
    Confirm the /cgi-bin/logs.cgi endpoint is exposed and accessible via HTTP/HTTPS on the IPFire appliance.
    Affected if The logs.cgi interface is reachable from the network where an attacker could send requests
  3. Check authentication configuration for logs.cgi
    Review the IPFire web UI access controls and determine whether the logs.cgi interface permits unauthenticated access or uses weak authentication. The CVE requires an authenticated attacker, so verify who can authenticate.
    Affected if Untrusted or unknown users have valid credentials to access the IPFire administrative interface
  4. Confirm mkreport helper exists
    Via SSH or shell access to IPFire, verify that the /usr/local/bin/mkreport helper script exists, as this is the binary invoked with the unsanitized parameters.
    Affected if The mkreport helper binary is present on the system

A system is affected if it runs IPFire version below or equal to 2.29 and has the logs.cgi interface accessible to users who can authenticate (including potentially compromised or untrusted accounts).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.29 or later
Fixed in 2.29
Interim mitigation

Upgrade to IPFire 2.29 (Core Update 198) or later which implements proper input validation and sanitization of all proxy report parameters before shell invocation.

Recommended fix High confidence

IPFire 2.29 Core Update 198

  1. Log into the IPFire administration interface
  2. Navigate to the System menu and select 'Update'
  3. Check for available updates and ensure the system updates to IPFire 2.29 Core Update 198 or later
  4. Alternatively, download the IPFire 2.29 Core Update 198 (or newer) installation image from www.ipfire.org
  5. Apply the update following IPFire's standard update procedure
  6. After updating, verify the version by checking System > Status to confirm Core Update 198 or higher is installed
Caveat Review IPFire release notes for Core Update 198 to check for any configuration or feature changes that may affect your setup

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipfire Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34311 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34311 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data