← Back
UBUNTU-CVE-2014-3566
Vulnerability in openjdk-6 (UBUNTU-CVE-2014-3566)
Summary
vulnerability in openjdk-6 (UBUNTU-CVE-2014-3566). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `6b34-1.13.6-1ubuntu0.14.04.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **UBUNTU-CVE-2014-3566** has been found in openjdk-6.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade openjdk-6 to **6b34-1.13.6-1ubuntu0.14.04.1** or later.
If unsure, ask your IT team or search "openjdk-6 UBUNTU-CVE-2014-3566" on the vendor's site.
UBUNTU-CVE-2014-3566 (openjdk-6) —
Attack vector: remote (network-reachable) / unauthenticated
Patched: `6b34-1.13.6-1ubuntu0.14.04.1` — 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.
❓ What is the problem
**A vulnerability** (unclassified) exists in openjdk-6.
📍 Affected scope
openjdk-6 — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6b34-1.13.6-1ubuntu0.14.04.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'openjdk-6' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'openjdk-6' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `openjdk-6` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade openjdk-6 to 6b34-1.13.6-1ubuntu0.14.04.1ステージング環境で 6b34-1.13.6-1ubuntu0.14.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:14.04:LTS
openjdk-6
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6b34-1.13.6-1ubuntu0.14.04.1"}]}]
Ubuntu:14.04:LTS
openjdk-7
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7u75-2.5.4-1~trusty1"}]}]
Ubuntu:14.04:LTS
openssl
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.1f-1ubuntu2.7"}]}]
Ubuntu:Pro:14.04:LTS
pound
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:25.10
pound
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:26.04:LTS
pound
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- advisory https://ubuntu.com/security/notices/USN-2486-1
- advisory https://ubuntu.com/security/notices/USN-2487-1
- report https://ubuntu.com/security/CVE-2014-3566
- report https://www.openssl.org/~bodo/ssl-poodle.pdf
- report https://www.imperialviolet.org/2014/10/14/poodle.html
- report http://marc.info/?l=openssl-dev&m=141333049205629&w=2
- report https://blog.mozilla.org/security/2014/10/14/the-poodle-attack-and-the-end-of-ssl-3-0/
- report https://www.openssl.org/news/secadv_20141015.txt
- report http://askubuntu.com/a/537196
- report https://www.cve.org/CVERecord?id=CVE-2014-3566