cve-2021-44878
Vulnerability from cvelistv5
Published
2022-01-06 12:52
Modified
2024-08-04 04:32
Severity ?
Summary
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.
References
cve@mitre.orghttps://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281aePatch, Third Party Advisory
cve@mitre.orghttps://openid.net/specs/openid-connect-core-1_0.html#IDTokenProduct, Third Party Advisory
cve@mitre.orghttps://www.pac4j.org/blog/cve_2021_44878_is_this_serious.htmlMitigation, Vendor Advisory
af854a3a-2127-422b-91ae-364da2661108https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281aePatch, Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://openid.net/specs/openid-connect-core-1_0.html#IDTokenProduct, Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.htmlMitigation, Vendor Advisory
Impacted products
Vendor Product Version
Show details on NVD website

To clipboard 

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-04T04:32:13.070Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://openid.net/specs/openid-connect-core-1_0.html#IDToken"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.html"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "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."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2022-03-30T01:57:49",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://openid.net/specs/openid-connect-core-1_0.html#IDToken"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.html"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve@mitre.org",
          "ID": "CVE-2021-44878",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "n/a",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "n/a"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "n/a"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "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."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "n/a"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae",
              "refsource": "MISC",
              "url": "https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae"
            },
            {
              "name": "https://openid.net/specs/openid-connect-core-1_0.html#IDToken",
              "refsource": "MISC",
              "url": "https://openid.net/specs/openid-connect-core-1_0.html#IDToken"
            },
            {
              "name": "https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.html",
              "refsource": "MISC",
              "url": "https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.html"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2021-44878",
    "datePublished": "2022-01-06T12:52:04",
    "dateReserved": "2021-12-13T00:00:00",
    "dateUpdated": "2024-08-04T04:32:13.070Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2021-44878\",\"sourceIdentifier\":\"cve@mitre.org\",\"published\":\"2022-01-06T13:15:08.180\",\"lastModified\":\"2024-11-21T06:31:38.873\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"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\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N\",\"baseScore\":7.5,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":3.9,\"impactScore\":3.6}],\"cvssMetricV2\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"2.0\",\"vectorString\":\"AV:N/AC:L/Au:N/C:N/I:P/A:N\",\"baseScore\":5.0,\"accessVector\":\"NETWORK\",\"accessComplexity\":\"LOW\",\"authentication\":\"NONE\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"PARTIAL\",\"availabilityImpact\":\"NONE\"},\"baseSeverity\":\"MEDIUM\",\"exploitabilityScore\":10.0,\"impactScore\":2.9,\"acInsufInfo\":false,\"obtainAllPrivilege\":false,\"obtainUserPrivilege\":false,\"obtainOtherPrivilege\":false,\"userInteractionRequired\":false}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-347\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:pac4j:pac4j:*:*:*:*:*:*:*:*\",\"versionEndExcluding\":\"4.5.5\",\"matchCriteriaId\":\"2C74CE58-A3A8-44B5-83EA-611E214FD060\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:pac4j:pac4j:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.0.0\",\"versionEndExcluding\":\"5.3.1\",\"matchCriteriaId\":\"949A0839-AB1F-4806-B5F9-8317835EB0E2\"}]}]}],\"references\":[{\"url\":\"https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae\",\"source\":\"cve@mitre.org\",\"tags\":[\"Patch\",\"Third Party Advisory\"]},{\"url\":\"https://openid.net/specs/openid-connect-core-1_0.html#IDToken\",\"source\":\"cve@mitre.org\",\"tags\":[\"Product\",\"Third Party Advisory\"]},{\"url\":\"https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.html\",\"source\":\"cve@mitre.org\",\"tags\":[\"Mitigation\",\"Vendor Advisory\"]},{\"url\":\"https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\",\"Third Party Advisory\"]},{\"url\":\"https://openid.net/specs/openid-connect-core-1_0.html#IDToken\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Product\",\"Third Party Advisory\"]},{\"url\":\"https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.html\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Mitigation\",\"Vendor Advisory\"]}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.