What is CVE-2022-44020?

CVE-2022-44020 is a medium-severity security vulnerability in sushy-tools (pip), affecting versions < 0.21.1. It is fixed in 0.21.1, 3.0.0.

How severe is CVE-2022-44020?

CVE-2022-44020 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2022-44020?

sushy-tools (pip) versions < 0.21.1; virtualbmc (pip) versions < 3.0.0.

Is there a fix for CVE-2022-44020?

Yes. CVE-2022-44020 is fixed in 0.21.1, 3.0.0. Upgrade to this version or later.

Is CVE-2022-44020 exploitable, and should I be worried?

Whether CVE-2022-44020 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-44020 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-44020?

Upgrade: sushy-tools to 0.21.1 or later, virtualbmc to 3.0.0 or later.

CVE-2022-44020 in sushy-tools

Q: How severe is CVE-2022-44020?

CVE-2022-44020 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2022-44020?

sushy-tools (pip) versions < 0.21.1; virtualbmc (pip) versions < 3.0.0.

Q: Is there a fix for CVE-2022-44020?

Yes. CVE-2022-44020 is fixed in 0.21.1, 3.0.0. Upgrade to this version or later.

Q: Is CVE-2022-44020 exploitable, and should I be worried?

Whether CVE-2022-44020 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-44020 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-44020?

Upgrade: sushy-tools to 0.21.1 or later, virtualbmc to 3.0.0 or later.

Summary

OpenStack Sushy-Tools and VirtualBMC Improper Preservation of Permissions

An issue was discovered in OpenStack Sushy-Tools through 0.21.0 and VirtualBMC through 2.2.2. Changing the boot device configuration with these packages removes password protection from the managed libvirt XML domain. NOTE: this only affects an "unsupported, production-like configuration."

Impact

CVE-2022-44020 has a CVSS score of 5.5 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.21.1, 3.0.0); upgrading removes the vulnerable code path.

Affected versions

sushy-tools (< 0.21.1) virtualbmc (< 3.0.0)

Security releases

sushy-tools → 0.21.1 (pip) virtualbmc → 3.0.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

sushy-tools to 0.21.1 or later; virtualbmc to 3.0.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-44020? CVE-2022-44020 is a medium-severity security vulnerability in sushy-tools (pip), affecting versions < 0.21.1. It is fixed in 0.21.1, 3.0.0.
How severe is CVE-2022-44020? CVE-2022-44020 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2022-44020?
- sushy-tools (pip) (versions < 0.21.1)
- virtualbmc (pip) (versions < 3.0.0)
Is there a fix for CVE-2022-44020? Yes. CVE-2022-44020 is fixed in 0.21.1, 3.0.0. Upgrade to this version or later.
Is CVE-2022-44020 exploitable, and should I be worried? Whether CVE-2022-44020 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-44020 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-44020?
- Upgrade sushy-tools to 0.21.1 or later
- Upgrade virtualbmc to 3.0.0 or later