Improper Certificate Validation Affecting botan package, versions <2.4.0-5
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN10-BOTAN-268771
- published2 Apr 2018
- disclosed2 Apr 2018
Introduced: 2 Apr 2018
CVE-2018-9127 (opens in a new tab)How to fix?
Upgrade Debian:10 botan to version 2.4.0-5 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream botan package and not the botan package as distributed by Debian.
See How to fix? for Debian:10 relevant fixed versions and status.
Botan 2.2.0 - 2.4.0 (fixed in 2.5.0) improperly handled wildcard certificates and could accept certain certificates as valid for hostnames when, under RFC 6125 rules, they should not match. This only affects certificates issued to the same domain as the host, so to impersonate a host one must already have a wildcard certificate matching other hosts in the same domain. For example, b*.example.com would match some hostnames that do not begin with a 'b' character.