{"answers":{"affected":"It affects 3 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-35508 exists.","fix":"No fix has been published for CVE-2022-35508 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2022-35508 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-35508 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-35508/ (Markdown: https://insights.sbomify.com/CVE-2022-35508/index.md)","id":"CVE-2022-35508","markdown":"https://insights.sbomify.com/CVE-2022-35508/index.md","name":"CVE-2022-35508","record":{"aliases":["GHSA-jfjw-xc26-6xpm"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Proxmox virtualization platform","requires_auth":"none","summary":"Unprivileged attackers can exploit SSRF to read server files and potentially escalate privileges to root via exposed backup keys in Proxmox environments.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"proxmox_mail_gateway","vendor":"proxmox"},{"product":"pve_http_server","vendor":"proxmox"},{"product":"virtual_environment","vendor":"proxmox"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Server-side request forgery in n/a","id":"CVE-2022-35508","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-35509"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2022-35507"},"products":["n/a"],"published":"2022-12-04","related":[{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2015-9057","kev_date_added":null,"published":"2017-05-03"},{"cvss_score":6.1,"headline":"Open redirect in n/a","id":"CVE-2015-9058","kev_date_added":null,"published":"2017-05-03"},{"cvss_score":4.3,"headline":"Other in n/a","id":"CVE-2022-35507","kev_date_added":null,"published":"2022-12-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-24","vendors":["n/a"]},"summary":"Unprivileged attackers can exploit SSRF to read server files and potentially escalate privileges to root via exposed backup keys in Proxmox environments.","url":"https://insights.sbomify.com/CVE-2022-35508/"}