Skip to main content
JG is here with you ✨
Back to Bulletins
πŸ”΄ CRITICALDecember 10, 2025

Patch-Window Pressure:
The 48-Hour Sprint

React2Shell mass exploitation, WinRAR KEV deadline, Microsoft zero-day, .NET SOAPwn

MAX CVSS

10.0

TOTAL THREATS

4

ACTOR GROUPS

5+

TIME TO EXPLOIT

<5h

πŸ“‹ Executive Summary

Four critical vulnerabilities disclosed this week require immediate action. React2Shell (CVE-2025-55182, CVSS 10.0) is actively exploited by Chinese APT groups, enabling full server compromise of React-based web applications with a single HTTP request β€” exploitation began within hours of disclosure.

WinRAR path traversal (CVE-2025-6218, CISA KEV deadline Dec 30) is being weaponized by three state-nexus threat actors in phishing campaigns targeting global organizations.

Microsoft Patch Tuesday addressed 57 flaws including one actively exploited zero-day (CVE-2025-62221) enabling privilege escalation on Windows systems.

.NET SOAP client vulnerabilities (CVSS 9.8) allow attackers to write files to disk and achieve remote code execution, with Microsoft declining to patch ("application behavior").

🚨 If You Only Do 3 Things Today

1️⃣

Patch React Server Components

CVE-2025-55182 β†’ Update react-server-dom-* to 19.0.1+ or Next.js 14.2.22+/15.1.4+

⏱️ Time: ~15 min per service | πŸ‘€ Owner: Platform/DevOps teams

2️⃣

Deploy December 2025 Windows Updates

CVE-2025-62221 actively exploited β†’ Install KB5072033/KB5071417

⏱️ Time: ~30 min per host | πŸ‘€ Owner: Windows admins

3️⃣

Hunt for Compromise

Check Startup folders (WinRAR), web directories for .aspx shells (SOAPwn), privilege escalation indicators (Microsoft)

⏱️ Time: ~1 hour | πŸ‘€ Owner: Security/SOC teams


β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ•—  β–ˆβ–ˆβ•—β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—     β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—  β–ˆβ–ˆβ•—
β•šβ•β•β–ˆβ–ˆβ•”β•β•β•β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β–ˆβ–ˆβ•”β•β•β•β•β•β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β•šβ•β•β–ˆβ–ˆβ•”β•β•β•    β–ˆβ–ˆβ•”β•β–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ–ˆβ•‘
   β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•‘β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β•β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—  β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘       β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•”β–ˆβ–ˆβ•‘β•šβ–ˆβ–ˆβ•‘
   β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β–ˆβ–ˆβ•”β•β•β•  β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘       β–ˆβ–ˆβ–ˆβ–ˆβ•”β•β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•‘
   β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘       β•šβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β• β–ˆβ–ˆβ•‘
   β•šβ•β•   β•šβ•β•  β•šβ•β•β•šβ•β•  β•šβ•β•β•šβ•β•β•β•β•β•β•β•šβ•β•  β•šβ•β•   β•šβ•β•        β•šβ•β•β•β•β•β•  β•šβ•β•
         REACT2SHELL β€” THE EXPLOITATION WAVE
πŸ”΄ CRITICAL⚠️ ACTIVELY EXPLOITEDπŸ›οΈ CISA KEV

THREAT 01 β€” React2Shell: The Exploitation Wave

NAME

React2Shell

CVE

CVE-2025-55182

CVSS

10.0

STATUS

Actively exploited; CISA KEV (Dec 5, deadline Dec 26)

One-liner:

Send one HTTP request, own the server. No auth required.

🚩 Red Flag Checklist

βœ… Check ALL that apply (if 2+ match, prioritize patching):

⚠️ If 3+ boxes checked: Stop reading. Patch now. Come back later.

πŸ“… Timeline to Compromise

Dec 3, 9:00 AM⚠️CVE disclosed by React team
Dec 3, 11:00 AMπŸ”Mass scanning begins (Shadowserver detects 10K scans/hour)
Dec 3, 2:00 PMπŸ’₯First successful exploits (Huntress observes PeerBlight deployment)
Dec 4, 8:00 AM🌍165,000+ vulnerable IPs identified (automated scanning at scale)
Dec 5, 12:00 PMπŸ›οΈCISA adds to KEV catalog (federal deadline: Dec 26)
Dec 8, 6:00 PMπŸ“Š<20% of vulnerable servers patched (you are reading this now)

⏰ YOUR WINDOW: 18 days left until CISA deadline. Attackers exploited in <5 hours.

βš”οΈ Your Unfair Advantage

While you're waiting for change control approval, deploy these defenses NOW:

1️⃣ Block RSC endpoints at the firewall (if app is internal-only)

iptables -A INPUT -p tcp --dport 3000 -s <internal-subnet> -j ACCEPT

Effect: External scans can't reach your app (buys you days)

2️⃣ Rate-limit POST requests to /_next/data/ (if WAF is available)

Cloudflare: 10 requests/min per IP

Effect: Mass exploitation campaigns fail (attackers move to easier targets)

3️⃣ Enable verbose logging for RSC endpoints (free, takes 2 min)

# Next.js: Set DEBUG=* in .env

Effect: You'll see exploitation attempts in real-time (early warning)

These won't stop a targeted attack, but they'll filter out 90% of automated scans. Patch is still required β€” but these buy you breathing room.

πŸ› οΈ Mitigations

πŸ”΄ IMMEDIATE (Do Today, Patch Window <24h)

  1. Upgrade react-server-dom-* to 19.0.1, 19.1.2, or 19.2.1 on all Internet-facing services

    ⏱️ Time: ~15 min per service

    # Check current versions
    npm list react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopack
    
    # Upgrade (example for webpack)
    npm install react-server-dom-webpack@19.0.1 --save
    
    # Restart services
    pm2 restart all # or systemctl restart your-app
  2. Update Next.js, React Router, Waku to vendor-patched versions

    ⏱️ Time: ~20 min per app

    βœ… Fixed versions: Next.js 14.2.22+, 15.1.4+

πŸ“š Sources


β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ•—  β–ˆβ–ˆβ•—β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—     β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— 
β•šβ•β•β–ˆβ–ˆβ•”β•β•β•β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β–ˆβ–ˆβ•”β•β•β•β•β•β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β•šβ•β•β–ˆβ–ˆβ•”β•β•β•    β–ˆβ–ˆβ•”β•β–ˆβ–ˆβ–ˆβ–ˆβ•—β•šβ•β•β•β•β–ˆβ–ˆβ•—
   β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•‘β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β•β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—  β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘       β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•”β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β•
   β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β–ˆβ–ˆβ•”β•β•β•  β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘       β–ˆβ–ˆβ–ˆβ–ˆβ•”β•β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•”β•β•β•β• 
   β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘       β•šβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β•β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—
   β•šβ•β•   β•šβ•β•  β•šβ•β•β•šβ•β•  β•šβ•β•β•šβ•β•β•β•β•β•β•β•šβ•β•  β•šβ•β•   β•šβ•β•        β•šβ•β•β•β•β•β• β•šβ•β•β•β•β•β•β•
      WINRAR β€” THREE APTs, ONE VULNERABILITY
🟠 HIGH⚠️ ACTIVELY EXPLOITEDπŸ›οΈ CISA KEV

THREAT 02 β€” WinRAR: Three APTs, One Vulnerability

NAME

WinRAR Path Traversal

CVE

CVE-2025-6218

CVSS

7.8

STATUS

Actively exploited by 3 APT groups; CISA KEV (Dec 9, deadline Dec 30)

One-liner:

Malicious RAR archives write files to Startup folder β†’ code execution on next login.

Technical Breakdown

Path traversal vulnerability allows attackers to place files in sensitive Windows locationsβ€”specifically the Startup folderβ€”via specially crafted RAR archives. When the victim extracts the archive (or even previews it in some configurations), malicious files auto-execute on next system login.

Three confirmed threat actors:

  • GOFFEE (Paper Werewolf) β€” Russian-nexus group, dual-exploit campaigns
  • Bitter (APT-C-08) β€” South Asia-focused espionage, drops C# trojan via Normal.dotm persistence
  • Gamaredon β€” Russian state-aligned, targeting Ukrainian military/government with Pteranodon malware + GamaWiper

πŸ“… Timeline to Compromise

June 2025πŸ› οΈRARLAB patches CVE-2025-6218 in WinRAR 7.12
July 2025πŸ’₯First exploitation by GOFFEE
Oct 2025πŸ‡ΊπŸ‡¦Gamaredon joins with Pteranodon malware
Nov 2025πŸ’£Gamaredon deploys GamaWiper (first observed destructive operations)
Dec 9, 2025πŸ›οΈCISA adds to KEV catalog (federal deadline: Dec 30)
Dec 10, 2025πŸ“ŠMajority of Windows users still on WinRAR < 7.12 (you are reading this now)

⏰ YOUR WINDOW: 20 days until CISA deadline. Attackers have been exploiting for 5+ months.

🚩 Red Flag Checklist

βœ… Check ALL that apply (if 2+ match, prioritize patching):

⚠️ If 3+ boxes checked: Update TODAY. This is not optional.

βš”οΈ Your Unfair Advantage

While you're waiting for change control approval, deploy these defenses NOW:

1️⃣ Block RAR file extraction at email gateway

Office 365: Transport Rule β†’ Block attachments with .rar extension
Gmail: Admin Console β†’ Attachments β†’ Add ".rar" to blocked list

⏱️ Time: 3 minutes | Effect: Eliminates delivery vector entirely

2️⃣ Enable Startup folder monitoring (Sysmon)

# Sysmon config (add to <RuleGroup name="FileCreate">)
<FileCreate onmatch="include">
  <TargetFilename condition="contains">\Start Menu\Programs\Startup\</TargetFilename>
</FileCreate>

⏱️ Time: 5 minutes | Effect: Real-time alerts on Startup folder writes

3️⃣ Audit existing Startup folders (hunt for compromise NOW)

Get-ChildItem "C:\Users\*\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\" -Recurse | Select-Object FullName, CreationTime, LastWriteTime

⏱️ Time: 2 minutes | Effect: Identifies if you're already compromised

πŸ› οΈ Mitigations

πŸ”΄ IMMEDIATE (Do Today)

  1. Upgrade WinRAR to 7.12+ on all Windows endpoints

    ⏱️ Time: ~5 min per endpoint (or deploy via GPO/SCCM)

  2. Block .rar attachments at email gateway

    ⏱️ Time: ~3 min | Effect: Stops phishing delivery entirely

  3. Hunt for Normal.dotm compromise (Bitter TTPs)
    Get-ChildItem "C:\Users\*\AppData\Roaming\Microsoft\Templates\Normal.dotm" | Where-Object {$_.LastWriteTime -gt (Get-Date).AddDays(-60)}

πŸ“š Sources

  • πŸ”΄ BI.ZONE: WinRAR Zero-Day

    β†’ GOFFEE campaign analysis + dual-exploit details

  • πŸ›οΈ CISA KEV: CVE-2025-6218

    β†’ Federal deadline (Dec 30) + KEV entry details

  • πŸ” Foresiet: APT-C-08 Exploitation

    β†’ Bitter APT campaign documentation + Normal.dotm TTPs


β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ•—  β–ˆβ–ˆβ•—β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—     β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— 
β•šβ•β•β–ˆβ–ˆβ•”β•β•β•β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β–ˆβ–ˆβ•”β•β•β•β•β•β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β•šβ•β•β–ˆβ–ˆβ•”β•β•β•    β–ˆβ–ˆβ•”β•β–ˆβ–ˆβ–ˆβ–ˆβ•—β•šβ•β•β•β•β–ˆβ–ˆβ•—
   β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•‘β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β•β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—  β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘       β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•”β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β•
   β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β–ˆβ–ˆβ•”β•β•β•  β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘       β–ˆβ–ˆβ–ˆβ–ˆβ•”β•β–ˆβ–ˆβ•‘ β•šβ•β•β•β–ˆβ–ˆβ•—
   β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘       β•šβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β•β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β•
   β•šβ•β•   β•šβ•β•  β•šβ•β•β•šβ•β•  β•šβ•β•β•šβ•β•β•β•β•β•β•β•šβ•β•  β•šβ•β•   β•šβ•β•        β•šβ•β•β•β•β•β• β•šβ•β•β•β•β•β• 
    MICROSOFT PATCH TUESDAY β€” 57 FLAWS, 3 ZERO-DAYS
πŸ”΄ CRITICAL⚠️ 1 ACTIVELY EXPLOITED🟑 2 PUBLICLY DISCLOSED

THREAT 03 β€” Microsoft Patch Tuesday: 57 Flaws, 3 Zero-Days

NAME

Microsoft December 2025 Patch Tuesday

CVEs

57 total (3 zero-days)

CVSS MAX

9.0

STATUS

CVE-2025-62221 actively exploited; 2 publicly disclosed

One-liner:

1 zero-day exploited in the wild, 2 publicly disclosed, 19 RCE flaws across Windows/Office.

Technical Breakdown

Microsoft's December 2025 Patch Tuesday addresses 57 vulnerabilities, including:

πŸ”΄ ACTIVELY EXPLOITED:

  • CVE-2025-62221 β€” Windows Cloud Files Mini Filter Driver EoP (CVSS 7.8)
  • Use-after-free β†’ local privilege escalation to SYSTEM
  • Any local user β†’ SYSTEM privileges β†’ full host compromise

🟑 PUBLICLY DISCLOSED (Not Yet Exploited):

  • CVE-2025-64671 β€” GitHub Copilot for JetBrains RCE (CVSS 7.3)
  • Malicious project files β†’ commands execute with developer privileges
  • CVE-2025-54100 β€” PowerShell RCE via Invoke-WebRequest (CVSS 7.8)
  • Scripts downloading web content β†’ malicious code execution

πŸ”΄ CRITICAL RCE FLAWS:

  • CVE-2025-62562 β€” Microsoft Outlook RCE (CVSS 9.0) ← Highest CVSS this month
  • CVE-2025-62554/62557 β€” Microsoft Office RCE (CVSS 8.8)

πŸ“… Timeline to Compromise

Dec 10, 10 AMπŸ“’Microsoft Patch Tuesday release (CVE-2025-62221 marked "Exploitation Detected")
Dec 10, 2 PMπŸ”Security researchers analyze patch diff
Dec 11, 12 PMπŸ’₯Public PoC likely published (historical pattern: 24-48h)
Dec 12-14🌍Mass exploitation campaigns begin
Dec 15-17πŸ“Š<30% of enterprises fully patched (holiday IT staffing shortages)

⏰ YOUR WINDOW: Patch THIS WEEK before public PoC drops. CVE-2025-62221 is SYSTEM-level EoP.

🚩 Red Flag Checklist

βœ… Check ALL that apply (if 3+ match, prioritize patching):

CVE-2025-62221 (Cloud Files EoP):

CVE-2025-54100 (PowerShell RCE):

⚠️ If 5+ boxes checked: You have multiple attack vectors. Patch TODAY.

βš”οΈ Your Unfair Advantage

While you're waiting for change control approval, deploy these defenses NOW:

1️⃣ Restrict local admin rights (mitigates CVE-2025-62221)

# Remove users from local Administrators group
net localgroup Administrators /delete DOMAIN\User

⏱️ Time: 10 minutes (GPO) | Effect: Limits EoP impact

2️⃣ Audit PowerShell scripts for Invoke-WebRequest

Get-ChildItem -Path "C:\Scripts" -Recurse -Filter "*.ps1" | Select-String -Pattern "Invoke-WebRequest|curl" | Select-Object Path, LineNumber, Line

⏱️ Time: 5 minutes | Effect: Identifies vulnerable scripts

3️⃣ Enable Office Protected View

Group Policy: User Configuration β†’ Administrative Templates β†’ Microsoft Office β†’ Security Settings β†’ Trust Center β†’ Protected View
Enable: "Protected View for files originating from the Internet"

⏱️ Time: 5 minutes (GPO) | Effect: Blocks Office RCE auto-execution

πŸ› οΈ Mitigations

πŸ”΄ IMMEDIATE (Do Today)

  1. Deploy December 2025 Windows Updates

    ⏱️ Time: ~30 min per host (or WSUS automation)

    βœ… Windows 11 24H2: KB5072033 | Windows 10 22H2: KB5071417

  2. Add -UseBasicParsing to all Invoke-WebRequest scripts

    ⏱️ Time: 15-30 min | Effect: Prevents CVE-2025-54100 exploitation

  3. Disable GitHub Copilot terminal auto-approve

    ⏱️ Time: 2 min per developer | Effect: Mitigates CVE-2025-64671

πŸ“š Sources

  • πŸ›οΈ Microsoft Security Update Guide

    β†’ Official Patch Tuesday details + CVE listings

  • πŸ“° BleepingComputer: Patch Tuesday Analysis

    β†’ Comprehensive breakdown of all 57 vulnerabilities

  • πŸ” Ari Marzuk: IDEsaster Disclosure

    β†’ GitHub Copilot CVE-2025-64671 technical analysis


β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ•—  β–ˆβ–ˆβ•—β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—     β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ•—  β–ˆβ–ˆβ•—
β•šβ•β•β–ˆβ–ˆβ•”β•β•β•β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β–ˆβ–ˆβ•”β•β•β•β•β•β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β•šβ•β•β–ˆβ–ˆβ•”β•β•β•    β–ˆβ–ˆβ•”β•β–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘
   β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•‘β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β•β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—  β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘       β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•”β–ˆβ–ˆβ•‘β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•‘
   β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β–ˆβ–ˆβ•”β•β•β•  β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘       β–ˆβ–ˆβ–ˆβ–ˆβ•”β•β–ˆβ–ˆβ•‘β•šβ•β•β•β•β–ˆβ–ˆβ•‘
   β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ•‘  β–ˆβ–ˆβ•‘   β–ˆβ–ˆβ•‘       β•šβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β•     β–ˆβ–ˆβ•‘
   β•šβ•β•   β•šβ•β•  β•šβ•β•β•šβ•β•  β•šβ•β•β•šβ•β•β•β•β•β•β•β•šβ•β•  β•šβ•β•   β•šβ•β•        β•šβ•β•β•β•β•β•      β•šβ•β•
      .NET SOAPwn β€” WHEN MICROSOFT SAYS "NOT A BUG"
🟠 HIGHπŸ”΄ MICROSOFT WON'T FIX⚠️ BLACK HAT DISCLOSED

THREAT 04 β€” .NET SOAPwn: When Microsoft Says "Not A Bug"

NAME

.NET SOAPwn (WSDL/Proxy Abuse)

CVEs

CVE-2025-34392 (Barracuda), CVE-2025-13659 (Ivanti)

CVSS MAX

9.8

STATUS

Black Hat EU 2025 disclosed; Microsoft declined to patch

One-liner:

Rogue WSDL files β†’ .NET HTTP client proxies write ASPX web shells to disk β†’ RCE.

Technical Breakdown

SOAPwn is a vulnerability class, not a single CVE. It exploits how .NET Framework handles SOAP clientsβ€”specifically, the ServiceDescriptionImporter class that generates HTTP client proxies from WSDL files.

The Core Bug:

  1. Attacker controls a WSDL file URL (via user input or compromised service)
  2. .NET's ServiceDescriptionImporter fetches and parses the WSDL
  3. No validation on URL scheme β†’ accepts file:// paths
  4. Generated HTTP client proxy writes SOAP requests to arbitrary file paths
  5. Result: ASPX web shell β†’ RCE

Why This Is Dangerous:

  • Microsoft won't fix it: "Users should not consume untrusted input"
  • Affects thousands of apps: Any .NET service generating proxies from external WSDL
  • Silent exploitation: No crashes, no errorsβ€”just a new web shell on disk
  • Supply chain risk: WSDL files often fetched from third-party services

Confirmed Victims:

  • Barracuda Service Center RMM (CVE-2025-34392, CVSS 9.8) β€” patched in 2025.1.1
  • Ivanti Endpoint Manager (CVE-2025-13659, CVSS 8.8) β€” patched in 2024 SU4 SR1
  • Umbraco 8 (unpatched as of Dec 2025)
  • Unknown custom .NET apps (likely thousands vulnerable)

πŸ“… Timeline to Compromise

Mar 2024πŸ”¬watchTowr Labs discovers SOAPwn β†’ privately discloses to Microsoft
July 2025❌Microsoft declines to patch ("application issue, not framework issue")
Dec 6, 2025πŸ“’Black Hat Europe 2025: Public disclosure
Dec 9, 2025πŸ› οΈBarracuda releases patch (v2025.1.1) | Ivanti releases patch
Dec 10-15🌍Scanning for vulnerable .NET apps begins
Jan 2026+⏰Long-tail risk: countless custom apps remain vulnerable (Microsoft won't fix)

⏰ YOUR WINDOW: If you use Barracuda/Ivanti, patch THIS WEEK. Custom .NET apps? Audit NOW.

🚩 Red Flag Checklist

βœ… Check ALL that apply (if 3+ match, investigate immediately):

Confirmed Vulnerable Products:

Custom .NET Applications:

⚠️ If 3+ boxes checked: You're vulnerable. Start code audit TODAY.

βš”οΈ Your Unfair Advantage

While auditing code or waiting for vendor patches, deploy these defenses NOW:

1️⃣ Block file:// scheme at WAF

# ModSecurity rule (example)
SecRule ARGS "@contains file://" \
  "id:1001,phase:2,deny,status:403,msg:'Blocked file:// in WSDL URL'"

⏱️ Time: 5 minutes | Effect: Prevents malicious WSDL with file:// handlers

2️⃣ Enable file integrity monitoring for web directories

# Monitor for new .aspx/.ashx files
Get-ChildItem -Path "C:\inetpub\wwwroot" -Recurse -Filter "*.aspx" | Where-Object {$_.CreationTime -gt (Get-Date).AddDays(-7)}

⏱️ Time: 10 minutes | Effect: Alerts when new web shells appear

3️⃣ Restrict IIS AppPool write permissions

# Remove write access from web root
icacls "C:\inetpub\wwwroot" /remove "IIS APPPOOL\YourAppPool" /T

⏱️ Time: 5 minutes | Effect: Prevents web shell creation even if exploited

πŸ› οΈ Mitigations

πŸ”΄ IMMEDIATE (Do Today)

  1. Update Barracuda Service Center RMM to 2025.1.1+

    ⏱️ Time: Vendor-dependent | Effect: Patches CVE-2025-34392

  2. Update Ivanti Endpoint Manager to 2024 SU4 SR1+

    ⏱️ Time: Vendor-dependent | Effect: Patches CVE-2025-13659

  3. Audit custom .NET apps for ServiceDescriptionImporter usage
    Get-ChildItem -Path "C:\Projects" -Recurse -Filter "*.cs" | Select-String -Pattern "ServiceDescriptionImporter"
  4. Implement WSDL URL validation (whitelist http/https only)

    Microsoft won't fix thisβ€”YOU must validate input in your code

πŸ“š Sources

  • πŸ”¬ watchTowr Labs: SOAPwn Deep-Dive

    β†’ Black Hat EU 2025 presentation + technical analysis

  • πŸ”΄ Barracuda CVE-2025-34392

    β†’ Service Center RMM vulnerability advisory + patch details

  • 🟠 Ivanti CVE-2025-13659

    β†’ Endpoint Manager vulnerability advisory + remediation

πŸ“Š Pattern Analysis: Post-Disclosure Automation

What We're Seeing This Week:

All four threats share a common pattern: hours-to-exploitation post-disclosure.

VulnerabilityDisclosureFirst ExploitTime to Exploit
React2ShellDec 3, 2025Dec 3, 2025<5 hours
WinRARJune 2025July 2025~30 days
Microsoft CVE-2025-62221Dec 10, 2025In the wild pre-disclosureZero-day

⚠️ YOUR NEW REALITY:

  • 48-hour patch windows are now the standard for internet-facing systems
  • Compensating controls (WAF, rate-limiting, network segmentation) must deploy within 4 hours
  • Hunt for compromise immediately β€” don't wait for alerts

🎯 Overall Response Scorecard

Rate your org's response across all 4 threats (be honest):

YOUR SCORE

0

❌ 0-99 pts

Critical gaps remain

🎯 Am I Vulnerable? Quick Check

Click your tech stack to see which threats apply to you:

πŸ’‘ Pro Tip:

Running multiple technologies? Your risk compounds. A React app on Windows with .NET backend = exposure to 3 of 4 threats. Use the Red Flag Checklists above to assess your actual risk.

πŸ“’ Share This Bulletin

Pre-written messages (copy-paste these):

Slack Your Dev Team

@channel 🚨 If you ship React/Next.js apps, drop what you're doing and read this: https://jmfg.ca/security-bulletin/december-10-2025...

Email Your CISO

Subject: URGENT: 4 Critical Vulns Require 48h Patch Window (React2Shell CVSS 10.0)

Open to AI-Focused Roles

AI Sales β€’ AI Strategy β€’ AI Success β€’ Creative Tech β€’ Toronto / Remote

Let's connect β†’
Terms of ServiceLicense AgreementPrivacy Policy
Copyright Β© 2026 JMFG. All rights reserved.