CVE-2021-42694

{"id": "CVE-2021-42694", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 5.1, "accessVector": "NETWORK", "vectorString": "AV:N/AC:H/Au:N/C:P/I:P/A:P", "authentication": "NONE", "integrityImpact": "PARTIAL", "accessComplexity": "HIGH", "availabilityImpact": "PARTIAL", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 6.4, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 4.9, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": true}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 8.3, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 6.0, "exploitabilityScore": 1.6}]}, "published": "2021-11-01T04:15:08.043", "references": [{"url": "http://www.openwall.com/lists/oss-security/2021/11/01/1", "tags": ["Mailing List", "Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "http://www.openwall.com/lists/oss-security/2021/11/01/6", "tags": ["Mailing List", "Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "http://www.unicode.org/versions/Unicode14.0.0/", "tags": ["Release Notes", "Vendor Advisory"], "source": "cve@mitre.org"}, {"url": "https://cwe.mitre.org/data/definitions/1007.html", "tags": ["Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://security.gentoo.org/glsa/202210-09", "tags": ["Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://trojansource.codes", "tags": ["Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://www.kb.cert.org/vuls/id/999008", "tags": ["Third Party Advisory", "US Government Resource"], "source": "cve@mitre.org"}, {"url": "https://www.scyon.nl/post/trojans-in-your-source-code", "tags": ["Exploit", "Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://www.unicode.org/reports/tr36/", "tags": ["Technical Description", "Vendor Advisory"], "source": "cve@mitre.org"}, {"url": "https://www.unicode.org/reports/tr39/", "tags": ["Technical Description", "Vendor Advisory"], "source": "cve@mitre.org"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "NVD-CWE-Other"}]}], "descriptions": [{"lang": "en", "value": "An issue was discovered in the character definitions of the Unicode Specification through 14.0. The specification allows an adversary to produce source code identifiers such as function names using homoglyphs that render visually identical to a target identifier. Adversaries can leverage this to inject code via adversarial identifier definitions in upstream software dependencies invoked deceptively in downstream software. NOTE: the Unicode Consortium offers the following alternative approach to presenting this concern. An issue is noted in the nature of international text that can affect applications that implement support for The Unicode Standard (all versions). Unless mitigated, an adversary could produce source code identifiers using homoglyph characters that render visually identical to but are distinct from a target identifier. In this way, an adversary could inject adversarial identifier definitions in upstream software that are not detected by human reviewers and are invoked deceptively in downstream software. The Unicode Consortium has documented this class of security vulnerability in its document, Unicode Technical Report #36, Unicode Security Considerations. The Unicode Consortium also provides guidance on mitigations for this class of issues in Unicode Technical Standard #39, Unicode Security Mechanisms."}, {"lang": "es", "value": "** EN DISPUTA ** Se ha detectado un problema en las definiciones de caracteres de la especificaci\u00f3n Unicode hasta la versi\u00f3n 14.0. La especificaci\u00f3n permite que un adversario produzca identificadores de c\u00f3digo fuente, tales como nombres de funciones, utilizando homoglifos que son visualmente id\u00e9nticos a un identificador de destino. Los adversarios pueden aprovechar esto para inyectar c\u00f3digo a trav\u00e9s de definiciones de identificadores adversos en dependencias de software ascendente invocadas de forma enga\u00f1osa en software descendente. NOTA: el Consorcio Unicode ofrece el siguiente enfoque alternativo para presentar este problema. Se observa un problema en la naturaleza del texto internacional que puede afectar a las aplicaciones que implementan la compatibilidad con el est\u00e1ndar Unicode (todas las versiones). A menos que se mitigue, un adversario podr\u00eda producir identificadores de c\u00f3digo fuente utilizando caracteres homog\u00e9neos que son visualmente id\u00e9nticos pero distintos a un identificador de destino. De esta manera, un adversario podr\u00eda inyectar definiciones de identificadores adversos en el software de entrada que no son detectados por los revisores humanos y son invocados enga\u00f1osamente en el software de salida. El Consorcio Unicode ha documentado esta clase de vulnerabilidad de seguridad en su documento, Informe T\u00e9cnico de Unicode #36, Consideraciones de Seguridad de Unicode. El Consorcio Unicode tambi\u00e9n proporciona orientaci\u00f3n sobre las mitigaciones para esta clase de problemas en la Norma T\u00e9cnica de Unicode #39, Mecanismos de Seguridad de Unicode."}], "lastModified": "2024-04-11T01:13:07.617", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:unicode:unicode:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "FAB64729-AF3D-46C0-B3B9-1588B46C524A", "versionEndExcluding": "14.0.0"}], "operator": "OR"}]}], "sourceIdentifier": "cve@mitre.org"}