Approved changes feed: RSS · Atom

cpe:2.3:a:apache:bookkeeper:4.15.0:rc0:*:*:*:*:*:*

part: a version: 4.15.0 update: rc0

VendorApache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95)
ProductBookkeeper (59000153-8cf4-5ae0-b54f-7e28f8be79df)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:apache/bookkeeper purl2cpe 2026-06-01 10:14:24.899524
pkg:deb/debian/bookkeeper purl2cpe 2026-06-01 10:14:24.899525
pkg:deb/ubuntu/bookkeeper purl2cpe 2026-06-01 10:14:24.899526
pkg:docker/apache/bookkeeper purl2cpe 2026-06-01 10:14:24.899528
pkg:github/apache/bookkeeper purl2cpe 2026-06-01 10:14:24.899529
pkg:maven/org.apache.bookkeeper/bookkeeper purl2cpe 2026-06-01 10:14:24.899530

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2022-32531 vulnerable 2026-06-08 05:44:44.929462 Apache BookKeeper: Java Client Uses Connection to Host that Failed Hostname Verification
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.
Published: 2022-12-15T10:17:19.660Z
Updated: 2025-04-17T18:20:47.178Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.