Security readout for executives and security teams
Plain-English summary
CVE-2018-13077 concerns a CTB Ethereum token smart contract. Its minting function has an integer overflow that lets the contract owner set any user balance to any value. This is mainly a trust and asset-integrity risk for anyone relying on that token implementation.
Executive priority
Treat this as targeted due diligence, not a broad enterprise emergency. Prioritize immediately only if the organization has CTB exposure or reused this code. Without CTB exposure, track as low operational relevance with incomplete public severity data.
Technical view
The reported flaw is in the CTB token contract's mintToken function. The CVE states an integer overflow permits the owner to assign arbitrary balances. The public data does not provide CVSS, affected versions, contract addresses, deployment status, or a named patch.
Likely exposure
Exposure appears limited to organizations that deployed, forked, integrated, custody, traded, or accounted for CTB tokens using this specific implementation. The CVE record does not identify packaged products, CPEs, versions, or live contract addresses.
Exploitation context
The source bundle does not show KEV listing or cited evidence of active exploitation. Practical abuse depends on the vulnerable contract being deployed and the owner role being controlled or misused. No exploit status should be assumed from the available evidence.
Researcher notes
The record is sparse: no CVSS, CWE, affected version, CPE, patch, deployment address, or exploitation evidence is provided. Analysis should stay tied to the CTB mintToken integer overflow and avoid extrapolating to unrelated Ethereum tokens.
Mitigation direction
- Inventory any CTB token deployments, forks, integrations, or accounting dependencies.
- Check the referenced project guidance before changing deployed smart contracts.
- Reduce reliance on affected contracts where balances can be owner-manipulated.
- For owned deployments, plan migration to audited arithmetic-safe token logic.
- Review governance and custody controls for contract owner privileges.
Validation and detection
- Confirm whether any deployed contract contains the reported mintToken implementation.
- Review source provenance for CTB forks or copied token code.
- Check owner-role custody, permissioning, and administrative activity history.
- Verify token balances against trusted records where CTB exposure exists.
- Document whether CTB has business, custody, trading, or reporting impact.
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-13077 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/CTB/CTB.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.