# CVE-2018-6353: Code injection in n/a

> Electrum's Python console allows arbitrary code execution, enabling attackers to steal Bitcoin via social engineering or physical access.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jan 2018
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2018-6353, GHSA-xpr2-2m5m-75jw

## What is CVE-2018-6353?

CVE-2018-6353 is a high-severity code injection vulnerability in n/a, published on 27 Jan 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Python console in Electrum through 2.9.4 and 3.x through 3.0.5 supports arbitrary Python code without considering (1) social-engineering attacks in which a user pastes code that they do not understand and (2) code pasted by a physically proximate attacker at an unattended workstation, which makes it easier for attackers to steal Bitcoin via hook code that runs at a later time when the wallet password has been entered, a different vulnerability than CVE-2018-1000022.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Electrum Electrum.

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

Upgrade to a fixed version.

## Is CVE-2018-6353 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-31246](https://insights.sbomify.com/CVE-2022-31246/): Server-side request forgery in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-6353 is a high-severity code injection vulnerability in n/a, published on 27 Jan 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-6353 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-6353/ (Markdown: https://insights.sbomify.com/CVE-2018-6353/index.md)
```

## Sources

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

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