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

> An attacker can manipulate the sweeper list in the UserWallet smart contract by adding a malicious contract, altering internal state variables.

- **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:** 16 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-h6pf-g657-4j3g

## What is CVE-2018-14085?

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

### Official description

An issue was discovered in a smart contract implementation for UserWallet 0x0a7bca9FB7AfF26c6ED8029BB6f0F5D291587c42, an Ethereum token. First, suppose that the owner adds the evil contract address to his sweepers. The evil contract looks like this: contract Exploit { uint public start; function sweep(address _token, uint _amount) returns (bool) { start = 0x123456789; return true;} }. Then, when one calls the function sweep() in the UserWallet contract, it will change the sweeperList to 0X123456789.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Userwallet Project Userwallet.

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

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

## Is CVE-2018-14085 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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