<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security on Red Mug Development</title>
    <link>https://www.redmugguy.dev/tags/security/</link>
    <description>Recent content in Security on Red Mug Development</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 19 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.redmugguy.dev/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Java4Shell and Your Spring Boot Service: A Triage Checklist</title>
      <link>https://www.redmugguy.dev/posts/java4shell-spring-boot-triage/</link>
      <pubDate>Thu, 19 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.redmugguy.dev/posts/java4shell-spring-boot-triage/</guid>
      <description>Java4Shell is real, but whether it can hurt your Spring Boot service comes down to three checks: your JDK build, your CPU, and whether untrusted Base64 reaches the JDK decoder. In a default Spring Boot 3 or 4 app, it does, through HTTP Basic, CSRF and file uploads. Here&amp;rsquo;s how to check a whole fleet, then patch and prove it.</description>
    </item>
  </channel>
</rss>
