{"id":"CVE-2023-24827","summary":"Credential disclosure in syft when SYFT_ATTEST_PASSWORD environment variable set in syft","details":"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 the `syft attest` command to generate attested SBOMs for the given container image. This environment variable is used to decrypt the private key (provided with `syft attest --key \u003cpath-to-key-file\u003e`)  during the signing process while generating an SBOM attestation. This vulnerability affects users running syft that have the `SYFT_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 variable `SYFT_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 \u003e= `DEBUG`) and in the attestation or SBOM only when the `syft-json` format is used. Note that as of v0.69.0 any generated attestations by the `syft attest` command are uploaded to the OCI registry (if you have write access to that registry) in the same way `cosign attach` is done. This means that any attestations generated for the affected versions of syft when the `SYFT_ATTEST_PASSWORD` environment variable was set would leak credentials in the attestation payload uploaded to the OCI registry. This issue has been patched in commit `9995950c70` and has been released as v0.70.0. There are no workarounds for this vulnerability. Users are advised to upgrade.","aliases":["GHSA-jp7v-3587-2956","GO-2023-1533"],"modified":"2026-04-02T08:49:30.534035Z","published":"2023-02-07T00:07:38.460Z","database_specific":{"cwe_ids":["CWE-200","CWE-532"],"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/24xxx/CVE-2023-24827.json","cna_assigner":"GitHub_M"},"references":[{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/24xxx/CVE-2023-24827.json"},{"type":"ADVISORY","url":"https://github.com/anchore/syft/security/advisories/GHSA-jp7v-3587-2956"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-24827"},{"type":"FIX","url":"https://github.com/anchore/syft/commit/9995950c70e849f9921919faffbfcf46401f71f3"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/anchore/syft","events":[{"introduced":"b81c9805dcc9bf25dad7659fd9c2bbf7dd3f3d90"},{"fixed":"9995950c70e849f9921919faffbfcf46401f71f3"}]}],"versions":["v0.69.0","v0.69.1"],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-24827.json"}}],"schema_version":"1.7.5","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N"}]}