-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[BUG] CVE-2025-0665 #35781
Comments
Hi @shiftie |
Hi B-Mahdj! We scanned using Wiz. |
Can you re-run the scan but this time on the latest-full image (https://hub.docker.com/layers/datadog/agent/latest-full/images/sha256-fbd1bea6598316367591f8a1ac65242afddec4225e945b43182ea0a8869d68a0) please @shiftie ? I'm trying to see if the vulnerability is on a specific image. |
i'm sorry i can't scan arbitrary images, we're scanning images in use only (latest tag only) :/ but essentially if you can check curl version in your container, it should be 8.12.0 or higher to fix the vuln. |
What is strange is that there is a full-upgrade later on the Dockerfile that shouldn't allow curl to be outdated datadog-agent/Dockerfiles/agent/Dockerfile Line 121 in 6b94a52
And when installing curl, there is no specific version that are required
My guess would be that maybe the repository from which curl is installed has not been updated yet ? |
Update : I tried to update the curl package inside of the container and the version downloaded was still 8.11 I think there is a repository issue / still not updated. |
Hi @shiftie, Datadog has reviewed CVE-2025-0665 and agrees with the Low severity rating that have been given by Curl.se and Ubuntu for this vulnerability. Within the context of the Datadog Agent standard configuration, it does not accept inbound network connections that would warrant a higher risk for this issue. Datadog will however be bumping the curl version included in the Agent v7.65 release, which is expected in the next couple weeks. |
Agent Environment
latest tagged Docker image (
sha256:766d72655ef255954c9e738aca2023e64e9cf823fee4fb2e79ff3617f0372b03
atm)Describe what happened:
critical level vulnerability detected on CURL binary in the image:
Describe what you expected:
CURL patched to remove the vulnerability.
Maybe here?
Steps to reproduce the issue:
Scan latest image.
Additional environment details (Operating System, Cloud provider, etc):
Not applicable.
The text was updated successfully, but these errors were encountered: