# CVE-2018-12511: Integer overflow in n/a

> An integer overflow in the mintToken function allows administrators to arbitrarily modify user account balances in the Substratum token.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rw23-7674-g3f6

## What is CVE-2018-12511?

CVE-2018-12511 is a high-severity vulnerability in n/a, published on 21 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the mintToken function of a smart contract implementation for Substratum (SUB), an Ethereum ERC20 token, the administrator can control mintedAmount, leverage an integer overflow, and modify a user account's balance arbitrarily.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2018-12511?

It affects 1 product.


Products: Substratum Substratum.

## How do I fix CVE-2018-12511?

No fix has been published for CVE-2018-12511 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-12511 being exploited?

There is no known exploitation of CVE-2018-12511 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-12067](https://insights.sbomify.com/CVE-2018-12067/): Integer overflow in n/a (high 7.5)
- [CVE-2018-12079](https://insights.sbomify.com/CVE-2018-12079/): Business logic in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12511 and fix it if it is affected.

What it is: CVE-2018-12511 is a high-severity vulnerability in n/a, published on 21 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-12511 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-12511/ (Markdown: https://insights.sbomify.com/CVE-2018-12511/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-12511
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-12511
- OSV: https://osv.dev/vulnerability/CVE-2018-12511

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-12511/
Summaries are generated and may contain mistakes; the official description above is the record.