Remove libcurl dependency #677
Open
Conversation
This file contains 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
cURL is purged after usage inside the Dockerfile, but the libcurl dependency was left. Container security scanners find CVEs related to cURL (like CVE-2023-38545). By adding `--autoremove` option to the purge command, the dependencies will also get purged.
|
|
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.
Summary
When building the Kong docker image for Ubuntu, some cURL/libcurl related CVE findings occur in the image when perfoming a container security scan.
cURL is purged after usage inside the Dockerfile, but the libcurl dependency is left. Container security scanners find CVEs related to cURL (like CVE-2023-38545). By adding
--autoremoveoption to the purge command, the libcurl dependency will also get purged.Manuel Gugel <manuel_sebastian.gugel@mercedes-benz.com>, Mercedes-Benz Tech Innovation GmbH, imprint