LiveActive security incident?Get immediate response
CVE Record

CVE-2022-32148: Exposure of client IP addresses in net/http

Improper exposure of client IP addresses in net/http before Go 1.17.12 and Go 1.18.4 can be triggered by calling httputil.ReverseProxy.ServeHTTP with a Request.Header map containing a nil value for the X-Forwarded-For header, which causes ReverseProxy to set the client IP as the value of the X-Forwarded-For header.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Some Go reverse proxy applications could unintentionally reveal a client IP address in the X-Forwarded-For header under a specific malformed-header condition. This is mainly a privacy and trust-boundary issue, not a full system compromise. Services built with affected Go versions should be upgraded and rebuilt.

Executive priority

Treat this as a moderate privacy and exposure fix. It should be included in normal security patch cycles, with faster handling for public reverse proxies or regulated environments where client IP exposure matters.

Technical view

In net/http before Go 1.17.12 and 1.18.4, httputil.ReverseProxy.ServeHTTP could populate X-Forwarded-For with the client IP when the request header map contained a nil X-Forwarded-For value. The issue is classified as CWE-200 with CVSS 6.5.

Likely exposure

Exposure is most likely in Go services using httputil.ReverseProxy and built with Go versions earlier than 1.17.12 or 1.18.4. Applications not using ReverseProxy, or rebuilt with fixed Go releases, are less likely exposed.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The vulnerable condition is network-reachable and low-complexity, but the documented impact is limited to client IP exposure and possible header trust issues.

Researcher notes

Evidence is specific to Go standard library net/http behavior and the nil X-Forwarded-For header case. No broader product list or exploitation claims are supported by the provided sources. Validation should focus on build version and ReverseProxy usage.

Mitigation direction

  • Upgrade Go toolchains to 1.17.12, 1.18.4, or later supported releases.
  • Rebuild and redeploy Go services that use net/http reverse proxy functionality.
  • Prioritize internet-facing reverse proxies and services processing sensitive client identity data.
  • Check Go advisory GO-2022-0520 and vendor guidance for downstream product-specific updates.

Validation and detection

  • Inventory Go services using httputil.ReverseProxy or net/http reverse proxy behavior.
  • Confirm each deployed binary was rebuilt with Go 1.17.12, 1.18.4, or later.
  • Review proxy header handling for trust decisions based on X-Forwarded-For.
  • Check logs and monitoring for unexpected client IP propagation in proxied requests.
Prepared
Confidence
high
Sources
7

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 · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-32148 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
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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
6Source 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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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
Go standard librarynet/httpnet/http, 0, 1.18.0-0unaffected
Weakness

CWE details

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

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.