ISC
ISC DHCP
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record ISC DHCP. Use that record for publisher support phases and retirement dates.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2022-2929 | 7 Oct 2022 | 1.0 through versions before 4.1-ESV-R16-P2; 4.2 through versions before 4.4.3.-P1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-2928 | 7 Oct 2022 | 4.4.0 through versions before 4.4.3-P1; 4.1 ESV 4.1-ESV-R1 through versions before 4.1-ESV-R16-P1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2021-25217 | 26 May 2021 | 4.1 ESV < 4.1-ESV-R16-P1; 4.4 < 4.4.2-P1 | Update to V2.15.0 or later version | Update reference ↗ |
| CVE-2018-5732 | 9 Oct 2019 | ISC DHCP 4.1.0 -> 4.1-ESV-R15, 4.2.0 -> 4.2.8, 4.3.0 -> 4.3.6, 4.4.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-5733 | 16 Jan 2019 | ISC DHCP 4.1.0 -> 4.1-ESV-R15, 4.2.0 -> 4.2.8, 4.3.0 -> 4.3.6, 4.4.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-3144 | 16 Jan 2019 | ISC DHCP 4.1.0 to 4.1-ESV-R15, 4.2.0 to 4.2.8, 4.3.0 to 4.3.6. Older versions may also be affected but are well beyond their end-of-life (EOL). Releases prior to 4.1.0 have not been tested. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.