EUVD-2015-0854
2025-06-26
[email protected]
9.8
CVSS 3.1
Share
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Lifecycle Timeline
4
Patch Released
Mar 31, 2026 - 21:13 nvd
Patch available
Analysis Generated
Mar 15, 2026 - 23:54 vuln.today
EUVD ID Assigned
Mar 15, 2026 - 23:54 euvd
EUVD-2015-0854
CVE Published
Jun 26, 2025 - 22:15 nvd
CRITICAL 9.8
Description
yubiserver before 0.6 is prone to SQL injection issues, potentially leading to an authentication bypass.
Analysis
yubiserver before 0.6 is prone to SQL injection issues, potentially leading to an authentication bypass.
Technical Context
SQL injection occurs when user-supplied input is incorporated into SQL queries without proper sanitization or parameterized queries.
Affected Products
Affected products: Debian Yubiserver 0.2-2
Remediation
Use parameterized queries or prepared statements. Apply input validation and escape special characters. Implement least-privilege database accounts.
Priority Score
49
Low
Medium
High
Critical
KEV: 0
EPSS: +0.0
CVSS: +49
POC: 0
Vendor Status
Ubuntu
Priority: Mediumyubiserver
| Release | Status | Version |
|---|---|---|
| artful | ignored | end of life |
| bionic | not-affected | 0.6-3 |
| cosmic | not-affected | 0.6-3 |
| disco | not-affected | 0.6-3 |
| precise | ignored | end of life |
| upstream | released | 0.6-1 |
| utopic | ignored | end of life |
| vivid | ignored | end of life |
| wily | ignored | end of life |
| xenial | not-affected | 0.6-3 |
| yakkety | ignored | end of life |
| zesty | ignored | end of life |
| trusty | DNE | trusty/esm was DNE [trusty was needed] |
Debian
Bug #796495yubiserver
| Release | Status | Fixed Version | Urgency |
|---|---|---|---|
| bookworm, bullseye | fixed | 0.6-3.1 | - |
| trixie | fixed | 0.6-3.2 | - |
| (unstable) | fixed | 0.6-1 | - |
Share
External POC / Exploit Code
Leaving vuln.today
Destination URL
POC code from unknown sources may be malicious, contain backdoors, or be fake.
Always review and test exploit code in a safe, isolated environment (VM/sandbox).
Verify the source reputation and cross-reference with known databases (Exploit-DB, GitHub Security).