LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13086: The mintToken function of a smart contract implementation for IADOWR Coin (IAD), an Ethereum token, has an...

The mintToken function of a smart contract implementation for IADOWR Coin (IAD), 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 analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-13086 concerns an Ethereum token contract for IADOWR Coin. Its minting function can overflow, letting the contract owner set any user balance to an arbitrary value. That creates integrity and trust risk for token holders or systems relying on token balances.

Executive priority

Treat as a targeted crypto-asset integrity risk, not a broad enterprise infrastructure emergency. Prioritize if your organization holds, lists, prices, accepts, or depends on IAD balances or reused contract code.

Technical view

The CVE describes an integer overflow in the mintToken function of an IADOWR Coin smart contract implementation. The reported effect is owner-controlled balance manipulation for arbitrary users. The source bundle provides no CVSS score, CPEs, fixed version, or named patch.

Likely exposure

Exposure appears limited to IADOWR Coin integrations, holders, exchanges, wallets, or forks that reuse the referenced Ethereum token implementation. The CVE record lists vendor, product, versions, and CPEs as n/a, so scoping requires asset-specific contract review.

Exploitation context

The bundle does not show active exploitation, KEV listing, public exploit use, or exploitation reports. The issue is described as owner-capable abuse or failure in a smart contract minting function, not a remotely exploitable server vulnerability.

Researcher notes

Evidence is sparse. The CVE states the vulnerable function and impact, but provides no CVSS, affected version range, deployed address, patch reference, or exploitation evidence. Validate against the exact contract implementation before making operational claims.

Mitigation direction

  • Check IADOWR Coin project guidance; no patch is named in the sources.
  • Inventory any IAD holdings, integrations, or forks using this implementation.
  • Review business reliance on affected token balances and supply integrity.
  • For owned forks, request smart-contract remediation planning with checked arithmetic.
  • Document acceptance, migration, or delisting decisions for impacted systems.

Validation and detection

  • Confirm whether your systems interact with IADOWR Coin or related contracts.
  • Map any deployed contract address to the referenced implementation.
  • Review mintToken arithmetic and access-control behavior in source code.
  • Check whether balance or supply data feeds depend on IAD.
  • Record that no active exploitation evidence is cited in the bundle.
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-13086 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.