Improper Validation of Certificate in CAS Client
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Apereo | Java Apereo CAS Client | unknown |
|
||||||
| Apereo | Jasig CAS Client | unknown |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Apereo | Jasig Cas Client |
|
||||||||
| Apereo | Java Cas Client |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.260% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apereo
Apereo jasig Cas Client Apereo java Cas Client |
|
| Vendors & Products |
Apereo
Apereo jasig Cas Client Apereo java Cas Client |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Apereo CAS Client accepts any CA-trusted certificate for any hostname, provided the URL the client is calling matches the configured allowlist or regex. An attacker with a MITM position (DNS poisoning, rogue Wi-Fi, malicious proxy, etc.) can provide any CA-signed certificate for a hostname that matches the configured allowlist or regex. This can lead to intercepting the CAS exchange, capturing the Ticket-Granting Ticket (TGT), and subsequently obtaining Service Tickets on behalf of the victim. Because maintainers contact attempts were unsuccessful, vulnerabilities have only been confirmed in version 4.1.0 (Java Apereo CAS Client) and 3.6.4 (Jasig CAS Client) but may also affect other versions. | |
| Title | Improper Validation of Certificate in CAS Client | |
| Weaknesses | CWE-297 | |
| References |
| |
| Metrics |
cvssV4_0
|