Is CVE-2020-28273 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2020-28273 being exploited in the wild.

How severe is CVE-2020-28273?

Low severity, with a CVSS score of 3.1, published 19 March 2021.

Which products and versions are affected?

set-in (npm) SEMVER:introduced=0,fixed=2.0.1.

Is there a fix for CVE-2020-28273?

Yes. set-in (npm): upgrade to 2.0.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2020-28273 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2020-28273?

Check whether you run set-in (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.

CVE-2020-28273: set-in prototype pollution

CVE-2020-28273 · Severity: low · CVSS 3.1 · Published 2021-03-19

set-in is a popular JavaScript utility library for manipulating nested object properties. A prototype pollution vulnerability in versions prior to 2.0.1 allows attackers to inject malicious properties into JavaScript object prototypes, potentially causing denial of service or remote code execution in applications that use this library.

Technologies: set-in (npm). Vendors: npm.

Quick answers

Is CVE-2020-28273 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2020-28273 being exploited in the wild.
How severe is CVE-2020-28273?: Low severity, with a CVSS score of 3.1, published 19 March 2021.
Which products and versions are affected?: set-in (npm) SEMVER:introduced=0,fixed=2.0.1.
Is there a fix for CVE-2020-28273?: Yes. set-in (npm): upgrade to 2.0.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2020-28273 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2020-28273?: Check whether you run set-in (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

set-in (npm): upgrade to 2.0.1 or later
```
npm install set-in@2.0.1
```

Technical details

The vulnerability is a prototype pollution flaw (CWE-1321) in the set-in library versions 1.0.0 through 2.0.0, which fails to properly sanitize user-supplied input when setting object properties. An attacker can exploit this by injecting specially crafted property names (such as "__proto__" or "constructor.prototype") to pollute the Object prototype, affecting all objects in the application. No authentication or user interaction is required; the attack is triggered through direct manipulation of the library's API with malicious input. This can lead to denial of service (application crash) or potentially remote code execution depending on how the application uses the polluted prototype. The vulnerability was patched in version 2.0.1.

Affected products

ahdinosaur set-in 1.0.0 through 2.0.0

Identifiers

CVE-2020-28273
GHSA-qr4p-c9wr-phr6

Timeline

2020-12-02: disclosed: CVE-2020-28273 published on NVD
2020: patched: Fix committed to repository
2021-03-19: advisory: GHSA-qr4p-c9wr-phr6 published

References

https://github.com/ahdinosaur/set-in/commit/e431effa00195a6f06b111e09733cd1445a91a88

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.