CVE-2015-9235

In jsonwebtoken node module before 4.2.2 it is possible for an attacker to bypass verification when a token digitally signed with an asymmetric key (RS/ES family) of algorithms but instead the attacker send a token digitally signed with a symmetric algorithm (HS* family).

CVSS v3 9.8 CRITICAL
CVSS v2.0 7.5 HIGH

9.8^/10

CVSS v3 : CRITICAL

Vector : AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitability : 3.9 / Impact : 5.9

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

7.5^/10

CVSS v2.0 : HIGH

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

Exploitability : 10.0 / Impact : 6.4

Access Vector NETWORK

Access Complexity LOW

Authentication NONE

Confidentiality Impact PARTIAL

Integrity Impact PARTIAL

Availability Impact PARTIAL

References

Link	Resource
https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/	Broken Link Vendor Advisory
https://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687	Patch Third Party Advisory
https://nodesecurity.io/advisories/17	Third Party Advisory
https://www.timmclean.net/2015/02/25/jwt-alg-none.html	Exploit Third Party Advisory

Configurations

Configuration 1 (hide)

cpe:2.3:a:auth0:jsonwebtoken:*:*:*:*:*:node.js:*:*

History

No history.

Information

Published : 2018-05-29 20:29

Updated : 2023-12-10 12:30

NVD link : CVE-2015-9235

Mitre link : CVE-2015-9235

CVE.ORG link : CVE-2015-9235

JSON object : View

Products Affected

auth0

jsonwebtoken

CWE

CWE-327

Use of a Broken or Risky Cryptographic Algorithm

CWE-20

Improper Input Validation

{"id": "CVE-2015-9235", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 7.5, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:N/C:P/I:P/A:P", "authentication": "NONE", "integrityImpact": "PARTIAL", "accessComplexity": "LOW", "availabilityImpact": "PARTIAL", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 6.4, "baseSeverity": "HIGH", "obtainAllPrivilege": false, "exploitabilityScore": 10.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV30": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.0", "baseScore": 9.8, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 3.9}]}, "published": "2018-05-29T20:29:00.330", "references": [{"url": "https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/", "tags": ["Broken Link", "Vendor Advisory"], "source": "support@hackerone.com"}, {"url": "https://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687", "tags": ["Patch", "Third Party Advisory"], "source": "support@hackerone.com"}, {"url": "https://nodesecurity.io/advisories/17", "tags": ["Third Party Advisory"], "source": "support@hackerone.com"}, {"url": "https://www.timmclean.net/2015/02/25/jwt-alg-none.html", "tags": ["Exploit", "Third Party Advisory"], "source": "support@hackerone.com"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-327"}]}, {"type": "Secondary", "source": "support@hackerone.com", "description": [{"lang": "en", "value": "CWE-20"}]}], "descriptions": [{"lang": "en", "value": "In jsonwebtoken node module before 4.2.2 it is possible for an attacker to bypass verification when a token digitally signed with an asymmetric key (RS/ES family) of algorithms but instead the attacker send a token digitally signed with a symmetric algorithm (HS* family)."}, {"lang": "es", "value": "En el m\u00f3dulo jsonwebtoken node en versiones anteriores a la 4.2.2 es posible que un atacante omita la verificaci\u00f3n cuando un token firmado digitalmente con una clave asim\u00e9trica (familia RS/ES) de algoritmos pero, en su lugar, el atacante env\u00eda un token firmado digitalmente con un algoritmo sim\u00e9trico (familia HS*)."}], "lastModified": "2019-10-09T23:15:57.760", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:auth0:jsonwebtoken:*:*:*:*:*:node.js:*:*", "vulnerable": true, "matchCriteriaId": "D90A8240-8BE4-4F66-A105-1966D8DE336A", "versionEndExcluding": "4.2.2"}], "operator": "OR"}]}], "sourceIdentifier": "support@hackerone.com"}