Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2132240 - dhcp-4.4.3-P1 is available
Summary: dhcp-4.4.3-P1 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dhcp
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Osvald 🛹
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-05 08:15 UTC by Upstream Release Monitoring
Modified: 2022-10-26 17:34 UTC (History)
5 users (show)

Fixed In Version: dhcp-4.4.3-4.P1.fc38 dhcp-4.4.3-4.P1.fc36 dhcp-4.4.3-4.P1.fc37
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-12 06:53:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2022-10-05 08:15:03 UTC
Releases retrieved: 4.1-ESV-R16-P2, 4.4.3-P1
Upstream release that is considered latest: 4.4.3-P1
Current version/release in rawhide: 4.4.3-3.fc37
URL: https://www.isc.org/dhcp/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/5584/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/dhcp

Comment 1 Xose Vazquez Perez 2022-10-05 23:44:53 UTC
(In reply to Upstream Release Monitoring from comment #0)
> Releases retrieved: 4.1-ESV-R16-P2, 4.4.3-P1
> Upstream release that is considered latest: 4.4.3-P1
> Current version/release in rawhide: 4.4.3-3.fc37
> URL: https://www.isc.org/dhcp/
> Based on the information from Anitya: https://release-monitoring.org/project/5584/

Changes since 4.4.3 (Bug Fixes):

! Corrected a reference count leak that occurs when the server builds
  responses to leasequery packets. Thanks to VictorV of Cyber Kunlun
  Lab for reporting the issue.
  [Gitlab #253]
  CVE: CVE-2022-2928

! Corrected a memory leak that occurs when unpacking a packet that has an
  FQDN option (81) that contains a label with length greater than 63 bytes.
  Thanks to VictorV of Cyber Kunlun Lab for reporting the issue.
  [Gitlab #254]
  CVE: CVE-2022-2929

Comment 2 Fedora Update System 2022-10-10 09:15:38 UTC
FEDORA-2022-5c58ef733f has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5c58ef733f

Comment 3 Fedora Update System 2022-10-10 09:47:27 UTC
FEDORA-2022-9ca9a94e28 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9ca9a94e28

Comment 4 Fedora Update System 2022-10-11 08:21:55 UTC
FEDORA-2022-9ca9a94e28 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-9ca9a94e28`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9ca9a94e28

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2022-10-11 10:35:18 UTC
FEDORA-2022-f5a45757df has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f5a45757df

Comment 6 Fedora Update System 2022-10-12 06:44:54 UTC
FEDORA-2022-c4f274a54f has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c4f274a54f

Comment 7 Fedora Update System 2022-10-12 06:53:25 UTC
FEDORA-2022-5c58ef733f has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2022-10-12 13:01:35 UTC
FEDORA-2022-f5a45757df has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-f5a45757df`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-f5a45757df

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2022-10-12 13:03:16 UTC
FEDORA-2022-c4f274a54f has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-c4f274a54f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c4f274a54f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2022-10-14 12:58:16 UTC
FEDORA-2022-f5a45757df has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2022-10-17 22:54:53 UTC
FEDORA-2022-9ca9a94e28 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2022-10-26 17:34:41 UTC
FEDORA-2022-c4f274a54f has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.


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