Bug 2179649 (CVE-2023-27539) - CVE-2023-27539 rubygem-rack: denial of service in header parsing
Summary: CVE-2023-27539 rubygem-rack: denial of service in header parsing
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2023-27539
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2179651 2179652 2179720 2180378 2180379 2180974 2180975 2180976 2180977 2180978 2180979 2180980 2182347
Blocks: 2178819
TreeView+ depends on / blocked
 
Reported: 2023-03-19 15:01 UTC by ybuenos
Modified: 2023-11-08 14:17 UTC (History)
25 users (show)

Fixed In Version: rubygem-rack 2.2.6.4, rubygem-rack 3.0.6.1
Doc Type: ---
Doc Text:
A denial of service vulnerability was found in rubygem-rack in how it parses headers. A carefully crafted input can cause header parsing to take an unexpected amount of time, possibly resulting in a denial of service.
Clone Of:
Environment:
Last Closed: 2023-06-13 06:16:46 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2023:1953 0 None None None 2023-04-26 07:58:26 UTC
Red Hat Product Errata RHSA-2023:1961 0 None None None 2023-04-25 08:29:19 UTC
Red Hat Product Errata RHSA-2023:1981 0 None None None 2023-04-25 10:21:24 UTC
Red Hat Product Errata RHSA-2023:2652 0 None None None 2023-05-09 11:35:40 UTC
Red Hat Product Errata RHSA-2023:3082 0 None None None 2023-05-16 09:59:10 UTC
Red Hat Product Errata RHSA-2023:3403 0 None None None 2023-05-31 15:44:54 UTC
Red Hat Product Errata RHSA-2023:3495 0 None None None 2023-06-12 19:08:59 UTC
Red Hat Product Errata RHSA-2023:6818 0 None None None 2023-11-08 14:17:22 UTC

Description ybuenos 2023-03-19 15:01:20 UTC
Carefully crafted input can cause header parsing in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector.

Comment 1 ybuenos 2023-03-19 15:05:24 UTC
Created rubygem-rack tracking bugs for this issue:

Affects: epel-all [bug 2179652]
Affects: fedora-all [bug 2179651]

Comment 7 errata-xmlrpc 2023-04-25 08:29:17 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.4 Extended Update Support

Via RHSA-2023:1961 https://access.redhat.com/errata/RHSA-2023:1961

Comment 8 errata-xmlrpc 2023-04-25 10:21:22 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.0 Extended Update Support

Via RHSA-2023:1981 https://access.redhat.com/errata/RHSA-2023:1981

Comment 9 errata-xmlrpc 2023-04-26 07:58:24 UTC
This issue has been addressed in the following products:

  RHOL-5.6-RHEL-8

Via RHSA-2023:1953 https://access.redhat.com/errata/RHSA-2023:1953

Comment 10 errata-xmlrpc 2023-05-09 11:35:37 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2023:2652 https://access.redhat.com/errata/RHSA-2023:2652

Comment 11 errata-xmlrpc 2023-05-16 09:59:08 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2023:3082 https://access.redhat.com/errata/RHSA-2023:3082

Comment 12 errata-xmlrpc 2023-05-31 15:44:52 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.6 Extended Update Support

Via RHSA-2023:3403 https://access.redhat.com/errata/RHSA-2023:3403

Comment 13 errata-xmlrpc 2023-06-12 19:08:57 UTC
This issue has been addressed in the following products:

  RHOL-5.7-RHEL-8

Via RHSA-2023:3495 https://access.redhat.com/errata/RHSA-2023:3495

Comment 14 Product Security DevOps Team 2023-06-13 06:16:43 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2023-27539

Comment 15 errata-xmlrpc 2023-11-08 14:17:19 UTC
This issue has been addressed in the following products:

  Red Hat Satellite 6.14 for RHEL 8

Via RHSA-2023:6818 https://access.redhat.com/errata/RHSA-2023:6818


Note You need to log in before you can comment on or make changes to this bug.