CVE-2021-44878

If an OpenID Connect provider supports the "none" algorithm (i.e., tokens with no signature), pac4j v5.3.0 (and prior) does not refuse it without an explicit configuration on its side or for the "idtoken" response type which is not secure and violates the OpenID Core Specification. The "none" algorithm does not require any signature verification when validating the ID tokens, which allows the attacker to bypass the token validation by injecting a malformed ID token using "none" as the value of "alg" key in the header with an empty signature value.

CVSS v3 7.5 HIGH
CVSS v2.0 5.0 MEDIUM

7.5^/10

CVSS v3 : HIGH

Vector :

Exploitability : 3.9 / Impact : 3.6

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact HIGH

Availability Impact NONE

Scope UNCHANGED

5.0^/10

CVSS v2.0 : MEDIUM

Vector : AV:N/AC:L/Au:N/C:N/I:P/A:N

Exploitability : 10.0 / Impact : 2.9

Access Vector NETWORK

Access Complexity LOW

Authentication NONE

Confidentiality Impact NONE

Integrity Impact PARTIAL

Availability Impact NONE

References

Link	Resource
https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae	Patch Third Party Advisory
https://openid.net/specs/openid-connect-core-1_0.html#IDToken	Product Third Party Advisory
https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.html	Mitigation Vendor Advisory

Configurations

Configuration 1 (hide)

OR	cpe:2.3:a:pac4j:pac4j::::::::
	cpe:2.3:a:pac4j:pac4j::::::::

History

No history.

Information

Published : 2022-01-06 13:15

Updated : 2024-02-28 18:48

NVD link : CVE-2021-44878

Mitre link : CVE-2021-44878

CVE.ORG link : CVE-2021-44878

JSON object : View

Products Affected

pac4j

pac4j

CWE

CWE-347

Improper Verification of Cryptographic Signature

{"id": "CVE-2021-44878", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 5.0, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:N/C:N/I:P/A:N", "authentication": "NONE", "integrityImpact": "PARTIAL", "accessComplexity": "LOW", "availabilityImpact": "NONE", "confidentialityImpact": "NONE"}, "acInsufInfo": false, "impactScore": 2.9, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 10.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "published": "2022-01-06T13:15:08.180", "references": [{"url": "https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae", "tags": ["Patch", "Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://openid.net/specs/openid-connect-core-1_0.html#IDToken", "tags": ["Product", "Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.html", "tags": ["Mitigation", "Vendor Advisory"], "source": "cve@mitre.org"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-347"}]}], "descriptions": [{"lang": "en", "value": "If an OpenID Connect provider supports the \"none\" algorithm (i.e., tokens with no signature), pac4j v5.3.0 (and prior) does not refuse it without an explicit configuration on its side or for the \"idtoken\" response type which is not secure and violates the OpenID Core Specification. The \"none\" algorithm does not require any signature verification when validating the ID tokens, which allows the attacker to bypass the token validation by injecting a malformed ID token using \"none\" as the value of \"alg\" key in the header with an empty signature value."}, {"lang": "es", "value": "Si un proveedor de OpenID Connect soporta el algoritmo \"none\" (es decir, tokens sin firma), pac4j v5.3.0 (y anteriores) no lo rechaza sin una configuraci\u00f3n expl\u00edcita por su parte o para el tipo de respuesta \"idtoken\", que no es seguro y viola la especificaci\u00f3n OpenID Core. El algoritmo \"none\" no requiere ninguna verificaci\u00f3n de firma al validar los tokens de identificaci\u00f3n, lo que permite al atacante saltarse la validaci\u00f3n de tokens inyectando un token de identificaci\u00f3n malformado utilizando \"none\" como valor de la clave \"alg\" en la cabecera con un valor de firma vac\u00edo"}], "lastModified": "2022-05-13T15:51:59.780", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:pac4j:pac4j:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "2C74CE58-A3A8-44B5-83EA-611E214FD060", "versionEndExcluding": "4.5.5"}, {"criteria": "cpe:2.3:a:pac4j:pac4j:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "949A0839-AB1F-4806-B5F9-8317835EB0E2", "versionEndExcluding": "5.3.1", "versionStartIncluding": "5.0.0"}], "operator": "OR"}]}], "sourceIdentifier": "cve@mitre.org"}