LiveActive security incident?Get immediate response
CVE Record

CVE-2022-31458: RTX TRAP v1.0 was discovered to be vulnerable to host header poisoning.

RTX TRAP v1.0 was discovered to be vulnerable to host header poisoning.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-31458 reports that RTX TRAP v1.0 is vulnerable to host header poisoning. In business terms, the application may trust attacker-controlled web request header data when generating links or routing behavior. The public record is sparse: no CVSS score, affected CPE, vendor advisory, patch, or confirmed exploitation is provided.

Executive priority

Treat this as an inventory and configuration validation item until better vendor data appears. Prioritize it higher if RTX TRAP v1.0 is internet-facing, supports account recovery, sends links by email, or sits behind shared caching infrastructure.

Technical view

The CVE description only states host header poisoning in RTX TRAP v1.0. Generic host header attacks involve an application using an untrusted Host header in security-sensitive logic, generated URLs, redirects, caches, or password-reset style workflows. The bundle does not provide vulnerable endpoints, prerequisites, exploit details, CWE mapping, or a fixed version.

Likely exposure

Exposure is limited to environments running RTX TRAP v1.0 with reachable HTTP services that process untrusted Host headers. The source bundle does not identify CPEs, deployment models, default ports, internet exposure, or whether later versions are affected.

Exploitation context

There is no KEV listing and no cited source in the bundle confirming active exploitation. The references support the vulnerability class and a public write-up, but the CVE metadata does not establish real-world abuse, exploit maturity, or weaponized availability.

Researcher notes

The public CVE record is unusually thin: no CVSS, CWE, CPE, patch reference, vulnerable endpoint, or exploitation evidence is included. Analysis should stay focused on host header trust boundaries and RTX TRAP v1.0 confirmation rather than assuming broader product impact.

Mitigation direction

  • Check RTX TRAP vendor or maintainer guidance for a fixed version or supported workaround.
  • Enforce trusted host allowlists at the application, web server, or reverse proxy layer.
  • Avoid generating security-sensitive absolute URLs from unvalidated request headers.
  • Review password reset, redirect, cache, and email-link flows for Host header trust.
  • Limit internet exposure until vendor guidance and validation are complete.

Validation and detection

  • Confirm whether RTX TRAP v1.0 exists in asset inventory or exposed web services.
  • Review reverse proxy and application configuration for trusted host enforcement.
  • Use authorized non-production testing to verify untrusted Host values are rejected or ignored.
  • Inspect generated links, redirects, and emails for attacker-controlled host influence.
  • Check web logs for anomalous Host header values against affected services.
Prepared
Confidence
low
Sources
4

Public sources used

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.

cve · low confidence lookup

CVE-2022-31458 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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