CVE-2022-24584

{"id": "CVE-2022-24584", "cveTags": [{"tags": ["disputed"], "sourceIdentifier": "cve@mitre.org"}], "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}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.5, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/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": "2022-05-11T18:15:23.973", "references": [{"url": "https://demo.yubico.com/otp/verify", "tags": ["Vendor Advisory"], "source": "cve@mitre.org"}, {"url": "https://pastebin.com/7iLR1EbW", "tags": ["Exploit", "Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://pastebin.com/xAh8uV6J", "tags": ["Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://upload.yubico.com/", "tags": ["Vendor Advisory"], "source": "cve@mitre.org"}, {"url": "https://demo.yubico.com/otp/verify", "tags": ["Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://pastebin.com/7iLR1EbW", "tags": ["Exploit", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://pastebin.com/xAh8uV6J", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://upload.yubico.com/", "tags": ["Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-863"}]}], "descriptions": [{"lang": "en", "value": "Incorrect access control in Yubico OTP functionality of the YubiKey hardware tokens along with the Yubico OTP validation server. The Yubico OTP supposedly creates hardware bound second factor credentials. When a user reprograms the OTP functionality by \"writing\" it on a token using the Yubico Personalization Tool, they can then upload the new configuration to Yubicos OTP validation servers. NOTE: the vendor disputes this because there is no way for a YubiKey device to prevent a user from deciding that a secret value, which is imported into the device, should also be stored elsewhere"}, {"lang": "es", "value": "Un control de acceso incorrecto en la funcionalidad Yubico OTP de los tokens de hardware YubiKey junto con el servidor de validaci\u00f3n Yubico OTP. El Yubico OTP supuestamente crea credenciales de segundo factor vinculadas al hardware. Cuando un usuario reprograma la funcionalidad OTP \"escribi\u00e9ndola\" en un token utilizando la herramienta de personalizaci\u00f3n de Yubico, puede cargar la nueva configuraci\u00f3n en los servidores de validaci\u00f3n OTP de Yubico. NOTA: el proveedor discute esto porque no hay forma de que un dispositivo YubiKey evite que un usuario decida que un valor secreto, que se importa en el dispositivo, se almacene tambi\u00e9n en otro lugar"}], "lastModified": "2024-11-21T06:50:41.893", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:yubico:otp:-:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "D7C73007-6D8E-4E61-B193-54A9C83083E0"}], "operator": "OR"}]}], "sourceIdentifier": "cve@mitre.org"}