8.2 CVE-2025-3501

 

A flaw was found in Keycloak. By setting a verification policy to 'ALL', the trust store certificate verification is skipped, which is unintended.
https://nvd.nist.gov/vuln/detail/CVE-2025-3501

Categories

CWE-297 : Improper Validation of Certificate with Host Mismatch
The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host. Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.) Set up an untrusted endpoint (e.g. a server) with which the product will connect. Create a test certificate that uses an invalid hostname but is signed by a trusted CA and provide this certificate from the untrusted endpoint. If the product performs any operations instead of disconnecting and reporting an error, then this indicates that the hostname is not being checked and the test certificate has been accepted. When Certificate Pinning is being used in a mobile application, consider using a tool such as Spinner [REF-955]. This methodology might be extensible to other technologies. Fully check the hostname of the certificate and provide the user with adequate information about the nature of the problem and how to proceed. If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname. Mobile banking application does not verify hostname, leading to financial loss. Mobile application for printing documents does not verify hostname, allowing attackers to read sensitive documents. Software for electronic checking does not verify hostname, leading to financial loss. Cloud-support library written in Python uses incorrect regular expression when matching hostname. Web browser does not correctly handle '' character (NUL) in Common Name, allowing spoofing of https sites. Database program truncates the Common Name during hostname verification, allowing spoofing. Incorrect handling of '' character (NUL) in hostname verification allows spoofing. Mail server's incorrect handling of '' character (NUL) in hostname verification allows spoofing. LDAP server's incorrect handling of '' character (NUL) in hostname verification allows spoofing. Payment processing module does not verify hostname when connecting to PayPal using PHP fsockopen function. Smartphone device does not verify hostname, allowing spoofing of mail services. E-commerce module does not verify hostname when connecting to payment site. Chat application does not validate hostname, leading to loss of privacy. Application uses third-party library that does not validate hostname. Cloud storage management application does not validate hostname. Java library uses JSSE SSLSocket and SSLEngine classes, which do not verify the hostname. SOAP platform does not verify the hostname. PHP library for payments does not verify the hostname. Merchant SDK for payments does not verify the hostname. Web browser does not validate Common Name, allowing spoofing of https sites.

References


 

CPE

cpe start end

REMEDIATION


EXPLOITS

Exploit-db.com

id description date
No known exploits

POC Github

Url
No known exploits

Other Nist (github, ...)

Url
No known exploits

CAPEC

Common Attack Pattern Enumerations and Classifications

id description severity
No entry