cvelist/2023/24xxx/CVE-2023-24827.json

100 lines
4.8 KiB
JSON
Raw Normal View History

2023-01-30 15:00:37 +00:00
{
2023-02-07 01:00:40 +00:00
"data_version": "4.0",
2023-01-30 15:00:37 +00:00
"data_type": "CVE",
"data_format": "MITRE",
"CVE_data_meta": {
"ID": "CVE-2023-24827",
2023-02-07 01:00:40 +00:00
"ASSIGNER": "security-advisories@github.com",
"STATE": "PUBLIC"
2023-01-30 15:00:37 +00:00
},
"description": {
"description_data": [
{
"lang": "eng",
2023-02-07 01:00:40 +00:00
"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."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "CWE-200: Exposure of Sensitive Information to an Unauthorized Actor",
"cweId": "CWE-200"
}
]
},
{
"description": [
{
"lang": "eng",
"value": "CWE-532: Insertion of Sensitive Information into Log File",
"cweId": "CWE-532"
}
]
}
]
},
"affects": {
"vendor": {
"vendor_data": [
{
"vendor_name": "anchore",
"product": {
"product_data": [
{
"product_name": "syft",
"version": {
"version_data": [
{
"version_value": ">= 0.69.0, < 0.70.0",
"version_affected": "="
}
]
}
}
]
}
}
]
}
},
"references": {
"reference_data": [
{
"url": "https://github.com/anchore/syft/security/advisories/GHSA-jp7v-3587-2956",
"refsource": "MISC",
"name": "https://github.com/anchore/syft/security/advisories/GHSA-jp7v-3587-2956"
},
{
"url": "https://github.com/anchore/syft/commit/9995950c70e849f9921919faffbfcf46401f71f3",
"refsource": "MISC",
"name": "https://github.com/anchore/syft/commit/9995950c70e849f9921919faffbfcf46401f71f3"
}
]
},
"source": {
"advisory": "GHSA-jp7v-3587-2956",
"discovery": "UNKNOWN"
},
"impact": {
"cvss": [
{
"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"
2023-01-30 15:00:37 +00:00
}
]
}
}