Windows DHCP server error loaded CallOut DLL

This rule is part of a beta feature. To learn more, contact Support.
이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Goal

Detects Windows DHCP server errors when loading CallOut DLLs that may indicate DLL hijacking attempts targeting DHCP services.

Strategy

This rule monitors Windows event logs where @evt.id is 1031, 1032, or 1034 from the Microsoft-Windows-DHCP-Server provider. These events indicate failures in the DHCP server’s CallOut DLL operations, which can occur when attackers attempt to hijack the execution flow by placing malicious DLLs in locations where the DHCP server expects to find legitimate CallOut DLLs. CallOut DLLs are third-party extensions that provide additional functionality to DHCP servers, making them attractive targets for persistence and privilege escalation attacks.

Triage and response

  • Examine the specific DHCP server error details on {{host}} to identify which CallOut DLL failed to load and the associated error code.
  • Verify the legitimacy of any recently added or modified DLL files in DHCP server directories and common DLL search paths.
  • Review recent system changes including software installations, updates, or configuration modifications that could have affected DHCP CallOut DLL functionality.
  • Check for unusual process executions or file modifications in DHCP-related directories prior to the error events.
  • Determine if the DHCP server errors correlate with any legitimate maintenance activities or if they represent unauthorized modification attempts.