<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nadide Beyza Dokur on Medium]]></title>
        <description><![CDATA[Stories by Nadide Beyza Dokur on Medium]]></description>
        <link>https://medium.com/@ndokur?source=rss-5466efedf630------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*APndtKMHKg1MVAQ7hN0XCA.jpeg</url>
            <title>Stories by Nadide Beyza Dokur on Medium</title>
            <link>https://medium.com/@ndokur?source=rss-5466efedf630------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:05:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ndokur/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Understanding the Log4j Weakness in WebLogic Patch Files — and Why You Shouldn’t Delete Them…]]></title>
            <link>https://medium.com/@ndokur/understanding-the-log4j-weakness-in-weblogic-patch-files-and-why-you-shouldnt-delete-them-3b8740535c5d?source=rss-5466efedf630------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b8740535c5d</guid>
            <category><![CDATA[log4j]]></category>
            <category><![CDATA[log4j-vulnerability]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[oracle-weblogic]]></category>
            <category><![CDATA[oracle-fusion-middleware]]></category>
            <dc:creator><![CDATA[Nadide Beyza Dokur]]></dc:creator>
            <pubDate>Thu, 04 Dec 2025 08:55:15 GMT</pubDate>
            <atom:updated>2025-12-04T08:55:15.512Z</atom:updated>
            <content:encoded><![CDATA[<h3>Understanding the Log4j Weakness in WebLogic Patch Files — and Why You Shouldn’t Delete Them Manually</h3><p>When security scanners flag old Log4j JAR files inside your WebLogic patch directories, it’s natural to be concerned.</p><p>You might think: <em>“We’ve already applied the latest patches — can’t we just delete the old ones to get rid of the alerts?”</em></p><p>Let’s explore why manual deletion isn’t a good idea, what Oracle officially recommends, and how to handle these false positives safely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/413/1*rrvBf9MLkgg1FE7zyDXl4A.png" /><figcaption><strong>Figure 1.</strong> Oracle &amp; Log4j</figcaption></figure><h3>The Situation: Log4j JARs Detected in WebLogic Patch Directories</h3><p>A common case looks like this:</p><blockquote><em>In some of our application servers, security scans report Log4j versions lower than 2.17 inside the WebLogic patch folders (for example, under April 2024 or January 2025 CPU patches).</em></blockquote><blockquote><em>Since we’ve already applied those patches, can we remove the files from the server without causing issues?</em></blockquote><p>The short answer: <strong>No, you should not remove them manually.</strong></p><h3>Why You Shouldn’t Delete Patch Files Manually</h3><p>According to Oracle’s official documentation, patch directories (like .patch_storage, April2024, or January2025) should never be manually deleted.<br> These directories are used by OPatch — Oracle’s patching tool — for several internal operations such as:</p><ul><li>Rollback</li><li>Reapply</li><li>Inventory management</li></ul><p>Deleting or modifying them manually may break future patching processes.</p><blockquote><em>“It is highly recommended that you back up the Oracle home before any patch operation.”<br> </em>(Oracle Fusion Middleware 12.2.1.4 Patching Guide — Chapter: Preparing to Use OPatch → Backup and Recovery Considerations for Patching)</blockquote><blockquote><a href="https://docs.oracle.com/en/middleware/fusion-middleware/12.2.1.4/opatc/patching-your-environment-using-opatch.html"><em>Read the official guide here</em></a></blockquote><h3>Official Oracle References Supporting This</h3><h4><strong>Doc ID 403218.1 — </strong>“Can You Delete $ORACLE_HOME/.patch_storage Directory?”</h4><blockquote>“It is not recommended to manually delete the contents of the .patch_storage directory, as it may impact future patch or rollback operations.”<br> <a href="https://support.oracle.com/knowledge/Oracle%20Database%20Products/403218_1.html">Oracle Support Doc ID 403218.1</a></blockquote><h4><strong>Doc ID 2991362.1 — “</strong>Can We Delete .patch_storage/backup_delete_inactive folder manually ?”</h4><blockquote>Mentions that <em>.patch_storage/backup_delete_inactive</em> folders should not be manually deleted, and should only be managed via OPatch’s cleanup functions.<br><a href="https://support.oracle.com/knowledge/Middleware/2991362_1.html">Oracle Support Doc ID 2991362.1</a></blockquote><h3>The Correct Way: Use OPatch Cleanup</h3><p>Starting with OPatch version 12.2.0.1.37, Oracle introduced an official cleanup feature for inactive patches.</p><blockquote><em>“From version 12.2.0.1.37 onward, OPatch includes a proper cleanup for inactive patches.”<br> </em>(MOS Doc ID 2942102.1 — Clean-Up the ‘.patch_storage’ Directory)</blockquote><p>You can safely use:</p><pre>$ORACLE_HOME/OPatch/opatch util cleanup</pre><p>This command removes unnecessary patch data without affecting rollback or inventory operations.</p><p><a href="https://oracle-base.com/articles/misc/clean-up-the-patch-storage-directory">Reference: Oracle-Base article on patch storage cleanup</a></p><h3>What About Log4j Vulnerabilities?</h3><p>Oracle has already addressed Log4j vulnerabilities (such as CVE-2021–44228) through Critical Patch Updates (CPUs).<br> These patches automatically upgrade or mitigate vulnerable Log4j versions within the WebLogic environment.</p><p>If you’ve applied the January 2025 or April 2024 CPU patches, your runtime environment should already be protected — even if older JARs appear inside patch directories.</p><p><a href="https://www.oracle.com/security-alerts/alert-cve-2021-44228.html">Oracle Security Alert for CVE-2021–44228 / Log4j</a></p><h3>️Security Scans and False Positives</h3><p>Many vulnerability scanners flag these JARs even though they aren’t used at runtime — they’re just archived patch artifacts.<br> This is a false positive scenario.</p><p>To address this:</p><ul><li>Open a Service Request (SR) with Oracle to mark them as false positives.</li><li>Or use OPatch cleanup if your version supports it.</li></ul><p>Avoid manual deletion.</p><h3>Key Takeaway</h3><blockquote><strong><em>Never manually delete WebLogic patch directories — even if they contain old Log4j versions.</em></strong></blockquote><blockquote><em>Use official OPatch utilities for cleanup, and rely on Oracle’s documented patching process to ensure long-term stability and compliance.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b8740535c5d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>