LiveActive security incident?Get immediate response
CVE Record

CVE-2020-35992: Fiserv Prologue through 2020-12-16 does not properly protect the database password.

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE describes weak protection of a database password in Fiserv Prologue through 2020-12-16. If someone can access the Prologue configuration file, they may decrypt the stored database password and reach sensitive financial records. The sources do not provide a CVSS score, named patch, or evidence of active exploitation.

Executive priority

Prioritize if Prologue supports financial records or if database access is reachable beyond tightly controlled application hosts. The main business risk is credential exposure leading to customer financial data access.

Technical view

The issue concerns the LogPassword attribute in appconfig.ini. The CVE states that an attacker with access to that configuration file can decrypt the stored password, yielding cleartext database credentials. In some cases, those credentials may allow remote database login. Public details are limited and no CWE or CVSS vector is provided.

Likely exposure

Likely exposure is limited to organizations running Fiserv Prologue through 2020-12-16, especially where appconfig.ini is readable by unauthorized users or the database accepts remote logins using the stored account.

Exploitation context

The CVE is not listed as KEV in the supplied bundle. A public GitHub reference exists, but the bundle does not prove active exploitation. The described attack depends on prior access to the Prologue configuration file.

Researcher notes

Evidence is sparse: no CVSS, CWE, vendor advisory, or patch details are included. Treat the GitHub reference as public technical context, not proof of exploitation. Validation should focus on configuration access, credential rotation, and database reachability.

Mitigation direction

  • Contact Fiserv for supported Prologue remediation guidance.
  • Restrict access to Prologue configuration files.
  • Rotate database credentials stored in affected configurations.
  • Limit database access to required hosts and service accounts.
  • Review logs for suspicious configuration file or database access.

Validation and detection

  • Inventory Prologue deployments and confirm version dates.
  • Check whether appconfig.ini contains a LogPassword value.
  • Verify only authorized accounts can read configuration files.
  • Confirm database accounts use least required privileges.
  • Review database authentication logs for unusual access.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-35992 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.