Improper Certificate Validation Affecting botan package, versions <2.5.0-r0
Threat Intelligence
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 ID SNYK-ALPINE320-BOTAN-7008452
- published 23 May 2024
- disclosed 2 Apr 2018
Introduced: 2 Apr 2018
CVE-2018-9127 Open this link in a new tabHow to fix?
Upgrade Alpine:3.20
botan
to version 2.5.0-r0 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 Alpine
.
See How to fix?
for Alpine:3.20
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.