LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13082: The mintToken function of a smart contract implementation for MODI Token (MODI), an Ethereum token, has an...

The mintToken function of a smart contract implementation for MODI Token (MODI), an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value.

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

Security readout for executives and security teams

Plain-English summary

CVE-2018-13082 concerns the MODI Token Ethereum smart contract. A flaw in its minting logic can let the contract owner set any user's token balance to an arbitrary value. This threatens token integrity, but the public sources do not show broader product impact or active exploitation.

Executive priority

Prioritize only if the organization has exposure to MODI Token. The issue can undermine token accounting and trust, but available sources do not indicate active exploitation or broad platform impact.

Technical view

The reported issue is an integer overflow in the mintToken function of a MODI Token ERC20 implementation. The CVE description says the owner can set an arbitrary account balance to any value. No CVSS score, CWE, patch, or precise affected deployed contract metadata is provided.

Likely exposure

Exposure appears limited to organizations that hold, list, integrate, custody, price, or otherwise rely on the affected MODI Token smart contract. General Ethereum infrastructure is not described as affected by the supplied sources.

Exploitation context

The source bundle does not report CISA KEV listing, active exploitation, or public weaponization. The described abuse path depends on the contract owner role or control of that role, making privileged-key governance and token trust the central risk.

Researcher notes

Evidence is sparse: the CVE record names the vulnerable function and impact, but affected vendor/product metadata is n/a and no CVSS, CWE, fixed version, or deployed contract address is included. Treat conclusions about scope as limited to the supplied references.

Mitigation direction

  • Check whether any systems, wallets, listings, or treasury assets depend on MODI Token.
  • Review project or contract maintainer guidance; no patch is named in the sources.
  • Avoid new business reliance on the affected contract until integrity is confirmed.
  • If you control the contract, assess migration or replacement with audited minting logic.
  • Monitor token supply, privileged minting, and abnormal balance changes.

Validation and detection

  • Identify any deployed MODI Token contract addresses used by your organization.
  • Confirm whether the deployed source matches the referenced vulnerable implementation.
  • Review owner-role control, key custody, and any ownership-transfer history.
  • Check token supply and holder balances for unexplained changes.
  • Document all business processes that depend on MODI balances or pricing.
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-13082 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.