Vulnerability in Big Ip Ltm (CVE-2017-6168)
Summary
Vulnerability in Big Ip Ltm (CVE-2017-6168). Confidential information can be exposed externally. Mitigation: upgrade to 11.6.2 or later.
Original description
The description as published by the source.
On BIG-IP versions 11.6.0-11.6.2 (fixed in 11.6.2 HF1), 12.0.0-12.1.2 HF1 (fixed in 12.1.2 HF2), or 13.0.0-13.0.0 HF2 (fixed in 13.0.0 HF3) a virtual server configured with a Client SSL profile may be vulnerable to an Adaptive Chosen Ciphertext attack (AKA Bleichenbacher attack) against RSA, which when exploited, may result in plaintext recovery of encrypted messages and/or a Man-in-the-middle (MiTM) attack, despite the attacker not having gained access to the server's private key itself, aka a ROBOT attack.
Source: NIST National Vulnerability Database NVD
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 CVE-2017-6168 has been found in Big Ip Ltm.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: upgrade Big Ip Ltm to 11.6.2 or later.
If unsure, ask your IT team or search "Big Ip Ltm CVE-2017-6168" on the vendor's site.
CVE-2017-6168 (Big Ip Ltm) — CWE-203 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 11.6.2 — 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 (CWE-203) exists in Big Ip Ltm.
Check the vendor advisory for the affected versions of Big Ip Ltm.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
Update to 11.6.2.
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. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Big Ip Ltm を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Big Ip Ltm to 11.6.2ステージング環境で 11.6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory securityfocus.com
- advisory securitytracker.com
- advisory robotattack.org
- advisory kb.cert.org
- patch support.f5.com