fix: nodejs-mixin-deep: prototype pollution in function mixin-deep#4
Merged
Merged
Conversation
Security fix for CVE-2019-10746: Update mixin-deep from 1.3.1 to 1.3.2 The mixin-deep package was vulnerable to prototype pollution attacks that could allow attackers to modify Object.prototype. This patch update resolves the vulnerability with no breaking changes. - Add mixin-deep@^1.3.2 to dependencies - Update package-lock.json to lock mixin-deep to 1.3.2
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
1 participant
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.
Summary
Automated remediation for trivy finding: nodejs-mixin-deep: prototype pollution in function mixin-deep (CVE-2019-10746)
Vulnerability Details
CVE: CVE-2019-10746
CVSS Score: 9.8 (Critical)
Affected Versions: mixin-deep < 1.3.2 and 2.0.0
Type: Prototype Pollution
The mixin-deep package was vulnerable to prototype pollution attacks in versions before 1.3.2. An attacker could craft a malicious input object with a constructor property to modify Object.prototype, potentially compromising application security and allowing arbitrary property injection.
Changes
Impact
Verification
To verify the fix:
npm install
npm audit --production
Confirm that mixin-deep is at version 1.3.2 or higher:
npm list mixin-deep
Generated by OpenSec remediation agent