FedoraOperating system · Fedoraproject
CVE-2022-0725
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 · uneditedA flaw was found in keepass. The vulnerability occurs due to logging the plain text passwords in system log and leads to an Information Exposure vulnerability. This flaw allows an attacker to interact and read sensitive passwords and logs.
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 confidenceKeepass improperly logs plain-text passwords to the system log, exposing sensitive credentials through standard log files. This information disclosure vulnerability allows any actor with log access to retrieve user passwords in clear text.
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
FedoraOperating system
= 35= 2.48= 7.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 KeePass installation and versionRun 'keepass --version' or check your package manager (rpm -q keepass, dpkg -l keepass) to find the installed KeePass versionAffected if Installed version equals exactly 2.48
-
Check operating system versionRun 'cat /etc/os-release' or 'cat /etc/redhat-release' to identify your OS versionAffected if Running Fedora 35 or EPEL 7.0 for Enterprise Linux
-
Locate KeePass log filesSearch for log files in common locations: ~/.config/KeePass/logs/, /var/log/, or check KeePass settings for custom log pathsAffected if Log files exist and contain entries from KeePass
-
Inspect log files for plaintext passwordsUse 'grep -i password <filename>' or manually examine identified log files for any plaintext credential stringsAffected if Log files contain any plaintext passwords or sensitive credential data in clear text
You are affected if KeePass version 2.48 is installed on Fedora 35 or EPEL 7.0, and log files contain plaintext passwords due to improper logging configuration.
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.
dbcve · scopedModify logging code to exclude password data from log output, either by removing password logging entirely or implementing proper masking/redaction of sensitive fields before logging.
Keepass 2.49 or later
- Upgrade Keepass from version 2.48 to a version that addresses the plain text password logging vulnerability (2.49 or later recommended)
- Verify that logging configuration does not write sensitive password data to system logs
- After upgrade, review system logs to confirm no plain text passwords were previously logged
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fedora
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0725 — 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-2022-0725 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