dbcve.org
VirtualizationApplication · Redhat

CVE-2022-2805

MEDIUM · 6.5 CVSS v3.1 Published 2022-10-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A flaw was found in ovirt-engine, which leads to the logging of plaintext passwords in the log file when using otapi-style. This flaw allows an attacker with sufficient privileges to read the log file, leading to confidentiality loss.

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 confidence

The ovirt-engine component logs plaintext passwords to log files when using otapi-style authentication. This occurs because passwords are being written directly to logs without redaction or masking, allowing any attacker with sufficient file system privileges to obtain credentials by reading the logs.

MitigationConfigure log output to redact or mask sensitive fields like passwords before logging, or modify the otapi authentication code to prevent password data from reaching log handlers.

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
VirtualizationApplication
Affected:= 4.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Redhat Virtualization version
    Run 'rpm -q redhat-release' or check /etc/redhat-release to determine the exact version number of the installed Redhat Virtualization environment
    Affected if The version equals 4.0 exactly, indicating the environment matches the affected version range
  2. Determine if otapi-style authentication is in use
    Review the ovirt-engine configuration files (typically in /etc/ovirt-engine/ or as defined in your deployment) for otapi authentication settings, or check for otapi client connections in active session logs
    Affected if otapi-style authentication is enabled or has been used, as this is the required condition for the vulnerable code path to execute
  3. Locate ovirt-engine log directories
    Identify where ovirt-engine writes its log files. Common paths include /var/log/ovirt-engine/ or the configured log directory from your ovirt-engine setup. Check engine logs and any integrated service logs
    Affected if Log directories exist and contain ovirt-engine logs, as these are the files potentially containing plaintext passwords
  4. Search log files for plaintext password patterns
    Use grep or similar tools to search log files for strings resembling passwords (keywords like 'password', 'passwd', or patterns of alphanumeric strings following password fields) appearing in plain text without masking characters
    Affected if Log files contain any plaintext password strings or credential values that appear unmasked, confirming the vulnerability is present in the environment
  5. Verify log configuration for password redaction settings
    Examine ovirt-engine logging configuration files for settings related to password masking, redaction, or sensitive data filtering in log output
    Affected if No password redaction or masking is configured, or configuration explicitly allows sensitive fields to be logged in plaintext

The environment is affected if it runs Redhat Virtualization 4.0 with otapi-style authentication enabled and log files contain plaintext passwords without redaction.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure log output to redact or mask sensitive fields like passwords before logging, or modify the otapi authentication code to prevent password data from reaching log handlers.

Fix this in Virtualization Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2805 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-2805 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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