Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

Jython before 2.7.1b3 allows attackers to execute arbitrary code via a crafted serialized PyFunction object.

Source: NIST National Vulnerability Database NVD GitHub Advisory

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-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

Check the vendor advisory for the affected versions of 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. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.python:jython-standalone を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.python:jython-standalone to 2.7.1b3

    ステージング環境で 2.7.1b3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

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"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details