Repository navigation
Conversation
🦋 Changeset detectedLatest commit: 259a1b2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
@icguner is attempting to deploy a commit to the TooTallNate's Team Team on Vercel. A member of the Team first needs to authorize it. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The
__proto__dictionary-key guard added for CVE-2022-22912 only covers the XML parser. The OpenStep parser (added in 5.0.0) and the binary parser have no such guard, andparse()dispatches to them automatically based on the input shape — soplist.parse(untrusted)is exploitable again even when the caller expects XML.Why
src/parse.tsguards<key>__proto__</key>, but only for XML.parse()routesBuffer/Uint8Array/ArrayBufferandbplist-prefixed strings to the binary parser, and any string starting with{or(to the OpenStep parser. Both assignobj[key] = valuewith no check._is a valid unquoted OpenStep character, so no quoting is needed.bplist00payload whose dict carries a__proto__key reaches the same sink viaparseBinary.Like the original CVE, this replaces the returned object's prototype; it does not reach the global
Object.prototype.Fix
A shared
assertSafeKeyhelper, used by both the OpenStep and binary parsers. It rejects__proto__, and also rejects non-string keys so the check cannot be bypassed by an OpenStep array key( )or a binary key ref that happens to coerce to"__proto__".Tests
Added
__proto__cases totest/parse-openstep.test.tsandtest/parse-binary.test.ts, mirroring the existing XML test attest/parse.test.ts. I was unable to run the suite in my environment, so I'd appreciate CI confirming it.