Trusted-node impersonation via stale certificate validation flag
Published May 27, 2025 · Updated May 27, 2025
Certificate validation in affected Icinga 2 releases allows remote attackers to impersonate trusted nodes through certificate renewal. VerifyCertificate reuses an OpenSSL X.509 object whose stale valid flag can skip checks when later validation uses a different trust anchor. Exploitation requires direct TLS access to a certificate-signing master built with OpenSSL before 1.1.0; other nodes only log and forward the request.
Summary
What happened
Certificate validation in affected Icinga 2 releases allows remote attackers to impersonate trusted nodes through certificate renewal. VerifyCertificate reuses an OpenSSL X.509 object whose stale valid flag can skip checks when later validation uses a different trust anchor. Exploitation requires direct TLS access to a certificate-signing master built with OpenSSL before 1.1.0; other nodes only log and forward the request.
The record
- CVE
- CVE-2025-48057
- Published
- May 27, 2025
- Updated
- May 27, 2025
- Vendor
- Icinga
- Product
- Icinga 2
- Classifications
- CWE-296, T1649
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 27, 2025CVE publishedPublication date reported by the CVE source.
- May 27, 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=< 2.12.12
- Affected versionversion=>= 2.13.0, < 2.13.12
- Affected versionversion=>= 2.14.0, < 2.14.6
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
No public exploit references are available in this record.
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