Virtualization ManagerApplication · Redhat
CVE-2019-10194
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 · uneditedSensitive passwords used in deployment and configuration of oVirt Metrics, all versions. were found to be insufficiently protected. Passwords could be disclosed in log files (if playbooks are run with -v) or in playbooks stored on Metrics or Bastion hosts.
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 confidenceSensitive passwords used in oVirt Metrics deployment and configuration are being logged in plaintext when Ansible playbooks run with verbose mode (-v) or are stored in plaintext within playbooks on Metrics or Bastion hosts, leading to credential disclosure.
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
Virtualization ManagerApplication
= 4.3all versionsCVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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.
-
Check if oVirt Metrics or Bastion hosts exist in your environmentInventory your infrastructure for hosts designated as Metrics or Bastion servers that were deployed as part of oVirt setupAffected if You have Metrics or Bastion hosts deployed as part of your oVirt environment
-
Identify Ansible playbooks used for oVirt deploymentLocate any Ansible playbooks or playbook files stored on Metrics or Bastion hosts, or in your deployment repository, that were used to configure oVirtAffected if Deployment playbooks are stored on these hosts
-
Inspect playbooks for hardcoded plaintext passwordsSearch playbook files for password= or passwd= parameters and other credential assignments, looking for plaintext values rather than variable referencesAffected if Playbooks contain hardcoded passwords in plaintext rather than using variable references or secure credential storage
-
Review Ansible log files for credential exposureExamine Ansible log files on Metrics or Bastion hosts, and any centralized logging locations, for plaintext passwords that may have been printed during playbook execution with verbose modeAffected if Verbose mode (-v or higher) was used during playbook execution and logs contain plaintext passwords
-
Check for verbose logging configurationReview Ansible configuration files (ansible.cfg) and any automation scripts to determine if verbose logging was enabled during deploymentAffected if Verbose logging was enabled in Ansible configuration or command execution
Your environment is affected if you deployed oVirt Metrics or Bastion hosts using Ansible playbooks that contain plaintext passwords or were run with verbose logging, resulting in credential exposure in logs or playbook files.
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 dataRotate all exposed passwords immediately, remove plaintext credentials from playbooks, implement secure credential storage (e.g., Ansible Vault, secrets management), avoid verbose logging of playbook execution, and clean or secure log files containing exposed credentials.
Fix this in Virtualization Manager
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10194 — 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-2019-10194 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