CVE-2021-42574

Public Exploit

Description

An issue was discovered in the Bidirectional Algorithm in the Unicode Specification through 14.0. It permits the visual reordering of characters via control sequences, which can be used to craft source code that renders different logic than the logical ordering of tokens ingested by compilers and interpreters. Adversaries can leverage this to encode source code for compilers accepting Unicode such that targeted vulnerabilities are introduced invisibly to human reviewers. 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 and the Unicode Bidirectional Algorithm (all versions). Due to text display behavior when text includes left-to-right and right-to-left characters, the visual order of tokens may be different from their logical order. Additionally, control characters needed to fully support the requirements of bidirectional text can further obfuscate the logical order of tokens. Unless mitigated, an adversary could craft source code such that the ordering of tokens perceived by human reviewers does not match what will be processed by a compiler/interpreter/etc. The Unicode Consortium has documented this class of 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, and in Unicode Standard Annex #31, Unicode Identifier and Pattern Syntax. Also, the BIDI specification allows applications to tailor the implementation in ways that can mitigate misleading visual reordering in program text; see HL4 in Unicode Standard Annex #9, Unicode Bidirectional Algorithm.

Category

8.3
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 22.25% Top 5%
Vendor Advisory fedoraproject.org Vendor Advisory fedoraproject.org Vendor Advisory fedoraproject.org Vendor Advisory gentoo.org Vendor Advisory unicode.org Vendor Advisory unicode.org Vendor Advisory unicode.org Vendor Advisory unicode.org Vendor Advisory unicode.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
http://www.unicode.org/versions/Unicode14.0.0/ release notes vendor advisory
https://trojansource.codes exploit third party advisory technical description
http://www.openwall.com/lists/oss-security/2021/11/01/1 mailing list mitigation exploit third party advisory
http://www.openwall.com/lists/oss-security/2021/11/01/4 mailing list exploit third party advisory
http://www.openwall.com/lists/oss-security/2021/11/01/6 third party advisory mailing list
http://www.openwall.com/lists/oss-security/2021/11/01/5 third party advisory mailing list
http://www.openwall.com/lists/oss-security/2021/11/02/10 mailing list
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QUPA37D57VPTDLSXOOGF4UXUEADOC4PQ/ vendor advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LQNTFF24ROHLVPLUOEISBN3F7QM27L4U/ vendor advisory
https://www.kb.cert.org/vuls/id/999008 third party advisory us government resource
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IH2RG5YTR6ZZOLUV3EUPZEIJR7XHJLVD/ vendor advisory
https://www.scyon.nl/post/trojans-in-your-source-code exploit third party advisory mitigation
https://www.unicode.org/reports/tr36/ technical description vendor advisory
https://www.unicode.org/reports/tr39/ technical description vendor advisory
https://www.unicode.org/reports/tr31/ technical description vendor advisory
https://www.unicode.org/reports/tr9/tr9-44.html#HL4 technical description vendor advisory
https://www.starwindsoftware.com/security/sw-20220804-0002/ third party advisory
https://security.gentoo.org/glsa/202210-09 third party advisory vendor advisory

Frequently Asked Questions

What is the severity of CVE-2021-42574?
CVE-2021-42574 has been scored as a high severity vulnerability.
How to fix CVE-2021-42574?
To fix CVE-2021-42574, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2021-42574 being actively exploited in the wild?
It is possible that CVE-2021-42574 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~22% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.