LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13074: The mintToken function of a smart contract implementation for FIBToken (FIB), an Ethereum token, has an int...

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

Security readout for executives and security teams

Plain-English summary

This CVE describes an integer overflow in FIBToken, an Ethereum token contract. The issue affects the mintToken function and can let the contract owner set any user balance to an arbitrary value. Business risk depends on whether the vulnerable contract or a clone is deployed or trusted.

Executive priority

Treat this as an exposure-confirmation item unless the organization holds, integrates, or operates FIBToken-related contracts. If exposure exists, prioritize because balance integrity is core to token value and downstream accounting.

Technical view

The reported flaw is in the FIBToken smart contract mintToken function. Overflow in balance calculation can allow the owner-controlled mint path to assign arbitrary balances. The CVE metadata does not provide CVSS, CWE, affected CPEs, patch status, or confirmed deployed contract scope.

Likely exposure

Exposure appears limited to FIBToken smart contract implementations, deployed instances, or copied code using the vulnerable mintToken logic. The CVE record lists affected vendor and product as n/a, so asset owners must validate exposure from source or contract inventory.

Exploitation context

The source bundle does not indicate active exploitation, and the CVE is not listed as KEV. The described abuse path depends on the contract owner role, so practical risk includes malicious ownership, compromised owner keys, or governance failures around minting authority.

Researcher notes

Evidence is sparse: no CVSS, CWE, CPEs, or patch details are provided in the CVE bundle. The key technical point is owner-reachable arbitrary balance assignment through integer overflow in mintToken. Validate against actual deployed bytecode or verified source before assigning business impact.

Mitigation direction

  • Check project or vendor guidance for any migration or patched contract direction.
  • Inventory contracts and dependencies for FIBToken or copied mintToken logic.
  • Review owner key custody and restrict minting authority where possible.
  • Avoid relying on affected token balances until exposure is resolved.
  • If maintaining a fork, replace unsafe arithmetic through audited contract changes.

Validation and detection

  • Compare deployed or repository code against the referenced FIBToken implementation.
  • Inspect mintToken for overflow checks around balance and supply updates.
  • Confirm whether any production wallet, service, or treasury holds FIBToken.
  • Identify who controls the contract owner role and related keys.
  • Review historical minting and balance changes for unexplained anomalies.
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-13074 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.