Vulnerability in botan
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as DEBIAN-CVE-2018-9127 has been found in botan.
Successful exploitation can lead to full system takeover.
What to do: upgrade botan to 2.5.0 or later.
If unsure, ask your IT team or search "botan DEBIAN-CVE-2018-9127" on the vendor's site.
DEBIAN-CVE-2018-9127 (botan)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.5.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in botan.
Check the vendor advisory for the affected versions of botan.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2.5.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'botan' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'botan' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
botanを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade botan to 2.5.0ステージング環境で 2.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Debian:12 | botan |
< 2.4.0-5 |
2.4.0-5 |
| Debian:13 | botan |
< 2.4.0-5 |
2.4.0-5 |
Original description The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory security-tracker.debian.org