https://www.haguest.com/tags/vulnerability/Recent content in Vulnerability on Cliff HultsHugo -- gohugo.ioen© 2026 Cliff HultsThu, 16 Dec 2021 14:59:43 -0500https://www.haguest.com/posts/2021-12-16-log4j/Thu, 16 Dec 2021 14:59:43 -0500https://www.haguest.com/posts/2021-12-16-log4j/<p>Lately, everyone has been talking about Log4Shell (CVE-2021-44228) and likely, if you&rsquo;re reading this, you&rsquo;re looking for info for what to do. Most people attempted to utilize <a href="https://log4shell.huntress.com/" target="_blank" rel="noreferrer">Huntress&rsquo;s Log4Shell detection tool</a> to show connections to a LDAP server they were hosting. Some people had issues with this as it was overburdened with requests (rightfully so) or didn&rsquo;t want to, or aren&rsquo;t allowed to send outbound traffic to a server they didn&rsquo;t own. At our organization, we were part of the latter group. In order to comply with our rules, we needed to find a reliable way to scan our devices for the vulnerability and look for requests to a domain that we owned.</p>https://www.haguest.com/posts/2020-11-20-adfs-cve-2020-17049/Fri, 20 Nov 2020 18:10:12 -0500https://www.haguest.com/posts/2020-11-20-adfs-cve-2020-17049/<p>Microsoft recently performed a patch for Kerberos and the KDC service on domain controllers. This would patch a heavy vulnerability in the Kerberos signing structure. However, this presented a problem with our domain joined NAS appliance, and disallowed any users from authenticating to SMB shares. In order to alleviate ourselves of the issue, we followed the instructions to disable the following registry key within <code>HKLM\SYSTEM\CurrentControlSet\Services\Kdc\</code> by adding <code>PerformTicketSignature</code> set to <code>DWORD 0</code>.</p>