Skip to content

GHSA-g954-5hwp-pp24 CVE-2022-25878

Prototype Pollution in protobufjs

High npm
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
2.33%
Chance of exploitation in the next 30 days. Higher than 83.53% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-1321 Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Fix
6.11.3
Upgrade protobufjs to this version or later

Description

The package protobufjs is vulnerable to Prototype Pollution, which can allow an attacker to add/modify properties of the Object.prototype. Versions after and including 6.10.0 until 6.10.3 and after and including 6.11.0 until 6.11.3 are vulnerable.

This vulnerability can occur in multiple ways:

  1. by providing untrusted user input to util.setProperty or to ReflectionObject.setParsedOption functions
  2. by parsing/loading .proto files

Affected versions

npm

PackageVulnerableFixed in
protobufjs
>= 6.11.0, < 6.11.3
6.11.3
protobufjs
>= 6.10.0, < 6.10.3
6.10.3

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

protobufjs npm → 6.11.3

npm
npm install protobufjs@6.11.3
yarn
yarn add protobufjs@6.11.3
pnpm
pnpm add protobufjs@6.11.3

Severity breakdown

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Weakness

CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

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 to prevent it
  • Implementation: By freezing the object prototype first (for example, Object.freeze(Object.prototype)), modification of the prototype becomes impossible.
  • Architecture and Design: By blocking modifications of attributes that resolve to object prototype, such as proto or prototype, this weakness can be mitigated.
  • Implementation: When handling untrusted objects, validating using a schema can be used.
  • Implementation: By using an object without prototypes (via Object.create(null) ), adding object prototype attributes by accessing the prototype via the special attributes becomes impossible, mitigating this weakness.
  • Implementation: Map can be used instead of objects in most cases. If Map methods are used instead of object attributes, it is not possible to access the object prototype or modify it.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-j3f2-48v5-ccww
protobufjs: Denial of Service via infinite loop in .proto option parsing
High Also affects protobufjs
GHSA-jfj6-75fj-8934
protobufjs: Text Format string map parsing can mutate returned map object prototype
Medium Also affects protobufjs
GHSA-94rc-8x27-4472
protobufjs: Memory amplification from preserved unknown fields in binary decode
Medium Also affects protobufjs
GHSA-wcpc-wj8m-hjx6
protobufjs: Denial of service through unbounded Any expansion during JSON conversion
High Also affects protobufjs
GHSA-f38q-mgvj-vph7
protobufjs : Schema-derived names can shadow runtime-significant properties
Medium Also affects protobufjs
GHSA-jggg-4jg4-v7c6
protobufjs: Denial of Service via unbounded recursive JSON descriptor expansion
High Also affects protobufjs
GHSA-2pr8-phx7-x9h3
protobuf.js: Denial of service from crafted field names in generated code
Medium Also affects protobufjs
GHSA-66ff-xgx4-vchm
protobuf.js: Code injection through bytes field defaults in generated toObject code
High Also affects protobufjs
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor