LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13087: The mintToken function of a smart contract implementation for Coinstar (CSTR), an Ethereum token, has an in...

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

CVE-2018-13087 concerns a Coinstar Ethereum token smart contract where the owner-controlled mint function can overflow and set any user balance to any value. This threatens token accounting integrity, but the source bundle does not provide CVSS, affected versions, deployment status, a patch, or active exploitation evidence.

Executive priority

Treat as a targeted integrity risk for organizations exposed to Coinstar CSTR or copied token code. It is not broadly actionable without confirmed exposure, but token holders, exchanges, and integrators should validate impact because balance manipulation could undermine financial trust.

Technical view

The issue is an integer overflow in mintToken within a Coinstar CSTR smart contract implementation. The CVE description says the contract owner can set an arbitrary user's balance to any value. Evidence is limited to CVE records and one referenced GitHub analysis page.

Likely exposure

Exposure appears limited to deployed Coinstar CSTR contracts or contracts derived from the referenced MyAdvancedToken implementation. The bundle lists no formal affected vendor, product, versions, CPEs, or deployment addresses, so asset-specific exposure must be confirmed from internal blockchain and code inventories.

Exploitation context

The CVE is not listed as KEV in the provided data, and the bundle provides no active exploitation evidence. The described condition is owner-scoped, so practical abuse would depend on owner action, owner key compromise, or use of derived vulnerable contract code.

Researcher notes

The public record is sparse: no CVSS, CWE, concrete affected versions, patch, deployed address, or exploitation report is included. Keep analysis bounded to the owner-reachable integer overflow and avoid extrapolating to unrelated ERC-20 implementations.

Mitigation direction

  • Check project or vendor guidance for migration, deprecation, or corrected contract recommendations.
  • Inventory exposure to Coinstar CSTR and derived MyAdvancedToken contracts.
  • Review and harden owner-key custody and transaction approval controls.
  • Monitor token supply and balance changes for unexpected administrative minting effects.
  • Avoid relying on affected token balances until integrity is validated.

Validation and detection

  • Confirm whether your organization holds, integrates, or operates CSTR-related contracts.
  • Compare deployed contract source with the referenced MyAdvancedToken implementation.
  • Identify owner-controlled mint functions and integer arithmetic behavior.
  • Review historical mint and balance events for abnormal accounting changes.
  • Document any vendor guidance or absence of available remediation.
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-13087 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.