Security readout for executives and security teams
Plain-English summary
CVE-2021-23624 affects the JavaScript package dotty before 0.1.2. If an application lets users influence dotty path keys, array-form keys can bypass an earlier prototype-pollution fix and potentially affect confidentiality, integrity, and availability at low levels.
Executive priority
Treat as a normal dependency remediation item, not an emergency, unless dotty is exposed to untrusted path input in a business-critical service. Prioritize inventory and upgrade validation.
Technical view
The issue is a type confusion prototype-pollution bypass of CVE-2021-25912 in dotty. The CVE states user-provided keys in the path parameter, when arrays, can bypass prior protections. CVSS 3.1 is 5.6 with network reachability, high attack complexity, no privileges, and no user interaction.
Likely exposure
Exposure is most likely in Node.js or JavaScript applications depending on dotty before 0.1.2, especially where untrusted input can reach dotty path parameters. The bundle does not identify affected applications beyond dotty itself.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. CVSS marks exploit code maturity as proof-of-concept, but no cited source here establishes real-world exploitation.
Researcher notes
Key research focus is whether array-typed path keys can cross trust boundaries in local call sites. Avoid assuming exposure from package presence alone; exploitability depends on how applications pass path data into dotty.
Mitigation direction
- Upgrade dotty to 0.1.2 or later where used.
- Identify and update transitive dependencies that include vulnerable dotty versions.
- Restrict untrusted input from reaching dotty path parameters.
- Check vendor and package maintainer guidance before relying on compensating controls.
Validation and detection
- Review package-lock, yarn.lock, pnpm-lock, or SBOM entries for dotty versions.
- Trace application call sites that pass user-controlled path data into dotty.
- Confirm dependency scanners no longer flag CVE-2021-23624 after updates.
- Regression test code paths that read or write nested object properties.
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.
CVE-2021-23624 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
- 5.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RC:C
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:H/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RC:C2.23.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.6MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RC:C
Source materials
- CVE List V5 sourceCVE List V5
- https://snyk.io/vuln/SNYK-JS-DOTTY-1577292CVE reference · x_refsource_MISC
- https://github.com/deoxxa/dotty/commit/88f61860dcc274a07a263c32cbe9d44c24ef02d7CVE 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.