CVE-2024-35192 json
Trivy possibly leaks registry credential when scanning images from malicious registries
published 2024-05-20 2 y ago modified 2026-09-10 1 mo ago also EUVD-2024-1860 , GHSA-xcq4-m2r3-cmrj , GO-2024-2870
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
Trivy is a security scanner. Prior to 0.51.2, if a malicious actor is able to trigger Trivy to scan container images from a crafted malicious registry, it could result in the leakage of credentials for legitimate registries such as AWS Elastic Container Registry (ECR), Google Cloud Artifact/Container Registry, or Azure Container Registry (ACR). These tokens can then be used to push/pull images from those registries to which the identity/user running Trivy has access. Systems are not affected if the default credential provider chain is unable to obtain valid credentials. This vulnerability only applies when scanning container images directly from a registry. This vulnerability is fixed in 0.51.2.
Patch / fix
- go github.com/aquasecurity/trivy 0.51.2
- aquasec trivy 0.51.2
- aquasecurity trivy 0.51.2
- trivy Package Hub 15 SP6, openSUSE Leap 15.6 0.54.1-bp156.2.3.1
- trivy Package Hub 15 SP5, openSUSE Leap 15.5 0.54.1-bp155.2.3.1
- trivy openSUSE Tumbleweed 0.52.0-1.1
opensuse advisories openSUSE-SU-2024:0269-1openSUSE-SU-2024:0268-1openSUSE-SU-2024:14030-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-35192 updated cvss 5.5
trivy: Possible registry credential leakage when scanning images from malicious registries
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N |
| GitHub | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/aquasecurity/trivy | <0.51.2 |
0.51.2 |
Affected products
- aquasecurity trivy
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
Sources
- CVE List CVE-2024-35192
- GitHub Advisory GHSA-xcq4-m2r3-cmrj
- NVD CVE-2024-35192
- OSV GO-2024-2870
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.