Security readout for executives and security teams
Plain-English summary
This issue lets misleading Unicode direction markers make Dart source code look harmless during review while compiling differently. The business risk is a source-code trust problem: a malicious contributor could hide behavior that changes program integrity or availability.
Executive priority
Treat as moderate priority. It is not a remote takeover issue, but it can undermine code review and supply-chain assurance where Dart code is accepted from multiple contributors.
Technical view
CVE-2021-22567 affects Google Dart SDK, with versions unspecified in the provided record. Bidirectional Unicode text can alter how code is displayed versus compiled. CVSS 3.1 is 4.6 medium: network vector, low complexity, low privileges, user interaction required, low integrity and availability impact.
Likely exposure
Exposure is most likely in organizations compiling Dart code with affected SDK versions and accepting source contributions or dependencies that may contain bidirectional Unicode controls. The provided sources do not identify exact affected or fixed versions.
Exploitation context
The bundle does not show CISA KEV listing or confirmed active exploitation. The credible scenario is code-review deception by someone able to submit Dart source for review, merge, or dependency inclusion.
Researcher notes
Evidence is limited to the CVE description, CVSS metadata, Dart SDK changelog reference, and a Dart SDK commit reference. Exact affected and fixed versions are not present in the supplied bundle, so version conclusions require vendor confirmation.
Mitigation direction
- Review Dart SDK changelog and vendor references for fixed release guidance.
- Upgrade Dart SDK in CI and developer environments when the fixed release is identified.
- Add review or lint checks that flag bidirectional Unicode control characters in source.
- Tighten contribution review for unusual Unicode in Dart source files.
Validation and detection
- Inventory Dart SDK versions used by developers, build images, and CI pipelines.
- Compare inventoried versions with the Dart changelog and referenced fix commit.
- Inspect Dart source for bidirectional Unicode control characters.
- Confirm code review tooling visibly warns on suspicious Unicode controls.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-22567 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L2.12.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.6MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/dart-lang/sdk/blob/main/CHANGELOG.mdCVE reference · x_refsource_MISC
- https://github.com/dart-lang/sdk/commit/52519ea8eb4780c468c4c2ed00e7c8046ccfed41CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.