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

> Attackers can obtain administrator credentials by extracting double-MD5 hashed values from the login page source code of Comba AP2600-I devices.

- **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:** 19 Mar 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-53vv-rvmf-598x

## What is CVE-2019-15653?

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

### Official description

Comba AP2600-I devices through A02,0202N00PD2 are prone to password disclosure via an insecure authentication mechanism. The HTML source code of the login page contains values that allow obtaining the username and password. The username are password values are a double md5 of the plaintext real value, i.e., md5(md5(value)).

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm), CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 1 product.


Products: Comba Ap2600-I - A02 - 0202n00pd2 Firmware.

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

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

## Is CVE-2019-15653 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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