# CVE-2022-0207: Race condition in vdsm > A race condition in vdsm may cause sensitive values to be stored in clear text in log files, leading to information disclosure. - **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 Aug 2022 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-32qr-rh8p-qfq7, RHSA-2022:4764 ## What is CVE-2022-0207? CVE-2022-0207 is a medium-severity vulnerability in Redhat Virtualization, published on 26 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A race condition was found in vdsm. Functionality to obfuscate sensitive values in log files that may lead to values being stored in clear text. Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization) ## Which versions are affected by CVE-2022-0207? It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `vdsm` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-api` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-client` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-common` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-gluster` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-hook-checkips` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-hook-cpuflags` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-hook-ethtool-options` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-hook-extra-ipv4-addrs` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-hook-fcoe` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-hook-localdisk` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-hook-nestedvt` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-hook-openstacknet` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-hook-vhostmd` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-http` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-jsonrpc` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-network` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-python` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | | `vdsm-yajsonrpc` | Red Hat:rhev_hypervisor:4.4::el8 | All versions | 0:4.50.0.13-1.el8ev | Products: Ovirt Vdsm, Redhat Virtualization, Redhat Virtualization for Ibm Power Little Endian, Redhat Virtualization Host. ## How do I fix CVE-2022-0207? Apply the vendor's patch. ## Is CVE-2022-0207 being exploited? There is no known exploitation of CVE-2022-0207 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Virtualization - [CVE-2012-5518](https://insights.sbomify.com/CVE-2012-5518/): Auth bypass in vdsm (high 7.5) - [CVE-2018-10908](https://insights.sbomify.com/CVE-2018-10908/): Denial of service in vdsm (medium 6.5) - [CVE-2019-3831](https://insights.sbomify.com/CVE-2019-3831/): Privilege escalation in vdsm (medium 6.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-0207 and fix it if it is affected. What it is: CVE-2022-0207 is a medium-severity vulnerability in Redhat Virtualization, published on 26 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-0207 in the wild and no public exploit code. Affected product: Redhat Virtualization. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-0207/ (Markdown: https://insights.sbomify.com/CVE-2022-0207/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0207 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0207 - OSV: https://osv.dev/vulnerability/CVE-2022-0207 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-0207/ Summaries are generated and may contain mistakes; the official description above is the record.