LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13071: The mintToken function of a smart contract implementation for CCindex10 (T10), an Ethereum token, has an in...

The mintToken function of a smart contract implementation for CCindex10 (T10), 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-13071 affects a CCindex10 (T10) Ethereum token smart contract. Its minting function has an integer overflow that lets the contract owner set any user’s balance to any value. This is mainly a token integrity and trust issue, not a general enterprise infrastructure vulnerability.

Executive priority

Treat as a targeted digital-asset exposure review. It warrants prompt attention only if your organization holds, lists, custodies, or integrates the affected token. For most enterprises without CCindex10/T10 exposure, business urgency is low.

Technical view

The reported flaw is an integer overflow in the mintToken function of a CCindex10 (T10) smart contract implementation. The CVE states the privileged owner can manipulate an arbitrary account balance to any value. Public metadata does not provide CVSS, CWE, fixed versions, or affected contract identifiers.

Likely exposure

Exposure appears limited to organizations or users holding, integrating, listing, custodying, or otherwise relying on the affected CCindex10/T10 Ethereum token implementation. The source bundle does not identify affected contract addresses, versions, exchanges, or downstream products.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation evidence. The stated abuse path is owner-controlled minting logic, so practical risk depends on the deployed contract, owner-key control, governance, and whether the token had real value or integrations.

Researcher notes

Evidence is sparse. The CVE description identifies the vulnerable function and privileged impact, but does not provide CVSS, CWE, affected versions, contract addresses, exploit observations, or a named fix. Avoid broad claims beyond the CCindex10/T10 smart contract implementation.

Mitigation direction

  • Check CCindex10/T10 project or maintainer guidance before taking operational action.
  • Identify any holdings, listings, custody, or integrations involving the affected token.
  • Review governance and owner-key controls for any exposed deployed contract.
  • Consider pausing reliance on token balances until exposure is resolved.
  • Coordinate with maintainers or exchanges on any migration or remediation plan.

Validation and detection

  • Confirm whether your systems reference CCindex10 or T10 token assets.
  • Review the relevant smart contract source for the mintToken overflow condition.
  • Determine whether deployed contracts include the vulnerable implementation.
  • Check token balance history for unexpected owner-driven minting or balance changes.
  • Document any business process that trusts the affected token balance.
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-13071 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.