Back to Database
Status published
Unknown
CVE-2022-32531
Apache BookKeeper: Java Client Uses Connection to Host that Failed Hostname Verification
Vulnerability 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.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
THREAT MONITOR
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2022-32531
Credits & Attribution
No credits recorded in the NVD database.
More from Apache Software Foundation
View All →CVE-2025-69233
Apache CloudStack: Domain/account resources limits not honored
Medium
6.5
CVE-2025-69219
Apache Airflow Providers Http: Unsafe Pickle Deserialization in apache-airflow-providers-http leading to RCE via HttpOperator
Unknown
0
CVE-2025-68675
Apache Airflow: proxy credentials for various providers might leak in task logs
Unknown
0
CVE-2025-68637
Apache Uniffle: Insecure SSL Configuration in Uniffle HTTP Client
Unknown
0
CVE-2025-68493
Apache Struts, Apache Struts: XXE vulnerability in outdated XWork component
Unknown
0
Affected Vendor
Apache Software Foundation
View all reports →Affected Software
Apache BookKeeper
Vulnerable Versions:
0, 4.15.0
Timeline
Official Publish:
December 15th, 2022
Last Modified:
April 17th, 2025
Added to House:
July 21st, 2026
CVSS Vectors
No vector data available