# CVE-2022-45299: webbrowser-rs allows attackers to access arbitrary files via supplying a crafted URL

> Attackers can access arbitrary files by supplying a crafted URL to the IpFile argument in the webbrowser-rs library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jan 2023
- **Updated:** 7 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-45299, GHSA-m589-mv4q-p7rj, UBUNTU-CVE-2022-45299, openSUSE-SU-2024:12620-1

## What is CVE-2022-45299?

CVE-2022-45299 is a critical path traversal vulnerability in n/a, published on 13 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in the IpFile argument of rust-lang webbrowser-rs v0.8.2 allows attackers to access arbitrary files via supplying a crafted URL.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

2 open source packages ship an affected version, including webbrowser. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `webbrowser` | crates.io | All versions | 0.8.3 |
| `webbrowser` | crates.io | All versions | 0.8.3 |

Products: Webbrowser Project Webbrowser.

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

Upgrade webbrowser to 0.8.3 or later.

## Is CVE-2022-45299 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45299 exists.

Public exploit code:

- CVE 2022-45299 (github_poc): https://github.com/offalltn/CVE-2022-45299

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45299 is a critical path traversal vulnerability in n/a, published on 13 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45299 exists.

Affected packages and fixed versions:
- webbrowser (crates.io): affected all versions; fixed in 0.8.3
- webbrowser (crates.io): affected all versions; fixed in 0.8.3

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-45299/ (Markdown: https://insights.sbomify.com/CVE-2022-45299/index.md)
```

## Sources

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

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