# CVE-2015-3960: Hardcoded credentials in n/a

> Hardcoded RSA keys in Belden GarrettCom Magnum switches allow remote attackers to decrypt HTTPS traffic and bypass cryptographic protections.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/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:** 4 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4c9f-wvvv-9w26

## What is CVE-2015-3960?

CVE-2015-3960 is a medium-severity vulnerability in n/a, published on 4 Aug 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The firmware in MNS before 4.5.6 on Belden GarrettCom Magnum 6K and Magnum 10K switches uses hardcoded RSA private keys and certificates across different customers' installations, which makes it easier for remote attackers to defeat cryptographic protection mechanisms for HTTPS sessions by leveraging knowledge of a private key from another installation.

Weakness: CWE-310

## Which versions are affected by CVE-2015-3960?

It affects 2 products.


Products: Garrettcom Magnum 10k Firmware, Garrettcom Magnum 6k Firmware.

## How do I fix CVE-2015-3960?

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

## Is CVE-2015-3960 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-3959](https://insights.sbomify.com/CVE-2015-3959/): Hardcoded credentials in n/a (high 7.2)
- [CVE-2015-3942](https://insights.sbomify.com/CVE-2015-3942/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2015-3961](https://insights.sbomify.com/CVE-2015-3961/): Memory corruption in n/a (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3960 and fix it if it is affected.

What it is: CVE-2015-3960 is a medium-severity vulnerability in n/a, published on 4 Aug 2015. 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-2015-3960 in the wild and no public exploit code.

Affected product: n/a. 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-2015-3960/ (Markdown: https://insights.sbomify.com/CVE-2015-3960/index.md)
```

## Sources

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

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