dhcp-4.2.5-83.1.0.1.el7.AXS7
エラータID: AXSA:2021-1902:02
リリース日:
2021/06/10 Thursday - 11:52
題名:
dhcp-4.2.5-83.1.0.1.el7.AXS7
影響のあるチャネル:
Asianux Server 7 for x86_64
Severity:
High
Description:
以下項目について対処しました。
[Security Fix]
- DHCP には、リースの読み取りに問題があり、dhclient と dhcpd が不適切なリースを読
み込むとクラッシュする可能性があるため、DHCP クライアントでネットワーク接続の問
題を引き起こす脆弱性があります。(CVE-2021-25217)
解決策:
パッケージをアップデートしてください。
CVE:
CVE-2021-25217
In ISC DHCP 4.1-ESV-R1 -> 4.1-ESV-R16, ISC DHCP 4.4.0 -> 4.4.2 (Other branches of ISC DHCP (i.e., releases in the 4.0.x series or lower and releases in the 4.3.x series) are beyond their End-of-Life (EOL) and no longer supported by ISC. From inspection it is clear that the defect is also present in releases from those series, but they have not been officially tested for the vulnerability), The outcome of encountering the defect while reading a lease that will trigger it varies, according to: the component being affected (i.e., dhclient or dhcpd) whether the package was built as a 32-bit or 64-bit binary whether the compiler flag -fstack-protection-strong was used when compiling In dhclient, ISC has not successfully reproduced the error on a 64-bit system. However, on a 32-bit system it is possible to cause dhclient to crash when reading an improper lease, which could cause network connectivity problems for an affected system due to the absence of a running DHCP client process. In dhcpd, when run in DHCPv4 or DHCPv6 mode: if the dhcpd server binary was built for a 32-bit architecture AND the -fstack-protection-strong flag was specified to the compiler, dhcpd may exit while parsing a lease file containing an objectionable lease, resulting in lack of service to clients. Additionally, the offending lease and the lease immediately following it in the lease database may be improperly deleted. if the dhcpd server binary was built for a 64-bit architecture OR if the -fstack-protection-strong compiler flag was NOT specified, the crash will not occur, but it is possible for the offending lease and the lease which immediately followed it to be improperly deleted.
In ISC DHCP 4.1-ESV-R1 -> 4.1-ESV-R16, ISC DHCP 4.4.0 -> 4.4.2 (Other branches of ISC DHCP (i.e., releases in the 4.0.x series or lower and releases in the 4.3.x series) are beyond their End-of-Life (EOL) and no longer supported by ISC. From inspection it is clear that the defect is also present in releases from those series, but they have not been officially tested for the vulnerability), The outcome of encountering the defect while reading a lease that will trigger it varies, according to: the component being affected (i.e., dhclient or dhcpd) whether the package was built as a 32-bit or 64-bit binary whether the compiler flag -fstack-protection-strong was used when compiling In dhclient, ISC has not successfully reproduced the error on a 64-bit system. However, on a 32-bit system it is possible to cause dhclient to crash when reading an improper lease, which could cause network connectivity problems for an affected system due to the absence of a running DHCP client process. In dhcpd, when run in DHCPv4 or DHCPv6 mode: if the dhcpd server binary was built for a 32-bit architecture AND the -fstack-protection-strong flag was specified to the compiler, dhcpd may exit while parsing a lease file containing an objectionable lease, resulting in lack of service to clients. Additionally, the offending lease and the lease immediately following it in the lease database may be improperly deleted. if the dhcpd server binary was built for a 64-bit architecture OR if the -fstack-protection-strong compiler flag was NOT specified, the crash will not occur, but it is possible for the offending lease and the lease which immediately followed it to be improperly deleted.
追加情報:
N/A
ダウンロード:
SRPMS
- dhcp-4.2.5-83.1.0.1.el7.AXS7.src.rpm
MD5: 9a6621ff42014831b999bd13374111bb
SHA-256: a810ae761f406b5a75902278d00ac18447423a80bc39f7831f50ccfcfe320d04
Size: 8.12 MB
Asianux Server 7 for x86_64
- dhclient-4.2.5-83.1.0.1.el7.AXS7.x86_64.rpm
MD5: 695f62624c0f67d382bd2d697f2ce3be
SHA-256: 7e9db6873e571418549986e48071cbd15bdc3f9bb6eee59b6ae7d5dd70b32d1b
Size: 285.21 kB - dhcp-4.2.5-83.1.0.1.el7.AXS7.x86_64.rpm
MD5: 31cfd45733181a15f33277c0f966ff72
SHA-256: 71c602a5a2e9667ba4a672f51c72b53ec9c200c0a11bad89aaa9ed71ca07114f
Size: 514.16 kB - dhcp-common-4.2.5-83.1.0.1.el7.AXS7.x86_64.rpm
MD5: 12f4ea3c874f7a565446e52c8e074a88
SHA-256: 631aa6493e5c5e8c5d7c641a6207b596a902dd21d95d0e8438cfa1595a39e6a7
Size: 175.64 kB - dhcp-libs-4.2.5-83.1.0.1.el7.AXS7.x86_64.rpm
MD5: d0df5ea428bcd6852ecb34142a7f60d6
SHA-256: 56bc8e84973afe7663fae67894eef8cb626d27feac3d44cfd9ad9da03a9c6b24
Size: 132.34 kB - dhcp-libs-4.2.5-83.1.0.1.el7.AXS7.i686.rpm
MD5: 29cf4fec492c6486bfc043a6ca5375f1
SHA-256: 4add435b104fc63c9d2b825b4db6b4605652e7aaf3221a2517837a74ab890acc
Size: 132.16 kB