Nimbus JOSE+JWT before 4.36 proceeds with ECKey construction without ensuring that the public x and y coordinates are on the specified curve

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• connect2id nimbus jose+jwt1.0
• connect2id nimbus jose+jwt1.1
• connect2id nimbus jose+jwt1.10
• connect2id nimbus jose+jwt1.11
• connect2id nimbus jose+jwt1.12
• connect2id nimbus jose+jwt1.2
• connect2id nimbus jose+jwt1.3
• connect2id nimbus jose+jwt1.4
• connect2id nimbus jose+jwt1.5
• connect2id nimbus jose+jwt1.6
• connect2id nimbus jose+jwt1.7
• connect2id nimbus jose+jwt1.8
• connect2id nimbus jose+jwt1.9
• connect2id nimbus jose+jwt1.9.1
• connect2id nimbus jose+jwt2.0
• connect2id nimbus jose+jwt2.0.1
• connect2id nimbus jose+jwt2.1
• connect2id nimbus jose+jwt2.1.1
• connect2id nimbus jose+jwt2.10
• connect2id nimbus jose+jwt2.10.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Other highest-scoring records for the same primary product.

• CVE-2019-17195Connect2id Nimbus JOSE+JWT before v7.9 can throw various uncaught exceptions while parsing a JWT, which could result in an application crash
  42Plan
• CVE-2023-52428In Connect2id Nimbus JOSE+JWT before 9.37.2, an attacker can cause a denial of service (resource consumption) via a large JWE p2c header val
  30Monitor
• CVE-2017-12972In Nimbus JOSE+JWT before 4.39, there is no integer-overflow check when converting length values from bytes to bits, which allows attackers
  30Monitor
• CVE-2017-12973Nimbus JOSE+JWT before 4.39 proceeds improperly after detection of an invalid HMAC in authenticated AES-CBC decryption, which allows attacke
  12Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1const claims = jwt.verify(token, publicKey);

1const claims = jwt.verify(token, publicKey, {2  algorithms: ["RS256"],3  issuer: "https://id.example.com",4  audience: "portal",5});

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.