Skip to content

Commit ba5da8f

Browse files
committed
GHSA SYNC: 1 brand new advisory - 2011/webrick
1 parent ff594be commit ba5da8f

File tree

1 file changed

+39
-0
lines changed

1 file changed

+39
-0
lines changed

rubies/ruby/CVE-2011-3624.yml

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
engine: ruby
3+
cve: 2011-3624
4+
ghsa: rc82-v3mm-rhj2
5+
url: https://nvd.nist.gov/vuln/detail/CVE-2011-3624
6+
title: WEBrick::HTTPRequest X-Forwarded-* allows arbitrary data
7+
date: 2019-11-25
8+
description: |
9+
Various methods in WEBrick::HTTPRequest do not validate the
10+
X-Forwarded-For, X-Forwarded-Host and X-Forwarded-Server headers in
11+
requests, which might allow remote attackers to inject arbitrary text
12+
into log files or bypass intended address parsing via a crafted header.
13+
cvss_v2: 5.0
14+
cvss_v3: 5.3
15+
patched_versions:
16+
- "~> 1.9.2"
17+
- ">= 3.0.0"
18+
related:
19+
url:
20+
- https://nvd.nist.gov/vuln/detail/CVE-2011-3624
21+
- https://www.ruby-lang.org/en/news/2020/12/25/ruby-3-0-0-released
22+
- https://github.com/ruby/ruby/blob/v3_0_0/NEWS.md
23+
- https://bugs.ruby-lang.org/issues/17303
24+
- https://raw.githubusercontent.com/ruby/ruby/refs/heads/ruby_1_9_2/ChangeLog
25+
- https://access.redhat.com/security/cve/cve-2011-3624
26+
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-3624
27+
- https://security-tracker.debian.org/tracker/CVE-2011-3624
28+
- https://github.com/advisories/GHSA-rc82-v3mm-rhj2
29+
notes: |
30+
- Ruby 3.0.0 was the release when webrick was moved into a separate gem.
31+
- Did not find references to 1.8.7 fix.
32+
- Found this in above 1.9.2 ChangeLog. Unclear if connected.
33+
-- Fri Jun 24 19:57:30 2011 Hiroshi Nakamura <nahi@ruby-lang.org>
34+
* lib/webrick/httprequest.rb (setup_forwarded_info): Parsing request
35+
header failed when the request is from 2 or more Apache reverse
36+
proxies. It's said that all X-Forwarded-* headers will contain more
37+
than one (comma-separated) value if the original request already
38+
contained one of these headers. Since we could use these values as
39+
Host header, we choose the initial(first) value. See #4922.

0 commit comments

Comments
 (0)