[Aikido] Fix security issue in protobufjs via minor version upgrade from 7.5.3 to 7.6.0#23
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Upgrade protobufjs to fix critical code injection vulnerability in protobuf type field compilation and medium-severity prototype pollution in message initialization.
✅ 2 CVEs resolved by this upgrade, including 1 critical 🚨 CVE
This PR will resolve the following CVEs:
protofield, enabling prototype chain manipulation and unintended property injection across the application.🤖 Remediation details
Fix transitive
protobufjsvulnerability via lockfile refreshShort summary
This PR remediates two security vulnerabilities in the transitive dependency
protobufjs(one critical, one medium severity). The vulnerable version (7.5.3) was resolved inpackage-lock.jsonas a transitive dependency pulled in by the direct dependency@gldywn/crlset.js. No changes topackage.jsonwere required; onlypackage-lock.jsonwas updated.protobufjs
protobufjs@7.5.3was resolved transitively via@gldywn/crlset.js@1.2.0, which declares it as^7.5.3. Because the patched minimum (7.5.5) falls within that existing caret range, no manifest edit or override was needed — runningnpm update protobufjs --package-lock-onlywas sufficient to advance the lockfile-resolved version to7.6.0, satisfying both patched version specs (≥ 7.5.5for the 7.x line). The fix addresses a critical CVE and a medium-severity advisory present in allprotobufjsversions below7.5.5.Version changes
protobufjs7.5.37.6.0@gldywn/crlset.js@1.2.0(^7.5.3), lockfile-only refresh