🚨 [security] [react-web-audio-graph] Update immer: 8.0.0 → 8.0.4 (patch)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ immer (8.0.0 → 8.0.4) · Repo

Security Advisories 🚨

🚨 Prototype Pollution in immer

Overview

Affected versions of immer are vulnerable to Prototype Pollution.

Proof of exploit

const {applyPatches, enablePatches} = require("immer");
enablePatches();
let obj = {};
console.log("Before : " + obj.polluted);
applyPatches({}, [ { op: 'add', path: [ "__proto__", "polluted" ], value: "yes" } ]);
// applyPatches({}, [ { op: 'replace', path: [ "__proto__", "polluted" ], value: "yes" } ]);
console.log("After : " + obj.polluted);

Remediation

Version 8.0.1 contains a fix for this vulnerability, updating is recommended.

Release Notes

8.0.4

8.0.4 (2021-03-19)

Bug Fixes

• make sure isPlainObject checks support objects send accross frames. Fixes #766 / #405 (5ae3547)

8.0.3

8.0.3 (2021-03-18)

Bug Fixes

• new Immer().produce now has the same type as produce. Fixes #749 (f8b77d1)

8.0.2

8.0.2 (2021-03-17)

Bug Fixes

• Add a type-checking fast path for primitive types (#755) (d395efe)
• Ignore equal reference assignments. Fixes #648 (3b4286d)

8.0.1

8.0.1 (2021-01-20)

Bug Fixes

• Fixed security issue #738: prototype pollution possible when applying patches CVE-2020-28477 (da2bd4f)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 35 commits:

• docs: add `break` to `switch` block (#769)
• fix: make sure isPlainObject checks support objects send accross frames. Fixes #766 / #405
• fix: new Immer().produce now has the same type as produce. Fixes #749
• chore: fixes with docusaurus2 setup
• fix: Add a type-checking fast path for primitive types (#755)
• fix: Ignore equal reference assignments. Fixes #648
• Merge branch 'proxy-set-ignore-equality' of https://github.com/smirea/immer into smirea-proxy-set-ignore-equality
• docs: Merge branch 'pvcresin-patch-1'
• Merge branch 'patch-1' of https://github.com/pvcresin/immer into pvcresin-patch-1
• docs: Update to docusaurus 2
• Some theming improvements
• Merge branch 'master' of https://github.com/RDIL/immer into RDIL-master
• Fix typo
• Fix typo
• docs: fix typo, tipes -> tips (#750)
• chore(deps): bump prismjs from 1.21.0 to 1.23.0 in /website (#762)
• Fix installation docs
• Migrate to Docusaurus v2
• Update introduction.md (#745)
• docs: fix typo, INITAL->INITIAL (#741)
• fix: Fixed security issue #738: prototype pollution possible when applying patches CVE-2020-28477
• chore: fix Buffer deprecation warning in test (#706)
• docs: Add referential equality to pitfalls (#731)
• docs: Update current.md (#728)
• docs: add cool-store into built-with.md (#724)
• chore(tests): use UTC date string in tests to be timezone independent (#705)
• chore(comments): update comments (#727)
• chore(docs): Fix typo in pitfalls.md (#729)
• chore(docs): Update example-reducer.md (#734)
• chore(deps): bump dot-prop from 4.2.0 to 4.2.1 in /website (#735)
• chore(deps): bump ini from 1.3.5 to 1.3.7 in /website (#723)
• chore(deps): bump ini from 1.3.5 to 1.3.7 (#722)
• chore(deps): bump highlight.js from 9.15.10 to 9.18.5 in /website (#709)
• chore(deps-dev): bump semantic-release from 17.0.2 to 17.2.3 (#704)
• docs: some refinements on freezing

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)