Skip to content

Commit 3632733

Browse files
postmodernRubySec CI
authored andcommitted
Updated advisory posts against rubysec/ruby-advisory-db@f50d023
1 parent 9543dd9 commit 3632733

File tree

3 files changed

+161
-0
lines changed

3 files changed

+161
-0
lines changed
Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
layout: advisory
3+
title: 'CVE-2024-25126 (rack): Denial of Service Vulnerability in Rack Content-Type
4+
Parsing'
5+
comments: false
6+
categories:
7+
- rack
8+
advisory:
9+
gem: rack
10+
cve: 2024-25126
11+
url: https://discuss.rubyonrails.org/t/denial-of-service-vulnerability-in-rack-content-type-parsing/84941
12+
title: Denial of Service Vulnerability in Rack Content-Type Parsing
13+
date: 2024-02-21
14+
description: |
15+
There is a possible denial of service vulnerability in the content type
16+
parsing component of Rack. This vulnerability has been assigned the CVE
17+
identifier CVE-2024-25126.
18+
19+
Versions Affected: >= 0.4 Not affected: < 0.4 Fixed Versions: 3.0.9.1, 2.2.8.1
20+
21+
# Impact
22+
23+
Carefully crafted content type headers can cause Rack’s media type parser to
24+
take much longer than expected, leading to a possible denial of service
25+
vulnerability.
26+
27+
Impacted code will use Rack’s media type parser to parse content type headers.
28+
This code will look like below:
29+
30+
```
31+
request.media_type
32+
33+
## OR
34+
request.media_type_params
35+
36+
## OR
37+
Rack::MediaType.type(content_type)
38+
```
39+
40+
Some frameworks (including Rails) call this code internally, so upgrading is
41+
recommended!
42+
43+
All users running an affected release should either upgrade or use one of the
44+
workarounds immediately.
45+
46+
# Releases
47+
48+
The fixed releases are available at the normal locations.
49+
50+
# Workarounds
51+
52+
There are no feasible workarounds for this issue.
53+
unaffected_versions:
54+
- "< 0.4"
55+
patched_versions:
56+
- "~> 2.2.8, >= 2.2.8.1"
57+
- ">= 3.0.9.1"
58+
related:
59+
url:
60+
- https://github.com/rack/rack/releases/tag/v3.0.9.1
61+
- https://github.com/rack/rack/releases/tag/v2.2.8.1
62+
- https://nvd.nist.gov/vuln/detail/CVE-2024-25126
63+
- https://access.redhat.com/security/cve/cve-2024-25126
64+
- https://ubuntu.com/security/CVE-2024-25126
65+
---
Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
---
2+
layout: advisory
3+
title: 'CVE-2024-26141 (rack): Possible DoS Vulnerability with Range Header in Rack'
4+
comments: false
5+
categories:
6+
- rack
7+
advisory:
8+
gem: rack
9+
cve: 2024-26141
10+
url: https://discuss.rubyonrails.org/t/possible-dos-vulnerability-with-range-header-in-rack/84944
11+
title: Possible DoS Vulnerability with Range Header in Rack
12+
date: 2024-02-21
13+
description: |
14+
There is a possible DoS vulnerability relating to the Range request header in
15+
Rack. This vulnerability has been assigned the CVE identifier CVE-2024-26141.
16+
17+
Versions Affected: >= 1.3.0. Not affected: < 1.3.0 Fixed Versions: 3.0.9.1, 2.2.8.1
18+
19+
# Impact
20+
21+
Carefully crafted Range headers can cause a server to respond with an
22+
unexpectedly large response. Responding with such large responses could lead
23+
to a denial of service issue.
24+
25+
Vulnerable applications will use the `Rack::File` middleware or the
26+
`Rack::Utils.byte_ranges` methods (this includes Rails applications).
27+
28+
# Releases
29+
30+
The fixed releases are available at the normal locations.
31+
32+
# Workarounds
33+
34+
There are no feasible workarounds for this issue.
35+
unaffected_versions:
36+
- "< 1.3.0"
37+
patched_versions:
38+
- "~> 2.2.8, >= 2.2.8.1"
39+
- ">= 3.0.9.1"
40+
related:
41+
url:
42+
- https://github.com/rack/rack/releases/tag/v3.0.9.1
43+
- https://github.com/rack/rack/releases/tag/v2.2.8.1
44+
- https://nvd.nist.gov/vuln/detail/CVE-2024-25141
45+
- https://access.redhat.com/security/cve/cve-2024-26141
46+
- https://ubuntu.com/security/CVE-2024-26141
47+
---
Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
layout: advisory
3+
title: 'CVE-2024-26146 (rack): Possible Denial of Service Vulnerability in Rack Header
4+
Parsing'
5+
comments: false
6+
categories:
7+
- rack
8+
advisory:
9+
gem: rack
10+
cve: 2024-26146
11+
url: https://discuss.rubyonrails.org/t/possible-denial-of-service-vulnerability-in-rack-header-parsing/84942
12+
title: Possible Denial of Service Vulnerability in Rack Header Parsing
13+
date: 2024-02-21
14+
description: |
15+
There is a possible denial of service vulnerability in the header parsing
16+
routines in Rack. This vulnerability has been assigned the CVE identifier
17+
CVE-2024-26146.
18+
19+
Versions Affected: All. Not affected: None Fixed Versions: 2.0.9.4, 2.1.4.4, 2.2.8.1, 3.0.9.1
20+
21+
# Impact
22+
23+
Carefully crafted headers can cause header parsing in Rack to take longer than
24+
expected resulting in a possible denial of service issue. `Accept` and
25+
`Forwarded` headers are impacted.
26+
27+
Ruby 3.2 has mitigations for this problem, so Rack applications using
28+
Ruby 3.2 or newer are unaffected.
29+
30+
# Releases
31+
32+
The fixed releases are available at the normal locations.
33+
34+
# Workarounds
35+
36+
There are no feasible workarounds for this issue.
37+
patched_versions:
38+
- "~> 2.0.9, >= 2.0.9.4"
39+
- "~> 2.1.4, >= 2.1.4.4"
40+
- "~> 2.2.8, >= 2.2.8.1"
41+
- ">= 3.0.9.1"
42+
related:
43+
url:
44+
- https://github.com/rack/rack/releases/tag/v3.0.9.1
45+
- https://github.com/rack/rack/releases/tag/v2.2.8.1
46+
- https://nvd.nist.gov/vuln/detail/CVE-2024-26146
47+
- https://access.redhat.com/security/cve/cve-2024-26146
48+
- https://ubuntu.com/security/CVE-2024-26146
49+
---

0 commit comments

Comments
 (0)