{"id":22908,"date":"2026-07-30T06:30:03","date_gmt":"2026-07-30T06:30:03","guid":{"rendered":"https:\/\/scannn.com\/how-we-hacked-thousands-of-data-centers-in-minutes-using-a-20-year-old-vulnerability\/"},"modified":"2026-07-30T06:30:03","modified_gmt":"2026-07-30T06:30:03","slug":"how-we-hacked-thousands-of-data-centers-in-minutes-using-a-20-year-old-vulnerability","status":"publish","type":"post","link":"https:\/\/scannn.com\/lv\/how-we-hacked-thousands-of-data-centers-in-minutes-using-a-20-year-old-vulnerability\/","title":{"rendered":"How We Hacked Thousands of Data Centers in Minutes Using a 20-Year-Old Vulnerability"},"content":{"rendered":"\n<div>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">A <strong class=\"font-semibold text-[#00161c]\">Baseboard Management Controller (BMC)<\/strong> is a highly privileged management processor that provides remote control over a server independently of its operating system. It allows administrators to manage and troubleshoot servers remotely, eliminating the need for physical access to the hardware.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">We identified <strong class=\"font-semibold text-[#00161c]\">36,872 internet-exposed server-management interfaces<\/strong> running IPMI, a protocol introduced more than two decades ago for remote control over physical servers. Of the systems we tested, <strong class=\"font-semibold text-[#00161c]\">24,650 disclosed password-derived authentication hashes before login<\/strong> because of CVE-2013-4786, a vulnerability in the IPMI 2.0 authentication protocol that enables offline password-cracking attempts. To visualize the scale of the exposure, we created <a href=\"https:\/\/lavahq.io\/bmc\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"font-medium text-[#00161c] underline underline-offset-4\"><strong class=\"font-semibold text-[#00161c]\">BMCRadar<\/strong><\/a>, an interactive map of the internet-exposed BMC interfaces identified during this research.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">More than <strong class=\"font-semibold text-[#00161c]\">30% of the returned hashes<\/strong> were associated with passwords that could be recovered using common wordlists and predictable factory chassis-sticker formats. We also found evidence that servers with internet-exposed BMC interfaces are <strong class=\"font-semibold text-[#00161c]\">already being targeted and exploited in the wild<\/strong>.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">The exposure also affected <strong class=\"font-semibold text-[#00161c]\">modern Supermicro and HPE servers operated by GPU providers<\/strong>, including systems that were still using factory-issued passwords.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">The risk extended well beyond a single server. In the environments we examined, BMC management networks lacked effective segmentation, access controls, and monitoring. A compromised BMC could therefore serve as a highly privileged foothold, allowing an attacker to reach additional management interfaces and put <strong class=\"font-semibold text-[#00161c]\">large portions of the data center infrastructure at risk<\/strong>.<\/p>\n<h2 id=\"what-is-a-bmc-and-why-is-it-so-powerful\" class=\"font-['Google_Sans',var(--font-geist-sans),sans-serif] font-normal capitalize leading-[1.2] text-[#00161c] mt-[24px] article-heading-anchor text-[32px] tracking-[-1.28px] first:mt-0 md:text-[40px] md:tracking-[-1.6px]\">What Is a BMC and Why Is It So Powerful?<\/h2>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">A <strong class=\"font-semibold text-[#00161c]\">Baseboard Management Controller (BMC)<\/strong> is a dedicated service processor attached to most modern server platforms. It is designed to manage the server <strong class=\"font-semibold text-[#00161c]\">even when the operating system is down, broken, or completely unresponsive<\/strong>.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">A BMC can usually power-cycle the host, expose a remote console, mount virtual media, update firmware, read hardware sensors, and change low-level platform configuration. In practice, it is <strong class=\"font-semibold text-[#00161c]\">one of the most privileged control points in a data center<\/strong>.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">BMCs commonly expose several management surfaces:<\/p>\n<ul class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px] flex list-disc flex-col gap-[12px] pl-6\">\n<li><strong class=\"font-semibold text-[#00161c]\">IPMI<\/strong>, the older out-of-band management protocol<\/li>\n<li><strong class=\"font-semibold text-[#00161c]\">Redfish<\/strong>, the newer HTTPS-based management API<\/li>\n<li>A browser-based administrative interface<\/li>\n<li>Remote console and virtual media features, depending on the platform<\/li>\n<\/ul>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">In many implementations, <strong class=\"font-semibold text-[#00161c]\">these interfaces share the same user database<\/strong>. A credential that works for IPMI may also work for the web interface or Redfish API. This matters because <strong class=\"font-semibold text-[#00161c]\">the IPMI authentication process can expose information that enables offline password recovery<\/strong>.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">BMC implementations differ across vendors. HPE calls its platform <strong class=\"font-semibold text-[#00161c]\">iLO<\/strong>, Dell calls it <strong class=\"font-semibold text-[#00161c]\">iDRAC<\/strong>, Lenovo uses <strong class=\"font-semibold text-[#00161c]\">XClarity Controller<\/strong>, and Supermicro provides its own BMC stack. <strong class=\"font-semibold text-[#00161c]\">OpenBMC is an <a href=\"https:\/\/github.com\/openbmc\/openbmc\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"font-medium text-[#00161c] underline underline-offset-4\">open-source<\/a> BMC firmware stack<\/strong> used across parts of the cloud, hyperscale, and hardware ecosystem.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><em>Figure 1: Example BMC web interface. BMCs often expose web, API, console, and IPMI management surfaces backed by the same privileged management plane.<\/em><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">A compromised BMC puts defenders in a uniquely difficult position. Most security tools monitor the operating system, kernel, containers, and workloads. <strong class=\"font-semibold text-[#00161c]\">The BMC operates outside that trust boundary<\/strong>, giving an attacker control beneath the host while remaining largely invisible to the tools designed to protect it.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">The risk rarely stops at one server. BMCs typically sit on shared out-of-band management networks, where administrative credentials are often reused and traffic is monitored less closely than on production networks. This gives attackers a path to <strong class=\"font-semibold text-[#00161c]\">move laterally between management controllers<\/strong>, turning one compromised BMC into a foothold across the broader data center management plane.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">BMC access can also enable <strong class=\"font-semibold text-[#00161c]\">persistence below the operating system<\/strong>. Malicious changes to BMC or other platform firmware can survive operating system reinstalls, disk replacement, and standard incident response procedures. <strong class=\"font-semibold text-[#00161c]\">Recovering trust becomes a platform-level recovery problem<\/strong>, requiring verified firmware reflashing, integrity validation, vendor-assisted recovery, or hardware replacement when the affected components can no longer be trusted.<\/p>\n<h2 id=\"why-bmc-compromise-is-especially-dangerous-in-ai-infrastructure\" class=\"font-['Google_Sans',var(--font-geist-sans),sans-serif] font-normal capitalize leading-[1.2] text-[#00161c] mt-[24px] article-heading-anchor text-[32px] tracking-[-1.28px] first:mt-0 md:text-[40px] md:tracking-[-1.6px]\">Why BMC Compromise Is Especially Dangerous in AI Infrastructure<\/h2>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">AI infrastructure concentrates thousands of high-value GPU systems behind shared management networks. These environments also rely heavily on shared storage, high-speed interconnects, and multi-tenant operational tooling. <strong class=\"font-semibold text-[#00161c]\">A single compromised BMC can therefore become a path to additional servers, critical infrastructure, and customer workloads.<\/strong><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">The risk is especially pronounced in <strong class=\"font-semibold text-[#00161c]\">Neocloud and GPU cloud environments<\/strong>. Even when a customer rents dedicated bare-metal servers, those systems are often still connected to a shared provider-managed out-of-band network. The BMCs, provisioning systems, orchestration services, credential stores, and administrative tools used to manage them may span infrastructure belonging to multiple customers. <strong class=\"font-semibold text-[#00161c]\">This makes the provider\u2019s management plane a central point of trust and a potential path across tenant boundaries.<\/strong><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">The impact can therefore extend beyond one machine or one customer. Compromising a server\u2019s BMC, or the systems used to manage it, can provide access to additional hosts and shared infrastructure, increasing both the blast radius and the cost of recovery.<\/p>\n<h2 id=\"the-20-year-old-vulnerability\" class=\"font-['Google_Sans',var(--font-geist-sans),sans-serif] font-normal capitalize leading-[1.2] text-[#00161c] mt-[24px] article-heading-anchor text-[32px] tracking-[-1.28px] first:mt-0 md:text-[40px] md:tracking-[-1.6px]\">The 20-Year-Old Vulnerability<\/h2>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">The issue at the center of this research is <a href=\"https:\/\/nvd.nist.gov\/vuln\/detail\/CVE-2013-4786\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"font-medium text-[#00161c] underline underline-offset-4\">CVE-2013-4786<\/a>, a long-known <strong class=\"font-semibold text-[#00161c]\">vulnerability in the IPMI 2.0 authentication protocol introduced in 2004<\/strong>.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">During authentication, the BMC can return an HMAC-SHA1 authentication code calculated using the account password and session values known to the requester.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">An unauthenticated remote party that can reach UDP port 623 can request this response and <strong class=\"font-semibold text-[#00161c]\">test password guesses offline<\/strong>. Unlike repeated online login attempts, this process does not require a new request to the BMC for every password candidate.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><strong class=\"font-semibold text-[#00161c]\">Weak, reused, factory-set, or predictably formatted passwords may therefore be recovered without generating the usual pattern of repeated failed logins.<\/strong><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><img decoding=\"async\" src=\"https:\/\/cdn.sanity.io\/images\/55i6rbo6\/production\/00a4c4e400ca64494cb029b98ae88b3c761b09e2-1170x871.png?w=2000&amp;fit=max&amp;auto=format\" alt=\"\"\/><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><em>Figure 2: Simplified IPMI 2.0 RAKP exchange. The BMC returns a password-derived HMAC-SHA1 value before client authentication is complete.<\/em><\/p>\n<h2 id=\"scanning-the-internet\" class=\"font-['Google_Sans',var(--font-geist-sans),sans-serif] font-normal capitalize leading-[1.2] text-[#00161c] mt-[24px] article-heading-anchor text-[32px] tracking-[-1.28px] first:mt-0 md:text-[40px] md:tracking-[-1.6px]\">Scanning the Internet<\/h2>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">We started with a simple question: <strong class=\"font-semibold text-[#00161c]\">how many BMCs are reachable from the public internet?<\/strong><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">We looked for IPMI services exposed on UDP port 623. On May 6, 2026, the query returned <strong class=\"font-semibold text-[#00161c]\">36,872 unique hosts<\/strong> exposing IPMI to the public internet. Across repeated measurements between May and July, we observed an average of <strong class=\"font-semibold text-[#00161c]\">approximately 60 previously unseen IP addresses exposing IPMI each day<\/strong>.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">That number alone was not the finding. Publicly exposed IPMI has been known for years. <strong class=\"font-semibold text-[#00161c]\">The more important question was how many of those services exposed a usable security vulnerability before authentication.<\/strong><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">To test this at scale, we used a lightweight auditor to check publicly exposed IPMI services for <strong class=\"font-semibold text-[#00161c]\">known vulnerabilities and risky configurations<\/strong>, including:<\/p>\n<ul class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px] flex list-disc flex-col gap-[12px] pl-6\">\n<li>Cipher suite 0 support, which can weaken IPMI authentication when enabled and improperly configured<\/li>\n<li>Empty or null usernames accepted during the authentication exchange<\/li>\n<li>Authentication modes advertised as <code class=\"rounded-[4px] bg-black\/5 px-[6px] py-[2px] font-mono text-[0.9em]\">NONE<\/code>, which do not require standard password validation<\/li>\n<li>RAKP responses associated with common vendor-default usernames<\/li>\n<li><strong class=\"font-semibold text-[#00161c]\">CVE-2013-4786<\/strong>, which can return password-derived authentication hashes before login completes<\/li>\n<\/ul>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">The findings fell into <strong class=\"font-semibold text-[#00161c]\">two categories<\/strong>: risky configurations visible during the pre-authentication exchange, and a deeper vulnerability in the IPMI 2.0 authentication flow that exposes hashes for offline password guessing.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><img decoding=\"async\" src=\"https:\/\/cdn.sanity.io\/images\/55i6rbo6\/production\/6759ea68778162be967fe4f3462dab07554b833e-2273x981.png?w=2000&amp;fit=max&amp;auto=format\" alt=\"\"\/><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><em>Figure 3: Shodan results for the query <code class=\"rounded-[4px] bg-black\/5 px-[6px] py-[2px] font-mono text-[0.9em]\">IPMI port:623<\/code>, showing publicly reachable IPMI services exposed on UDP port 623.<\/em><\/p>\n<h2 id=\"explore-the-exposure\" class=\"font-['Google_Sans',var(--font-geist-sans),sans-serif] font-normal capitalize leading-[1.2] text-[#00161c] mt-[24px] article-heading-anchor text-[32px] tracking-[-1.28px] first:mt-0 md:text-[40px] md:tracking-[-1.6px]\">Explore the Exposure<\/h2>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">To make the scale of the exposure easier to understand, we created <a href=\"https:\/\/lavahq.io\/bmc\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"font-medium text-[#00161c] underline underline-offset-4\"><strong class=\"font-semibold text-[#00161c]\">BMCRadar24<\/strong><\/a>, an interactive map of the internet-exposed BMCs identified during this research.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><img decoding=\"async\" src=\"https:\/\/cdn.sanity.io\/images\/55i6rbo6\/production\/59fd833eb5fb967e1216008e8a07c523b7bbc7cf-2357x912.png?w=2000&amp;fit=max&amp;auto=format\" alt=\"\"\/><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">The map provides an aggregate view of where publicly reachable server management interfaces are distributed around the world.<\/p>\n<h2 id=\"what-we-found\" class=\"font-['Google_Sans',var(--font-geist-sans),sans-serif] font-normal capitalize leading-[1.2] text-[#00161c] mt-[24px] article-heading-anchor text-[32px] tracking-[-1.28px] first:mt-0 md:text-[40px] md:tracking-[-1.6px]\">What We Found<\/h2>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">After testing the exposed endpoints, we observed a consistent pattern.<\/p>\n<div class=\"w-full overflow-x-auto\">\n<table class=\"w-full border-collapse text-left text-[15px] text-[#00161c] md:text-[16px]\">\n<thead>\n<tr>\n<th class=\"border border-[#ded7cb] bg-[#f2eee3] px-[12px] py-[8px] font-semibold\">Finding<\/th>\n<th class=\"border border-[#ded7cb] bg-[#f2eee3] px-[12px] py-[8px] font-semibold\">Result<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td class=\"border border-[#ded7cb] px-[12px] py-[8px] align-top\">Internet-exposed IPMI hosts<\/td>\n<td class=\"border border-[#ded7cb] px-[12px] py-[8px] align-top\">36,872<\/td>\n<\/tr>\n<tr>\n<td class=\"border border-[#ded7cb] px-[12px] py-[8px] align-top\">Endpoints returning at least one RAKP response before client authentication<\/td>\n<td class=\"border border-[#ded7cb] px-[12px] py-[8px] align-top\">24,650 (66.9%)<\/td>\n<\/tr>\n<tr>\n<td class=\"border border-[#ded7cb] px-[12px] py-[8px] align-top\">Endpoints accepting an empty username with a weak password<\/td>\n<td class=\"border border-[#ded7cb] px-[12px] py-[8px] align-top\">6,240 (16.9%)<\/td>\n<\/tr>\n<tr>\n<td class=\"border border-[#ded7cb] px-[12px] py-[8px] align-top\">Endpoints with a named account using a common password<\/td>\n<td class=\"border border-[#ded7cb] px-[12px] py-[8px] align-top\">2,340 (6.3%)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><strong class=\"font-semibold text-[#00161c]\">Approximately two-thirds of the exposed BMCs we tested returned at least one password-derived authentication hash before client authentication was complete.<\/strong> Across those systems, two weaknesses stood out.<\/p>\n<h3 class=\"font-['Google_Sans',var(--font-geist-sans),sans-serif] font-normal capitalize leading-[1.2] text-[#00161c] mt-[24px] text-[24px] tracking-[-0.96px] first:mt-0 md:text-[28px] md:tracking-[-1.12px]\">Blank or Null Usernames<\/h3>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">A total of <strong class=\"font-semibold text-[#00161c]\">6,240 BMCs<\/strong> returned authentication material for an empty username that matched a weak password candidate during offline analysis.<\/p>\n<h3 class=\"font-['Google_Sans',var(--font-geist-sans),sans-serif] font-normal capitalize leading-[1.2] text-[#00161c] mt-[24px] text-[24px] tracking-[-0.96px] first:mt-0 md:text-[28px] md:tracking-[-1.12px]\">Common Passwords Worked<\/h3>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">On <strong class=\"font-semibold text-[#00161c]\">2,340 BMCs<\/strong>, the authentication material returned for a named account such as <code class=\"rounded-[4px] bg-black\/5 px-[6px] py-[2px] font-mono text-[0.9em]\">ADMIN<\/code> or <code class=\"rounded-[4px] bg-black\/5 px-[6px] py-[2px] font-mono text-[0.9em]\">root<\/code> matched a password from publicly available wordlists during offline analysis. This represented approximately <strong class=\"font-semibold text-[#00161c]\">9.5% of the endpoints that returned a RAKP response<\/strong>.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">We tested each captured response independently against publicly available wordlists of common passwords. <strong class=\"font-semibold text-[#00161c]\">Many matches were identified during the first pass and within minutes.<\/strong><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">We did not submit the matching passwords to the affected BMCs or use them to authenticate.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">A complete brute-force search was not practical across the entire exposed population. Each IPMI authentication exchange contains unique random values and a new session ID, meaning every captured response must be processed separately.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><strong class=\"font-semibold text-[#00161c]\">Common passwords were only part of the problem.<\/strong> Some passwords that did not appear in standard wordlists still followed constrained and predictable factory-issued formats.<\/p>\n<h2 id=\"the-supermicro-pattern\" class=\"font-['Google_Sans',var(--font-geist-sans),sans-serif] font-normal capitalize leading-[1.2] text-[#00161c] mt-[24px] article-heading-anchor text-[32px] tracking-[-1.28px] first:mt-0 md:text-[40px] md:tracking-[-1.6px]\">The Supermicro Pattern<\/h2>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">Many BMCs that did not match our initial wordlists appeared to be Supermicro systems. <strong class=\"font-semibold text-[#00161c]\">Supermicro hardware accounted for more than 50% of the responding BMCs in our dataset<\/strong> and is widely used across data centers, hosting environments, and GPU infrastructure.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">The legacy <code class=\"rounded-[4px] bg-black\/5 px-[6px] py-[2px] font-mono text-[0.9em]\">ADMIN:ADMIN<\/code> factory credential produced only a few hundred matches. Most Supermicro endpoints did not match passwords in our initial wordlists.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">This was expected. Beginning in November 2019, Supermicro replaced the shared <code class=\"rounded-[4px] bg-black\/5 px-[6px] py-[2px] font-mono text-[0.9em]\">ADMIN<\/code> password on affected products with a unique, preprogrammed password to support compliance with California&#8217;s SB-327 requirements. The username remains <code class=\"rounded-[4px] bg-black\/5 px-[6px] py-[2px] font-mono text-[0.9em]\">ADMIN<\/code>, while the password consists of <strong class=\"font-semibold text-[#00161c]\">exactly ten uppercase letters printed on a chassis label<\/strong>.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><img decoding=\"async\" src=\"https:\/\/cdn.sanity.io\/images\/55i6rbo6\/production\/773a8b1c4d547afcd25dedca9d05a53815bc1abf-3000x600.png?w=2000&amp;fit=max&amp;auto=format\" alt=\"\"\/><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><em>Figure 4: Supermicro guidance describing the unique preprogrammed BMC password introduced for affected products.<\/em><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><img decoding=\"async\" src=\"https:\/\/cdn.sanity.io\/images\/55i6rbo6\/production\/77708b9c00864467e3864f517aa4933180f1cce1-1509x279.png?w=2000&amp;fit=max&amp;auto=format\" alt=\"\"\/><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><em>Figure 5: Supermicro&#8217;s documented password format: exactly ten uppercase alphabetic characters.<\/em><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">This format has a keyspace of <code class=\"rounded-[4px] bg-black\/5 px-[6px] py-[2px] font-mono text-[0.9em]\">26^10<\/code>, or approximately 141 trillion possible passwords. Although this is too large for a simple wordlist, <strong class=\"font-semibold text-[#00161c]\">its constrained format makes exhaustive recovery practical for a targeted attacker with modern GPU hardware<\/strong>. On a modern server with eight GPUs running Hashcat, the complete candidate space could be searched in approximately one hour.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">Testing the entire exposed population this way would have been expensive because each captured response had to be processed separately. <strong class=\"font-semibold text-[#00161c]\">For a targeted attacker focusing on a small number of selected systems, however, the search was practical.<\/strong><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">To determine whether Supermicro factory-format passwords could be recovered in practice, we tested two adjacent IP addresses belonging to a US-based bare-metal GPU provider. The provider&#8217;s published security policy permitted testing of its internet-facing systems, and we limited the test to password material disclosed through the IPMI authentication flow.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">Both endpoints were modern Supermicro systems with X13DEM motherboards manufactured in 2023. <strong class=\"font-semibold text-[#00161c]\">In both cases, the recovered password matched Supermicro&#8217;s ten-character chassis-sticker format.<\/strong> We did not submit the recovered credentials to the BMCs, attempt to authenticate, access any management interface, or change the state of either system.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">We reported the issue the same day, shared the affected IP addresses and remediation guidance, and stopped testing. <strong class=\"font-semibold text-[#00161c]\">The provider later fixed the exposure.<\/strong><\/p>\n<h2 id=\"testing-our-own-hpe-ilo-system\" class=\"font-['Google_Sans',var(--font-geist-sans),sans-serif] font-normal capitalize leading-[1.2] text-[#00161c] mt-[24px] article-heading-anchor text-[32px] tracking-[-1.28px] first:mt-0 md:text-[40px] md:tracking-[-1.6px]\">Testing Our Own HPE iLO System<\/h2>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">The Supermicro result pointed to a broader issue: <strong class=\"font-semibold text-[#00161c]\">even unique factory passwords can become vulnerable to targeted offline recovery when their format is constrained and IPMI exposes password-derived authentication hashes before login.<\/strong><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">To determine whether the same pattern applied to another vendor, we tested a server in our office lab using its factory-issued HPE iLO password.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><img decoding=\"async\" src=\"https:\/\/cdn.sanity.io\/images\/55i6rbo6\/production\/4c2751267c54a381a33a40f24f9a050438d32495-1412x1068.png?w=2000&amp;fit=max&amp;auto=format\" alt=\"\"\/><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><em>Figure 6: Factory-issued HPE iLO credential label on a server in our lab.<\/em><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">HPE iLO uses a different factory password format: eight characters made up of uppercase letters and digits, giving a keyspace of <code class=\"rounded-[4px] bg-black\/5 px-[6px] py-[2px] font-mono text-[0.9em]\">36^8<\/code>, or approximately 2.8 trillion combinations. <strong class=\"font-semibold text-[#00161c]\">This is roughly 50 times smaller than Supermicro&#8217;s <code class=\"rounded-[4px] bg-black\/5 px-[6px] py-[2px] font-mono text-[0.9em]\">26^10<\/code> keyspace.<\/strong><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">On an Apple M3 system, searching the full candidate space took approximately one day for each captured response. On our lab server with eight RTX 6000 PRO GPUs, <strong class=\"font-semibold text-[#00161c]\">the same search took approximately 32 seconds per response<\/strong>.<\/p>\n<h2 id=\"a-ransom-note-on-an-exposed-bmc-interface\" class=\"font-['Google_Sans',var(--font-geist-sans),sans-serif] font-normal capitalize leading-[1.2] text-[#00161c] mt-[24px] article-heading-anchor text-[32px] tracking-[-1.28px] first:mt-0 md:text-[40px] md:tracking-[-1.6px]\">A Ransom Note on an Exposed BMC Interface<\/h2>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">During our research, we found <strong class=\"font-semibold text-[#00161c]\">an exposed HPE iLO 4 login page displaying a ransom note<\/strong> in its Security Notice panel. The message claimed that the server&#8217;s data had been encrypted and demanded <strong class=\"font-semibold text-[#00161c]\">0.3 BTC<\/strong>.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">We could not confirm whether the server itself had been encrypted, but <strong class=\"font-semibold text-[#00161c]\">the modified page showed that someone had gained access to the management interface<\/strong>.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><img decoding=\"async\" src=\"https:\/\/cdn.sanity.io\/images\/55i6rbo6\/production\/823e4cf1669265a7e9b0602921833989cb7c6336-2543x974.png?w=2000&amp;fit=max&amp;auto=format\" alt=\"\"\/><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><em>Figure 7: An internet-exposed iLO 4 login page displaying an RSA-2048 ransom message, a 0.3 BTC demand, and a disposable email address in the Security Notice pane.<\/em><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">This was not the first indication that attackers target iLO. Previous research has documented malicious activity involving HPE iLO, including iLOBleed, a persistent iLO 4 rootkit associated with destructive attacks against servers.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">The page we observed made the risk tangible: <strong class=\"font-semibold text-[#00161c]\">an exposed BMC is not simply a forgotten administrative interface. It is a privileged path to the server below the operating system.<\/strong> Although we could not confirm what happened on this particular system, prior incidents show that attackers have targeted this layer in real-world operations.<\/p>\n<h2 id=\"how-to-fix-it\" class=\"font-['Google_Sans',var(--font-geist-sans),sans-serif] font-normal capitalize leading-[1.2] text-[#00161c] mt-[24px] article-heading-anchor text-[32px] tracking-[-1.28px] first:mt-0 md:text-[40px] md:tracking-[-1.6px]\">How to Fix It<\/h2>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><strong class=\"font-semibold text-[#00161c]\">The main fix is simple: IPMI should not be reachable from the public internet.<\/strong><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">Operators should:<\/p>\n<ul class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px] flex list-disc flex-col gap-[12px] pl-6\">\n<li>Block UDP port 623 at the network edge<\/li>\n<li>Replace factory-issued passwords during provisioning<\/li>\n<li>Disable legacy or weak options such as IPMI 1.5, cipher suite 0, anonymous accounts, and <code class=\"rounded-[4px] bg-black\/5 px-[6px] py-[2px] font-mono text-[0.9em]\">NONE<\/code> authentication<\/li>\n<li>Restrict BMC access to a dedicated private management network, VPN, bastion host, or another controlled administrative path<\/li>\n<li>Apply network access controls so only approved administrative systems can reach BMC interfaces<\/li>\n<li>Monitor the management network separately from production workloads<\/li>\n<\/ul>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">Where supported, prefer Redfish over TLS within an isolated management network. <strong class=\"font-semibold text-[#00161c]\">Neither Redfish nor IPMI should be exposed directly to the public internet.<\/strong><\/p>\n<h2 id=\"responsible-disclosure\" class=\"font-['Google_Sans',var(--font-geist-sans),sans-serif] font-normal capitalize leading-[1.2] text-[#00161c] mt-[24px] article-heading-anchor text-[32px] tracking-[-1.28px] first:mt-0 md:text-[40px] md:tracking-[-1.6px]\">Responsible Disclosure<\/h2>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">As part of this research, <strong class=\"font-semibold text-[#00161c]\">we reported relevant findings to affected vendors and operators where we could identify direct ownership.<\/strong><\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">In June 2026, we notified Supermicro that the factory BMC password format used on affected modern systems can be recovered within a practical time frame when IPMI is exposed to the internet and a password-derived response can be collected remotely.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><strong class=\"font-semibold text-[#00161c]\">Supermicro acknowledged that this is a plausible scenario with modern multi-GPU cracking capabilities<\/strong>, reiterated that customers should rotate default BMC passwords during setup, and recommended keeping management networks off the public internet behind management VLANs and ACLs.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><strong class=\"font-semibold text-[#00161c]\">Supermicro also stated that it will review possible improvements to the default password policy for future hardware revisions<\/strong>, including longer passwords or an expanded character set.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">We also notified operators where we could identify direct ownership of affected systems. These reports included systems exposing weak passwords or risky IPMI configurations.<\/p>\n<h2 id=\"conclusion\" class=\"font-['Google_Sans',var(--font-geist-sans),sans-serif] font-normal capitalize leading-[1.2] text-[#00161c] mt-[24px] article-heading-anchor text-[32px] tracking-[-1.28px] first:mt-0 md:text-[40px] md:tracking-[-1.6px]\">Conclusion<\/h2>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><strong class=\"font-semibold text-[#00161c]\">This vulnerability exposes a broader security gap in the data center management plane.<\/strong> BMCs control critical infrastructure, yet they often receive far less monitoring and protection than the systems they manage.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">Combined with modern GPU cracking and predictable factory passwords, this vulnerability can turn a single exposed BMC into a privileged and difficult-to-detect foothold across the management network.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\"><strong class=\"font-semibold text-[#00161c]\">Organizations must treat management layers as critical security boundaries:<\/strong> isolate them, remove public exposure, rotate factory credentials, and monitor them continuously.<\/p>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">This research is part of Lava&#8217;s broader work to secure the infrastructure powering the AI revolution. The <a href=\"https:\/\/forge-framework.io\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"font-medium text-[#00161c] underline underline-offset-4\">FORGE framework<\/a> provides a broader view of the risks facing data centers and AI infrastructure.<br \/>\nIf your organization operates data centers or AI, GPU, or bare-metal infrastructure, we\u2019d be happy to <a href=\"https:\/\/lavahq.io\/research?contact_us=true\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"font-medium text-[#00161c] underline underline-offset-4\">speak with you<\/a> about broader infrastructure management and security challenges.<\/p>\n<h2 id=\"prior-work-and-further-reading\" class=\"font-['Google_Sans',var(--font-geist-sans),sans-serif] font-normal capitalize leading-[1.2] text-[#00161c] mt-[24px] article-heading-anchor text-[32px] tracking-[-1.28px] first:mt-0 md:text-[40px] md:tracking-[-1.6px]\">Prior Work and Further Reading<\/h2>\n<p class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px]\">This research builds on earlier work on IPMI, BMC security, and firmware resilience:<\/p>\n<ul class=\"font-['Google_Sans_Flex',var(--font-geist-sans),sans-serif] text-[16px] font-normal leading-[1.4] tracking-[-0.48px] text-[#00161c] [overflow-wrap:anywhere] md:text-[18px] md:tracking-[-0.54px] flex list-disc flex-col gap-[12px] pl-6\">\n<li><strong class=\"font-semibold text-[#00161c]\">Dan Farmer, <a href=\"https:\/\/fish2.com\/ipmi\/itrain.pdf\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"font-medium text-[#00161c] underline underline-offset-4\">&#8220;IPMI: Freight Train to Hell&#8221;<\/a> (2013).<\/strong> A foundational analysis of IPMI&#8217;s design and security weaknesses, including remote hash disclosure and highly privileged BMC access.<\/li>\n<li><strong class=\"font-semibold text-[#00161c]\">HD Moore, <a href=\"https:\/\/www.rapid7.com\/blog\/post\/2013\/07\/02\/a-penetration-testers-guide-to-ipmi\/\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"font-medium text-[#00161c] underline underline-offset-4\">&#8220;A Penetration Tester&#8217;s Guide to IPMI and BMCs&#8221;<\/a> (Rapid7, 2013).<\/strong> A practical guide to discovering and testing common IPMI and BMC weaknesses, including cipher suite 0, default credentials, and RAKP hash disclosure.<\/li>\n<li><strong class=\"font-semibold text-[#00161c]\">Eclypsium, <a href=\"https:\/\/eclypsium.com\/blog\/supply-chain-vulnerabilities-put-server-ecosystem-at-risk\/\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"font-medium text-[#00161c] underline underline-offset-4\">&#8220;BMC&amp;C: Supply Chain Vulnerabilities Put Server Ecosystem at Risk&#8221;<\/a> (2022-2023).<\/strong> Research into vulnerabilities in AMI MegaRAC BMC software used by multiple server vendors.<\/li>\n<li><strong class=\"font-semibold text-[#00161c]\">Amnpardaz, <a href=\"https:\/\/threats.amnpardaz.com\/wp-content\/uploads\/sites\/2\/2021\/12\/Implant.ARM_.iLOBleed.a-en.pdf\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"font-medium text-[#00161c] underline underline-offset-4\">&#8220;The iLOBleed Implant&#8221;<\/a> (2021).<\/strong> Analysis of a persistent firmware rootkit discovered in HPE iLO 4.<\/li>\n<li><strong class=\"font-semibold text-[#00161c]\">HPE, <a href=\"https:\/\/support.hpe.com\/hpesc\/public\/docDisplay?docId=emr_na-c04197764-1\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"font-medium text-[#00161c] underline underline-offset-4\">IPMI 2.0 RAKP RMCP+ Authentication HMAC Password Hash Exposure<\/a>.<\/strong> HPE&#8217;s advisory covering the IPMI password-hash disclosure issue affecting earlier iLO generations.<\/li>\n<li><strong class=\"font-semibold text-[#00161c]\">Supermicro, <a href=\"https:\/\/www.supermicro.com\/products\/nfo\/files\/IPMI\/BMC_Server_Management_Feature_Guide.pdf\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"font-medium text-[#00161c] underline underline-offset-4\">&#8220;Server Management: BMC Firmware Security&#8221;<\/a> (2022).<\/strong> Guidance for securing BMC deployments, including restricting UDP port 623, isolating BMCs on dedicated management networks, applying IP access controls, and replacing factory-assigned passwords.<\/li>\n<li><strong class=\"font-semibold text-[#00161c]\">Supermicro, <a href=\"https:\/\/www.supermicro.com\/en\/support\/BMC_Unique_Password\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"font-medium text-[#00161c] underline underline-offset-4\">BMC Unique Password Security Feature<\/a> (November 2019).<\/strong> Details of Supermicro&#8217;s unique factory BMC password implementation.<\/li>\n<\/ul>\n<\/div>\n<p><a href=\"https:\/\/lavahq.io\/research\/bmc-exposure-alert?utm_source=tldrinfosec\">Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A Baseboard Management Controller (BMC) is a highly privileged management processor that provides remote control over a server independently of its operating system. It allows administrators to manage and troubleshoot servers remotely, eliminating the need for physical access to the hardware. We identified 36,872 internet-exposed server-management interfaces running IPMI, a protocol introduced more than two [&hellip;]<\/p>\n","protected":false},"author":16,"featured_media":22909,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[143],"tags":[],"class_list":["post-22908","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai"],"_links":{"self":[{"href":"https:\/\/scannn.com\/lv\/wp-json\/wp\/v2\/posts\/22908","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scannn.com\/lv\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/scannn.com\/lv\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/scannn.com\/lv\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/scannn.com\/lv\/wp-json\/wp\/v2\/comments?post=22908"}],"version-history":[{"count":0,"href":"https:\/\/scannn.com\/lv\/wp-json\/wp\/v2\/posts\/22908\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/scannn.com\/lv\/wp-json\/wp\/v2\/media\/22909"}],"wp:attachment":[{"href":"https:\/\/scannn.com\/lv\/wp-json\/wp\/v2\/media?parent=22908"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/scannn.com\/lv\/wp-json\/wp\/v2\/categories?post=22908"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/scannn.com\/lv\/wp-json\/wp\/v2\/tags?post=22908"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}