Skip to content
Fencer Intel
medium 5.3

CVE-2022-41316 json

HashiCorp Vault's revocation list not respected

published 4y ago modified last mo. also BIT-vault-2022-41316 , EUVD-2023-2017 , GHSA-9mh8-9j64-443f , GO-2023-1897

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

Summary

HashiCorp Vault and Vault Enterprise’s TLS certificate auth method did not initially load the optionally configured CRL issued by the role's CA into memory on startup, resulting in the revocation list not being checked if the CRL has not yet been retrieved. Fixed in 1.12.0, 1.11.4, 1.10.7, and 1.9.10.

Patch / fix

  • go github.com/hashicorp/vault 1.9.10, 1.10.7, 1.11.4
  • bitnami vault 1.9.10, 1.10.7, 1.11.4
  • hashicorp vault 1.9.10, 1.10.7, 1.11.4
  • vault Alpine 3.16 1.10.7-r0
  • vault Alpine 3.18, Alpine 3.17 1.11.4-r0

alpine advisories ALPINE-CVE-2022-41316

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-41316 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2022-41316 updated cvss 5.3

vault: insufficient certificate revocation list checking

  • Red Hat OpenShift Container Platform 4 openshift4/topology-aware-lifecycle-manager-rhel8-operator
    affected: no fix available
  • Red Hat Openshift Container Storage 4 ocs4/cephcsi-rhel8, ocs4/mcg-rhel8-operator, ocs4/ocs-rhel8-operator, ocs4/rook-ceph-rhel8-operator
    affected: no fix planned “Out of support scope”
  • Red Hat Openshift Data Foundation 4 ocs4/mcg-rhel8-operator, odf4/ocs-rhel9-operator, odf4/odf-rhel8-operator, odf4/odr-rhel8-operator, odf4/odf-multicluster-rhel9-operator
    affected: no fix available, no fix planned “Will not fix”
  • Red Hat OpenShift Container Platform 4.12 openshift4/ose-installer v4.12.0-202301090455.p0.gba94031.assembly.stream
    fixed: vendor fix RHSA-2022:7399
  • Red Hat OpenShift Container Platform 4.13 openshift4/ose-installer v4.13.0-202305091542.p0.g44db7b2.assembly.stream
    fixed: vendor fix RHSA-2023:1326
  • Red Hat RHODF 4.13 for RHEL 9 odf4/mcg-rhel9-operator v4.13.0-41, odf4/rook-ceph-rhel9-operator v4.13.0-70
    fixed: vendor fix RHSA-2023:3742
  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/logging-loki-rhel8 Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/cluster-curator-controller-rhel8, rhacm2/managedcluster-import-controller-rhel8 Red Hat OpenShift Container Platform 4.12 openshift4/ose-cli v4.12.0-202301042354.p0.g854f807.assembly.stream, openshift4/ose-pod v4.12.0-202301042354.p0.g77bec7a.assembly.stream, openshift4/ose-etcd v4.12.0-202212121125.p0.g89a451c.assembly.stream, openshift4/ose-tests v4.12.0-202301050335.p0.g5e41b22.assembly.stream, openshift4/ose-console v4.12.0-202301062016.p0.gb237c34.assembly.stream, openshift4/ose-coredns v4.12.0-202301042354.p0.g9aaa7e0.assembly.stream, +172 more Red Hat OpenShift Container Platform 4.13 openshift4/ose-cli v4.13.0-202304190216.p0.g92b1a3d.assembly.stream, openshift4/ose-pod v4.13.0-202304211155.p0.gb404935.assembly.stream, openshift4/ose-etcd v4.13.0-202304190216.p0.gf70da9d.assembly.stream, openshift4/ose-tests v4.13.0-202305031828.p0.g893ae57.assembly.stream, openshift4/ose-console v4.13.0-202305031828.p0.ga551d28.assembly.stream, openshift4/ose-coredns v4.13.0-202304190216.p0.g5560e4a.assembly.stream, +174 more Red Hat Openshift Data Foundation 4 odf4/cephcsi-rhel9 Red Hat RHODF 4.13 for RHEL 9 odf4/cephcsi-rhel9 v4.13.0-35, odf4/mcg-cli-rhel9 v4.13.0-17, odf4/mcg-core-rhel9 v4.13.0-41, odf4/odf-console-rhel9 v4.13.0-85, odf4/ocs-rhel9-operator v4.13.0-67, odf4/odf-rhel9-operator v4.13.0-24, +16 more
    not 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
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/vault
>=1.11.0, <1.11.4
>=1.10.0, <1.10.7
<1.9.10
1.11.4
1.10.7
1.9.10
bitnami vault
<1.9.10
>=1.10.0, <1.10.7
>=1.11.0, <1.11.4
1.9.10
1.10.7
1.11.4

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Intel 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.