Failure to properly clean up closed OMAPI connections can exhaust available sockets
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| ISC | ISC DHCP | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
Configuration 4 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 7 | |||
| dhcp-12:4.2.5-58.el7_4.1 | cpe:/o:redhat:enterprise_linux:7 | RHSA-2018:0158 | 2018-01-25T00:00:00Z |
No data available yet.
Vendor Workaround
The recommended remedy is to disallow access to the OMAPI control port from unauthorized clients (in accordance with best practices for server operation).
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-4133-1 | isc-dhcp security update |
Ubuntu USN |
USN-3586-1 | DHCP vulnerabilities |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 72.7% (72.724% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.