CVE-2023-24827: Github.com/anchore/syft Credential Disclosure Vulnerability

MODERATE
Advisory Identifier: GHSA-jp7v-3587-2956
CVSS 6.5
CWE-532 CWE-200
Published
Advisory Summary

CVE-2023-24827 is a MODERATE (CVSS 6.5) credential disclosure vulnerability (CWE-532: Insertion of Sensitive Information into Log File) affecting Github.com/anchore/syft libraries in the Go ecosystem. The issue involves credential disclosure in syft when syft_attest_password environment variable set. Remediation is available by upgrading affected packages to version 0.70.0.

CVE-2023-24827 at a Glance

CVE Identifier CVE-2023-24827
GHSA Identifier GHSA-jp7v-3587-2956
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-532: Insertion of Sensitive Information into Log File
Affected Product Github.com/anchore/syft
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2023-24827

To remediate this vulnerability, upgrade all affected Github.com/anchore/syft dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/anchore/syft fixed: 0.70.0
Upgrade github.com/anchore/syft to 0.70.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/anchore/syft

How to Check if You Are Affected

To determine whether your application is affected by CVE-2023-24827, inspect your project dependencies for Github.com/anchore/syft:

inspect dependencies for github.com/anchore/syft

Analyze the terminal output to locate any version of Github.com/anchore/syft in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.70.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-532: Insertion of Sensitive Information into Log File, where the product writes sensitive information to a log file. In Github.com/anchore/syft, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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. ### Impact 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`) - 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. Example commands run from affected versions of syft that show the credential disclosure: ```bash $ SYFT_ATTEST_PASSWORD=123456 syft <container-image-or-directory-input> -o syft-json | grep 123456 # "123456" is in the output $ SYFT_ATTEST_PASSWORD=123456 syft attest <container-image-input> -o syft-json $ cosign download attestation <container-image-input> | jq -r '.payload' | base64 -d | grep 123456 # "123456" is in the output ``` ### Patches The patch has been released in v0.70.0. ### Workarounds There are no workarounds for this vulnerability. ### References Patch pull request: https://github.com/anchore/syft/pull/1538

CVE-2023-24827 Affected Github.com/anchore/syft Versions

1 component(s)
Fixed Versions:
0.70.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/anchore/syft
Go
≥ 0.69.0
< 0.70.0
0.70.0

References

Frequently Asked Questions

What is CVE-2023-24827?
CVE-2023-24827 is a security vulnerability in Github.com/anchore/syft involving Credential disclosure in syft when SYFT_ATTEST_PASSWORD environment variable set under CWE-532: Insertion of Sensitive Information into Log File.
Which Github.com/anchore/syft versions are affected?
Affected versions include releases prior to 0.70.0 across affected packages: github.com/anchore/syft.
What version fixes CVE-2023-24827?
Upgrading to 0.70.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/anchore/syft affected?
Yes, github.com/anchore/syft is affected in releases prior to 0.70.0. Upgrade your dependency to 0.70.0 or later.
What is the CVSS score of CVE-2023-24827?
CVE-2023-24827 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2023-24827?
CVE-2023-24827 is classified under CWE-532: Insertion of Sensitive Information into Log File (The product writes sensitive information to a log file.).
How can I check Go dependencies for CVE-2023-24827?
Run the dependency tree command: 'inspect dependencies for github.com/anchore/syft'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jp7v-3587-2956",
  "modified" : "2023-02-08T21:38:46Z",
  "published" : "2023-02-08T21:38:46Z",
  "aliases" : [ "CVE-2023-24827" ],
  "summary" : "Credential disclosure in syft when SYFT_ATTEST_PASSWORD environment variable set",
  "details" : "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.\n\n### Impact\nThe `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. \n\nThis 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.\n\nThe credentials are leaked in two ways:\n- in the syft logs when `-vv` or `-vvv` are used in the syft command (which is any log level >= `DEBUG`)\n- in the attestation or SBOM only when the `syft-json` format is used \n\nNote 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.\n\nExample commands run from affected versions of syft that show the credential disclosure:\n```bash\n$ SYFT_ATTEST_PASSWORD=123456 syft <container-image-or-directory-input> -o syft-json | grep 123456\n# \"123456\" is in the output\n\n$ SYFT_ATTEST_PASSWORD=123456 syft attest <container-image-input> -o syft-json \n$ cosign download attestation <container-image-input> | jq -r '.payload' | base64 -d | grep 123456\n# \"123456\" is in the output\n```\n\n### Patches\n\nThe patch has been released in v0.70.0.\n\n### Workarounds\n\nThere are no workarounds for this vulnerability.\n\n### References\n\nPatch pull request: https://github.com/anchore/syft/pull/1538",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/anchore/syft"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.69.0"
      }, {
        "fixed" : "0.70.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "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" : "WEB",
    "url" : "https://github.com/anchore/syft/commit/9995950c70e849f9921919faffbfcf46401f71f3"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/anchore/syft"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-532" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-02-08T21:38:46Z",
    "nvd_published_at" : "2023-02-07T01:15:00Z"
  }
}