CVE-2022-32531

Apache BookKeeper: Java Client Uses Connection to Host that Failed Hostname Verification

Description

The Apache Bookkeeper Java Client (before 4.14.6 and also 4.15.0) does not close the connection to the bookkeeper server when TLS hostname verification fails. This leaves the bookkeeper client vulnerable to a man in the middle attack. The problem affects BookKeeper client prior to versions 4.14.6 and 4.15.1.

Remediation

Solution:

  • Upgrade to 4.14.6 or to 4.15.1

Category

5.9
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.12%
Vendor Advisory apache.org
Affected: Apache Software Foundation Apache BookKeeper
Published at:
Updated at:

References

Link Tags
https://lists.apache.org/thread/xyk2lfc7lzof8mksmwyympbqxts1b5s9 mailing list vendor advisory

Frequently Asked Questions

What is the severity of CVE-2022-32531?
CVE-2022-32531 has been scored as a medium severity vulnerability.
How to fix CVE-2022-32531?
To fix CVE-2022-32531: Upgrade to 4.14.6 or to 4.15.1
Is CVE-2022-32531 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-32531 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-32531?
CVE-2022-32531 affects Apache Software Foundation Apache BookKeeper.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.