aquasecurity trivy up to 0.51.1 Scan insufficiently protected credentials

Summaryinfo

A vulnerability classified as problematic has been found in aquasecurity trivy up to 0.51.1. This issue affects some unknown processing of the component Scan Handler. The manipulation leads to insufficiently protected credentials. This vulnerability is listed as CVE-2024-35192. The attack must be carried out locally. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in aquasecurity trivy up to 0.51.1. This issue affects some unknown processing of the component Scan Handler. The manipulation with an unknown input leads to a insufficiently protected credentials vulnerability. Using CWE to declare the problem leads to CWE-522. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. Impacted is confidentiality. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-35192 since 05/10/2024. The exploitation is known to be difficult. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.

Upgrading to version 0.51.2 eliminates this vulnerability. Applying the patch e7f14f729de259551203f313e57d2d9d3aa2ff87 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• aquasecurity

Name

• trivy

Version

• 0.51.0
• 0.51.1

License

• open-source

Website

• Product: https://github.com/aquasecurity/trivy/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion