CVE-2020-35992
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFiserv 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceFiserv Prologue stores database credentials (LogPassword) in an encrypted form within the appconfig.ini configuration file, but the encryption mechanism is flawed. An attacker who gains read access to this config file can decrypt the password and obtain plaintext database credentials, potentially enabling unauthorized access to financial customer records and remote database login.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2020-12-16CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Fiserv Prologue installationSearch for the Prologue application installation directory, typically found in program files or application data folders. Look for executables named Prologue or related Fiserv components.Affected if Fiserv Prologue software is present on the system
-
Check installed versionLocate version information in the Prologue installation directory, often in a version.txt, about dialog, or the executable file properties. Compare the version or build date to the affected range (before 2020-12-17).Affected if The installed version is dated 2020-12-16 or earlier, or the version number is at or below the affected release
-
Locate appconfig.ini configuration fileFind the appconfig.ini file within the Prologue installation directory or configuration folder. This file typically stores application settings including database connection parameters.Affected if The appconfig.ini file exists and is readable by the analysis process
-
Inspect LogPassword entryOpen appconfig.ini with a text editor or command and search for the LogPassword parameter. Verify it contains an encrypted or hashed value rather than being blank or absent.Affected if The LogPassword field contains a non-empty encrypted value, indicating credentials are stored in this file
A system is affected if Fiserv Prologue version 2020-12-16 or earlier is installed and the appconfig.ini file contains an encrypted LogPassword entry that uses the flawed encryption mechanism.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict file system permissions on appconfig.ini to prevent unauthorized read access; rotate the compromised database credentials immediately; contact Fiserv for any available patch addressing the weak encryption; consider implementing external secret management (e.g., Windows DPAPI, keystore) as a longer-term hardening measure.
- Consultation6.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35992 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-35992 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data