← Back
CVE-2017-12626
high
CVSS 7.5
Vulnerability in org.apache.poi:poi (CVE-2017-12626)
Summary
vulnerability in org.apache.poi:poi (CVE-2017-12626). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `3.17` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2017-12626** has been found in org.apache.poi:poi.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade org.apache.poi:poi to **3.17** or later.
If unsure, ask your IT team or search "org.apache.poi:poi CVE-2017-12626" on the vendor's site.
CVE-2017-12626 (org.apache.poi:poi) — CWE-835 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `3.17` — 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** (CWE-835) exists in org.apache.poi:poi.
📍 Affected scope
org.apache.poi:poi — .
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.17**.
🛡️ 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 'org.apache.poi:poi' .` 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 'org.apache.poi:poi' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.apache.poi:poi` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.apache.poi:poi to 3.17ステージング環境で 3.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.apache.poi:poi
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.17"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2017-12626
- package https://github.com/apache/poi
- web http://www.securityfocus.com/bid/102879
- web https://access.redhat.com/errata/RHSA-2018:1322
- web https://lists.apache.org/thread.html/453d9af5dbabaccd9afb58d27279a9dbfe8e35f4e5ea1645ddd6960b%40%3Cdev.poi.apache.org%3E
- web https://lists.apache.org/thread.html/708d94141126eac03011144a971a6411fcac16d9c248d1d535a39451%40%3Csolr-user.lucene.apache.org%3E
- web https://www.oracle.com/security-alerts/cpuApr2021.html
- web https://www.oracle.com/security-alerts/cpuapr2020.html
- web https://www.oracle.com/security-alerts/cpujan2020.html
- web https://www.oracle.com/security-alerts/cpujan2021.html
- web https://www.oracle.com/security-alerts/cpujul2020.html
- web https://www.oracle.com/security-alerts/cpuoct2020.html
- web https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html
- web https://lists.apache.org/thread.html/453d9af5dbabaccd9afb58d27279a9dbfe8e35f4e5ea1645ddd6960b@%3Cdev.poi.apache.org%3E
- web https://lists.apache.org/thread.html/708d94141126eac03011144a971a6411fcac16d9c248d1d535a39451@%3Csolr-user.lucene.apache.org%3E
- web https://github.com/advisories/GHSA-523c-xh4g-mh5m