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

> Attackers can read sensitive customer PII from local files because the application stores data in cleartext despite offering password protection.

- **Severity:** High 7.5 (`CVSS:3.0/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:** 26 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r7c7-wwxg-74wm

## What is CVE-2018-14608?

CVE-2018-14608 is a high-severity vulnerability in n/a, published on 26 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Thomson Reuters UltraTax CS 2017 on Windows has a password protection option; however, the level of protection might be inconsistent with some customers' expectations because the data is directly accessible in cleartext. Specifically, it stores customer data in unique directories (%install_path%\WinCSI\UT17DATA\client_ID\file_name.XX17) that can be bypassed without authentication by examining the strings of the .XX17 file. The strings stored in the .XX17 file contain each customer's: Full Name, Spouse's Name, Social Security Number, Date of Birth, Occupation, Home Address, Daytime Phone Number, Home Phone Number, Spouse's Address, Spouse's Daytime Phone Number, Spouse's Social Security Number, Spouse's Home Phone Number, Spouse's Occupation, Spouse's Date of Birth, and Spouse's Filing Status.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 1 product.


Products: Thomsonreuters Ultratax Cs.

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

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

## Is CVE-2018-14608 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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