Bug 2220812 (CVE-2023-36665) - CVE-2023-36665 protobufjs: prototype pollution using user-controlled protobuf message
Summary: CVE-2023-36665 protobufjs: prototype pollution using user-controlled protobuf...
Keywords:
Status: NEW
Alias: CVE-2023-36665
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On: 2220815 2220816 2220830 2220831 2220832
Blocks: 2220817
TreeView+ depends on / blocked
 
Reported: 2023-07-06 06:12 UTC by TEJ RATHI
Modified: 2024-07-18 13:23 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description TEJ RATHI 2023-07-06 06:12:07 UTC
protobuf.js (aka protobufjs) 6.10.0 through 7.x before 7.2.4 allows Prototype Pollution, a different vulnerability than CVE-2022-25878. A user-controlled protobuf message can be used by an attacker to pollute the prototype of Object.prototype by adding and overwriting its data and functions. 

Exploitation can involve: 
(1) using the function parse to parse protobuf messages on the fly, 
(2) loading .proto files by using load/loadSync functions, or 
(3) providing untrusted input to the functions ReflectionObject.setParsedOption and util.setProperty. NOTE: this CVE Record is about "Object.constructor.prototype.<new-property> = ...;" whereas CVE-2022-25878 was about "Object.__proto__.<new-property> = ...;" instead.

https://github.com/protobufjs/protobuf.js/commit/e66379f451b0393c27d87b37fa7d271619e16b0d
https://github.com/protobufjs/protobuf.js/compare/protobufjs-v7.2.3...protobufjs-v7.2.4
https://github.com/protobufjs/protobuf.js/pull/1899
https://www.code-intelligence.com/blog/cve-protobufjs-prototype-pollution-cve-2023-36665
https://github.com/protobufjs/protobuf.js/releases/tag/protobufjs-v7.2.4

Comment 3 TEJ RATHI 2023-07-06 07:58:34 UTC
Created cockatrice tracking bugs for this issue:

Affects: fedora-37 [bug 2220832]


Note You need to log in before you can comment on or make changes to this bug.