Bookkeeper vulnerabilitiesRanked by how likely they are to be used.
Bookkeeper is made by Apache. We track 7 published vulnerabilities in it, across 39 versions. None of them is on the list of flaws known to be exploited today. If you run Bookkeeper, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Bookkeeper vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Bookkeeper's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Bookkeeper flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 70%CVE-2019-17571Critical
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when...
- 12%CVE-2020-36230High
A flaw was discovered in OpenLDAP before 2.4.57 leading in an assertion failure in slapd in the X.509 DN parsing in decode.c ber_next_element, resulting in denial of service.
- 11%CVE-2019-19924Medium
SQLite 3.30.1 mishandles certain parser-tree rewriting, related to expr.c, vdbeaux.c, and window.c.
- 8.0%CVE-2019-19906High
cyrus-sasl (aka Cyrus SASL) 2.1.27 has an out-of-bounds write leading to unauthenticated remote denial-of-service in OpenLDAP via a malformed LDAP packet.
- 5.6%CVE-2017-6891High
Two errors in the "asn1_find_node()" function (lib/parser_aux.c) within GnuTLS libtasn1 version 4.10 can be exploited to cause a stacked-based buffer overflow by tricking a user into processing a specially crafted...
- 2.2%CVE-2020-23922High
An issue was discovered in giflib through 5.1.4.
- 1.1%CVE-2022-32531Medium
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.
Running Bookkeeper? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
- Matched to
- Bookkeeper on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 7 published vulnerabilities listed under the name Bookkeeper, across 39 versions.
None of Bookkeeper's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Bookkeeper. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.