Skip to content
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

CVE-2024-0056 vulnerability in dotnet v4 image #1029

Open
hctan opened this issue Jan 22, 2024 · 5 comments
Open

CVE-2024-0056 vulnerability in dotnet v4 image #1029

hctan opened this issue Jan 22, 2024 · 5 comments

Comments

@hctan
Copy link

hctan commented Jan 22, 2024

I'm getting security CVE-2024-0056 vulnerability in security scan of the azure function dotnet v4 image. It's due to the image using outdated packages. Would the image be updated soon to use the updated packages?
I think this is similar issue to #1004 (for a different vulnerability)

image

@abegun
Copy link

abegun commented Jan 22, 2024

I accidentally thought I saw this fixed in latest, but am still seeing it in 4.28.3

@hctan
Copy link
Author

hctan commented Jan 23, 2024

I was using the scanner that came with docker desktop, it's using docker Scout, I'm not sure of the version.

If I check in azure portal, under Container Registry -> Microsoft Defender for Cloud. One of the scanner that's marked deprecated "[Deprecated] Azure registry container images should have vulnerabilities resolved (powered by Qualys)" would show the same vulnerability.

However if I check the scan result under "Azure registry container images should have vulnerabilities resolved (powered by Microsoft Defender Vulnerability Management)" then the same image is reported as healthy (no vulnerability).

I'm not sure why its not showing up on the latter one.

@Uriil
Copy link

Uriil commented Feb 23, 2024

We have similar problem but for CVE-2024-0057 issue. We are using AquaSec scanner, started failing today.

We are using mcr.microsoft.com/azure-functions/dotnet-isolated:4-dotnet-isolated8.0 image

@FinVamp1
Copy link
Member

We have a fix coming for CVE-2024-0056 . We normally update the images once a week and I'll check and update this thread. For CVE-2024-0057 let me check into this.

@FinVamp1
Copy link
Member

FinVamp1 commented Mar 4, 2024

Hello, the fix for CVE-2024-0057 will roll out in the image for 4.31.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants