{"answers":{"affected":"It affects 3 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-35507 exists.","fix":"No fix has been published for CVE-2022-35507 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-35507 is a medium-severity vulnerability in n/a, published on 4 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-35507 and fix it if it is affected.\n\nWhat it is: CVE-2022-35507 is a medium-severity vulnerability in n/a, published on 4 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-35507 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-35507/ (Markdown: https://insights.sbomify.com/CVE-2022-35507/index.md)","id":"CVE-2022-35507","markdown":"https://insights.sbomify.com/CVE-2022-35507/index.md","name":"CVE-2022-35507","record":{"aliases":["GHSA-xfgp-gpjw-wmqr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Proxmox web interface","requires_auth":"none","summary":"Remote attackers can cause client-side denial of service in Chromium browsers via CRLF injection in Proxmox web interface response headers.","user_interaction":"required","vuln_class":"other"},"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":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"A response-header CRLF injection vulnerability in the Proxmox Virtual Environment (PVE) and Proxmox Mail Gateway (PMG) web interface allows a remote attacker to set cookies for a victim's browser that are longer than the server expects, causing a client-side DoS. This affects Chromium-based browsers because they allow injection of response headers with %0d. 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":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2022/CVE-2022-35507.yaml","stars":null,"title":"Proxmox - CRLF Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"Other in n/a","id":"CVE-2022-35507","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2022-35508"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2022-35506"},"products":["n/a"],"published":"2022-12-04","related":[{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2022-35508","kev_date_added":null,"published":"2022-12-04"},{"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"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-24","vendors":["n/a"]},"summary":"Remote attackers can cause client-side denial of service in Chromium browsers via CRLF injection in Proxmox web interface response headers.","url":"https://insights.sbomify.com/CVE-2022-35507/"}