dbcve.org
OpenstackApplication · Redhat

CVE-2022-3100

MEDIUM · 5.9 CVSS v3.1 Published 2023-01-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A flaw was found in the openstack-barbican component. This issue allows an access policy bypass via a query string when accessing the API.

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 · moderate confidence

OpenStack Barbican (Key Manager) has an access policy bypass vulnerability where query string parameters in API requests can be used to circumvent access control checks. An authenticated user could potentially access resources or operations outside their intended permission scope by manipulating query strings in API calls.

MitigationApply the vendor patch for CVE-2022-3100 to Barbican, which should enforce proper validation of query string parameters against access policies. Verify that keystone integration properly validates all request parameters.

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
OpenstackApplication
Affected:= 13= 16.1= 16.2= 17
Openstack For Ibm PowerApplication
Affected:= 13= 16.1= 16.2
Openstack PlatformApplication
Affected:= 13.0
BarbicanApplication
Affected:all versions

CVSS 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
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Barbican service is running
    Check if the Barbican (key-manager) service is deployed in your OpenStack environment. Run 'openstack service list' or check the keystone catalog for 'barbican' service type.
    Affected if Barbican service is listed and active in the environment
  2. Identify installed Barbican version
    Run 'barbican-manage --version' or check the package version via 'pip show barbican' or your package manager (e.g., 'rpm -q python-barbican').
    Affected if Version is unpatched or all versions (if no version info available, assume affected)
  3. Check OpenStack platform version
    Run 'openstack version show' or check /etc/rhosp-release for Red Hat OpenStack versions 13, 16.1, 16.2, or 17.
    Affected if Running Red Hat OpenStack 13, 16.1, 16.2, or 17 without the CVE-2022-3100 patch applied
  4. Verify access policy configuration
    Locate and inspect the policy.json file for Barbican, typically at /etc/barbican/policy.json or within the Barbican container at /etc/barbican/policy.json. Check for any policy rules that rely on query string parameters.
    Affected if Policy rules do not explicitly validate query parameters or use overly permissive wildcard rules
  5. Test query string parameter handling
    As an authenticated user with limited permissions, attempt an API request to Barbican with modified query string parameters (e.g., ?project_id=alternate_project) to see if access control is bypassed.
    Affected if User can access resources or perform operations outside their assigned role permissions

You are affected if Barbican is running and the installed version or OpenStack platform version matches the affected ranges without the CVE-2022-3100 patch applied, or if access policies do not properly validate query string parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch for CVE-2022-3100 to Barbican, which should enforce proper validation of query string parameters against access policies. Verify that keystone integration properly validates all request parameters.

Fix this in Openstack Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3100 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3100 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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