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

> Remote attackers can obtain cleartext FTP or SMB passwords by abusing the Test button in the machine address book.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jq4c-3qxg-g7cc

## What is CVE-2019-6452?

CVE-2019-6452 is a high-severity vulnerability in n/a, published on 6 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Kyocera Command Center RX TASKalfa4501i and TASKalfa5052ci allows remote attackers to abuse the Test button in the machine address book to obtain a cleartext FTP or SMB password.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Kyocera Command Center Rx.

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

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

## Is CVE-2019-6452 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-50932](https://insights.sbomify.com/CVE-2022-50932/): Kyocera Command Center RX ECOSYS M2035dn - Directory Traversal File Disclosure (Unauthenticated) (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6452 is a high-severity vulnerability in n/a, published on 6 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6452 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-6452/ (Markdown: https://insights.sbomify.com/CVE-2019-6452/index.md)
```

## Sources

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

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