# CVE-2015-7276: Hardcoded credentials in C2000T

> Attackers can exploit hard-coded cryptographic keys in Technicolor C2000T and C2100T routers to bypass security controls and access sensitive data.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 6 Nov 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v75w-cq75-j76p

## What is CVE-2015-7276?

CVE-2015-7276 is a medium-severity vulnerability in Technicolor C2000T, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Technicolor C2000T and C2100T uses hard-coded cryptographic keys.

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

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

It affects 2 products.


Products: Technicolor C2000t Firmware, Technicolor C2100t Firmware.

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

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

## Is CVE-2015-7276 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-7276 is a medium-severity vulnerability in Technicolor C2000T, published on 6 Nov 2019. 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-7276 in the wild and no public exploit code.

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

## Sources

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

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