LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1000070: Bitmessage PyBitmessage version v0.6.2 (and introduced in or after commit 8ce72d8d2d25973b7064b1cf76a6b0b3d...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

PyBitmessage v0.6.2 had an eval injection flaw that could allow code execution when a victim processed a malformed Bitmessage message. The source says messages could come from any sender on the Bitmessage network. The issue is reported fixed in v0.6.3.

Executive priority

Treat as urgent where PyBitmessage is deployed. The business risk is code execution from untrusted network messages, but urgency depends on actual use because the affected product appears niche.

Technical view

CVE-2018-1000070 affects PyBitmessage v0.6.2, introduced in or after commit 8ce72d8d2d25973b7064b1cf76a6b0b3d62f0ba0. The flaw is in src/messagetypes/__init__.py, constructObject, where eval injection can lead to code execution during message processing. Public metadata does not provide CVSS or CWE classification.

Likely exposure

Exposure is likely limited to systems running PyBitmessage v0.6.2 or vulnerable code derived from the stated commit range, especially systems connected to the Bitmessage network and processing inbound messages.

Exploitation context

The source describes remote exploitability through a malformed message that must be processed by the victim. No KEV listing is present, and the provided sources do not state active exploitation in the wild.

Researcher notes

The strongest evidence is the CVE description and linked PyBitmessage commit. Affected-product metadata is sparse, CVSS is absent, and no exploitation evidence is provided. Keep findings scoped to PyBitmessage v0.6.2 and the stated commit range.

Mitigation direction

  • Inventory endpoints and servers for PyBitmessage, especially version v0.6.2.
  • Upgrade affected installations to PyBitmessage v0.6.3 or later per vendor guidance.
  • Disable or isolate Bitmessage message processing on systems that cannot be upgraded promptly.
  • Monitor Bitmessage/PyBitmessage guidance for any additional remediation detail.
  • Review affected hosts for unexpected process behavior after suspected message processing.

Validation and detection

  • Confirm installed PyBitmessage versions from package metadata or application source.
  • Verify affected systems are not running v0.6.2 or vulnerable derived code.
  • Check whether src/messagetypes/__init__.py includes the vendor fix.
  • Review logs around inbound message processing for unusual crashes or execution behavior.
  • Confirm no production system still processes Bitmessage traffic before remediation.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-1000070 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.