Skip to content

Commit 6ca514c

Browse files
postmodernRubySec CI
authored andcommitted
Updated advisory posts against rubysec/ruby-advisory-db@95316e8
1 parent 196568d commit 6ca514c

File tree

3 files changed

+132
-0
lines changed

3 files changed

+132
-0
lines changed
Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
layout: advisory
3+
title: 'CVE-2024-26142 (actionpack): Possible ReDoS vulnerability in Accept header
4+
parsing in Action Dispatch'
5+
comments: false
6+
categories:
7+
- actionpack
8+
- rails
9+
advisory:
10+
gem: actionpack
11+
framework: rails
12+
cve: 2024-26142
13+
url: https://discuss.rubyonrails.org/t/possible-redos-vulnerability-in-accept-header-parsing-in-action-dispatch/84946
14+
title: Possible ReDoS vulnerability in Accept header parsing in Action Dispatch
15+
date: 2024-02-21
16+
description: |
17+
There is a possible ReDoS vulnerability in the Accept header parsing routines
18+
of Action Dispatch. This vulnerability has been assigned the CVE identifier
19+
CVE-2024-26142.
20+
21+
Versions Affected: >= 7.1.0, < 7.1.3.1 Not affected: < 7.1.0 Fixed Versions: 7.1.3.1
22+
23+
# Impact
24+
25+
Carefully crafted Accept headers can cause Accept header parsing in
26+
Action Dispatch to take an unexpected amount of time, possibly resulting in a
27+
DoS vulnerability. All users running an affected release should either upgrade
28+
or use one of the workarounds immediately.
29+
30+
Ruby 3.2 has mitigations for this problem, so Rails applications using
31+
Ruby 3.2 or newer are unaffected.
32+
33+
# Releases
34+
35+
The fixed releases are available at the normal locations.
36+
37+
# Workarounds
38+
39+
There are no feasible workarounds for this issue.
40+
unaffected_versions:
41+
- "< 7.1.0"
42+
patched_versions:
43+
- ">= 7.1.3.1"
44+
---
Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
layout: advisory
3+
title: 'CVE-2024-26143 (actionpack): Possible XSS Vulnerability in Action Controller'
4+
comments: false
5+
categories:
6+
- actionpack
7+
- rails
8+
advisory:
9+
gem: actionpack
10+
framework: rails
11+
cve: 2024-26143
12+
url: https://discuss.rubyonrails.org/t/possible-xss-vulnerability-in-action-controller/84947
13+
title: Possible XSS Vulnerability in Action Controller
14+
date: 2024-02-21
15+
description: "There is a possible XSS vulnerability when using the translation helpers\n(`translate`,
16+
`t`, etc) in Action Controller. This vulnerability has been\nassigned the CVE
17+
identifier CVE-2024-26143.\n\nVersions Affected: All. Not affected: None Fixed
18+
Versions: 7.1.3.1, 7.0.8.1\n\n# Impact\n\nApplications using translation methods
19+
like `translate`, or `t` on a\ncontroller, with a key ending in “_html”, a `:default`
20+
key which contains\nuntrusted user input, and the resulting string is used in
21+
a view, may be\nsusceptible to an XSS vulnerability.\n\nFor example, impacted
22+
code will look something like this:\n\n```\nclass ArticlesController < ApplicationController\n
23+
\ def show \n @message = t(\"message_html\", default: untrusted_input)\n #
24+
The `show` template displays the contents of `@message`\n end\nend\n```\n\nTo
25+
reiterate the pre-conditions, applications must:\n\n* Use a translation function
26+
from a controller (i.e. *not* `I18n.t`, or\n`t` from a view)\n* Use a key that
27+
ends in `_html`\n* Use a default value where the default value is untrusted and
28+
unescaped input\n* Send the text to the victim (whether that’s part of a template,
29+
or a\n `render` call)\n\nAll users running an affected release should either
30+
upgrade or use one of the workarounds immediately.\n\n# Releases\n\nThe fixed
31+
releases are available at the normal locations.\n\n# Workarounds\n\nThere are
32+
no feasible workarounds for this issue.\n"
33+
patched_versions:
34+
- "~> 7.0.8, >= 7.0.8.1"
35+
- ">= 7.1.3.1"
36+
---
Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
layout: advisory
3+
title: 'CVE-2024-26144 (actionpack): Possible Sensitive Session Information Leak in
4+
Active Storage'
5+
comments: false
6+
categories:
7+
- actionpack
8+
- rails
9+
advisory:
10+
gem: actionpack
11+
framework: rails
12+
cve: 2024-26144
13+
url: https://discuss.rubyonrails.org/t/possible-sensitive-session-information-leak-in-active-storage/84945
14+
title: Possible Sensitive Session Information Leak in Active Storage
15+
date: 2024-02-21
16+
description: |
17+
There is a possible sensitive session information leak in Active Storage.
18+
By default, Active Storage sends a `Set-Cookie` header along with the user’s
19+
session cookie when serving blobs. It also sets `Cache-Control` to public.
20+
Certain proxies may cache the `Set-Cookie`, leading to an information leak.
21+
22+
This vulnerability has been assigned the CVE identifier CVE-2024-26144.
23+
24+
Versions Affected: >= 5.2.0, < 7.1.0 Not affected: < 5.2.0, >= 7.1.0 Fixed Versions: 7.0.8.1, 6.1.7.7
25+
26+
# Impact
27+
28+
A proxy which chooses to caches this request can cause users to share
29+
sessions. This may include a user receiving an attacker’s session or vice
30+
versa.
31+
32+
This was patched in 7.1.0 but not previously identified as a security
33+
vulnerability.
34+
35+
All users running an affected release should either upgrade or use one of the
36+
workarounds immediately.
37+
38+
# Releases
39+
40+
The fixed releases are available at the normal locations.
41+
42+
# Workarounds
43+
44+
Upgrade to Rails 7.1.X, or configure caching proxies not to cache the
45+
`Set-Cookie` headers.
46+
unaffected_versions:
47+
- "< 5.2.0"
48+
- ">= 7.1.0"
49+
patched_versions:
50+
- "~> 6.1.7, >= 6.1.7.7"
51+
- ">= 7.0.8.1"
52+
---

0 commit comments

Comments
 (0)