Security readout for executives and security teams
Plain-English summary
This CVE concerns an Ethereum token smart contract for ETHEREUMBLACK (ETCBK). Its mintToken logic can overflow, letting the contract owner set any user's token balance to any value. The issue undermines token supply and balance integrity for anyone relying on ETCBK value or accounting.
Executive priority
Treat this as a targeted token-integrity risk, not a broad platform emergency. Prioritize review only if the business holds, lists, processes, or reports ETCBK exposure.
Technical view
The reported flaw is an integer overflow in mintToken in the ETCBK Ethereum token implementation. Because minting is owner-controlled, the described impact is arbitrary balance assignment by the owner, not unauthenticated takeover. The source bundle does not provide CVSS, CWE, fixed versions, or deployment addresses.
Likely exposure
Exposure appears limited to organizations holding, listing, integrating, or valuing the ETHEREUMBLACK token contract. General Ethereum infrastructure is not identified as affected in the supplied sources.
Exploitation context
No active exploitation is stated in the CVE data, and the issue is not listed as KEV. The public description indicates abuse requires contract owner capability, but evidence is incomplete.
Researcher notes
The source bundle names only the ETCBK smart contract implementation and one GitHub analysis reference. It lacks CVSS, CWE, affected version identifiers, fixed contract information, and deployment-specific details, so conclusions should remain tightly scoped.
Mitigation direction
- Identify whether ETCBK is held, listed, custodied, or used in accounting systems.
- Check project or vendor guidance for corrected contract details or migration instructions.
- Avoid relying on ETCBK balances for material value until contract risk is reviewed.
- For exchanges or custodians, consider enhanced monitoring or temporary risk controls.
Validation and detection
- Review token inventories for ETHEREUMBLACK or ETCBK exposure.
- Confirm the exact smart contract implementation used by any integration.
- Assess whether mintToken behavior can affect internal balances or customer-facing records.
- Document whether the organization depends on ETCBK price, supply, or balance integrity.
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-13073 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/VenusADLab/EtherTokens/blob/master/ETHEREUMBLACK/ETHEREUMBLACK.mdCVE 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.