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

> Contract owner can issue arbitrary tokens by bypassing supply caps, devaluing the asset for all holders.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7qvr-f99m-rpch

## What is CVE-2018-18425?

CVE-2018-18425 is a medium-severity vulnerability in n/a, published on 19 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The doAirdrop function of a smart contract implementation for Primeo (PEO), an Ethereum token, does not check the numerical relationship between the amount of the air drop and the token's total supply, which lets the owner of the contract issue an arbitrary amount of currency. (Increasing the total supply by using 'doAirdrop' ignores the hard cap written in the contract and devalues the token.)

Weakness: CWE-330 (Use of Insufficiently Random Values)

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

It affects 1 product.


Products: Primeo Project Primeo.

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

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

## Is CVE-2018-18425 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18425 is a medium-severity vulnerability in n/a, published on 19 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-18425 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-18425/ (Markdown: https://insights.sbomify.com/CVE-2018-18425/index.md)
```

## Sources

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

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