LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13130: Bitotal (TFUND) is a smart contract running on Ethereum.

Bitotal (TFUND) is a smart contract running on Ethereum. The mintTokens function has an integer overflow that allows minted tokens to be arbitrarily retrieved by the contract owner.

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-13130 concerns the Bitotal TFUND Ethereum smart contract. Its token minting function reportedly has an integer overflow that lets the contract owner retrieve arbitrarily minted tokens. The main business risk is token supply manipulation and loss of trust where this contract is held, traded, or integrated.

Executive priority

Treat this as a targeted blockchain asset exposure review, not a broad enterprise software emergency. Prioritize only if TFUND holdings, exchange listings, customer integrations, or financial reporting depend on this contract.

Technical view

The CVE describes an integer overflow in Bitotal TFUND's mintTokens function. The reported impact is arbitrary token retrieval by the contract owner. The source bundle does not provide CVSS, CWE mapping, affected CPEs, a vendor patch, or confirmed exploit-in-the-wild evidence.

Likely exposure

Exposure appears limited to organizations or users holding, trading, integrating, or valuing the Bitotal TFUND Ethereum smart contract. The source bundle does not identify conventional software products, versions, or infrastructure packages affected.

Exploitation context

The described capability is tied to the contract owner, not an unauthenticated external attacker. The bundle does not show CISA KEV listing, active exploitation, public weaponization, or a named patch. Risk depends on ownership control, contract use, and whether TFUND has business value.

Researcher notes

Evidence is sparse. The CVE record names Bitotal TFUND and an integer overflow in mintTokens, but provides no CVSS, CWE, affected version range, patch, or exploitation confirmation. Analysis should stay anchored to the contract code and cited GitHub references.

Mitigation direction

  • Identify whether your organization holds, trades, or integrates Bitotal TFUND.
  • Check the referenced project and CVE record for vendor or maintainer guidance.
  • Avoid new business reliance on the contract until exposure is understood.
  • Monitor TFUND supply and owner-controlled minting activity where relevant.
  • Review counterparties or integrations that assign value to TFUND.

Validation and detection

  • Confirm whether Bitotal TFUND exists in asset inventories, wallets, exchanges, or integrations.
  • Review the mintTokens function for unchecked arithmetic behavior.
  • Verify who controls the contract owner address and related governance process.
  • Check historical token supply changes for unexplained or owner-driven inflation.
  • Document whether the contract is still economically or operationally relevant.
Prepared
Confidence
medium
Sources
4

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.

cve · low confidence lookup

CVE-2018-13130 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
3Source 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.