Libksba vulnerabilitiesRanked by how likely they are to be used.
Libksba is made by Gnupg. We track 9 published vulnerabilities in it, across 52 versions. None of them is on the list of flaws known to be exploited today. If you run Libksba, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Libksba vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Libksba's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Libksba 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.
- 5.7%CVE-2014-9087High
Integer underflow in the ksba_oid_to_str function in Libksba before 1.3.2, as used in GnuPG, allows remote attackers to cause a denial of service (crash) via a crafted OID in a (1) S/MIME message or (2) ECC based...
- 3.3%CVE-2016-4579High
Libksba before 1.3.4 allows remote attackers to cause a denial of service (out-of-bounds read and crash) via unspecified vectors, related to the "returned length of the object from _ksba_ber_parse_tl."
- 3.3%CVE-2016-4356High
The append_utf8_value function in the DN decoder (dn.c) in Libksba before 1.3.3 allows remote attackers to cause a denial of service (out-of-bounds read) by clearing the high bit of the byte after invalid utf-8...
- 2.8%CVE-2016-4574High
Off-by-one error in the append_utf8_value function in the DN decoder (dn.c) in Libksba before 1.3.4 allows remote attackers to cause a denial of service (out-of-bounds read) via invalid utf-8 encoded data.
- 2.1%CVE-2016-4355High
Multiple integer overflows in ber-decoder.c in Libksba before 1.3.3 allow remote attackers to cause a denial of service (crash) via crafted BER data, which leads to a buffer overflow.
- 2.1%CVE-2016-4353High
ber-decoder.c in Libksba before 1.3.3 does not properly handle decoder stack overflows, which allows remote attackers to cause a denial of service (abort) via crafted BER data.
- 1.9%CVE-2016-4354High
ber-decoder.c in Libksba before 1.3.3 uses an incorrect integer data type, which allows remote attackers to cause a denial of service (crash) via crafted BER data, which leads to a buffer overflow.
- 1.6%CVE-2022-3515Critical
A vulnerability was found in the Libksba library due to an integer overflow within the CRL parser.
- 1.6%CVE-2022-47629Critical
Libksba before 1.6.3 is prone to an integer overflow vulnerability in the CRL signature parser.
Running Libksba? 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
Integer underflow in the ksba_oid_to_str function in Libksba before 1.3.2, as used in GnuPG, allows remote attackers to cause a denial of service (crash) via a crafted OID in a (1) S/MIME message or (2) ECC based OpenPGP data, which triggers a buffer overflow.
- Matched to
- Libksba 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 9 published vulnerabilities listed under the name Libksba, across 52 versions.
None of Libksba's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Libksba. 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.