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

> Attackers can steal digital assets from SmartMesh tokens via replay attacks exploiting identical function signatures in other tokens.

- **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:** 10 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-53rj-fp6v-2893

## What is CVE-2018-10769?

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

### Official description

The transferProxy and approveProxy functions of a smart contract implementation for SmartMesh (SMT), an Ethereum ERC20 token, allow attackers to accomplish an unauthorized transfer of digital assets because replay attacks can occur with the same-named functions (with the same signatures) in other tokens: First (FST), GG Token (GG), M2C Mesh Network (MTC), M2C Mesh Network (mesh), and UG Token (UGT).

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

It affects 6 products.


Products: First Project First, Gg Token Project Gg Token, Mesh Project Mesh, Mtc Project Mtc, Smartmesh Project Smartmesh, Ugtoken Project Ugtoken.

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

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

## Is CVE-2018-10769 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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