Security readout for executives and security teams
Plain-English summary
CVE-2018-13128 concerns the Etherty Token (ETY) Ethereum smart contract. Its mint function reportedly has an integer overflow that lets the contract owner retrieve arbitrary minted tokens. Business impact depends on whether your organization holds, accepts, or integrates ETY; the source bundle does not provide CVSS, affected versions, a patch, or live exploitation evidence.
Executive priority
Prioritize if the organization has financial, custody, exchange, or contractual exposure to ETY. Otherwise, track as a niche smart-contract integrity issue. The absence of severity, patch, and affected-version detail prevents a stronger urgency rating from the provided evidence alone.
Technical view
The CVE describes an integer overflow in ETY's mint function, with impact limited by the stated prerequisite that the contract owner can trigger arbitrary token retrieval. No CWE, CVSS vector, affected contract address, fixed version, or vendor remediation is provided in the bundle. KEV status is false, so active exploitation is not established here.
Likely exposure
Exposure is likely limited to parties holding ETY, integrating ETY into wallets, exchanges, custody workflows, analytics, or contracts, or relying on its supply integrity. The source bundle lists affected vendor, product, and versions as n/a, so precise scoping requires contract-level confirmation from the linked project materials.
Exploitation context
The bundle does not show public active exploitation or KEV inclusion. The described abuse path depends on contract-owner control of the mint function, so the main risk is supply manipulation or loss of trust rather than broad unauthenticated compromise. Evidence is incomplete on deployment status and real-world usage.
Researcher notes
Key gaps are contract address, deployed bytecode confirmation, compiler version, affected deployment status, fixed code, and exploit-in-the-wild evidence. The CVE text attributes arbitrary minted token retrieval to integer overflow in mint, but the bundle does not include enough detail to assess reachability beyond owner authority.
Mitigation direction
- Check project or vendor guidance before assuming any fixed contract or migration path.
- Inventory ETY holdings, integrations, listings, custody support, and smart-contract dependencies.
- Treat ETY supply integrity as untrusted until contract status is verified.
- Avoid new ETY integrations until remediation or migration guidance is confirmed.
- Review business exposure to owner-controlled token minting risk.
Validation and detection
- Confirm whether your systems reference the ETY contract from the linked project.
- Review the mint logic for overflow-prone arithmetic and owner-only access assumptions.
- Check token supply, balances, and issuance history for unexplained anomalies.
- Verify whether any project migration, replacement contract, or deprecation notice exists.
- Document whether ETY is held, accepted, listed, or only observed analytically.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
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 lookupCVE-2018-13128 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/dwfault/AirTokens/blob/master/SPXToken/mint%20interger%20overflow.mdCVE reference · x_refsource_MISC
- https://github.com/dwfault/AirTokens/tree/master/ETYCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.