LiveActive security incident?Get immediate response
CVE Record

CVE-2018-14087: An issue was discovered in a smart contract implementation for EUC (EUC), an Ethereum token.

An issue was discovered in a smart contract implementation for EUC (EUC), an Ethereum token. The contract has an integer overflow. If the owner sets the value of buyPrice to a large number in setPrices() then the "msg.value * buyPrice" will cause an integer overflow in the fallback function.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-14087 describes an integer overflow in the EUC Ethereum token smart contract. If the contract owner sets buyPrice to an excessively large value, token purchase calculations can wrap around instead of producing the intended amount. The public record does not provide CVSS, affected CPEs, patch details, or evidence of active exploitation.

Executive priority

Treat this as a targeted smart-contract exposure review, not an enterprise-wide infrastructure emergency. Priority rises if the organization holds EUC, accepts it, integrates it, or depends on its market value.

Technical view

The flaw is in EUC token contract logic: setPrices() can set buyPrice, and the fallback function multiplies msg.value by buyPrice. With a large buyPrice, that multiplication can overflow. The source bundle identifies the affected implementation only as EUC, an Ethereum token, with no vendor/product metadata beyond that.

Likely exposure

Exposure appears limited to parties holding, integrating with, or transacting against the vulnerable EUC token contract implementation. The bundle does not identify broader Ethereum platform impact, package versions, or downstream forks.

Exploitation context

The CVE is not listed as KEV in the provided bundle. No cited source claims active exploitation. The described condition depends on the owner setting buyPrice to a large value, so owner behavior or owner-key compromise matters to practical risk.

Researcher notes

The public data is sparse: no CVSS, CWE, CPE, patch, or exploit evidence is provided. Analysis should stay tied to the referenced EUC contract behavior and avoid generalizing to unrelated Ethereum tokens.

Mitigation direction

  • Check EUC project or contract maintainer guidance for migration or replacement details.
  • Avoid new reliance on the affected EUC contract until status is confirmed.
  • Inventory wallets, services, and integrations that touch EUC token contracts.
  • Assess business exposure from EUC holdings, payment flows, or exchange integrations.

Validation and detection

  • Confirm whether your organization holds or processes EUC tokens.
  • Review integrations for direct interaction with the vulnerable EUC contract implementation.
  • Check whether monitored contracts expose setPrices() and fallback purchase logic.
  • Review contract history for buyPrice changes by the owner account.
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-14087 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.