Security readout for executives and security teams
Plain-English summary
CVE-2021-31922 affects Pulse Secure Virtual Traffic Manager before the fixed releases. It could let an attacker hide one HTTP request inside another via an HTTP/2 header, potentially confusing downstream request handling. The source bundle does not provide CVSS, impact detail, or evidence of active exploitation.
Executive priority
Treat this as a targeted remediation item for any vTM deployment at application ingress. Business urgency depends on exposure and version because the source bundle lacks severity scoring and exploitation evidence. Internet-facing HTTP/2 deployments should be checked first.
Technical view
The CVE describes HTTP request smuggling through an HTTP/2 header in Pulse Secure Virtual Traffic Manager. Fixed versions are 21.1, 20.3R1, 20.2R1, 20.1R2, 19.2R4, and 18.2R3. No CWE, CVSS vector, exploit detail, or affected CPE list is provided in the bundle.
Likely exposure
Organizations using Pulse Secure Virtual Traffic Manager versions earlier than the listed fixed releases are the likely exposed population, especially where vTM processes HTTP/2 traffic at application ingress. The bundle does not identify specific editions, configurations, or CPEs.
Exploitation context
The provided data does not show CISA KEV listing or other cited evidence of active exploitation. The vulnerability class is serious because request smuggling can affect routing, authentication boundaries, caching, or backend request interpretation, but those impacts are not specifically confirmed here.
Researcher notes
Evidence is limited to the CVE description and Pulse Secure advisory reference. Do not assume exploit availability, affected CPEs, or mitigations beyond fixed releases without vendor confirmation. Focus validation on version state, HTTP/2 exposure, and ingress placement.
Mitigation direction
- Upgrade vTM to 21.1 or the fixed release for your supported branch.
- Review Pulse Secure advisory SA44790 for vendor-specific instructions.
- Prioritize internet-facing and HTTP/2-enabled vTM deployments.
- If upgrade is delayed, check vendor guidance for supported compensating controls.
Validation and detection
- Inventory all Pulse Secure Virtual Traffic Manager instances and versions.
- Confirm each instance is on 21.1 or a listed fixed branch release.
- Identify whether HTTP/2 traffic is accepted or proxied through vTM.
- Document public ingress routes that traverse vulnerable vTM instances.
- Review relevant proxy logs for unusual request parsing or routing anomalies.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2021-31922 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA44790CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.