CyberSecBulletin
CVE-2022-25354NVD status: Modified

set-in: Improperly Controlled Modification of Object Prototype Attributes

CVE-2022-25354 is a critical-severity improperly controlled modification of object prototype attributes vulnerability in set-in, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 2.0.3 as the first without the flaw, so updating set-in to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.93% chance of exploitation within 30 days, higher than 80% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update set-in to 2.0.3 or a later version.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Set-inset-inbefore 2.0.32.0.3

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.6HighCNA (snyk.io)
CVSS 3.19.8CriticalNVD
CVSS 2.07.5HighNVD

Official description

The package set-in before 2.0.3 are vulnerable to Prototype Pollution via the setIn method, as it allows an attacker to merge object prototypes into it. **Note:** This vulnerability derives from an incomplete fix of [CVE-2020-28273](https://security.snyk.io/vuln/SNYK-JS-SETIN-1048049)

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improperly Controlled Modification of Object Prototype Attributes

The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

How developers prevent this class of flaw

  • By freezing the object prototype first (for example, Object.freeze(Object.prototype)), modification of the prototype becomes impossible.
  • By blocking modifications of attributes that resolve to object prototype, such as proto or prototype, this weakness can be mitigated.
  • When handling untrusted objects, validating using a schema can be used.

More Improperly Controlled Modification of Object Prototype Attributes vulnerabilities (CWE-1321)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Recent Improperly Controlled Modification of Object Prototype Attributes vulnerabilities

Spotted an error? Tell us.