CVE-2022-47951

An issue was discovered in OpenStack Cinder before 19.1.2, 20.x before 20.0.2, and 21.0.0; Glance before 23.0.1, 24.x before 24.1.1, and 25.0.0; and Nova before 24.1.2, 25.x before 25.0.2, and 26.0.0. By supplying a specially created VMDK flat image that references a specific backing file path, an authenticated user may convince systems to return a copy of that file's contents from the server, resulting in unauthorized access to potentially sensitive data.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2022-47951 has a CVSS score of 5.7 (Medium). The vector is network-reachable, low privileges required, and user interaction required. 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 (19.1.2, 20.0.2, 23.0.1, 24.1.1, 24.1.2, 25.0.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2022-47951? CVE-2022-47951 is a medium-severity path traversal vulnerability in cinder (pip), affecting versions < 19.1.2. It is fixed in 19.1.2, 20.0.2, 23.0.1, 24.1.1, 24.1.2, 25.0.2. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2022-47951? CVE-2022-47951 has a CVSS score of 5.7 (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.
3. Which packages are affected by CVE-2022-47951?
   • cinder (pip) (versions < 19.1.2)
   • glance (pip) (versions < 23.0.1)
   • nova (pip) (versions < 24.1.2)
4. Is there a fix for CVE-2022-47951? Yes. CVE-2022-47951 is fixed in 19.1.2, 20.0.2, 23.0.1, 24.1.1, 24.1.2, 25.0.2. Upgrade to this version or later.
5. Is CVE-2022-47951 exploitable, and should I be worried? Whether CVE-2022-47951 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
6. What actually determines whether CVE-2022-47951 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.
7. How do I fix CVE-2022-47951?
   • Upgrade cinder to 19.1.2 or later
   • Upgrade cinder to 20.0.2 or later
   • Upgrade glance to 23.0.1 or later
   • Upgrade glance to 24.1.1 or later
   • Upgrade nova to 24.1.2 or later
   • Upgrade nova to 25.0.2 or later