LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13090: The mintToken function of a smart contract implementation for YiTongCoin (YTC), an Ethereum token, has an i...

The mintToken function of a smart contract implementation for YiTongCoin (YTC), 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
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-13090 affects a YiTongCoin (YTC) Ethereum token smart contract implementation. Its token minting logic can overflow, allowing the contract owner to set any user balance to any value. This threatens token integrity, but the source bundle does not identify broad affected products, a patch, or active exploitation.

Executive priority

Treat this as a token-integrity risk, not a general infrastructure emergency. Prioritize review if the organization holds YTC, lists it, accepts it, or built services around it. Otherwise, document non-exposure and monitor only for project guidance.

Technical view

The CVE describes an integer overflow in the YTC smart contract mintToken function. The privileged owner can manipulate balance assignment for arbitrary users. Available sources do not provide CVSS, CWE, CPE, deployed contract identifiers, or fixed versions, so validation depends on matching local or on-chain contract code to the referenced implementation.

Likely exposure

Exposure appears limited to parties holding, operating, listing, or integrating the vulnerable YiTongCoin (YTC) Ethereum token implementation. The bundle does not support exposure claims for unrelated Ethereum tokens, wallets, exchanges, or generic smart contracts.

Exploitation context

The CVE is not listed as KEV in the bundle, and no cited source states active exploitation. The described abuse path requires contract owner privileges, so practical risk is highest if the owner is malicious, compromised, or operational controls are weak.

Researcher notes

Evidence is sparse: the CVE record gives the core flaw but no CVSS, CWE, fixed version, or affected CPEs. The key technical constraint is owner-only abuse, which reduces broad exploitability but leaves serious integrity impact for the specific token implementation.

Mitigation direction

  • Check the YTC project or contract owner guidance for an official remediation path.
  • Suspend new reliance on the affected token implementation until reviewed.
  • Restrict and monitor access to any owner key controlling the contract.
  • Assess whether migration to a corrected project-approved contract is required.

Validation and detection

  • Inventory any holdings, listings, integrations, or services tied to YiTongCoin (YTC).
  • Compare relevant contract source against the referenced YiTongCoin implementation.
  • Confirm whether mintToken uses vulnerable arithmetic and owner-controlled balance assignment.
  • Review token activity for unexplained balance changes or abnormal minting events.
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-13090 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.