LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13088: The mintToken function of a smart contract implementation for Futures Pease (FP), an Ethereum token, has an...

The mintToken function of a smart contract implementation for Futures Pease (FP), 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-13088 concerns the Futures Pease (FP) Ethereum token contract. Its mintToken function has an integer overflow that can let the contract owner set any user balance to any value. The main business risk is token balance and supply integrity if this specific contract is used or trusted.

Executive priority

Prioritize if your organization holds, lists, integrates, or accounts for FP tokens. Otherwise, this is likely a narrow blockchain-specific issue with limited enterprise urgency based on the provided evidence.

Technical view

The issue is an integer overflow in mintToken within a smart contract implementation for Futures Pease (FP). The CVE states the owner can set an arbitrary user balance to any value. The source bundle does not provide CVSS, CWE, contract address, patch details, or affected version metadata.

Likely exposure

Exposure appears limited to organizations holding, trading, integrating, auditing, or relying on the specific Futures Pease (FP) Ethereum token contract implementation.

Exploitation context

The bundle does not show CISA KEV listing or any cited evidence of active exploitation. The described abuse requires owner-level mintToken capability, so risk also depends on owner key control and whether this contract was deployed.

Researcher notes

Evidence is sparse. The CVE identifies the vulnerable function and impact, but affected vendor/product fields are n/a and no CVSS, CWE, deployed address, exploit evidence, or remediation is included. Validate against the referenced repository and any actual deployed contract before concluding exposure.

Mitigation direction

  • Identify whether FP token exposure exists in wallets, exchanges, contracts, or accounting systems.
  • Check the project or contract maintainer guidance for any corrected implementation or migration path.
  • Treat balances from the affected contract as integrity-risk data until validated.
  • Assess owner-key custody and compromise risk for any deployed instance.
  • Avoid new integrations with unverified FP contract implementations.

Validation and detection

  • Confirm the exact FP contract address and source code before assessing impact.
  • Review whether the deployed mintToken logic matches the referenced vulnerable implementation.
  • Verify whether mintToken is owner-restricted and who controls that owner role.
  • Check whether dependent systems trust FP balances for financial or operational decisions.
  • Document absence or presence of vendor patch, migration, or maintainer advisory.
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-13088 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.