# CVE-2022-3100: Auth bypass in Red Hat OpenStack Platform > Attackers can bypass access policies in OpenStack Barbican via query strings, potentially accessing restricted API resources. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 18 Jan 2023 - **Updated:** 3 Apr 2025 - **Also known as:** DEBIAN-CVE-2022-3100, DLA-3136-1, DSA-5247-1, GHSA-5hg3-ffv7-g5ff, RHSA-2022:6750, SUSE-SU-2023:0071-1, UBUNTU-CVE-2022-3100, USN-5697-1 ## What is CVE-2022-3100? CVE-2022-3100 is a medium-severity authentication bypass vulnerability in Redhat Openstack, published on 18 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A flaw was found in the openstack-barbican component. This issue allows an access policy bypass via a query string when accessing the API. Weakness: CWE-305 (Authentication Bypass by Primary Weakness) ## Which versions are affected by CVE-2022-3100? It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `openstack-barbican` | Red Hat:openstack:13::el7 | All versions | 0:6.0.1-6.el7ost | | `openstack-barbican-api` | Red Hat:openstack:13::el7 | All versions | 0:6.0.1-6.el7ost | | `openstack-barbican-common` | Red Hat:openstack:13::el7 | All versions | 0:6.0.1-6.el7ost | | `openstack-barbican` | Red Hat:openstack:16.1::el8 | All versions | 0:9.0.1-1.20220112203416.07be198.el8ost | | `openstack-barbican-api` | Red Hat:openstack:16.1::el8 | All versions | 0:9.0.1-1.20220112203416.07be198.el8ost | | `openstack-barbican-common` | Red Hat:openstack:16.1::el8 | All versions | 0:9.0.1-1.20220112203416.07be198.el8ost | | `python3-barbican` | Red Hat:openstack:16.1::el8 | All versions | 0:9.0.1-1.20220112203416.07be198.el8ost | | `openstack-barbican` | Red Hat:openstack:16.2::el8 | All versions | 0:9.0.2-2.20220122185349.c718783.el8ost | | `openstack-barbican-api` | Red Hat:openstack:16.2::el8 | All versions | 0:9.0.2-2.20220122185349.c718783.el8ost | | `openstack-barbican-common` | Red Hat:openstack:16.2::el8 | All versions | 0:9.0.2-2.20220122185349.c718783.el8ost | | `python3-barbican` | Red Hat:openstack:16.2::el8 | All versions | 0:9.0.2-2.20220122185349.c718783.el8ost | | `openstack-barbican` | Red Hat:openstack:17.0::el9 | All versions | 0:12.0.1-0.20220614210405.486e607.el9ost | | `openstack-barbican-api` | Red Hat:openstack:17.0::el9 | All versions | 0:12.0.1-0.20220614210405.486e607.el9ost | | `openstack-barbican-common` | Red Hat:openstack:17.0::el9 | All versions | 0:12.0.1-0.20220614210405.486e607.el9ost | | `python3-barbican` | Red Hat:openstack:17.0::el9 | All versions | 0:12.0.1-0.20220614210405.486e607.el9ost | | `openstack-barbican` | SUSE:HPE Helion OpenStack 8 | All versions | 5.0.2~dev3-3.17.2 | | `openstack-barbican-doc` | SUSE:HPE Helion OpenStack 8 | All versions | 5.0.2~dev3-3.17.2 | | `venv-openstack-barbican` | SUSE:HPE Helion OpenStack 8 | All versions | 5.0.2~dev3-12.43.2 | | `openstack-barbican` | SUSE:OpenStack Cloud 8 | All versions | 5.0.2~dev3-3.17.2 | | `openstack-barbican-doc` | SUSE:OpenStack Cloud 8 | All versions | 5.0.2~dev3-3.17.2 | | `venv-openstack-barbican` | SUSE:OpenStack Cloud 8 | All versions | 5.0.2~dev3-12.43.2 | | `openstack-barbican` | SUSE:OpenStack Cloud Crowbar 8 | All versions | 5.0.2~dev3-3.17.2 | | `openstack-barbican-doc` | SUSE:OpenStack Cloud Crowbar 8 | All versions | 5.0.2~dev3-3.17.2 | Products: Openstack Barbican, Redhat Openstack, Redhat Openstack for Ibm Power, Redhat Openstack Platform. ## How do I fix CVE-2022-3100? Apply the vendor's patch. ## Is CVE-2022-3100 being exploited? There is no known exploitation of CVE-2022-3100 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Openstack - [CVE-2022-23451](https://insights.sbomify.com/CVE-2022-23451/): Barbican authorization flaw before v14.0.0 (high 8.1) - [CVE-2023-1633](https://insights.sbomify.com/CVE-2023-1633/): Insecure barbican configuration file leaking credential (medium 6.6) - [CVE-2023-1636](https://insights.sbomify.com/CVE-2023-1636/): Incomplete container isolation (medium 6.0) - [CVE-2022-23452](https://insights.sbomify.com/CVE-2022-23452/): openstack-barbican Denial of Service vulnerability (medium 4.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-3100 and fix it if it is affected. What it is: CVE-2022-3100 is a medium-severity authentication bypass vulnerability in Redhat Openstack, published on 18 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-3100 in the wild and no public exploit code. Affected product: Redhat Openstack. 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-3100/ (Markdown: https://insights.sbomify.com/CVE-2022-3100/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3100 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3100 - OSV: https://osv.dev/vulnerability/CVE-2022-3100 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-3100/ Summaries are generated and may contain mistakes; the official description above is the record.