LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13145: The mintToken function of a smart contract implementation for JavaSwapTest (JST), an Ethereum token, has an...

The mintToken function of a smart contract implementation for JavaSwapTest (JST), an Ethereum token, has an integer overflow.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes an integer overflow in the mintToken function of an Ethereum token smart contract implementation for JavaSwapTest (JST). Arithmetic during token minting may wrap around instead of failing, which can corrupt token supply or balances. The public record does not identify maintained products, deployments, CVSS severity, or a vendor fix.

Executive priority

Treat this as a targeted exposure check, not a broad emergency. Priority rises if your organization deployed, forked, invested in, or depends on the referenced JST contract code. The available sources do not support claims of active exploitation or a confirmed patch.

Technical view

The record names mintToken in JavaSwapTest (JST) and describes the issue as integer overflow. No CWE, CVSS vector, affected CPEs, patch version, or exploit details are provided. Because this is smart-contract code, exposure depends on whether the referenced JST implementation or derived code was deployed or reused.

Likely exposure

Likely limited to Ethereum smart contracts or forks that use the referenced JavaSwapTest mintToken implementation. The CVE bundle lists vendor, product, and version as n/a, so enterprise exposure cannot be inferred from standard asset inventory alone.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not in KEV. The public description only says integer overflow in mintToken; it does not provide exploitability conditions, deployed contract addresses, or evidence of exploitation.

Researcher notes

Evidence is sparse. The CVE record provides a function name, token implementation, and vulnerability class, but lacks CVSS, CWE, affected versions, contract addresses, and remediation details. Analysis should focus on source-code lineage and deployed contract provenance rather than generic product matching.

Mitigation direction

  • Identify whether owned contracts reuse the referenced JavaSwapTest JST code.
  • Check the linked repository and CVE record for maintainer guidance.
  • If affected code exists, disable or restrict minting until reviewed.
  • Use checked arithmetic or compiler protections in any replacement contract.

Validation and detection

  • Search internal repositories for JavaSwapTest, JST, and mintToken references.
  • Review deployed contract source for the referenced vulnerable implementation.
  • Confirm whether minting arithmetic can overflow under permitted inputs.
  • Document any deployed addresses, owners, and reachable minting permissions.
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-13145 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.

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.