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

> Unauthenticated attackers can download configuration files containing cleartext credentials from Comba AC2400 routers via a specific URL request.

- **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-7xq3-42gv-rc2r

## What is CVE-2019-15654?

CVE-2019-15654 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 AC2400 devices are prone to password disclosure via a simple crafted /09/business/upgrade/upcfgAction.php?download=true request to the web management server. The request doesn't require any authentication and will lead to saving the DBconfig.cfg file. At the end of the file, the login information is stored in cleartext.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Comba Ac2400 Firmware.

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

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

## Is CVE-2019-15654 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-15654 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-15654 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-15654/ (Markdown: https://insights.sbomify.com/CVE-2019-15654/index.md)
```

## Sources

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

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