Vulnerability in Bitmessage PyBitmessage (CVE-2018-1000070)

Summary

Vulnerability in Bitmessage PyBitmessage (CVE-2018-1000070). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.6.3 or later.

Original description

The description as published by the source.

Bitmessage PyBitmessage version v0.6.2 (and introduced in or after commit 8ce72d8d2d25973b7064b1cf76a6b0b3d62f0ba0) contains a Eval injection vulnerability in main program, file src/messagetypes/init.py function constructObject that can result in Code Execution. This attack appears to be exploitable via remote attacker using a malformed message which must be processed by the victim - e.g. arrive from any sender on bitmessage network. This vulnerability appears to have been fixed in v0.6.3.

Source: OSV.dev (Open Source Vulnerabilities) NVD OSV

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-2018-1000070 has been found in Bitmessage PyBitmessage.
Successful exploitation can lead to full system takeover.
What to do: upgrade Bitmessage PyBitmessage to 0.6.3 or later.
If unsure, ask your IT team or search "Bitmessage PyBitmessage CVE-2018-1000070" on the vendor's site.

CVE-2018-1000070 (Bitmessage PyBitmessage)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.6.3 — 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 Bitmessage PyBitmessage.

📍 Affected scope

Check the vendor advisory for the affected versions of Bitmessage PyBitmessage.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 0.6.3.

🛡️ 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
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで Bitmessage PyBitmessage を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade Bitmessage PyBitmessage to 0.6.3
```
ステージング環境で 0.6.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

patch github.com