{"resultsPerPage":1,"startIndex":0,"totalResults":1,"format":"NVD_CVE","version":"2.0","timestamp":"2026-04-29T12:00:16.298","vulnerabilities":[{"cve":{"id":"CVE-2023-24827","sourceIdentifier":"security-advisories@github.com","published":"2023-02-07T01:15:09.660","lastModified":"2024-11-21T07:48:28.527","vulnStatus":"Modified","cveTags":[],"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."},{"lang":"es","value":"syft es una herramienta CLI y una librería Go para generar una lista de materiales de software (SBOM) a partir de imágenes de contenedores y sistemas de archivos. Se encontró una falla de divulgación de contraseña en las versiones v0.69.0 y v0.69.1 de Syft. Esta falla filtra la contraseña almacenada en la variable de entorno SYFT_ATTEST_PASSWORD. La variable de entorno `SYFT_ATTEST_PASSWORD` es para que el comando `syft attest` genere SBOM certificado para la imagen del contenedor dada. Esta variable de entorno se utiliza para descifrar la clave privada (proporcionada con `syft attest --key `) durante el proceso de firma mientras se genera una certificación SBOM. Esta vulnerabilidad afecta a los usuarios que ejecutan syft y tienen la variable de entorno `SYFT_ATTEST_PASSWORD` configurada con credenciales (independientemente de si se está utilizando el comando attest o no). Los usuarios que no tienen configurada la variable de entorno `SYFT_ATTEST_PASSWORD` no se ven afectados por este problema. Las credenciales se filtran de dos maneras: en los registros de syft cuando se usan `-vv` o `-vvv` en el comando syft (que es cualquier nivel de registro &gt;= `DEBUG`) y en la atestación o SBOM solo cuando Se utiliza el formato `syft-json`. Tenga en cuenta que a partir de la versión 0.69.0, cualquier certificación generada por el comando `syft attest` se carga en el registro OCI (si tiene acceso de escritura a ese registro) de la misma manera que se realiza `cosign adjunto`. Esto significa que cualquier certificación generada para las versiones afectadas de syft cuando se configuró la variable de entorno `SYFT_ATTEST_PASSWORD` filtraría credenciales en el payload de certificación cargada en el registro OCI. Este problema se solucionó en el commit `9995950c70` y se lanzó como v0.70.0. No existen workarounds para esta vulnerabilidad. Se recomienda a los usuarios que actualicen."}],"metrics":{"cvssMetricV31":[{"source":"security-advisories@github.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","baseScore":6.5,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"REQUIRED","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"NONE","availabilityImpact":"NONE"},"exploitabilityScore":2.8,"impactScore":3.6},{"source":"nvd@nist.gov","type":"Primary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","baseScore":7.5,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"NONE","availabilityImpact":"NONE"},"exploitabilityScore":3.9,"impactScore":3.6}]},"weaknesses":[{"source":"security-advisories@github.com","type":"Secondary","description":[{"lang":"en","value":"CWE-200"},{"lang":"en","value":"CWE-532"}]},{"source":"nvd@nist.gov","type":"Primary","description":[{"lang":"en","value":"CWE-532"}]}],"configurations":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:a:anchore:syft:0.69.0:*:*:*:*:*:*:*","matchCriteriaId":"6FF5D298-D6A2-4D2A-B6B4-B544F7B0CAE5"},{"vulnerable":true,"criteria":"cpe:2.3:a:anchore:syft:0.69.1:*:*:*:*:*:*:*","matchCriteriaId":"1588A629-B860-4DDF-95C2-9CBE56E86FE8"}]}]}],"references":[{"url":"https://github.com/anchore/syft/commit/9995950c70e849f9921919faffbfcf46401f71f3","source":"security-advisories@github.com","tags":["Patch","Vendor Advisory"]},{"url":"https://github.com/anchore/syft/security/advisories/GHSA-jp7v-3587-2956","source":"security-advisories@github.com","tags":["Exploit","Vendor Advisory"]},{"url":"https://github.com/anchore/syft/commit/9995950c70e849f9921919faffbfcf46401f71f3","source":"af854a3a-2127-422b-91ae-364da2661108","tags":["Patch","Vendor Advisory"]},{"url":"https://github.com/anchore/syft/security/advisories/GHSA-jp7v-3587-2956","source":"af854a3a-2127-422b-91ae-364da2661108","tags":["Exploit","Vendor Advisory"]}]}}]}