{"id":"CVE-2023-24827","state":"PUBLISHED","title":"Credential disclosure in syft when SYFT_ATTEST_PASSWORD environment variable set in syft","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 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 <path-to-key-file>`)  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 >= `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.","publishedAt":"2023-02-07T00:07:38.460Z","updatedAt":"2025-03-10T21:15:45.771Z","severity":{"score":6.5,"label":"Medium","version":"3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","source":"GitHub_M"},"assigner":"GitHub_M","products":["anchore syft"],"affected":[{"vendor":"anchore","product":"syft","versions":[{"version":">= 0.69.0, < 0.70.0","status":"affected"}]}],"references":["https://github.com/anchore/syft/security/advisories/GHSA-jp7v-3587-2956","https://github.com/anchore/syft/commit/9995950c70e849f9921919faffbfcf46401f71f3"],"weaknesses":["CWE-200","CWE-532"],"ingestedAt":"2026-10-29T20:05:43.909Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2023/24xxx/CVE-2023-24827.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.1","cveMetadata":{"cveId":"CVE-2023-24827","state":"PUBLISHED","datePublished":"2023-02-07T00:07:38.460Z","dateUpdated":"2025-03-10T21:15:45.771Z","assignerShortName":"GitHub_M","assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","dateReserved":"2023-01-30T14:43:33.706Z"},"containers":{"cna":{"title":"Credential disclosure in syft when SYFT_ATTEST_PASSWORD environment variable set in syft","descriptions":[{"lang":"en","value":"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 <path-to-key-file>`)  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 >= `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."}],"affected":[{"vendor":"anchore","product":"syft","versions":[{"version":">= 0.69.0, < 0.70.0","status":"affected"}]}],"references":[{"url":"https://github.com/anchore/syft/security/advisories/GHSA-jp7v-3587-2956","name":"https://github.com/anchore/syft/security/advisories/GHSA-jp7v-3587-2956","tags":["x_refsource_CONFIRM"]},{"url":"https://github.com/anchore/syft/commit/9995950c70e849f9921919faffbfcf46401f71f3","name":"https://github.com/anchore/syft/commit/9995950c70e849f9921919faffbfcf46401f71f3","tags":["x_refsource_MISC"]}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":6.5,"baseSeverity":"MEDIUM","confidentialityImpact":"HIGH","integrityImpact":"NONE","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"REQUIRED","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-200","lang":"en","description":"CWE-200: Exposure of Sensitive Information to an Unauthorized Actor","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-532","lang":"en","description":"CWE-532: Insertion of Sensitive Information into Log File","type":"CWE"}]}],"providerMetadata":{"shortName":"GitHub_M","orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","dateUpdated":"2023-02-07T00:07:38.460Z"},"source":{"advisory":"GHSA-jp7v-3587-2956","discovery":"UNKNOWN"}},"adp":[{"title":"CVE Program Container","references":[{"url":"https://github.com/anchore/syft/security/advisories/GHSA-jp7v-3587-2956","name":"https://github.com/anchore/syft/security/advisories/GHSA-jp7v-3587-2956","tags":["x_refsource_CONFIRM","x_transferred"]},{"url":"https://github.com/anchore/syft/commit/9995950c70e849f9921919faffbfcf46401f71f3","name":"https://github.com/anchore/syft/commit/9995950c70e849f9921919faffbfcf46401f71f3","tags":["x_refsource_MISC","x_transferred"]}],"providerMetadata":{"shortName":"CVE","orgId":"af854a3a-2127-422b-91ae-364da2661108","dateUpdated":"2024-08-02T11:03:19.257Z"}},{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2025-03-10T21:01:17.191366Z","id":"CVE-2023-24827","options":[{"Exploitation":"poc"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2025-03-10T21:15:45.771Z"}}]}}}