LiveActive security incident?Get immediate response
CVE Record

CVE-2011-3624: Various methods in WEBrick::HTTPRequest in Ruby 1.9.2 and 1.8.7 and earlier do not validate the X-Forwarded...

Various methods in WEBrick::HTTPRequest in Ruby 1.9.2 and 1.8.7 and earlier do not validate the X-Forwarded-For, X-Forwarded-Host and X-Forwarded-Server headers in requests, which might allow remote attackers to inject arbitrary text into log files or bypass intended address parsing via a crafted header.

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

Security readout for executives and security teams

Plain-English summary

CVE-2011-3624 affects older Ruby WEBrick HTTP request handling. Certain forwarded headers were not validated, allowing a remote requester to place arbitrary text in logs or interfere with intended address parsing. Business impact depends on whether old Ruby WEBrick is internet-facing or trusted for logging, access decisions, or audit trails.

Executive priority

Prioritize discovery over emergency response unless legacy WEBrick is internet-facing or used for access decisions. The issue is old, lacks confirmed active exploitation in the provided sources, and has unclear severity, but it can undermine logs and address-based controls.

Technical view

Ruby WEBrick::HTTPRequest in Ruby 1.9.2, 1.8.7, and earlier did not validate X-Forwarded-For, X-Forwarded-Host, and X-Forwarded-Server headers. Crafted request headers may cause log injection or bypass intended address parsing. The source bundle provides no CVSS, CWE, or confirmed fixed version details.

Likely exposure

Exposure is most likely in legacy Ruby deployments using WEBrick to receive untrusted HTTP traffic. Risk increases where forwarded headers influence logs, client address handling, host processing, auditing, or security decisions.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The issue is remotely reachable when WEBrick processes crafted forwarded headers, but exploit prevalence and real-world use are not established in the bundle.

Researcher notes

Key gaps are absence of CVSS, CWE, patch metadata, and exploitation evidence in the supplied bundle. Analysis should focus on legacy Ruby WEBrick exposure and whether downstream code trusts forwarded header-derived address or host values.

Mitigation direction

  • Inventory Ruby versions 1.9.2, 1.8.7, and earlier using WEBrick.
  • Check Ruby, Debian, and Red Hat guidance for fixed package versions.
  • Upgrade legacy Ruby runtimes where vendor-supported fixes are available.
  • Accept X-Forwarded headers only from trusted proxy boundaries.
  • Treat affected logs as potentially untrusted until remediated.

Validation and detection

  • Confirm whether WEBrick::HTTPRequest is used in production or exposed services.
  • Verify Ruby runtime versions across servers, containers, and build images.
  • Review proxy configuration controlling forwarded headers before WEBrick.
  • Check logs for malformed forwarded header values during relevant periods.
  • Document whether client IP or host decisions depend on these headers.
Prepared
Confidence
medium
Sources
6

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-2011-3624 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
5Source 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
RubyRuby1.9.2, 1.8.7 and earlierListed
Weakness

CWE details

No CWE listed

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