Improper Data Validation in liboauth2
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| OpenIDC | liboauth2 | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Openidc | Liboauth2 |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.178% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Openidc
Openidc liboauth2 |
|
| Vendors & Products |
Openidc
Openidc liboauth2 |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In liboauth2 the Demonstrating Proof-of-Possession (DPoP) verifier accepts a proof whose JSON Web Key (jwk) header contains private key material. RFC 9449 section 4.3 step 7 requires the verifier to reject such a proof but oauth2_token_verify() function returns success for a malformed DPoP proof that embeds the private Elliptic Curve (EC) key in the header. This issue was fixed in version 2.3.0 | |
| Title | Improper Data Validation in liboauth2 | |
| Weaknesses | CWE-358 | |
| References |
| |
| Metrics |
cvssV4_0
|