fkie_cve-2025-27371
Vulnerability from fkie_nvd
Published
2025-03-03 18:15
Modified
2025-04-25 15:15
Severity ?
6.9 (Medium) - CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N
Summary
In certain IETF OAuth 2.0-related specifications, when the JSON Web Token Profile for OAuth 2.0 Client Authentication mechanism is used, there are ambiguities in the audience values of JWTs sent to authorization servers. The affected RFCs may include RFC 7523, and also RFC 7521, RFC 7522, RFC 9101 (JAR), and RFC 9126 (PAR).
References
cve@mitre.orghttps://eprint.iacr.org/2025/629
cve@mitre.orghttps://github.com/OWASP/ASVS/issues/2678
cve@mitre.orghttps://openid.net/notice-of-a-security-vulnerability/
cve@mitre.orghttps://openid.net/wp-content/uploads/2025/01/OIDF-Responsible-Disclosure-Notice-on-Security-Vulnerability-for-private_key_jwt.pdf
cve@mitre.orghttps://talks.secworkshop.events/osw2025/talk/R8D9BS/
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In certain IETF OAuth 2.0-related specifications, when the JSON Web Token Profile for OAuth 2.0 Client Authentication mechanism is used, there are ambiguities in the audience values of JWTs sent to authorization servers. The affected RFCs may include RFC 7523, and also RFC 7521, RFC 7522, RFC 9101 (JAR), and RFC 9126 (PAR)."
    },
    {
      "lang": "es",
      "value": "En ciertas especificaciones relacionadas con OAuth 2.0 de IETF, cuando se utiliza el mecanismo de autenticaci\u00f3n de cliente JSON Web Token Profile for OAuth 2.0, existen ambig\u00fcedades en los valores de audiencia de los JWT enviados a los servidores de autorizaci\u00f3n. Las RFC afectadas pueden incluir RFC 7523, y tambi\u00e9n RFC 7521, RFC 7522, RFC 9101 (JAR) y RFC 9126 (PAR)."
    }
  ],
  "id": "CVE-2025-27371",
  "lastModified": "2025-04-25T15:15:35.937",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 6.9,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "LOW",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "CHANGED",
          "userInteraction": "REQUIRED",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 1.6,
        "impactScore": 4.7,
        "source": "cve@mitre.org",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-03-03T18:15:40.850",
  "references": [
    {
      "source": "cve@mitre.org",
      "url": "https://eprint.iacr.org/2025/629"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://github.com/OWASP/ASVS/issues/2678"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://openid.net/notice-of-a-security-vulnerability/"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://openid.net/wp-content/uploads/2025/01/OIDF-Responsible-Disclosure-Notice-on-Security-Vulnerability-for-private_key_jwt.pdf"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://talks.secworkshop.events/osw2025/talk/R8D9BS/"
    }
  ],
  "sourceIdentifier": "cve@mitre.org",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-305"
        }
      ],
      "source": "cve@mitre.org",
      "type": "Secondary"
    }
  ]
}


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.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • 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.