# CVE-2018-1000093: Cross-site request forgery in n/a

> An attacker can execute remote commands and take over the cryptocurrency wallet by tricking a victim into visiting a malicious webpage that interacts with the unauthenticated local RPC server.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pmh5-hfq5-56mq

## What is CVE-2018-1000093?

CVE-2018-1000093 is a high-severity vulnerability in n/a, published on 13 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

CryptoNote version version 0.8.9 and possibly later contain a local RPC server which does not require authentication, as a result the walletd and the simplewallet RPC daemons will process any commands sent to them, resulting in remote command execution and a takeover of the cryptocurrency wallet if an attacker can trick an application such as a web browser into connecting and sending a command for example. This attack appears to be exploitable via a victim visiting a webpage hosting malicious content that trigger such behavior.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Cryptonote Cryptonote.

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

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

## Is CVE-2018-1000093 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1000093 is a high-severity vulnerability in n/a, published on 13 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1000093 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-1000093/ (Markdown: https://insights.sbomify.com/CVE-2018-1000093/index.md)
```

## Sources

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

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