# CVE-2024-29961: supply-chain attack risk

> An unauthenticated attacker can exploit background update checks to launch a supply-chain attack against Brocade SANnav appliances.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-59h2-5xw9-v6wf

## What is CVE-2024-29961?

CVE-2024-29961 is a high-severity vulnerability in Broadcom Brocade Sannav, published on 19 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability affects Brocade SANnav before v2.3.1 and v2.3.0a. It allows a Brocade SANnav service to send ping commands in the background at regular intervals to gridgain.com to check if updates are available for the Component. This could make an unauthenticated, remote attacker aware of the behavior and launch a supply-chain attack against a Brocade SANnav appliance.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-29961?

It affects 1 product.


Products: Broadcom Brocade Sannav.

## How do I fix CVE-2024-29961?

No fix has been published for CVE-2024-29961 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-29961 being exploited?

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

## Other vulnerabilities in Broadcom Brocade Sannav

- [CVE-2019-16211](https://insights.sbomify.com/CVE-2019-16211/): Hardcoded credentials in Brocade SANnav (critical 9.8)
- [CVE-2024-3596](https://insights.sbomify.com/CVE-2024-3596/): RADIUS Protocol under RFC2865 is vulnerable to forgery attacks. (critical 9.0)
- [CVE-2019-16212](https://insights.sbomify.com/CVE-2019-16212/): A vulnerability in Brocade SANnav versions before v2.1.0 could allow a remote authenticated attacker to conduct an LDAP injection. (high 8.8)
- [CVE-2019-16205](https://insights.sbomify.com/CVE-2019-16205/): Weak cryptography in Brocade SANnav (high 8.8)
- [CVE-2024-2240](https://insights.sbomify.com/CVE-2024-2240/): Docker implementation in Brocade SANnav is missing Audit Rules. (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-29961 and fix it if it is affected.

What it is: CVE-2024-29961 is a high-severity vulnerability in Broadcom Brocade Sannav, published on 19 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-29961 in the wild and no public exploit code.

Affected product: Broadcom Brocade Sannav. 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-2024-29961/ (Markdown: https://insights.sbomify.com/CVE-2024-29961/index.md)
```

## Sources

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

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