# CVE-2020-35992: Hardcoded credentials in n/a

> Attackers with file access can decrypt database credentials from the configuration file, enabling unauthorized access to financial records.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 23 Aug 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-55qq-wp4m-g5qv

## What is CVE-2020-35992?

CVE-2020-35992 is a medium-severity vulnerability in n/a, published on 23 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Fiserv Prologue through 2020-12-16 does not properly protect the database password. If an attacker were to gain access to the configuration file (specifically, the LogPassword attribute within appconfig.ini), they would be able to decrypt the password stored within the configuration file. This would yield cleartext credentials for the database (to gain access to financial records of customers stored within the database), and in some cases would allow remote login to the database.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2020-35992?

It affects 1 product.


Products: Fiserv Prologue.

## How do I fix CVE-2020-35992?

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

## Is CVE-2020-35992 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-35992 and fix it if it is affected.

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

## Sources

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

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