# CVE-2022-31246: Server-side request forgery in n/a

> Attackers can exploit file:// URLs in payment requests to steal credentials via SMB on Windows or cause denial of service on Linux.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-31246, GHSA-4fh4-hx35-r355, GHSA-h899-2p3m-3gm2

## What is CVE-2022-31246?

CVE-2022-31246 is a medium-severity server-side request forgery vulnerability in n/a, published on 17 Jun 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

paymentrequest.py in Electrum before 4.2.2 allows a file:// URL in the r parameter of a payment request (e.g., within QR code data). On Windows, this can lead to capture of credentials over SMB. On Linux and UNIX, it can lead to a denial of service by specifying the /dev/zero filename.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2022-31246?

It affects 1 product.


Products: Electrum Electrum.

## How do I fix CVE-2022-31246?

Upgrade to a fixed version.

## Is CVE-2022-31246 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-6353](https://insights.sbomify.com/CVE-2018-6353/): Code injection in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31246 and fix it if it is affected.

What it is: CVE-2022-31246 is a medium-severity server-side request forgery vulnerability in n/a, published on 17 Jun 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-31246 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-2022-31246/ (Markdown: https://insights.sbomify.com/CVE-2022-31246/index.md)
```

## Sources

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

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