← Back

CVE-2025-34304

nvd nist
Published: Oct 28, 2025Modified: Nov 3, 2025

JSON object

Loading...
7.1
Vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Show more
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XShow less
Source: disclosure@vulncheck.com (Secondary)

Description

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.

Affected (16)

Products: Ipfire: Ipfire
Ipfire
1 product
Ipfire
Configuration A
16 vulnerable
Vulnerable SoftwareAffected Versions
Ipfire
Ipfire
Before 2.29
Ipfire
Version 2.29 core_update183
Ipfire
Version 2.29 core_update184
Ipfire
Version 2.29 core_update185
Ipfire
Version 2.29 core_update186
Ipfire
Version 2.29 core_update187
Ipfire
Version 2.29 core_update188
Ipfire
Version 2.29 core_update189
Ipfire
Version 2.29 core_update190
Ipfire
Version 2.29 core_update191
Ipfire
Version 2.29 core_update192
Ipfire
Version 2.29 core_update193
Ipfire
Version 2.29 core_update194
Ipfire
Version 2.29 core_update195
Ipfire
Version 2.29 core_update196
Ipfire
Version 2.29 core_update197

Related CWEs

CWE-89
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

References (3)

Source: disclosure@vulncheck.com
Issue TrackingThird Party Advisory
Source: disclosure@vulncheck.com
Release Notes
Source: disclosure@vulncheck.com
Third Party Advisory

Timeline

No history available yet.