<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Log4Shell on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/log4shell/</link>
    <description>Recent content in Log4Shell on guy@secdev.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>Guy Dixon | guy@secdev.uk</copyright>
    <lastBuildDate>Sat, 13 Sep 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.secdev.uk/blog/tags/log4shell/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Java Security: From Spring Boot Misconfigs to Deserialization</title>
      <link>https://www.secdev.uk/blog/technology/2025-09-13-java-security-spring-boot-deserialization/</link>
      <pubDate>Sat, 13 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/technology/2025-09-13-java-security-spring-boot-deserialization/</guid>
      <description>&lt;p&gt;Java has this reputation for being &amp;ldquo;safe&amp;rdquo; because of its type system, managed memory, and mature ecosystem. The more I&amp;rsquo;ve dug into Java security, the more I think that reputation is misleading, and honestly, a bit dangerous. Java&amp;rsquo;s security pitfalls aren&amp;rsquo;t about buffer overflows or memory corruption. They&amp;rsquo;re about the language&amp;rsquo;s powerful runtime features: deserialization, reflection, JNDI lookups, expression languages, and the Spring framework&amp;rsquo;s convention-over-configuration philosophy that silently enables dangerous defaults. In this post I want to walk through the Java-specific anti-patterns that lead to remote code execution, data leaks, and authentication bypasses, from the classic &lt;code&gt;ObjectInputStream&lt;/code&gt; gadget chain to the Spring Boot actuator endpoint that can expose entire environments.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
