← Back
CVE-2016-4000
critical
CVSS 9.8
Unsafe Deserialization in org.python:jython-standalone (CVE-2016-4000)
Summary
vulnerability in org.python:jython-standalone (CVE-2016-4000). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `2.7.1b3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2016-4000** has been found in org.python:jython-standalone.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade org.python:jython-standalone to **2.7.1b3** or later.
If unsure, ask your IT team or search "org.python:jython-standalone CVE-2016-4000" on the vendor's site.
CVE-2016-4000 (org.python:jython-standalone) — CWE-502 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `2.7.1b3` — 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
**unsafe deserialization** (CWE-502) exists in org.python:jython-standalone.
📍 Affected scope
org.python:jython-standalone — .
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.7.1b3**.
🛡️ 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.python:jython-standalone' .` 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.python:jython-standalone' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.python:jython-standalone` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.python:jython-standalone to 2.7.1b3ステージング環境で 2.7.1b3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.python:jython-standalone
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.7.1b3"}]}]
maven
org.python:jython
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.7.1b3"}]}]
References
- web http://bugs.jython.org/issue2454
- web http://www.debian.org/security/2017/dsa-3893
- web http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html
- web af854a3a-2127-422b-91ae-364da2661108
- web https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864859
- web https://hg.python.org/jython/file/v2.7.1rc1/NEWS
- web https://hg.python.org/jython/rev/d06e29d100c0
- web af854a3a-2127-422b-91ae-364da2661108
- web https://security-tracker.debian.org/tracker/CVE-2016-4000
- web https://security.gentoo.org/glsa/201710-28
- web https://snyk.io/vuln/SNYK-JAVA-ORGPYTHON-31451
- 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/cpujul2020.html
- web https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html
- web https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html
- web https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html
- web https://nvd.nist.gov/vuln/detail/CVE-2016-4000
- web https://lists.apache.org/thread.html/0919ec1db20b1022f22b8e78f355667df74d6142b463ff17d03ad533@%3Cdevnull.infra.apache.org%3E
- web https://github.com/jython/jython/commit/ee4200fdd5385d3f74a5cf1a781fa52d33bbb274
- web https://bugs.jython.org/issue2454
- web https://github.com/advisories/GHSA-6r7r-jj8h-pq6v