Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Update dependency mixme to 0.5.2 [SECURITY] - abandoned - autoclosed #32

Closed
wants to merge 8 commits into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 9, 2021

Mend Renovate

This PR contains the following updates:

Package Change
mixme 0.3.5 -> 0.5.2

GitHub Vulnerability Alerts

CVE-2021-29491

Impact

In Node.js mixme v0.5.0, an attacker can add or alter properties of an object via 'proto' through the mutate() and merge() functions. The polluted attribute will be directly assigned to every object in the program. This will put the availability of the program at risk causing a potential denial of service (DoS).

Patches

The problem is corrected starting with version 0.5.1.

References

Issue: https://github.com/adaltas/node-mixme/issues/1
Commit: adaltas/node-mixme@cfd5fbf

GHSA-84p7-fh9c-6g8h

Impact

When copying properties from a source object to a target object, the target object can gain access to certain properties of the source object and modify their content.

Patches

The problem was patch with a more agressive discovery of secured properties to filter out.

CVE-2021-28860

Node.js mixme 0.5.0, an attacker can add or alter properties of an object via 'proto' through the mutate() and merge() functions. The polluted attribute will be directly assigned to every object in the program. This will put the availability of the program at risk causing a potential denial of service (DoS).


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title Update dependency mixme to 0.5.1 [SECURITY] Update dependency mixme to 0.5.2 [SECURITY] Oct 18, 2021
@renovate renovate bot force-pushed the renovate/npm-mixme-vulnerability branch from 51d2a19 to f20d481 Compare March 7, 2022 08:42
@renovate renovate bot changed the title Update dependency mixme to 0.5.2 [SECURITY] Update dependency mixme to 0.5.2 [SECURITY] - abandoned Mar 24, 2023
@renovate
Copy link
Author

renovate bot commented Mar 24, 2023

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

@renovate renovate bot changed the title Update dependency mixme to 0.5.2 [SECURITY] - abandoned Update dependency mixme to 0.5.2 [SECURITY] - abandoned - autoclosed Apr 4, 2023
@renovate renovate bot closed this Apr 4, 2023
@renovate renovate bot deleted the renovate/npm-mixme-vulnerability branch April 4, 2023 01:24
@renovate renovate bot changed the title Update dependency mixme to 0.5.2 [SECURITY] - abandoned - autoclosed Update dependency mixme to 0.5.2 [SECURITY] - abandoned Apr 4, 2023
@renovate renovate bot reopened this Apr 4, 2023
@renovate renovate bot restored the renovate/npm-mixme-vulnerability branch April 4, 2023 09:13
@renovate renovate bot changed the title Update dependency mixme to 0.5.2 [SECURITY] - abandoned Update dependency mixme to 0.5.2 [SECURITY] - abandoned - autoclosed Apr 17, 2023
@renovate renovate bot closed this Apr 17, 2023
@renovate renovate bot deleted the renovate/npm-mixme-vulnerability branch April 17, 2023 09:20
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants