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

> Remote attackers can defeat cryptographic protections on N-Tron industrial wireless access points by leveraging shared SSH and HTTPS private keys across installations.

- **Severity:** High 8.8 (`AV:N/AC:M/Au:N/C:C/I:C/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:** 13 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j28j-mmv9-g2wx

## What is CVE-2012-4716?

CVE-2012-4716 is a high-severity vulnerability in n/a, published on 13 Jun 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

N-Tron 702-W Industrial Wireless Access Point devices use the same (1) SSH and (2) HTTPS private keys across different customers' installations, which makes it easier for remote attackers to defeat cryptographic protection mechanisms by leveraging knowledge of a key.

Weakness: CWE-310

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

It affects 1 product.


Products: N-Tron 702w Industrial Wireless Access Point.

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

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

## Is CVE-2012-4716 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4716 is a high-severity vulnerability in n/a, published on 13 Jun 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-2012-4716 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-4716/ (Markdown: https://insights.sbomify.com/CVE-2012-4716/index.md)
```

## Sources

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

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