# CVE-2024-29011: Hardcoded credentials in GMS

> Attackers can bypass authentication in SonicWall GMS using hard-coded credentials in the ECM endpoint, leading to unauthorized access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2024
- **Updated:** 16 Dec 2025
- **Also known as:** GHSA-87r7-45xw-v92f

## What is CVE-2024-29011?

CVE-2024-29011 is a high-severity vulnerability in SonicWall GMS, published on 1 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of hard-coded password in the GMS ECM endpoint leading to authentication bypass vulnerability.

This issue affects GMS: 9.3.4 and earlier versions.

Weakness: CWE-259 (Use of Hard-coded Password)

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


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

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

## Is CVE-2024-29011 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29011 is a high-severity vulnerability in SonicWall GMS, published on 1 May 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-29011 in the wild and no public exploit code.

Affected product: SonicWall GMS. 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-29011/ (Markdown: https://insights.sbomify.com/CVE-2024-29011/index.md)
```

## Sources

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

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