LiveActive security incident?Get immediate response
CVE Record

CVE-2022-31045: Ill-formed headers may lead to unexpected behavior in Istio

Istio is an open platform to connect, manage, and secure microservices. In affected versions ill-formed headers sent to Envoy in certain configurations can lead to unexpected memory access resulting in undefined behavior or crashing. Users are most likely at risk if they have an Istio ingress Gateway exposed to external traffic. This vulnerability has been resolved in versions 1.12.8, 1.13.5, and 1.14.1. Users are advised to upgrade. There are no known workarounds for this issue.

HighCVSS 7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-31045 affects Istio deployments where malformed HTTP headers can make Envoy behave unpredictably or crash. The main business concern is disruption to externally exposed ingress gateways, with limited confidentiality and integrity impact also scored. Vendor guidance says to upgrade; no workaround is identified in the provided sources.

Executive priority

Treat this as high priority for internet-facing Istio ingress. The issue can cause service disruption without authentication, and the vendor names upgrades as the fix. It is less urgent for isolated deployments, but exposure should be verified quickly.

Technical view

Affected Istio versions can pass ill-formed headers to Envoy in certain configurations, causing unexpected memory access, undefined behavior, or crashes. The CVSS 3.1 score is 7.0 with network attack vector, no privileges, no user interaction, high attack complexity, and high availability impact.

Likely exposure

Highest exposure is an Istio ingress Gateway reachable from external traffic. Internal-only mesh components may still matter where untrusted clients can reach affected Envoy/Istio paths. The source bundle does not define the exact risky configurations beyond “certain configurations.”

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. Exploitation is network-reachable and unauthenticated, but CVSS marks attack complexity high. Expected impact is mainly crash or undefined behavior rather than confirmed full compromise.

Researcher notes

The provided data has an apparent 1.12 branch inconsistency: the description says fixed in 1.12.8, while the affected list says versions before 1.12.18. Use vendor advisories as authoritative and validate installed versions directly.

Mitigation direction

  • Upgrade Istio to 1.12.8, 1.13.5, 1.14.1, or later vendor-fixed releases.
  • Prioritize externally exposed Istio ingress Gateways for emergency maintenance windows.
  • Check Istio vendor guidance because the sources state no known workarounds.
  • Inventory clusters running affected Istio branches before changing production routing.

Validation and detection

  • Identify Istio versions deployed across clusters and compare against fixed versions.
  • Confirm whether any Istio ingress Gateway is exposed to external traffic.
  • Review gateway and proxy crash history around malformed-header handling symptoms.
  • Track vendor advisories for clarification on affected 1.12 branch version ranges.
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-125: 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-31045 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
High
CVSS
7 (3.1)
Known Exploited
No
Published

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

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
7CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H2.24.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7High
CVSS 3.1 vector shape for CVE-2022-31045Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
istioistio< 1.12.18, >= 1.13.0, < 1.13.5, >= 1.14.0, < 1.14.1Listed
Weakness

CWE details

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

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.