-
Notifications
You must be signed in to change notification settings - Fork 260
[NPM] [CVE] Resolve CVE-2025-6020 #3763
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
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
Contributor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR addresses CVE-2025-6020 by updating the Ubuntu packages in the Dockerfile to their fixed versions.
- Update the package versions for libpam-modules, libpam-modules-bin, libpam-runtime, and libpam0g in the Dockerfile.
- Ensure the container image is free from the Vulnerability based on the updated dependency versions.
Comments suppressed due to low confidence (1)
npm/linux.Dockerfile:11
- The Dockerfile correctly pins the vulnerable libpam packages to their fixed versions. Double-check that these fixed versions are available for Ubuntu 24.04 to maintain compatibility in future updates.
RUN apt-get update && apt-get install -y libsystemd0=255.4-1ubuntu8.8 libudev1=255.4-1ubuntu8.8 libpam-modules=1.5.3-5ubuntu5.4 libpam-modules-bin=1.5.3-5ubuntu5.4 libpam-runtime=1.5.3-5ubuntu5.4 libpam0g=1.5.3-5ubuntu5.4 iptables ipset ca-certificates && apt-get autoremove -y && apt-get clean
Contributor
Author
|
/azp run Azure Container Networking PR |
Contributor
Author
|
/azp run NPM Conformance Tests |
Contributor
Author
|
/azp run NPM Scale Test |
|
Azure Pipelines successfully started running 1 pipeline(s). |
2 similar comments
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
vakalapa
approved these changes
Jun 27, 2025
This was referenced Jun 27, 2025
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jul 1, 2025
[NPM] [CVE] Resolve CVE-2025-6020 (#3763) fixed cve CVE-2025-6020
NihaNallappagari
pushed a commit
to NihaNallappagari/azure-container-networking
that referenced
this pull request
Sep 4, 2025
[NPM] [CVE] Resolve CVE-2025-6020 (Azure#3763) fixed cve CVE-2025-6020
sivakami-projects
pushed a commit
that referenced
this pull request
Oct 23, 2025
[NPM] [CVE] Resolve CVE-2025-6020 (#3763) fixed cve CVE-2025-6020
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.
Reason for Change:
Resolves
CVE-2025-6020present in the currentv1.6.26version.Issue Fixed:
Requirements:
Notes: