CVE-2022-36083

{"id": "CVE-2022-36083", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 3.9}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 3.9}]}, "published": "2022-09-07T22:15:08.657", "references": [{"url": "https://github.com/panva/jose/commit/03d6d013bf6e070e85adfe5731f526978e3e8e4d", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/panva/jose/releases/tag/v4.9.2", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/panva/jose/security/advisories/GHSA-jv3g-j58f-9mq9", "tags": ["Exploit", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/panva/jose/commit/03d6d013bf6e070e85adfe5731f526978e3e8e4d", "tags": ["Patch", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/panva/jose/releases/tag/v4.9.2", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/panva/jose/security/advisories/GHSA-jv3g-j58f-9mq9", "tags": ["Exploit", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-400"}]}, {"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-834"}]}], "descriptions": [{"lang": "en", "value": "JOSE is \"JSON Web Almost Everything\" - JWA, JWS, JWE, JWT, JWK, JWKS with no dependencies using runtime's native crypto in Node.js, Browser, Cloudflare Workers, Electron, and Deno. The PBKDF2-based JWE key management algorithms expect a JOSE Header Parameter named `p2c` PBES2 Count, which determines how many PBKDF2 iterations must be executed in order to derive a CEK wrapping key. The purpose of this parameter is to intentionally slow down the key derivation function in order to make password brute-force and dictionary attacks more expensive. This makes the PBES2 algorithms unsuitable for situations where the JWE is coming from an untrusted source: an adversary can intentionally pick an extremely high PBES2 Count value, that will initiate a CPU-bound computation that may take an unreasonable amount of time to finish. Under certain conditions, it is possible to have the user's environment consume unreasonable amount of CPU time. The impact is limited only to users utilizing the JWE decryption APIs with symmetric secrets to decrypt JWEs from untrusted parties who do not limit the accepted JWE Key Management Algorithms (`alg` Header Parameter) using the `keyManagementAlgorithms` (or `algorithms` in v1.x) decryption option or through other means. The `v1.28.2`, `v2.0.6`, `v3.20.4`, and `v4.9.2` releases limit the maximum PBKDF2 iteration count to `10000` by default. It is possible to adjust this limit with a newly introduced `maxPBES2Count` decryption option. If users are unable to upgrade their required library version, they have two options depending on whether they expect to receive JWEs using any of the three PBKDF2-based JWE key management algorithms. They can use the `keyManagementAlgorithms` decryption option to disable accepting PBKDF2 altogether, or they can inspect the JOSE Header prior to using the decryption API and limit the PBKDF2 iteration count (`p2c` Header Parameter)."}, {"lang": "es", "value": "JOSE es \"JSON Web Almost Everything\" - JWA, JWS, JWE, JWT, JWK, JWKS sin dependencias usando la criptograf\u00eda nativa del tiempo de ejecuci\u00f3n en Node.js, Browser, Cloudflare Workers, Electron y Deno. Los algoritmos de administraci\u00f3n de claves JWE basados en PBKDF2 esperan un par\u00e1metro de encabezado JOSE llamado \"p2c\" PBES2 Count, que determina cu\u00e1ntas iteraciones de PBKDF2 deben ejecutarse para derivar una clave envolvente CEK. El prop\u00f3sito de este par\u00e1metro es ralentizar intencionadamente la funci\u00f3n de derivaci\u00f3n de la clave para que los ataques de fuerza bruta y de diccionario a las contrase\u00f1as sean m\u00e1s costosos. Esto hace que los algoritmos PBES2 sean inapropiados para situaciones en las que el JWE procede de una fuente no confiable: un adversario puede elegir intencionadamente un valor de PBES2 Count extremadamente alto, que iniciar\u00e1 un c\u00e1lculo limitado por la CPU que puede tardar una cantidad de tiempo irrazonable en terminar. Bajo determinadas condiciones, es posible que el entorno del usuario consuma una cantidad irrazonable de tiempo de CPU. El impacto es limitado s\u00f3lo a usuarios que usan las API de descifrado de JWE con secretos sim\u00e9tricos para descifrar JWE de partes no confiables que no limitan los algoritmos de administraci\u00f3n de claves JWE aceptados (par\u00e1metro de cabecera \"alg\") usando la opci\u00f3n de descifrado \"keyManagementAlgorithms\" (o \"algorithms\" en v1.x) o por otros medios. Las versiones \"v1.28.2\", \"v2.0.6\", \"v3.20.4\" y \"v4.9.2\" limitan el n\u00famero m\u00e1ximo de iteraciones de PBKDF2 a \"10000\" por defecto. Es posible ajustar este l\u00edmite con la nueva opci\u00f3n de descifrado \"maxPBES2Count\". Si los usuarios no pueden actualizar la versi\u00f3n de la biblioteca que necesitan, se presentan dos opciones dependiendo de si esperan recibir JWEs que usen alguno de los tres algoritmos de administraci\u00f3n de claves JWE basados en PBKDF2. Pueden usar la opci\u00f3n de descifrado \"keyManagementAlgorithms\" para deshabilitar la aceptaci\u00f3n de PBKDF2 por completo, o pueden inspeccionar el encabezado JOSE antes de usar la API de descifrado y limitar el recuento de iteraciones de PBKDF2 (par\u00e1metro de encabezado \"p2c\")"}], "lastModified": "2024-11-21T07:12:20.793", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:jose_project:jose:*:*:*:*:*:node.js:*:*", "vulnerable": true, "matchCriteriaId": "197D5C8A-778B-4EB5-9BD3-6E1E66CEBA64", "versionEndExcluding": "1.28.2", "versionStartIncluding": "1.0.0"}, {"criteria": "cpe:2.3:a:jose_project:jose:*:*:*:*:*:node.js:*:*", "vulnerable": true, "matchCriteriaId": "8C66BF3F-66C3-4D1E-A1FC-8404E9E666C6", "versionEndExcluding": "2.0.6", "versionStartIncluding": "2.0.0"}, {"criteria": "cpe:2.3:a:jose_project:jose:*:*:*:*:*:node.js:*:*", "vulnerable": true, "matchCriteriaId": "99118C06-35D4-47A4-9AEC-5553D6EBCB65", "versionEndExcluding": "3.20.4", "versionStartIncluding": "3.0.0"}, {"criteria": "cpe:2.3:a:jose_project:jose:*:*:*:*:*:node.js:*:*", "vulnerable": true, "matchCriteriaId": "C4DB52C4-C832-40DE-98F8-EED53AA21EFE", "versionEndExcluding": "4.9.2", "versionStartIncluding": "4.0.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}