Quick answers
- Is CVE-2020-8158 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2020-8158 being exploited in the wild.
- How severe is CVE-2020-8158?
- Low severity, with a CVSS score of 3.1, published 7 May 2021.
- Which products and versions are affected?
- typeorm (npm) SEMVER:introduced=0,fixed=0.2.25.
- Is there a fix for CVE-2020-8158?
- Yes. typeorm (npm): upgrade to 0.2.25 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- Am I affected by CVE-2020-8158?
- Check whether you run typeorm (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- typeorm (npm): upgrade to 0.2.25 or later
npm install typeorm@0.2.25
Technical details
This is a prototype pollution vulnerability (CWE-1321, CWE-471) affecting TypeORM versions prior to 0.2.25. The vulnerability allows attackers to add or modify JavaScript object properties through specially crafted input, bypassing normal property constraints. No authentication or user interaction is required; the vulnerability is network-accessible. Successful exploitation can lead to denial of service conditions or facilitate SQL injection attacks against the underlying database. The fix is available in version 0.2.25 and later.
Affected products
- TypeORM TypeORM <0.2.25
Identifiers
- CVE-2020-8158
- GHSA-pf2j-9qmp-jqr2
Timeline
- 2020-09-18: disclosed: NVD published
- 2021-05-07: advisory: GHSA advisory published
- 0.2.25: patched