Vulnerability-Lookup

CNVD-2022-09804

Vulnerability from cnvd - Published: 2022-02-12

Title

Pac4j数据伪造问题漏洞

Description

Pac4j是一个简单而强大的Java安全引擎。用于验证用户、获取他们的配置文件和管理授权，以保护Web应用程序和Web服务。 Pac4j存在数据伪造问题漏洞，该漏洞源于产品在验证ID令牌时未使用有效算法，攻击者可利用该漏洞绕过令牌验证。

Severity

中

Patch Name

Pac4j数据伪造问题漏洞的补丁

Patch Description

Pac4j是一个简单而强大的Java安全引擎。用于验证用户、获取他们的配置文件和管理授权，以保护Web应用程序和Web服务。 Pac4j存在数据伪造问题漏洞，该漏洞源于产品在验证ID令牌时未使用有效算法，攻击者可利用该漏洞绕过令牌验证。目前，供应商发布了安全公告及相关补丁信息，修复了此漏洞。

Formal description

厂商已发布了漏洞修复程序，请及时关注更新： https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae

Reference

https://nvd.nist.gov/vuln/detail/CVE-2021-44878

Impacted products

Name
Pac4j Pac4j <=5.1

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2021-44878"
    }
  },
  "description": "Pac4j\u662f\u4e00\u4e2a\u7b80\u5355\u800c\u5f3a\u5927\u7684Java\u5b89\u5168\u5f15\u64ce\u3002\u7528\u4e8e\u9a8c\u8bc1\u7528\u6237\u3001\u83b7\u53d6\u4ed6\u4eec\u7684\u914d\u7f6e\u6587\u4ef6\u548c\u7ba1\u7406\u6388\u6743\uff0c\u4ee5\u4fdd\u62a4Web\u5e94\u7528\u7a0b\u5e8f\u548cWeb\u670d\u52a1\u3002\n\nPac4j\u5b58\u5728\u6570\u636e\u4f2a\u9020\u95ee\u9898\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u4ea7\u54c1\u5728\u9a8c\u8bc1ID\u4ee4\u724c\u65f6\u672a\u4f7f\u7528\u6709\u6548\u7b97\u6cd5\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u7ed5\u8fc7\u4ee4\u724c\u9a8c\u8bc1\u3002",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u4e86\u6f0f\u6d1e\u4fee\u590d\u7a0b\u5e8f\uff0c\u8bf7\u53ca\u65f6\u5173\u6ce8\u66f4\u65b0\uff1a\r\nhttps://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2022-09804",
  "openTime": "2022-02-12",
  "patchDescription": "Pac4j\u662f\u4e00\u4e2a\u7b80\u5355\u800c\u5f3a\u5927\u7684Java\u5b89\u5168\u5f15\u64ce\u3002\u7528\u4e8e\u9a8c\u8bc1\u7528\u6237\u3001\u83b7\u53d6\u4ed6\u4eec\u7684\u914d\u7f6e\u6587\u4ef6\u548c\u7ba1\u7406\u6388\u6743\uff0c\u4ee5\u4fdd\u62a4Web\u5e94\u7528\u7a0b\u5e8f\u548cWeb\u670d\u52a1\u3002\r\n\r\nPac4j\u5b58\u5728\u6570\u636e\u4f2a\u9020\u95ee\u9898\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u4ea7\u54c1\u5728\u9a8c\u8bc1ID\u4ee4\u724c\u65f6\u672a\u4f7f\u7528\u6709\u6548\u7b97\u6cd5\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u7ed5\u8fc7\u4ee4\u724c\u9a8c\u8bc1\u3002\u76ee\u524d\uff0c\u4f9b\u5e94\u5546\u53d1\u5e03\u4e86\u5b89\u5168\u516c\u544a\u53ca\u76f8\u5173\u8865\u4e01\u4fe1\u606f\uff0c\u4fee\u590d\u4e86\u6b64\u6f0f\u6d1e\u3002",
  "patchName": "Pac4j\u6570\u636e\u4f2a\u9020\u95ee\u9898\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": "Pac4j Pac4j \u003c=5.1"
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2021-44878",
  "serverity": "\u4e2d",
  "submitTime": "2022-01-07",
  "title": "Pac4j\u6570\u636e\u4f2a\u9020\u95ee\u9898\u6f0f\u6d1e"
}

CVE-2021-44878 (GCVE-0-2021-44878)

Vulnerability from cvelistv5 – Published: 2022-01-06 12:52 – Updated: 2024-08-04 04:32

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.

Severity

No CVSS data available.

CWE

Assigner

mitre mitre root

References

3 references

URL	Tags
https://github.com/pac4j/pac4j/commit/22b82ffd702…	x_refsource_MISC
https://openid.net/specs/openid-connect-core-1_0.…	x_refsource_MISC
https://www.pac4j.org/blog/cve_2021_44878_is_this…	x_refsource_MISC

Show details on NVD website

JSON

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.000Z",
        "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.000Z",
    "dateReserved": "2021-12-13T00:00:00.000Z",
    "dateUpdated": "2024-08-04T04:32:13.070Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

CNVD-2022-09804

CVE-2021-44878 (GCVE-0-2021-44878)

Tags

Sightings

Nomenclature

Related by attack behaviour