# CVE-2019-19967: Information disclosure in n/a

> Attackers can intercept cleartext admin passwords transmitted over HTTP on the gateway's administration page, leading to credential theft and unauthorized access.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 25 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rp7x-9gh4-8c2q

## What is CVE-2019-19967?

CVE-2019-19967 is a high-severity vulnerability in n/a, published on 25 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Administration page on Connect Box EuroDOCSIS 3.0 Voice Gateway CH7465LG-NCIP-6.12.18.25-2p6-NOSH devices accepts a cleartext password in a POST request on port 80, as demonstrated by the Password field to the xml/setter.xml URI.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2019-19967?

It affects 1 product.


Products: Upc Connect Box Eurodocsis Firmware.

## How do I fix CVE-2019-19967?

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

## Is CVE-2019-19967 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19967 and fix it if it is affected.

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

## Sources

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

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