LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35507: A response-header CRLF injection vulnerability in the Proxmox Virtual Environment (PVE) and Proxmox Mail Ga...

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.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects the Proxmox VE and Proxmox Mail Gateway web interface. A crafted interaction could make a victim’s Chromium-based browser store oversized cookies, causing a client-side denial of service. It is not listed as actively exploited in CISA KEV, and the supplied sources name pve-http-server 4.1-3 as the fix.

Executive priority

Treat this as a moderate maintenance priority. It can disrupt administrator browser sessions but the sources do not support active exploitation, server compromise, or data exposure. Prioritize patching where Proxmox web interfaces are used by administrators.

Technical view

CVE-2022-35507 is a response-header CRLF injection issue in the Proxmox web interface. The source description says Chromium-based browsers allow response header injection with %0d, enabling cookie manipulation beyond server expectations and client-side DoS. CVSS is 4.3, network reachable, low complexity, no privileges required, and user interaction required.

Likely exposure

Exposure is likely limited to organizations running Proxmox VE or Proxmox Mail Gateway web interfaces with vulnerable pve-http-server versions before 4.1-3. The bundle does not provide precise affected version ranges, deployment counts, or PMG-specific fixed package mapping.

Exploitation context

The supplied evidence does not show active exploitation, and KEV is false. Exploitation requires victim interaction and is described as affecting Chromium-based browsers. The documented impact is client-side denial of service through oversized cookies, not server takeover or data theft.

Researcher notes

The public record ties the bug to CWE-74 and response-header CRLF injection. Evidence is incomplete on affected version ranges and PMG fixed package details. Avoid assuming broader browser impact beyond the Chromium-specific behavior stated in the description.

Mitigation direction

  • Upgrade affected Proxmox systems to a release containing pve-http-server 4.1-3.
  • Check Proxmox vendor guidance for PMG-specific fixed package mapping.
  • Confirm browser-side DoS reports before treating this as an incident.
  • Keep Proxmox management interfaces limited to authorized administrative access.

Validation and detection

  • Inventory Proxmox VE and Proxmox Mail Gateway web interfaces.
  • Verify installed pve-http-server versions against the 4.1-3 fixed version.
  • Confirm whether administrators use Chromium-based browsers for affected interfaces.
  • Review vendor release notes for matching Proxmox package updates.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-74: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-35507 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2022-35507Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-74 · source CWE mapping

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.