CVE-2023-1633 json
Insecure barbican configuration file leaking credential
published 2023-09-24 3 y ago modified 2026-07-07 4 mo ago also GHSA-6qqp-4vm3-359v , PYSEC-2026-1213 , EUVD-2023-2449
- cvss
- 6.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
A credentials leak flaw was found in OpenStack Barbican. This flaw allows a local authenticated attacker to read the configuration file, gaining access to sensitive credentials.
Patch / fix
- openstack-barbican openstack 16.2 9.0.2-2.20230515185056.1cd585c.el8ost
red hat advisories RHSA-2023:6231
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-1633 updated cvss 6.6
openstack-barbican: Insecure Barbican configuration file leaking credential
-
Red Hat OpenStack Platform 13 (Queens) python-barbican, openstack-barbican, openstack-barbican-api, openstack-barbican-common, openstack-barbican-worker, openstack-barbican-keystone-listeneraffected: no fix planned “Out of support scope”
-
Red Hat OpenStack Platform 16.1 python3-barbican, openstack-barbican, openstack-barbican-api, openstack-barbican-common, openstack-barbican-worker, openstack-barbican-keystone-listeneraffected: no fix planned “Will not fix”
-
Red Hat OpenStack Platform 17.0 python3-barbican, openstack-barbican, openstack-barbican-api, openstack-barbican-common, openstack-barbican-worker, openstack-barbican-keystone-listener Red Hat OpenStack Platform 17.1 python3-barbican, openstack-barbican, openstack-barbican-api, openstack-barbican-common, openstack-barbican-worker, openstack-barbican-keystone-listeneraffected: no fix planned “Out of support scope”
-
Red Hat OpenStack Platform 18.0 openstack-barbicanaffected: no fix available “Fix deferred”
-
Red Hat OpenStack Platform 16.2 openstack-barbican 9.0.2-2.20230515185056.1cd585c.el8ostfixed: vendor fix RHSA-2023:6231
-
Red Hat OpenStack Platform 16.2 python3-barbican 9.0.2-2.20230515185056.1cd585c.el8ost, openstack-barbican-api 9.0.2-2.20230515185056.1cd585c.el8ost, openstack-barbican-common 9.0.2-2.20230515185056.1cd585c.el8ost, openstack-barbican-worker 9.0.2-2.20230515185056.1cd585c.el8ost, openstack-barbican-keystone-listener 9.0.2-2.20230515185056.1cd585c.el8ostnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.6 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 6.6 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
| OSV | 3.1 | 6.6 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | barbican | <=16.0.0 |
no fix listed |
Affected products
- n/a openstack-barbican
- Red Hat Red Hat OpenStack Platform 13 (Queens)
- Red Hat Red Hat OpenStack Platform 16.1
- Red Hat Red Hat OpenStack Platform 16.2
- Red Hat Red Hat OpenStack Platform 17.0
- RDO OpenStack RDO
Classification
References
-
access.redhat.com
/security/cve/CVE-2023-1633
vdb-entry, web, third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=2181761
issue-tracking, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-1633
advisory
-
github.com
/openstack/barbican
package
-
pypi.org
/project/barbican
package
-
github.com
/advisories/GHSA-6qqp-4vm3-359v
advisory
Sources
- CVE List CVE-2023-1633
- GitHub Advisory GHSA-6qqp-4vm3-359v
- NVD CVE-2023-1633
- OSV PYSEC-2026-1213
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.