LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10944: The request_dividend function of a smart contract implementation for ROC (aka Rasputin Online Coin), an Eth...

The request_dividend function of a smart contract implementation for ROC (aka Rasputin Online Coin), an Ethereum ERC20 token, allows attackers to steal all of the contract's Ether.

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

Security readout for executives and security teams

Plain-English summary

CVE-2018-10944 concerns a ROC, Rasputin Online Coin, Ethereum ERC20 smart contract flaw. The reported issue is that the request_dividend function can let an attacker drain all Ether held by the contract. The source bundle does not provide CVSS, affected versions, or a confirmed fix.

Executive priority

Treat as urgent only if the organization controls, funds, or relies on the affected ROC contract. For general enterprise environments without ROC exposure, business urgency is low, but any funded affected contract could face total loss of held Ether.

Technical view

The vulnerability is in a smart contract implementation for ROC. The CVE description specifically names request_dividend as the vulnerable function and says it allows theft of all contract Ether. Available data does not identify CPEs, affected versions, CWE classification, or vendor remediation details.

Likely exposure

Exposure appears limited to organizations that deployed, held funds in, integrated with, or depended on the affected ROC smart contract implementation. The bundle lists affected vendor, product, and versions as n/a, so scope cannot be reliably expanded beyond that contract context.

Exploitation context

The bundle references a public analysis, but CISA KEV status is false and no cited source in the bundle confirms active exploitation. The described impact is direct loss of Ether from the contract if the vulnerable implementation is reachable and funded.

Researcher notes

Evidence is sparse: the CVE record gives the vulnerable function and consequence, while affected versions and remediation are not specified. Do not assume other ERC20 tokens are affected without matching contract evidence. Validation should focus on contract provenance, deployed addresses, and current Ether exposure.

Mitigation direction

  • Check ROC project or vendor guidance for a corrected contract or migration path.
  • Avoid retaining Ether in potentially affected ROC contract instances until reviewed.
  • Pause dependent integrations that use dividend functionality until exposure is confirmed.
  • Monitor associated contract balances and transactions for unexplained Ether movement.

Validation and detection

  • Confirm whether your organization deployed or integrates with ROC Rasputin Online Coin contracts.
  • Review contract source or verified bytecode for the named request_dividend function.
  • Determine whether any affected contract instance currently holds Ether.
  • Check transaction history for unexplained withdrawals from relevant contract addresses.
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

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. 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-10944 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.