CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2018 · Botan Project

CVE-2018-9127
Botan Project Botan vulnerability

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.

High priority: this vulnerability is rated critical and can be attacked over the network without a login.

Affected products

Botan. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Botan Project Botan runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.

References

More vulnerabilities in Botan Project products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.