x/vulndb: potential Go vuln in github.com/anchore/syft: CVE-2023-24827 #1533
Labels
excluded: EFFECTIVELY_PRIVATE
This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
CVE-2023-24827 references github.com/anchore/syft, which may be a Go module.
Description:
syft is a a CLI tool and Go library for generating a Software Bill of Materials (SBOM) from container images and filesystems. A password disclosure flaw was found in Syft versions v0.69.0 and v0.69.1. This flaw leaks the password stored in the SYFT_ATTEST_PASSWORD environment variable. The
SYFT_ATTEST_PASSWORD
environment variable is for thesyft attest
command to generate attested SBOMs for the given container image. This environment variable is used to decrypt the private key (provided withsyft attest --key <path-to-key-file>
) during the signing process while generating an SBOM attestation. This vulnerability affects users running syft that have theSYFT_ATTEST_PASSWORD
environment variable set with credentials (regardless of if the attest command is being used or not). Users that do not have the environment variableSYFT_ATTEST_PASSWORD
set are not affected by this issue. The credentials are leaked in two ways: in the syft logs when-vv
or-vvv
are used in the syft command (which is any log level >=DEBUG
) and in the attestation or SBOM only when thesyft-json
format is used. Note that as of v0.69.0 any generated attestations by thesyft attest
command are uploaded to the OCI registry (if you have write access to that registry) in the same waycosign attach
is done. This means that any attestations generated for the affected versions of syft when theSYFT_ATTEST_PASSWORD
environment variable was set would leak credentials in the attestation payload uploaded to the OCI registry. This issue has been patched in commit9995950c70
and has been released as v0.70.0. There are no workarounds for this vulnerability. Users are advised to upgrade.References:
Cross references:
No existing reports found with this module or alias.
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: