LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13078: The mintToken function of a smart contract implementation for Jitech (JTH), an Ethereum token, has an integ...

The mintToken function of a smart contract implementation for Jitech (JTH), an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-13078 concerns a Jitech (JTH) Ethereum token contract where the minting function can overflow. The reported impact is token-balance integrity: the contract owner could set any user's balance to an arbitrary value. This matters mainly to organizations holding, accepting, listing, auditing, or reusing that specific token contract.

Executive priority

Treat this as targeted due diligence, not a broad enterprise emergency. Escalate if the business custodies, trades, lists, accepts, or depends on Jitech (JTH) balances. Otherwise, record it as a historical smart-contract integrity issue with limited direct exposure.

Technical view

The issue is described as an integer overflow in mintToken for a Jitech (JTH) Ethereum token smart contract. The CVE states the overflow allows the contract owner to set an arbitrary user's balance to any value. The source bundle does not include CVSS, CWE mapping, deployed address, patch status, or affected version detail.

Likely exposure

Exposure appears limited to the Jitech (JTH) token implementation and any direct forks or integrations relying on its balance accounting. The CVE record lists vendor, product, and versions as n/a, so asset-specific confirmation is required.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The described abuse depends on owner-controlled minting behavior, so the immediate risk is privileged manipulation of token balances rather than unauthenticated compromise.

Researcher notes

Evidence is sparse. The CVE describes the flaw and one GitHub reference, but gives no CVSS score, CWE, affected versions, deployed address, exploit report, or remediation. Researchers should avoid assuming affected deployments beyond the named Jitech contract implementation.

Mitigation direction

  • Identify whether any systems hold, accept, list, or integrate Jitech (JTH).
  • Check the referenced project and CVE record for vendor guidance or fixes.
  • Avoid relying on affected token balances until exposure is confirmed.
  • For forks, review mint arithmetic and use overflow-safe token logic.
  • Document any compensating controls for token listing or custody decisions.

Validation and detection

  • Inventory token contracts and integrations referencing Jitech or JTH.
  • Inspect mintToken logic for unsafe arithmetic and balance assignment behavior.
  • Confirm whether the deployed contract matches the vulnerable implementation.
  • Review token balance and supply history for unexplained changes.
  • Verify any forked contracts use overflow-safe compiler or libraries.
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-13078 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.

Source materials

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.