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

> Unprivileged attackers can exploit SSRF to read server files and potentially escalate privileges to root via exposed backup keys in Proxmox environments.

- **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:** No
- **Published:** 4 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-jfjw-xc26-6xpm

## What is CVE-2022-35508?

CVE-2022-35508 is a critical server-side request forgery vulnerability in n/a, published on 4 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Proxmox Virtual Environment (PVE) and Proxmox Mail Gateway (PMG) are vulnerable to SSRF when proxying HTTP requests between pve(pmg)proxy and pve(pmg)daemon. An attacker with an unprivileged account can craft an HTTP request to achieve SSRF and file disclosure of any files on the server. Also, in Proxmox Mail Gateway, privilege escalation to the root@pam account is possible if the backup feature has ever been used, because backup files such as pmg-backup_YYYY_MM_DD_*.tgz have 0644 permissions and contain an authkey value. This is fixed in pve-http-server 4.1-3.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 3 products.


Products: Proxmox Proxmox Mail Gateway, Proxmox Pve Http Server, Proxmox Virtual Environment.

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

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

## Is CVE-2022-35508 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-9057](https://insights.sbomify.com/CVE-2015-9057/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2015-9058](https://insights.sbomify.com/CVE-2015-9058/): Open redirect in n/a (medium 6.1)
- [CVE-2022-35507](https://insights.sbomify.com/CVE-2022-35507/): Other in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-35508 is a critical server-side request forgery vulnerability in n/a, published on 4 Dec 2022. 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-35508 exists.

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

## Sources

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

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