LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13076: The mintToken function of a smart contract implementation for Betcash (BC), an Ethereum token, has an integ...

The mintToken function of a smart contract implementation for Betcash (BC), 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-13076 concerns Betcash (BC), an Ethereum token smart contract. The reported flaw is an integer overflow in mintToken that can let the contract owner set any user balance to any value. Business impact depends entirely on whether the organization holds, lists, or relies on this token.

Executive priority

Prioritize immediately only if the organization holds, lists, custodies, or depends on Betcash. Otherwise, track as a narrow smart-contract issue with incomplete severity data and no cited active exploitation.

Technical view

The CVE describes an integer overflow in the Betcash token mintToken function. The stated effect is arbitrary balance assignment by the contract owner. The bundle does not provide CVSS, affected version detail, patch status, or broader product impact beyond the referenced smart contract implementation.

Likely exposure

Exposure appears limited to organizations, users, exchanges, custodians, or applications interacting with the Betcash (BC) Ethereum token contract. The source bundle lists vendor and product as n/a, so broader platform exposure is not established.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not state active exploitation. The described capability is tied to the contract owner role, so practical risk depends on contract deployment, owner trust, and whether balances are operationally relied upon.

Researcher notes

Evidence is sparse: the CVE description and one GitHub reference identify the vulnerable function and impact, but not patch status, deployed contract address, exploit history, or affected versions. Treat conclusions as limited to the provided Betcash smart contract report.

Mitigation direction

  • Determine whether Betcash (BC) is held, listed, or integrated anywhere.
  • Check the referenced project and CVE sources for authoritative remediation or migration guidance.
  • Reduce reliance on affected token balances until risk is accepted or remediated.
  • Review custodial, exchange, and accounting exposure to BC balances.
  • Monitor for updated vendor or community guidance before resuming normal reliance.

Validation and detection

  • Inventory wallet, exchange, custody, and application exposure to Betcash (BC).
  • Confirm the specific contract implementation against the referenced Betcash report.
  • Review whether any business process trusts BC balances for value or access.
  • Check balance history and administrative ownership assumptions for anomalies.
  • Document whether exposure exists, is historical only, or remains active.
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-13076 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.