Security readout for executives and security teams
Plain-English summary
CVE-2019-20149 affects the JavaScript package kind-of v6.0.2. Crafted external input can alter how the library identifies a value’s type, potentially causing application logic to make the wrong security or validation decision. The public sources do not provide severity scoring, broad affected-product details, or evidence of active exploitation.
Executive priority
Treat this as a dependency hygiene and validation-risk item, not an emergency based on current evidence. Prioritize confirmation in software inventories and remediation where kind-of influences authorization, validation, or routing decisions.
Technical view
The reported issue is in ctorName handling in index.js in kind-of v6.0.2. A conflicting property name, demonstrated with constructor.name set to Symbol, can overwrite internal attributes and manipulate type detection results. Impact depends on whether application decisions trust kind-of output for untrusted data.
Likely exposure
Exposure is likely limited to JavaScript projects that directly or transitively depend on kind-of v6.0.2 and run type checks on attacker-controlled objects. The source bundle does not identify affected downstream products or platforms.
Exploitation context
The CVE description references a crafted payload that changes type-detection behavior. No CISA KEV listing or provided source states active exploitation. The available evidence supports a logic-manipulation risk, not confirmed widespread exploitation.
Researcher notes
The public record is sparse: no CVSS, CWE, CPE, or confirmed fixed version is included in the provided bundle. Analysis should focus on dependency reachability and whether manipulated type results can alter meaningful application behavior.
Mitigation direction
- Inventory direct and transitive dependencies for kind-of v6.0.2.
- Check the maintainer issue and pull request for confirmed fix guidance.
- Avoid relying on kind-of results for security decisions on untrusted objects.
- Update or replace the package when a fixed release is confirmed.
- Monitor package advisories and the CVE record for updated severity data.
Validation and detection
- Review lockfiles and SBOMs for kind-of version 6.0.2.
- Identify code paths where untrusted objects reach kind-of checks.
- Confirm scanners or SCA tools detect this CVE in affected dependencies.
- Verify remediation against maintainer guidance before closing the finding.
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-2019-20149 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/jonschlinkert/kind-of/issues/30CVE reference · x_refsource_MISC
- https://github.com/jonschlinkert/kind-of/pull/31CVE 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.