# CVE-2022-3474: Bazel leaks user credentials through the remote assets API

> Bazel leaks all user-provided credentials instead of only required ones via the remote assets API, exposing sensitive authentication data.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Oct 2022
- **Updated:** 3 Aug 2024
- **Also known as:** AZL-11350, GHSA-mxr8-q875-rhwq

## What is CVE-2022-3474?

CVE-2022-3474 is a medium-severity vulnerability in Google LLC Bazel, published on 26 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A bad credential handling in the remote assets API for Bazel versions prior to 5.3.2 and 4.2.3 sends all user-provided credentials instead of only the required ones for the requests. We recommend upgrading to versions later than or equal to 5.3.2 or 4.2.3.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2022-3474?

It affects 1 product.


Products: Google Bazel.

## How do I fix CVE-2022-3474?

Upgrade to a fixed version.

## Is CVE-2022-3474 being exploited?

There is no known exploitation of CVE-2022-3474 in the wild and no public exploit code.

## Other vulnerabilities in Google LLC Bazel

- [CVE-2021-22539](https://insights.sbomify.com/CVE-2021-22539/): Code execution in VSCode-bazel via malicious Bazel config files (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3474 and fix it if it is affected.

What it is: CVE-2022-3474 is a medium-severity vulnerability in Google LLC Bazel, published on 26 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-3474 in the wild and no public exploit code.

Affected product: Google LLC Bazel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-3474/ (Markdown: https://insights.sbomify.com/CVE-2022-3474/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3474
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3474
- OSV: https://osv.dev/vulnerability/CVE-2022-3474

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-3474/
Summaries are generated and may contain mistakes; the official description above is the record.