# CVE-2012-3014: Hardcoded credentials in n/a

> Hardcoded administrative password in GarrettCom Magnum MNS-6K allows local users to gain elevated privileges.

- **Severity:** High 7.7 (`AV:A/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4v76-pc3g-jgg8

## What is CVE-2012-3014?

CVE-2012-3014 is a high-severity vulnerability in n/a, published on 4 Sep 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Management Software application in GarrettCom Magnum MNS-6K before 4.4.0, and 14.x before 14.4.0, has a hardcoded password for an administrative account, which allows local users to gain privileges via unspecified vectors.

Weakness: CWE-255

## Which versions are affected by CVE-2012-3014?

It affects 2 products.


Products: Garrettcom Magnum Managed Networks Software-6k, Garrettcom Magnum Managed Networks Software-6k Secure.

## How do I fix CVE-2012-3014?

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

## Is CVE-2012-3014 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-3014 and fix it if it is affected.

What it is: CVE-2012-3014 is a high-severity vulnerability in n/a, published on 4 Sep 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-3014 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-2012-3014/ (Markdown: https://insights.sbomify.com/CVE-2012-3014/index.md)
```

## Sources

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

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