<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CWE-1104 on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/cwe-1104/</link>
    <description>Recent content in CWE-1104 on guy@secdev.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>Guy Dixon | guy@secdev.uk</copyright>
    <lastBuildDate>Sat, 12 Apr 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.secdev.uk/blog/tags/cwe-1104/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Vulnerable Components</title>
      <link>https://www.secdev.uk/blog/technology/2025-04-12-vulnerable-components/</link>
      <pubDate>Sat, 12 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/technology/2025-04-12-vulnerable-components/</guid>
      <description>&lt;p&gt;Your application is only as secure as its least-maintained dependency, and this is one of those lessons that really sinks in once you start digging into dependency trees. OWASP A06 (Vulnerable and Outdated Components) covers the reality that most modern applications are more dependency code than application code, and a single outdated library can undermine every security measure you&amp;rsquo;ve built. CWE-1104 captures this: the use of unmaintained third-party components with known vulnerabilities. In this post I&amp;rsquo;ll walk through real dependency chains in Python, Java, and JavaScript, from the Log4Shell-level disasters that make headlines to the subtle version pins that quietly accumulate CVEs while nobody&amp;rsquo;s watching.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
