Apache BookKeeper: Java Client Uses Connection to Host that Failed Hostname Verification
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache BookKeeper | unaffected |
|
Configuration 1 [-]
|
No data.
No data available yet.
Vendor Solution
Upgrade to 4.14.6 or to 4.15.1
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-0020 | 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\nthe bookkeeper client vulnerable to a man in the middle attack.\n\nThe problem affects BookKeeper client prior to versions 4.14.6 and 4.15.1. |
Github GHSA |
GHSA-gxq5-79m2-gvvq | Apache Bookkeeper vulnerable to Improper Certificate Validation |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.1% (1.088% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|