# CVE-2014-1677: Information disclosure in n/a

> Remote attackers can obtain sensitive information from Technicolor TC7200 devices, posing a risk to network security and privacy.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/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:** 3 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5phr-5283-mg7g

## What is CVE-2014-1677?

CVE-2014-1677 is a high-severity vulnerability in n/a, published on 3 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Technicolor TC7200 with firmware STD6.01.12 could allow remote attackers to obtain sensitive information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2014-1677?

It affects 1 product.


Products: Technicolor Tc7200 Firmware.

## How do I fix CVE-2014-1677?

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

## Is CVE-2014-1677 being exploited?

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

Public exploit code:

- Technicolor TC7200 - Credentials Disclosure CVE : CVE-2014-1677 (github_poc): https://github.com/tihmstar/freePW_tc7200Eploit
- Technicolor TC7200 - Credentials Disclosure (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1677 and fix it if it is affected.

What it is: CVE-2014-1677 is a high-severity vulnerability in n/a, published on 3 Apr 2017. 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-2014-1677 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-2014-1677/ (Markdown: https://insights.sbomify.com/CVE-2014-1677/index.md)
```

## Sources

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

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