Lucene search

K
osvGoogleOSV:GO-2024-2870
HistoryMay 22, 2024 - 4:46 p.m.

Credential leakage in github.com/aquasecurity/trivy

2024-05-2216:46:37
Google
osv.dev
10
trivy
credential leakage
malicious registry
aws ecr
google cloud registry
azure acr
docker
containerd
image sources validation

CVSS3

5.5

Attack Vector

LOCAL

Attack Complexity

HIGH

Privileges Required

NONE

User Interaction

REQUIRED

Scope

CHANGED

Confidentiality Impact

HIGH

Integrity Impact

NONE

Availability Impact

NONE

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N

AI Score

7

Confidence

High

EPSS

0

Percentile

9.0%

A malicious registry can cause Trivy to leak credentials for legitimate registries such as AWS Elastic Container Registry (ECR), Google Cloud Artifact/Container Registry, or Azure Container Registry (ACR) if the registry is scanned from directly using Trivy. These tokens can then be used to push/pull images from those registries to which the identity/user running Trivy has access. This vulnerability only applies when scanning container images directly from a registry. If you use Docker, containerd or other runtime to pull images locally and scan them with Trivy, you are not affected. To enforce this behavior, you can use the --image-src flag to select which sources you trust.

CVSS3

5.5

Attack Vector

LOCAL

Attack Complexity

HIGH

Privileges Required

NONE

User Interaction

REQUIRED

Scope

CHANGED

Confidentiality Impact

HIGH

Integrity Impact

NONE

Availability Impact

NONE

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N

AI Score

7

Confidence

High

EPSS

0

Percentile

9.0%