Vulnerability report

Exploited in the wild High confidence Not in CISA KEV

CVE-2018-11239

HXG (Ethereum ERC20 token)

Hexagon / HXG (Ethereum ERC20 token)

Watch CVE-2018-11239 Browse KEV feed
Severity
CVSS 7.5 · High
Confidence
High
Exploit status
Exploited in the wild
EPSS
0.9%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2018-11239 is an unauthenticated vulnerability affecting Hexagon HXG (Ethereum ERC20 token). An integer overflow in the _transfer function of a smart contract implementation for Hexagon (HXG), an Ethereum ERC20...

Is it exploited?

Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is high. Also confirmed by third-party sources.

Who is affected?

Hexagon / HXG (Ethereum ERC20 token).

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

HXG (Ethereum ERC20 token)

An integer overflow in the _transfer function of a smart contract implementation for Hexagon (HXG), an Ethereum ERC20 token, allows attackers to accomplish an unauthorized increase of digital assets by providing a _to argument in conjunction with a large _value argument, as exploited in the wild in May 2018, aka the "burnOverflow" issue.

Published
19 May 2018
Exploitation Reported
19 May 2018
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

CVE

Recorded 19 May 2018

A trusted third party reported exploitation.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CVE First 2018-05-19 18:00 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
0
0
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

Risk and context

Severity, weaknesses, and research context

CVSS v3.0

7.5 High

Potential damage if exploited. Separate from whether attackers are using it.

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS

0.9%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Weaknesses

Integer Overflow or Wraparound CWE-190

All CVSS Scores

CVSS v3.0 7.5 High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

CVSS v2.0 5.0 Medium

AV:N/AC:L/Au:N/C:N/I:P/A:N

Timeline

From disclosure to observed exploitation

  1. 18:00 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party attested exploitation

  2. 18:00 UTC

    CVE published

    Vulnerability disclosed publicly

  3. 00:00 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

Start 14-day Pro trial Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2018-11239

Sample API response 
{
  "cve_id": "CVE-2018-11239",
  "confidence": "High",
  "cvss_score": 7.5,
  "cvss_estimated": false,
  "epss_score": 0.00912,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}