CVE-2016-10555

Since "algorithm" isn't enforced in jwt.decode()in jwt-simple 0.3.0 and earlier, a malicious user could choose what algorithm is sent sent to the server. If the server is expecting RSA but is sent HMAC-SHA with RSA's public key, the server will think the public key is actually an HMAC private key. This could be used to forge any data an attacker wants.

CVSS v3 6.5 MEDIUM
CVSS v2.0 4.0 MEDIUM

6.5^/10

CVSS v3 : MEDIUM

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

Exploitability : 2.8 / Impact : 3.6

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact HIGH

Availability Impact NONE

Scope UNCHANGED

4.0^/10

CVSS v2.0 : MEDIUM

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

Exploitability : 8.0 / Impact : 2.9

Access Vector NETWORK

Access Complexity LOW

Authentication SINGLE

Confidentiality Impact NONE

Integrity Impact PARTIAL

Availability Impact NONE

References

Link	Resource
https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/	Broken Link Third Party Advisory
https://github.com/hokaccha/node-jwt-simple/pull/14	Issue Tracking Third Party Advisory
https://github.com/hokaccha/node-jwt-simple/pull/16	Issue Tracking Third Party Advisory
https://nodesecurity.io/advisories/87	Third Party Advisory

Configurations

Configuration 1 (hide)

cpe:2.3:a:jwt-simple_project:jwt-simple:*:*:*:*:*:node.js:*:*

History

No history.

Information

Published : 2018-05-31 20:29

Updated : 2023-12-10 12:30

NVD link : CVE-2016-10555

Mitre link : CVE-2016-10555

CVE.ORG link : CVE-2016-10555

JSON object : View

Products Affected

jwt-simple_project

jwt-simple

CWE

CWE-310

Cryptographic Issues

CWE-20

Improper Input Validation

{"id": "CVE-2016-10555", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 4.0, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:S/C:N/I:P/A:N", "authentication": "SINGLE", "integrityImpact": "PARTIAL", "accessComplexity": "LOW", "availabilityImpact": "NONE", "confidentialityImpact": "NONE"}, "acInsufInfo": false, "impactScore": 2.9, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 8.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV30": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.0", "baseScore": 6.5, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 2.8}]}, "published": "2018-05-31T20:29:02.067", "references": [{"url": "https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/", "tags": ["Broken Link", "Third Party Advisory"], "source": "support@hackerone.com"}, {"url": "https://github.com/hokaccha/node-jwt-simple/pull/14", "tags": ["Issue Tracking", "Third Party Advisory"], "source": "support@hackerone.com"}, {"url": "https://github.com/hokaccha/node-jwt-simple/pull/16", "tags": ["Issue Tracking", "Third Party Advisory"], "source": "support@hackerone.com"}, {"url": "https://nodesecurity.io/advisories/87", "tags": ["Third Party Advisory"], "source": "support@hackerone.com"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-310"}]}, {"type": "Secondary", "source": "support@hackerone.com", "description": [{"lang": "en", "value": "CWE-20"}]}], "descriptions": [{"lang": "en", "value": "Since \"algorithm\" isn't enforced in jwt.decode()in jwt-simple 0.3.0 and earlier, a malicious user could choose what algorithm is sent sent to the server. If the server is expecting RSA but is sent HMAC-SHA with RSA's public key, the server will think the public key is actually an HMAC private key. This could be used to forge any data an attacker wants."}, {"lang": "es", "value": "Como \"algorithm\" no se aplica en jwt.decode() en jwt-simple en versiones 0.3.0 y anteriores, un usuario malicioso podr\u00eda elegir qu\u00e9 algoritmo se env\u00eda al servidor. Si el servidor espera RSA pero recibe HMAC-SHA con la clave p\u00fablica RSA, el servidor pensar\u00e1 que la clave p\u00fablica es, en realidad, una clave privada HMAC. Esto podr\u00eda emplearse para falsificar cualquier dato que quiera un atacante."}], "lastModified": "2019-10-09T23:16:46.277", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:jwt-simple_project:jwt-simple:*:*:*:*:*:node.js:*:*", "vulnerable": true, "matchCriteriaId": "FB7173F7-05CB-4AF1-866F-BC98BB7996DE", "versionEndIncluding": "0.3.0"}], "operator": "OR"}]}], "sourceIdentifier": "support@hackerone.com"}