LiveActive security incident?Get immediate response
CVE Record

CVE-2018-11411: The transferFrom function of a smart contract implementation for DimonCoin (FUD), an Ethereum ERC20 token,...

The transferFrom function of a smart contract implementation for DimonCoin (FUD), an Ethereum ERC20 token, allows attackers to steal assets (e.g., transfer all victims' balances into their account) because certain computations involving _value are incorrect.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-11411 describes a flaw in the DimonCoin (FUD) ERC20 token contract that could let attackers transfer victims' token balances to themselves. The public record does not provide CVSS scoring, affected versions, a patch, or evidence of active exploitation.

Executive priority

Treat as high priority only where DimonCoin exposure exists. The business risk is potential token asset loss, but urgency is lower for organizations with no FUD holdings, listings, integrations, or reused vulnerable contract code.

Technical view

The reported issue is in the token contract's transferFrom function. The CVE states that incorrect computations involving _value allow asset theft, including transferring victims' balances. Available source data identifies DimonCoin (FUD), not ERC20 generally, and does not name a fixed contract or version.

Likely exposure

Exposure is likely limited to parties holding, custodying, listing, integrating, or transacting with DimonCoin (FUD), or reusing the same vulnerable contract logic. The source bundle does not identify broader Ethereum or ERC20 platform exposure.

Exploitation context

CISA KEV status is false in the bundle, and no cited source confirms active exploitation. The CVE description does describe a theft primitive, but the available evidence is incomplete on real-world abuse, patch status, and affected deployment details.

Researcher notes

Evidence is sparse: no CVSS vector, CWE, CPE, affected versions, patch reference, or KEV listing are provided. Keep analysis scoped to DimonCoin (FUD) and the transferFrom arithmetic issue; do not generalize to all ERC20 tokens without code evidence.

Mitigation direction

  • Check DimonCoin or platform guidance for an official remediation or migration path.
  • Avoid new integrations with the affected token contract until risk is resolved.
  • Custodians should consider pausing FUD deposits and withdrawals pending review.
  • Review copied token code for the same transferFrom _value computation issue.
  • Document business exposure for wallets, listings, accounting, and customer balances.

Validation and detection

  • Confirm whether the organization holds, lists, custodies, or processes DimonCoin (FUD).
  • Identify any deployed contract code derived from the referenced implementation.
  • Review transferFrom arithmetic against the CVE description and public write-up.
  • Check transaction history for unexpected third-party transfers of FUD balances.
  • Record absence or presence of vendor guidance before deciding remediation.
Prepared
Confidence
medium
Sources
3

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

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.