dbcve.org
IpfireApplication

CVE-2025-34304

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-28
Fix available
A fix is available. Upgrade to 2.29 or later.
See remediation →
71/100
Remediation priority · Elevated
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 SQL injection vulnerability that allows an authenticated attacker to manipulate the SQL query used when viewing OpenVPN connection logs via the CONNECTION_NAME parameter. When viewing a range of OpenVPN connection logs, the application issues an HTTP POST request to the Request-URI /cgi-bin/logs.cgi/ovpnclients.dat and inserts the value of the CONNECTION_NAME parameter directly into the WHERE clause without proper sanitization or parameterization. The unsanitized value can alter the executed query and be used to disclose sensitive information from the database.

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 SQL injection vulnerability in the OpenVPN connection logs viewer (logs.cgi/ovpnclients.dat). The CONNECTION_NAME parameter from HTTP POST requests is inserted directly into the SQL WHERE clause without sanitization or parameterization, allowing authenticated attackers to manipulate queries and extract sensitive database information.

MitigationUpgrade to IPFire 2.29 (Core Update 198) or later, which includes proper input sanitization or parameterized queries for the CONNECTION_NAME parameter.

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
None
Availability
None

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

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
    Inspect the IPFire web UI status page or check /etc/os-release file for the installed version number
    Affected if The installed version is earlier than 2.29 (Core Update 198) or exactly 2.29
  2. Confirm OpenVPN is configured
    Look for active OpenVPN client or roadwarrior configurations in the IPFire web UI under Services > OpenVPN
    Affected if OpenVPN is enabled and connection logs are accessible via the logs viewer
  3. Verify logs.cgi access
    Locate the logs.cgi script in the /cgi-bin/ directory of the IPFire web interface
    Affected if The logs.cgi script exists and responds to requests for ovpnclients.dat
  4. Check authentication to the logs viewer
    Verify that the IPFire web UI authentication is active and determine whether remote or local users have access to the OpenVPN logs
    Affected if An attacker can authenticate to the IPFire web interface to submit POST requests to the vulnerable endpoint

You are affected if your IPFire version is 2.29 or earlier and you have OpenVPN enabled with authenticated access to the logs viewer, as the CONNECTION_NAME parameter in the ovpnclients.dat logs endpoint can be exploited for SQL injection.

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 includes proper input sanitization or parameterized queries for the CONNECTION_NAME parameter.

Recommended fix High confidence

2.29 (Core Update 198)

  1. Log into the IPFire web interface
  2. Navigate to the System menu and select 'Update'
  3. Check for available updates and ensure the system updates to Core Update 198 (version 2.29)
  4. Apply the update and wait for the system to reboot
  5. Verify the installation by checking System > Update to confirm version 2.29 is installed
  6. Alternatively, from the console run: pakfire update && pakfire upgrade to fetch and install the latest Core Update

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

Fix this in Ipfire Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34304 — 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-34304 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