# CVE-2017-20234: GarrettCom Magnum 6K and 10K Authentication Bypass via Hardcoded String

> Unauthenticated attackers can bypass login controls on GarrettCom Magnum switches using a hardcoded string to access administrative functions and sensitive configuration.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-vrjf-6q9f-r3qr

## What is CVE-2017-20234?

CVE-2017-20234 is a critical vulnerability in Belden GarrettCom Magnum 6K and 10K Managed Switches, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GarrettCom Magnum 6K and 10K managed switches contain an authentication bypass vulnerability that allows unauthenticated attackers to gain unauthorized access by exploiting a hardcoded string in the authentication mechanism. Attackers can bypass login controls to access administrative functions and sensitive switch configuration without valid credentials.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2017-20234?


## How do I fix CVE-2017-20234?

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

## Is CVE-2017-20234 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-20234 and fix it if it is affected.

What it is: CVE-2017-20234 is a critical vulnerability in Belden GarrettCom Magnum 6K and 10K Managed Switches, published on 3 Apr 2026. 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-2017-20234 in the wild and no public exploit code.

Affected product: Belden GarrettCom Magnum 6K and 10K Managed Switches. 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-2017-20234/ (Markdown: https://insights.sbomify.com/CVE-2017-20234/index.md)
```

## Sources

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

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