# CVE-2018-12082: Business logic in n/a

> The smart contract owner can arbitrarily increase token supply due to missing constraints, allowing for potential financial manipulation and profit extraction.

- **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:** 25 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7r7w-6h49-2fqr

## What is CVE-2018-12082?

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

### Official description

The mintToken function of a smart contract implementation for Fujinto (NTO), a tradable Ethereum ERC20 token, has no period constraint, which allows the owner to increase the total supply of the digital assets arbitrarily so as to make profits, aka the "tradeTrap" issue.

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

It affects 1 product.


Products: Fujinto Project Fujinto.

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

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

## Is CVE-2018-12082 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-12082 is a high-severity vulnerability in n/a, published on 25 Jun 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-12082 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-12082/ (Markdown: https://insights.sbomify.com/CVE-2018-12082/index.md)
```

## Sources

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

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