blog mentions hot patch cli

lunasec-io · Dec 15, 2021 · cc2b915 · cc2b915
1 parent eac07fd
commit cc2b915
Showing 1 changed file with 2 additions and 3 deletions.
diff --git a/docs/blog/2021-12-12-log4j-zero-day-mitigation-guide.mdx b/docs/blog/2021-12-12-log4j-zero-day-mitigation-guide.mdx
@@ -301,10 +301,9 @@ Because of the extensive control Log4Shell gives an attacker, it's actually poss
 This isn't the recommended strategy for various reasons, but it could be a last resort for systems that you can't easily restart or modify.  Note that doing this on a system 
 you don't have permission to is most likely illegal. The fix will only work until the server (or the JVM) is restarted.
 
-How to accomplish this is explained in [this guide](https://github.com/Cybereason/Logout4Shell).
+**Update:** We have added this functionality to the [latest release](https://github.com/lunasec-io/lunasec/releases/tag/v1.1.0-log4shell) of our Log4Shell CLI tool.
 
-We are currently adding this functionality to our CLI. 
-[Subscribe below](#stay-in-the-loop) to be alerted when it's live.
+How it works and how to accomplish it manually is explained in [this guide](https://github.com/Cybereason/Logout4Shell).
 
 ## How to protect yourself from future 0-days