Bug 2132001 (CVE-2022-2929) - CVE-2022-2929 dhcp: DHCP memory leak
Summary: CVE-2022-2929 dhcp: DHCP memory leak
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2022-2929
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: 2132245 2132246 2132430
Blocks: 2131939
TreeView+ depends on / blocked
 
Reported: 2022-10-04 12:39 UTC by TEJ RATHI
Modified: 2023-05-16 16:52 UTC (History)
16 users (show)

Fixed In Version: dhcp 4.4.3-P1, dhcp 4.1-ESV-R16-P2
Clone Of:
Environment:
Last Closed: 2023-05-16 16:52:47 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2023:2502 0 None None None 2023-05-09 07:54:09 UTC
Red Hat Product Errata RHSA-2023:3000 0 None None None 2023-05-16 08:41:08 UTC

Description TEJ RATHI 2022-10-04 12:39:43 UTC 
A vulnerability was found in DHCP, where, a system with access to a DHCP server, sending DHCP packets crafted to include "fqdn" labels longer than 63 bytes, could eventually cause the server to run out of memory.

Versions affected:

- 1.0.0 -> 4.1-ESV-R16-P1
- 4.2.0 -> 4.4.3
Comment 5 Guilherme de Almeida Suckevicz 2022-10-05 16:36:17 UTC 
Created dhcp tracking bugs for this issue:

Affects: fedora-all [bug 2132430]
Comment 7 errata-xmlrpc 2023-05-09 07:54:07 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2023:2502 https://access.redhat.com/errata/RHSA-2023:2502
Comment 8 errata-xmlrpc 2023-05-16 08:41:06 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2023:3000 https://access.redhat.com/errata/RHSA-2023:3000
Comment 9 Product Security DevOps Team 2023-05-16 16:52:45 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-2022-2929
Note You need to log in before you can comment on or make changes to this bug.