# CVE-2018-17287: Information disclosure in n/a

> Attackers can exfiltrate cleartext passwords from the Kofax Front Office Server Administration Console by exploiting the back-end download feature.

- **Severity:** Medium 4.9 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pjpc-vgm9-wp5g

## What is CVE-2018-17287?

CVE-2018-17287 is a medium-severity vulnerability in n/a, published on 18 Apr 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In Kofax Front Office Server Administration Console 4.1.1.11.0.5212, some fields, such as passwords, are obfuscated in the front-end, but the cleartext value can be exfiltrated by using the back-end "download" feature, as demonstrated by an mfp.password downloadsettingvalue operation.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity), CWE-311 (Missing Encryption of Sensitive Data)

## Which versions are affected by CVE-2018-17287?

It affects 1 product.


Products: Kofax Front Office Server.

## How do I fix CVE-2018-17287?

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

## Is CVE-2018-17287 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-17289](https://insights.sbomify.com/CVE-2018-17289/): XML external entity in n/a (medium 6.5)
- [CVE-2018-17288](https://insights.sbomify.com/CVE-2018-17288/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-17287 and fix it if it is affected.

What it is: CVE-2018-17287 is a medium-severity vulnerability in n/a, published on 18 Apr 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-17287 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-2018-17287/ (Markdown: https://insights.sbomify.com/CVE-2018-17287/index.md)
```

## Sources

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

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