LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13131: SpadePreSale is a smart contract running on Ethereum.

SpadePreSale is a smart contract running on Ethereum. The mint function has an integer overflow that allows minted tokens to be arbitrarily retrieved by the contract owner.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-13131 concerns the SpadePreSale Ethereum smart contract. Its mint function reportedly has an integer overflow that lets the contract owner retrieve minted tokens arbitrarily. The business risk is token supply or balance integrity, not conventional server compromise.

Executive priority

Treat this as a targeted blockchain asset-integrity issue. Prioritize it if the organization holds, lists, accepts, or operates the affected token; otherwise urgency is likely low but should be confirmed.

Technical view

The CVE describes an integer overflow in the SpadePreSale mint function. The affected asset is identified only as an Ethereum smart contract, with no standard vendor, product, CPE, CVSS score, CWE, or fixed version listed in the provided sources.

Likely exposure

Exposure appears limited to parties operating, integrating, listing, holding, or relying on the SpadePreSale/SPXToken contract or related token balances. The bundle does not identify broader affected products.

Exploitation context

The CVE and references describe owner-enabled arbitrary token retrieval through overflow behavior. The source bundle does not cite active exploitation, and the CVE is not marked KEV.

Researcher notes

Evidence is sparse: the CVE names the vulnerable contract behavior, but provides no CVSS, CWE, patch, affected version range, or exploit status. Avoid extrapolating beyond SpadePreSale/SPXToken without direct contract evidence.

Mitigation direction

  • Inventory any dependency on SpadePreSale or SPXToken balances.
  • Check the referenced repository and CVE record for vendor guidance.
  • Suspend new reliance on affected token balances until assessed.
  • If operating the contract, obtain a smart-contract review before mint-related changes.

Validation and detection

  • Confirm whether your deployed contract matches the referenced SpadePreSale source.
  • Review mint arithmetic and owner permissions for overflow risk.
  • Check token supply history for unexpected minting anomalies.
  • Document whether business systems rely on this token’s balances.
Prepared
Confidence
medium
Sources
4

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-13131 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.

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.