{"id":4452,"date":"2026-11-20T06:33:03","date_gmt":"2026-11-20T14:33:03","guid":{"rendered":"https:\/\/cyber.mag212.com\/vmware-vcenter-cve-2026-123890-zero-day-armory-castle-patch-guide\/"},"modified":"2026-11-20T06:33:03","modified_gmt":"2026-11-20T14:33:03","slug":"vmware-vcenter-cve-2026-123890-zero-day-armory-castle-patch-guide","status":"publish","type":"post","link":"https:\/\/cyber.mag212.com\/fr\/vmware-vcenter-cve-2026-123890-zero-day-armory-castle-patch-guide\/","title":{"rendered":"Vuln\u00e9rabilit\u00e9 zero-day CVE-2026-123890 de VMware vCenter\u00a0: Comment ARMORY CASTLE a d\u00e9rob\u00e9 les cl\u00e9s de vSphere, et comment corriger et traquer cette vuln\u00e9rabilit\u00e9."},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><em>From the <a href=\"https:\/\/cyber.mag212.com\/the-keys-to-vsphere-mag212-cyber-daily-november-20-2026\/\">MAG212 CYBER Daily, 20 November 2026<\/a>. Every command is copied from official documentation or the cited analysis and was <strong>not tested by MAG212<\/strong>; run it only on systems you are authorised to administer.<\/em><\/p>\n\n\n\n<p class=\"m2-status wp-block-paragraph\"><strong>Status:<\/strong> <strong>Fixed on 19 November 2026<\/strong> in vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m, and in VMware Cloud Foundation 5.2.5. <strong>Exploited as a zero-day since early September<\/strong>, according to Google&#8217;s threat intelligence group (GTIG) and Mandiant. Broadcom lists <strong>no workaround<\/strong>. CVSS 9.8. Broadcom&#8217;s advisory does not itself flag exploitation, and the CVE was not in CISA&#8217;s KEV catalog as of 20 November, according to the outlets we cite. <sup><a href=\"#src-1\">[1]<\/a><\/sup><sup><a href=\"#src-3\">[3]<\/a><\/sup><sup><a href=\"#src-4\">[4]<\/a><\/sup><sup><a href=\"#src-5\">[5]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What happened<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">On 19 November 2026 Broadcom published VMSA-2026-0009, fixing CVE-2026-123890 in vCenter Server. It is an authentication bypass in the VMware Directory Service (VMDIR), reached over DCE\/RPC on TCP port 2012. An unauthenticated attacker who can reach that port can become administrator@vsphere.local, the top single sign-on account. Broadcom updated the advisory to VMSA-2026-0009.1 on 20 November. <sup><a href=\"#src-1\">[1]<\/a><\/sup><sup><a href=\"#src-2\">[2]<\/a><\/sup><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The same day, GTIG and Mandiant published an investigation showing the flaw had already been used for about ten weeks. GTIG writes that it &#8220;attributes this activity to the suspected PRC-nexus espionage actor ARMORY CASTLE (formerly tracked as UNC5221)&#8221;. The group is also tracked as Warp Panda. Victim names and numbers are not public. <sup><a href=\"#src-3\">[3]<\/a><\/sup><sup><a href=\"#src-4\">[4]<\/a><\/sup><sup><a href=\"#src-5\">[5]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why this matters<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">vCenter controls every virtual machine it manages. An attacker who becomes its administrator can read domain controllers&#x27; disks without logging in to Windows, forge single sign-on tokens, and hide in an appliance that few security tools watch. This flaw needs no password, only network reach to one port that many organisations never filter internally. And because the attackers stole the signing key, a patch alone does not lock them out. <em>(MAG212 analysis)<\/em><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/vcenter-20nov-diagram.png\"><img decoding=\"async\" src=\"https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/vcenter-20nov-diagram.png\" alt=\"The keys to vSphere. Diagram by MAG212 CYBER.\"\/><\/a><figcaption class=\"wp-element-caption\">Diagram: MAG212 CYBER. Solid red = observed or confirmed; dashed amber = reported or unverified; green = recommended control.<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">How the attack works<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Mandiant&#8217;s reconstruction of one intrusion runs like this: <sup><a href=\"#src-3\">[3]<\/a><\/sup><\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Entry through another product.<\/strong> The actor first got in through a BeyondTrust Remote Support appliance using CVE-2026-102764, which gave it a foothold inside the network.<\/li>\n\n<li><strong>Directory bypass.<\/strong> From inside, it reached vCenter on TCP 2012 and abused the SRP-6a password exchange in VMDIR to become SSO administrator.<\/li>\n\n<li><strong>Webshells.<\/strong> It dropped two JSP webshells, <code>ActiveSer.jsp<\/code> (SLIMSAVAGE) and <code>u.jsp<\/code> (CAGEMATCH), and set the SUID bit on <code>\/bin\/env<\/code> to keep root.<\/li>\n\n<li><strong>Key theft.<\/strong> A tool Mandiant calls BONESAW (<code>\/tmp\/123<\/code>) copied the directory database <code>data.mdb<\/code> and the SAML signing keys, and created an extra SSO administrator.<\/li>\n\n<li><strong>Forged logins.<\/strong> SAWSNAKE (<code>\/tmp\/sss<\/code>) used the stolen key to mint &#8220;Golden SAML&#8221; tokens, valid admin logins that never touch a password.<\/li>\n\n<li><strong>Persistence.<\/strong> BEARBONES (<code>\/tmp\/dbr<\/code>), a Dropbear SSH backdoor, listened on ports 53 and 33992 with the banner <code>SSH-2.0-pulsesecure_23345<\/code>. The actor added a rogue <code>sps-*@vsphere.local<\/code> account and switched SSH on and off through the appliance REST API.<\/li>\n\n<li><strong>Domain secrets.<\/strong> A script, <code>vmfs_browser.py<\/code>, read Windows domain controllers&#8217; virtual disks directly from the datastore and packed NTDS into <code>o.tar.gz<\/code>.<\/li>\n\n<li><strong>Command and control.<\/strong> LAZYBONES (<code>\/usr\/bin\/vmtoolscs<\/code>) used Slack as its channel.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Who is affected<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Product<\/th><th>Fixed version<\/th><th>Note<\/th><\/tr><\/thead><tbody><tr><td>vCenter Server 9.1<\/td><td>9.1.1.0200<\/td><td>no workaround<\/td><\/tr><tr><td>vCenter Server 9.0<\/td><td>9.0.2.0200<\/td><td>no workaround<\/td><\/tr><tr><td>vCenter Server 8.0<\/td><td>8.0 U3m<\/td><td>not available as a Quick Patch<\/td><\/tr><tr><td>VMware Cloud Foundation 5.2<\/td><td>5.2.5<\/td><td>updates the bundled vCenter<\/td><\/tr><tr><td>vCenter Server 7.0<\/td><td>none public<\/td><td>contact Broadcom support<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Source: Broadcom VMSA-2026-0009.1 and its FAQ. The same advisory also fixes SDDC Manager (CVE-2026-123891, -123892, -123893) and VMware Tools (CVE-2026-123894). Check your exact build against the advisory before upgrading. <sup><a href=\"#src-1\">[1]<\/a><\/sup><sup><a href=\"#src-2\">[2]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to check your environment<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">These read-only checks come from Ostorlab&#8217;s write-up or are MAG212 suggestions built from GTIG&#8217;s indicators. They were <strong>not tested by MAG212<\/strong>. Run them only on systems you administer. <sup><a href=\"#src-3\">[3]<\/a><\/sup><sup><a href=\"#src-6\">[6]<\/a><\/sup><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In PowerCLI, check the version and look for accounts matching the rogue-account pattern:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>$global:DefaultVIServer.Build<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>Get-VIAccount | Where-Object { $_.Name -like &#x27;sps-*&#x27; }<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">On the vCenter appliance shell, look for GTIG&#8217;s file and port indicators:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ls -la \/tmp\/123 \/tmp\/sss \/tmp\/dbr \/usr\/bin\/vmtoolscs 2&gt;\/dev\/null<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>ss -ltnp | grep -E &#x27;:(53|33992) &#x27;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">From an ordinary user network, this test should fail. If it connects, port 2012 is reachable from places it should not be:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>nc -vz vcenter.example.com 2012<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Any hit on these indicators means incident response, not cleanup.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Indicators<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Files:<\/strong> <code>ActiveSer.jsp<\/code>, <code>u.jsp<\/code>, <code>\/tmp\/123<\/code>, <code>\/tmp\/sss<\/code>, <code>\/tmp\/dbr<\/code>, <code>\/usr\/bin\/vmtoolscs<\/code>, <code>o.tar.gz<\/code>, plus <code>\/tmp\/gdb_file<\/code>, <code>\/tmp\/rar<\/code>, <code>\/tmp\/123.key<\/code> and a hidden <code>.a<\/code> directory on a VMFS volume. <sup><a href=\"#src-3\">[3]<\/a><\/sup><\/li>\n\n<li><strong>Network:<\/strong> SSH banner <code>SSH-2.0-pulsesecure_23345<\/code> on ports 53 and 33992. GTIG lists 11 &#8220;suspected obfuscation network&#8221; IP addresses, including 103.147.251[.]5 and 103.190.38[.]3; see its report for the full list. <sup><a href=\"#src-3\">[3]<\/a><\/sup><\/li>\n\n<li><strong>Accounts:<\/strong> <code>sps-&lt;random&gt;@vsphere.local<\/code>. <sup><a href=\"#src-3\">[3]<\/a><\/sup><\/li>\n\n<li><strong>Detection content:<\/strong> GTIG published YARA rules for SLIMSAVAGE, CAGEMATCH, SAWSNAKE, BONESAW, BEARBONES and LAZYBONES. No file hashes are public. <sup><a href=\"#src-3\">[3]<\/a><\/sup><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Contain, fix and verify<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Restrict access first.<\/strong> Allow TCP 443, 2012, 22 and 5480 on vCenter only from admin and peer networks. Mandiant&#8217;s vcsa-hardening-tool helps with this. <sup><a href=\"#src-3\">[3]<\/a><\/sup><sup><a href=\"#src-7\">[7]<\/a><\/sup><\/li>\n\n<li><strong>Patch every vCenter<\/strong>, including lab, test and disaster-recovery instances. <sup><a href=\"#src-1\">[1]<\/a><\/sup><\/li>\n\n<li><strong>If any indicator hits,<\/strong> rotate the STS signing certificate, reset SSO and vCenter credentials, and treat Active Directory as exposed: the actor may hold NTDS. Patching does not revoke a stolen key. <sup><a href=\"#src-3\">[3]<\/a><\/sup><\/li>\n\n<li><strong>Check BeyondTrust Remote Support appliances<\/strong> for the entry bug. <sup><a href=\"#src-3\">[3]<\/a><\/sup><\/li>\n\n<li><strong>Verify:<\/strong> the build number matches the advisory, and TCP 2012 no longer answers from user networks.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">The bigger picture<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Today&#8217;s issue has two exploited bugs on infrastructure ports: vCenter&#8217;s directory service and Cisco Expressway&#8217;s cluster database. Directory and cluster ports are built for trusted peers, yet they often answer anyone on the internal network. The lesson from this case is to filter east-west traffic to infrastructure, not just the internet edge. <em>(MAG212 analysis)<\/em><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Related on MAG212 CYBER<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/cyber.mag212.com\/the-keys-to-vsphere-mag212-cyber-daily-november-20-2026\/\">MAG212 CYBER Daily, 20 November 2026: The keys to vSphere<\/a> (full issue and PDF)<\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/a-ten-year-old-counter-mag212-cyber-daily-november-19-2026\/\">MAG212 CYBER Daily, 19 November 2026: A ten-year-old counter<\/a><\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/one-equals-sign-too-many-mag212-cyber-daily-november-18-2026\/\">MAG212 CYBER Daily, 18 November 2026: One equals sign too many<\/a><\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/the-keys-were-already-inside-mag212-cyber-weekly-november-14-2026\/\">MAG212 CYBER Weekly, 14 November 2026<\/a><\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/subscribe-free\/\">Subscribe free to MAG212 CYBER<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Sources<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><span id=\"src-1\">[1]<\/span> Broadcom, &#8220;<a href=\"https:\/\/support.broadcom.com\/web\/ecx\/support-content-notification\/-\/external\/content\/SecurityAdvisories\/0\/39495\" rel=\"noopener\" target=\"_blank\">VMSA-2026-0009.1: VMware vCenter Server, Cloud Foundation and Tools updates<\/a>&#8220;, 19\u201320 Nov 2026.<\/li>\n\n<li><span id=\"src-2\">[2]<\/span> VMware (GitHub), &#8220;<a href=\"https:\/\/github.com\/vmware\/vcf-security-and-compliance-guidelines\/blob\/main\/security-advisories\/vmsa-2026-0009\/README.md\" rel=\"noopener\" target=\"_blank\">VMSA-2026-0009 questions and answers<\/a>&#8220;, 19 Nov 2026.<\/li>\n\n<li><span id=\"src-3\">[3]<\/span> Google GTIG \/ Mandiant, &#8220;<a href=\"https:\/\/cloud.google.com\/blog\/topics\/threat-intelligence\/armory-castle-exploits-vsphere?hl=en\" rel=\"noopener\" target=\"_blank\">ARMORY CASTLE exploits vSphere zero-day<\/a>&#8220;, 19 Nov 2026.<\/li>\n\n<li><span id=\"src-4\">[4]<\/span> The Hacker News, &#8220;<a href=\"https:\/\/thehackernews.com\/2026\/11\/china-linked-hackers-exploit-critical.html\" rel=\"noopener\" target=\"_blank\">China-linked hackers exploit critical VMware vCenter flaw<\/a>&#8220;, 19 Nov 2026.<\/li>\n\n<li><span id=\"src-5\">[5]<\/span> SecurityWeek, &#8220;<a href=\"https:\/\/www.securityweek.com\/newly-patched-vmware-vcenter-flaw-exploited-as-zero-day-by-chinese-apt\/\" rel=\"noopener\" target=\"_blank\">Newly patched VMware vCenter flaw exploited as zero-day by Chinese APT<\/a>&#8220;, 19 Nov 2026.<\/li>\n\n<li><span id=\"src-6\">[6]<\/span> Ostorlab, &#8220;<a href=\"https:\/\/blog.ostorlab.co\/vmware-vcenter-auth-bypass-cve-2026-123890.html\" rel=\"noopener\" target=\"_blank\">VMware vCenter authentication bypass CVE-2026-123890<\/a>&#8220;, 19 Nov 2026.<\/li>\n\n<li><span id=\"src-7\">[7]<\/span> Mandiant (GitHub), &#8220;<a href=\"https:\/\/github.com\/mandiant\/vcsa-hardening-tool\" rel=\"noopener\" target=\"_blank\">vcsa-hardening-tool<\/a>&#8220;, accessed 20 Nov 2026.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Written and edited by El Mostafa Ouchen for MAG212 CYBER. Facts checked against the sources above as of 20 November 2026, 6:00 AM PT.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Broadcom a corrig\u00e9 la vuln\u00e9rabilit\u00e9 CVE-2026-123890, une faille de contournement de l'authentification vCenter, le 19 novembre. Google indique que le groupe ARMORY CASTLE, soup\u00e7onn\u00e9 d'\u00eatre li\u00e9 \u00e0 la Chine, l'a exploit\u00e9e d\u00e8s d\u00e9but septembre comme une vuln\u00e9rabilit\u00e9 zero-day pour falsifier des identifiants d'administrateur et copier les secrets d'Active Directory. Versions corrig\u00e9es, indicateurs, v\u00e9rifications de d\u00e9tection et proc\u00e9dures d'\u00e9viction.<\/p>","protected":false},"author":1,"featured_media":4450,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,15],"tags":[503,511,502,510,509,501,500,417,365],"class_list":["post-4452","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-critical-cves","category-threat-intelligence","tag-armory-castle","tag-broadcom","tag-cve-2026-123890","tag-golden-saml","tag-unc5221","tag-vcenter","tag-vmware","tag-vulnerability-management","tag-zero-day"],"_links":{"self":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts\/4452","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/comments?post=4452"}],"version-history":[{"count":0,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts\/4452\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/media\/4450"}],"wp:attachment":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/media?parent=4452"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/categories?post=4452"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/tags?post=4452"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}