Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
When Trivy downloads an OCI artifact, it uses the org.opencontainers.image.title annotation from the artifact manifest as the destination filename without validation. An attacker who can make Trivy fetch an attacker-controlled artifact can supply a crafted annotation that resolves to a path outside the intended destination, causing Trivy to write the layer content to an arbitrary location on the host filesystem. Affected configurations Exploitation requires the attacker to direct Trivy at an attacker-controlled OCI artifact via one of the following inputs: | Input | Used for | | --- | --- | | --db-repository flag, TRIVYDBREPOSITORY environment variable, or db.repository in trivy.yaml | Vulnerability database | | --java-db-repository flag, TRIVYJAVADBREPOSITORY environment variable, or db.java-repository in trivy.yaml | Java vulnerability database | | --checks-bundle-repository flag (and the deprecated --policy-bundle-repository alias), TRIVYCHECKSBUNDLEREPOSITORY environment…
Recommended action: Upgrade to 0.71.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Trivy's plugin manager does not fully validate metadata from a plugin's manifest before using it to construct filesystem paths under the plugin root (~/.trivy/plugins). A crafted plugin can cause Trivy to write its files (the manifest and the downloaded plugin binary) outside the plugin root, to an arbitrary location writable by the user running Trivy. Plugins are third-party binaries that Trivy downloads and executes, so Trivy's documentation already advises installing only plugins you trust. This issue does not change that trust boundary: exploitation requires the user to install a malicious plugin in the first place. Affected configurations The vulnerability is triggered only when a user installs an attacker-controlled plugin, for example via trivy plugin install <SOURCE or trivy plugin run <SOURCE. An attacker has to trick a user into installing a plugin they crafted, for instance by publishing it or by getting a malicious source pasted into a command or documentation…
Recommended action: Upgrade to 0.72.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When Trivy scans a Helm chart archive (.tgz), its custom tar unpacker reads each entry with io.ReadAll(tr) and no size limit. An attacker who can place a malicious .tgz file in the scanned path can craft a small compressed archive that decompresses to gigabytes, causing the Trivy process to be killed by the OS OOM killer. Affected configurations Exploitation requires the attacker to place a crafted .tgz file in a location that Trivy will scan as a Helm chart. This applies to the following scan targets: | Command | Condition | | --- | --- | | trivy config <dir | Directory contains a crafted .tgz Helm chart (misconfiguration scanning is always enabled) | | trivy filesystem --scanners misconf <dir | Directory contains a crafted .tgz Helm chart and --scanners misconf is explicitly enabled | | trivy image --scanners misconf <image | Image contains a crafted .tgz Helm chart and --scanners misconf is explicitly enabled | Realistic scenarios include: - A CI pipeline that runs trivy…
Recommended action: Upgrade to 0.71.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact 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. Taking AWS as an example, the leakage only occurs when Trivy is able to transparently obtain registry credentials from the default credential provider chain. You are affected if Trivy is executed in any of the following situations: - The environment variables contain static AWS credentials (AWSACCESSKEYID, AWSSECRETACCESSKEY, AWSSESSIONTOKEN) that have access to ECR. - Within a Pod running on an EKS cluster that has been assigned a role with access to ECR using an IAM Roles for Service Accounts (IRSA) annotation. - etc. You are not affected if the default…
Recommended action: Upgrade to 0.51.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.