CVE-2024-6104 — go-retryablehttp can leak basic auth credentials to log files

Affected: HashiCorp Shared library

go-retryablehttp prior to 0.7.7 did not sanitize urls when writing them to its log file. This could lead to go-retryablehttp writing sensitive HTTP basic auth credentials to its log file. This vulnerability, CVE-2024-6104, was fixed in go-retryablehttp 0.7.7.

GHSA-pmwq-pjrm-6p5r — in-toto-golang and in-toto-python have inconsistent negation behavior

Affected: Go: github.com/in-toto/in-toto-golang

### Impact _What kind of vulnerability is it? Who is impacted?_

in-toto-golang and in-toto-python both support glob patterns in artifact rules to indicate the artifacts that a rule applies to. Both support negations in character classes to indicate what should *not* be matched, but they used different operators to indicate the negation. in-toto-python uses `!` while in-toto-golang used `^`. A layout authored with the expectations of one implementation can therefore exhibit different behavior in the other implementation.

This impacts users in a specific set of circumstances where two different implementations are used to verify the same layout + attestation bundle at different stages of the same pipeline. As a rule of thumb, we advise using a single implementation across all aspects of a pipeline, from layout creation to pipeline execution and verification to prevent this class of bugs.

### Patches _Has the problem been patched? What versions should users upgrade to?_

in-toto-golang has been updated to use `!` instead of `^` to indicate negation. See https://github.com/in-toto/in-toto-golang/pull/462. This is part of v0.11.0.

Most recent entries from all

CVE-2024-6104 — go-retryablehttp can leak basic auth credentials to log files

GHSA-pmwq-pjrm-6p5r — in-toto-golang and in-toto-python have inconsistent negation behavior