Security readout for executives and security teams
Plain-English summary
CVE-2018-13092 concerns the Reimburse Token (REIM) Ethereum token contract. Its mintToken function can overflow, allowing the contract owner to set any user balance to an arbitrary value. This threatens token integrity and trust, but the source bundle does not identify active exploitation, affected versions, or a vendor fix.
Executive priority
Treat this as a targeted smart-contract integrity risk, not a broad infrastructure emergency. Prioritize review if your organization holds, lists, prices, or automates decisions based on REIM balances.
Technical view
The CVE describes an integer overflow in REIM's mintToken smart contract function. The vulnerable behavior is owner-scoped: the contract owner can manipulate an arbitrary account balance to any value. Public metadata lacks CVSS, CWE, CPE, affected version details, and remediation guidance.
Likely exposure
Exposure appears limited to parties holding, integrating, auditing, or depending on the referenced REIM Ethereum token contract. The bundle does not identify broader products, package versions, exchanges, wallets, or enterprise platforms as affected.
Exploitation context
No CISA KEV listing is provided, and the bundle does not cite active exploitation. The described issue requires owner-level contract authority, so practical risk centers on malicious ownership, compromised owner keys, or trust failure in the token contract.
Researcher notes
Evidence is sparse. The CVE record names the function and impact but provides no CVSS, CWE, CPE, affected version range, deployed address, patch, or exploit confirmation. Analysis should stay tied to the referenced REIM contract materials.
Mitigation direction
- Check the token project's current guidance and contract status.
- Avoid relying on vulnerable REIM balances for critical business decisions.
- Review integrations that accept or value REIM balances.
- Assess owner-key governance and trust assumptions for the contract.
- Consider disabling REIM support until risk is resolved.
Validation and detection
- Confirm whether your systems reference the REIM contract.
- Review token balance dependencies in wallets, exchanges, or accounting workflows.
- Check whether any REIM holdings affect financial reporting or customer services.
- Inspect source references for mintToken overflow analysis.
- Document unknowns: affected versions, deployed address, and remediation status.
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-13092 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/ReimburseToken/ReimburseToken.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.