What is the severity of CVE-2022-3474?

CVE-2022-3474 is classified as a moderate severity vulnerability due to improper credential handling.

How do I fix CVE-2022-3474?

To fix CVE-2022-3474, upgrade Bazel to version 5.3.2 or later, or to version 4.2.3 or later.

What impact does CVE-2022-3474 have?

CVE-2022-3474 may allow an attacker to access unnecessary user credentials, leading to potential security breaches.

Which versions of Bazel are affected by CVE-2022-3474?

CVE-2022-3474 affects Bazel versions before 5.3.2 and 4.2.3.

Is there a workaround for CVE-2022-3474?

There currently are no known workarounds for CVE-2022-3474, and the recommended action is to upgrade.

Vulnerability/
CVE-2022-3474

medium

4.3

CWE

522

26/10/2022

3/8/2024

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

First published: Wed Oct 26 2022(Updated: )

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.

Credit: cve-coordination@google.com cve-coordination@google.com

Affected Software	Affected Version	How to fix
Google Bazel	>=3.1.0<4.2.3
Google Bazel	>=5.0.0<5.3.2

Never miss a vulnerability like this again

Reference Links

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

Frequently Asked Questions

What is the severity of CVE-2022-3474?
CVE-2022-3474 is classified as a moderate severity vulnerability due to improper credential handling.
How do I fix CVE-2022-3474?
To fix CVE-2022-3474, upgrade Bazel to version 5.3.2 or later, or to version 4.2.3 or later.
What impact does CVE-2022-3474 have?
CVE-2022-3474 may allow an attacker to access unnecessary user credentials, leading to potential security breaches.
Which versions of Bazel are affected by CVE-2022-3474?
CVE-2022-3474 affects Bazel versions before 5.3.2 and 4.2.3.
Is there a workaround for CVE-2022-3474?
There currently are no known workarounds for CVE-2022-3474, and the recommended action is to upgrade.

collector/nvd-index
agent/type
agent/softwarecombine
agent/weakness
agent/severity
agent/title
agent/references
agent/first-publish-date
agent/description
agent/event
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/author
agent/tags
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/source
vendor/google
canonical/google bazel
version/google bazel/3.1.0
version/google bazel/5.0.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-3474?
CVE-2022-3474 is classified as a moderate severity vulnerability due to improper credential handling.
How do I fix CVE-2022-3474?
To fix CVE-2022-3474, upgrade Bazel to version 5.3.2 or later, or to version 4.2.3 or later.
What impact does CVE-2022-3474 have?
CVE-2022-3474 may allow an attacker to access unnecessary user credentials, leading to potential security breaches.
Which versions of Bazel are affected by CVE-2022-3474?
CVE-2022-3474 affects Bazel versions before 5.3.2 and 4.2.3.
Is there a workaround for CVE-2022-3474?
There currently are no known workarounds for CVE-2022-3474, and the recommended action is to upgrade.