Skip to content

CVE-2024-45337: Trivy reports Critical vulnerability in current version of mint #769

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

Open
hobthross opened this issue Apr 2, 2025 · 1 comment

Comments

@hobthross
Copy link

hobthross commented Apr 2, 2025

I ran “trivy image --severity=CRITICAL --no-progress --exit-code 1 $(IMAGE)” on an image where I’d installed docker-slim (SLIM_VERSION=1.40.11). It triggered this failure.

usr/local/bin/mint (gobinary)

Total: 1 (CRITICAL: 1)

┌─────────────────────┬────────────────┬──────────┬────────┬───────────────────┬───────────────┬────────────────────────────────────────────────────────┐
│       Library       │ Vulnerability  │ Severity │ Status │ Installed Version │ Fixed Version │                         Title                          │
├─────────────────────┼────────────────┼──────────┼────────┼───────────────────┼───────────────┼────────────────────────────────────────────────────────┤
│ golang.org/x/crypto │ CVE-2024-45337 │ CRITICAL │ fixed  │ v0.29.0           │ 0.31.0        │ golang.org/x/crypto/ssh: Misuse of                     │
│                     │                │          │        │                   │               │ ServerConfig.PublicKeyCallback may cause authorization │
│                     │                │          │        │                   │               │ bypass in golang.org/x/crypto                          │
│                     │                │          │        │                   │               │ https://avd.aquasec.com/nvd/cve-2024-45337             │
└─────────────────────┴────────────────┴──────────┴────────┴───────────────────┴───────────────┴────────────────────────────────────────────────────────┘
@hobthross
Copy link
Author

I think it would probably be fixed by updating the version of go that is being used. Not an urgent problem for me so I can’t spend time learning how to build this app in order to suggest a PR, but I’d be happy to test any new version if that’s useful.

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

1 participant