Harden property accessors against untrusted keys#6040
Merged
dylans merged 2 commits intoianstormtaylor:mainfrom Apr 2, 2026
Merged
Harden property accessors against untrusted keys#6040dylans merged 2 commits intoianstormtaylor:mainfrom
dylans merged 2 commits intoianstormtaylor:mainfrom
Conversation
🦋 Changeset detectedLatest commit: 2e03e4b The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
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 |
Contributor
|
@codex review (just trying) |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 778fbb2692
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
dylans
approved these changes
Apr 2, 2026
This was referenced Apr 2, 2026
5 tasks
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.
Description
It's sometimes possible to cause mischief in JavaScript by supplying unexpected keys to square bracket property accessors. These unexpected keys can come from unexpected places. For example,
path.lengthmight be a non-number if a user is able to supply a path of{ length: 'Untrusted value' }as part of JSON input, such as serialised operations.I've gone through and hardened every property accessor I could find where it's remotely possible that an untrusted key might be used with harmful consequences.
As part of this, I've banned
set_nodeoperations from shadowing any property on the Object prototype (e.g.__proto__,toString,hasOwnProperty), since overwriting these default properties may cause unexpected behaviour.The list of banned properties is currently:
toString,toLocaleString,valueOf,hasOwnProperty,isPrototypeOf,propertyIsEnumerable,__defineGetter__,__defineSetter__,__lookupGetter__,__lookupSetter__,__proto__,constructor. This list is subject to change automatically as new properties are added toObject.prototype, but I think the risk of a collision between a future prototype property and a genuine user-supplied property name is very small.Checks
yarn test.yarn lint. (Fix errors withyarn fix.)yarn start.)yarn changeset add.)