CVE-2022-23541

{"id": "CVE-2022-23541", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.0, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "LOW", "privilegesRequired": "LOW", "confidentialityImpact": "LOW"}, "impactScore": 3.4, "exploitabilityScore": 1.6}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "LOW", "confidentialityImpact": "LOW"}, "impactScore": 3.4, "exploitabilityScore": 2.8}]}, "published": "2022-12-22T18:15:09.390", "references": [{"url": "https://github.com/auth0/node-jsonwebtoken/commit/e1fa9dcc12054a8681db4e6373da1b30cf7016e3", "tags": ["Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/auth0/node-jsonwebtoken/releases/tag/v9.0.0", "tags": ["Release Notes"], "source": "security-advisories@github.com"}, {"url": "https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-hjrf-2m68-5959", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://security.netapp.com/advisory/ntap-20240621-0007/", "source": "security-advisories@github.com"}, {"url": "https://github.com/auth0/node-jsonwebtoken/commit/e1fa9dcc12054a8681db4e6373da1b30cf7016e3", "tags": ["Patch"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/auth0/node-jsonwebtoken/releases/tag/v9.0.0", "tags": ["Release Notes"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-hjrf-2m68-5959", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://security.netapp.com/advisory/ntap-20240621-0007/", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-287"}, {"lang": "en", "value": "CWE-1259"}]}, {"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "NVD-CWE-Other"}]}], "descriptions": [{"lang": "en", "value": "jsonwebtoken is an implementation of JSON Web Tokens. Versions `<= 8.5.1` of `jsonwebtoken` library can be misconfigured so that passing a poorly implemented key retrieval function referring to the `secretOrPublicKey` argument from the readme link will result in incorrect verification of tokens. There is a possibility of using a different algorithm and key combination in verification, other than the one that was used to sign the tokens. Specifically, tokens signed with an asymmetric public key could be verified with a symmetric HS256 algorithm. This can lead to successful validation of forged tokens. If your application is supporting usage of both symmetric key and asymmetric key in jwt.verify() implementation with the same key retrieval function. This issue has been patched, please update to version 9.0.0."}, {"lang": "es", "value": "jsonwebtoken es una implementaci\u00f3n de JSON Web Tokens. Las versiones `&lt;= 8.5.1` de la librer\u00eda `jsonwebtoken` pueden estar mal configuradas, de modo que pasar una funci\u00f3n de recuperaci\u00f3n de claves mal implementada que haga referencia al argumento `secretOrPublicKey` desde el enlace readme resultar\u00e1 en una verificaci\u00f3n incorrecta de los tokens. Existe la posibilidad de utilizar un algoritmo y una combinaci\u00f3n de claves diferentes en la verificaci\u00f3n, distintos al que se utiliz\u00f3 para firmar los tokens. En concreto, los tokens firmados con una clave p\u00fablica asim\u00e9trica podr\u00edan verificarse con un algoritmo sim\u00e9trico HS256. Esto puede conducir a una validaci\u00f3n exitosa de tokens falsificados. Si su aplicaci\u00f3n admite el uso de claves sim\u00e9tricas y asim\u00e9tricas en la implementaci\u00f3n de jwt.verify() con la misma funci\u00f3n de recuperaci\u00f3n de claves. Este problema ha sido solucionado; actualice a la versi\u00f3n 9.0.0."}], "lastModified": "2024-11-21T06:48:46.580", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:auth0:jsonwebtoken:*:*:*:*:*:node.js:*:*", "vulnerable": true, "matchCriteriaId": "7E5DD3C1-F5DD-4BFD-BCA3-561BC167CB35", "versionEndIncluding": "8.5.1"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}