Cybersecurity Podcasts
  • All Technology
  • AI
  • Autonomy
  • B2B Growth
  • Big Data
  • BioTech
  • ClimateTech
  • Consumer Tech
  • Crypto
  • Cybersecurity
  • DevOps
  • Digital Marketing
  • Ecommerce
  • EdTech
  • Enterprise
  • FinTech
  • GovTech
  • Hardware
  • HealthTech
  • HRTech
  • LegalTech
  • Nanotech
  • PropTech
  • Quantum
  • Robotics
  • SaaS
  • SpaceTech
AllNewsDealsSocialBlogsVideosPodcastsDigests

Cybersecurity Pulse

EMAIL DIGESTS

Daily

Every morning

Weekly

Sunday recap

NewsDealsSocialBlogsVideosPodcasts
CybersecurityPodcastsSANS Stormcast Friday, December 12th, 2025: Local AI Models; Mystery Chrome 0-Day; SOAPwn Attack
SANS Stormcast Friday, December 12th, 2025: Local AI Models; Mystery Chrome 0-Day; SOAPwn Attack
Cybersecurity

SANS Internet StormCast

SANS Stormcast Friday, December 12th, 2025: Local AI Models; Mystery Chrome 0-Day; SOAPwn Attack

SANS Internet StormCast
•December 12, 2025•6 min
0
SANS Internet StormCast•Dec 12, 2025

Key Takeaways

  • •Running local AI models on Horizon chips reveals Proxmox pitfalls.
  • •Chrome mystery 0‑day lacks CVE, coordination with vendors pending.
  • •SOAP request handling flaw enables arbitrary file writes in .NET.
  • •Hacktivist attacks target small manufacturers’ OT sensors and infrastructure.
  • •Microsoft blames developers for SOAP vulnerability, not fixing core issue.

Pulse Analysis

The episode opens with a practical guide to deploying local AI models, specifically Gamma 3, on a modest home lab using a Horizon chip and Proxmox virtualization. Running models locally gives organizations greater data sovereignty and reduces reliance on cloud APIs, but the host notes several configuration hurdles—device passthrough, memory allocation, and networking quirks—that can trip up even seasoned engineers. By documenting these pitfalls, the discussion highlights the growing accessibility of edge AI while reminding practitioners that hardware compatibility and container orchestration remain critical success factors for secure, performant deployments.

The hosts then shift to a newly disclosed Chrome vulnerability described only as a “mystery 0‑day.” No CVE identifier has been assigned, and Google’s advisory offers a single line—“under coordination”—suggesting that the flaw may affect multiple browsers or shared libraries. This lack of detail underscores the challenges of coordinated vulnerability disclosure when multiple vendors are involved. Listeners are urged to keep Chrome up‑to‑date, as the patch is already rolling out, and to monitor vendor bulletins for related browsers that might share the same underlying component.

Finally, the show examines a critical SOAP handling weakness in .NET that can turn crafted file‑scheme URLs into arbitrary file writes or remote code execution. Watchtower Labs demonstrated a proof‑of‑concept exploit against Barracuda appliances, proving the issue is exploitable in real‑world products. Microsoft’s response places responsibility on developers rather than the framework, a stance that raises concerns for enterprises building .NET services. Coupled with a CISA report on hacktivist campaigns targeting small manufacturers’ OT sensors, the episode stresses the need for secure coding practices, timely patching, and robust monitoring across both IT and operational environments.

Episode Description

Using AI Gemma 3 Locally with a Single CPU

https://isc.sans.edu/diary/Using%20AI%20Gemma%203%20Locally%20with%20a%20Single%20CPU%20/32556

https://chromereleases.googleblog.com/2025/12/stable-channel-update-for-desktop_10.html

https://labs.watchtowr.com/soapwn-pwning-net-framework-applications-through-http-client-proxies-and-wsdl/

Show Notes

0

Comments

Want to join the conversation?

Loading comments...