LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13091: The mintToken function of a smart contract implementation for sumocoin (SUMO), an Ethereum token, has an in...

The mintToken function of a smart contract implementation for sumocoin (SUMO), 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-13091 describes a token-accounting flaw in a SUMO Ethereum token smart contract implementation. The vulnerable mintToken function can overflow, allowing the contract owner to set any user balance to any value. This threatens token integrity where that specific contract is trusted.

Executive priority

Treat this as a targeted smart-contract integrity issue, not a broad enterprise software emergency. Prioritize review if your organization has exposure to this SUMO Ethereum token contract or relies on its balances for financial decisions.

Technical view

The CVE reports an integer overflow in mintToken for a smart contract implementation for sumocoin (SUMO), an Ethereum token. The stated impact is owner-controlled arbitrary balance assignment. The source bundle provides no CVSS score, CWE mapping, patch details, or concrete affected CPEs.

Likely exposure

Exposure appears limited to organizations that operate, integrate with, custody, trade, audit, or otherwise trust the referenced SUMO Ethereum token contract implementation. The bundle does not identify broader affected products or versions.

Exploitation context

The provided sources do not cite active exploitation, and the CVE is not listed as KEV. The described abuse path requires the contract owner role, so risk depends heavily on who controls ownership and whether the vulnerable contract is economically relevant.

Researcher notes

Evidence is sparse: the CVE description and one GitHub reference establish the flaw, but no patch, exploit report, CVSS, CWE, or precise product version data is provided. Validate against actual deployed bytecode/source before drawing exposure conclusions.

Mitigation direction

  • Identify whether the referenced SUMO Ethereum token contract is in your asset or dependency inventory.
  • Check project or vendor guidance before relying on the contract for token accounting.
  • Avoid new integrations with the vulnerable implementation until ownership and arithmetic behavior are reviewed.
  • If you operate similar code, use audited token logic with safe arithmetic protections.

Validation and detection

  • Compare deployed contract source against the referenced sumocoin implementation.
  • Review mintToken for unchecked arithmetic and owner-controlled balance changes.
  • Confirm who controls the contract owner role and whether that key is trusted.
  • Check transaction history for unexpected minting or abnormal balance changes.
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-13091 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.