LiveActive security incident?Get immediate response
CVE Record

CVE-2018-14088: An issue was discovered in a smart contract implementation for STeX White List (STE(WL)), an Ethereum token.

An issue was discovered in a smart contract implementation for STeX White List (STE(WL)), an Ethereum token. The contract has an integer overflow. If the owner sets the value of amount to a large number then the "amount * 1000000000000000" will cause an integer overflow in withdrawToFounders().

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-14088 concerns an Ethereum token smart contract for STeX White List. A large owner-supplied withdrawal amount can overflow during calculation, potentially causing incorrect token or value handling. Business urgency depends on whether this exact contract or derived code is deployed and holds assets.

Executive priority

Treat this as an exposure-confirmation task, not a broad emergency. Prioritize it if your organization owns, operates, audits, or depends on this contract or reused code handling real assets.

Technical view

The reported flaw is an integer overflow in withdrawToFounders(), where amount is multiplied by 1000000000000000. Sources describe the issue when the contract owner sets amount to a large value. No CVSS, affected versions, patch, or broader product mapping is provided.

Likely exposure

Exposure appears limited to the STeX White List Ethereum token contract or code copied from it. The source bundle does not identify CPEs, package versions, contract addresses, deployments, or downstream projects.

Exploitation context

No active exploitation is shown in the provided sources, and the CVE is not marked KEV. The described trigger involves an owner-set amount, so practical impact depends on ownership controls, deployed contract state, and whether valuable assets remain managed by the contract.

Researcher notes

Evidence is sparse: the CVE description and linked GitHub reference identify the overflow pattern, but not deployment addresses, impacted balances, remediation commits, or exploit activity. Avoid assuming exploitability beyond the owner-controlled overflow condition described.

Mitigation direction

  • Identify any deployed STeX White List or derived smart contracts under your control.
  • Check project or vendor guidance; no official patch is named in the provided sources.
  • Review withdrawToFounders() for unsafe arithmetic before further operational use.
  • If maintaining derived code, use overflow-safe arithmetic after engineering review.
  • Restrict owner-key access and monitor owner-only withdrawal activity.

Validation and detection

  • Inventory Ethereum contracts and repositories for STeX White List or STE(WL) references.
  • Inspect withdrawToFounders() for amount multiplied by 1000000000000000.
  • Confirm whether the vulnerable code is deployed and still manages assets.
  • Review historical owner-only withdrawals for anomalous large amount values.
  • Document findings separately for deployed contracts and source-only copies.
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-14088 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.