Posts with #Log4shell
#Log4shell
Public posts on X that use #Log4shell.
Related hashtags

Sophos X-Ops@SophosXOpsNEW on #Log4Shell... Inside the code: How the Log4Shell exploit works 1/213196639
Rob Fuller@mubixIf you have LDAP servers inside your network, or trust external 3rd-party ones, and either of them allow the schema attributes javaClassName, javaCodeBase or javaSerializedObject as writable, you should be making sure attackers aren't using them for #Log4j #Log4Shell5179534
Docker Hub public Log4Shell detection is now live on Docker Official Images. Check the status of #Log4Shell remediation directly from #DockerHub here:33494
FireEye Developers@FireEyeDevFireEye has released a public repo to facilitate hunting for IOC related to the #log4j vulnerability. Shout out to @0xF2EDCA5A and Elazar Broad! #log4shell #infosec179168
Probably one of the best curated lists on affected systems for Log4j side of the house: #Log4J #Log4Shell5122335
Thomas Patzke@blubbfictionPublished some data from my #Log4Shell honeypot ( instances: • raw exploits: • deobfuscated exploits: • URLs: CSVs are updated every 6 hours.446105
Rob Fuller@mubix10 #Log4Shell Facts vs Fiction: a 🧵 1. 1.x is NOT vuln to this RCE. While it doesn't have another RCE, it requires access to send serialized data to a listener ON the log server. This is much MUCH harder to exploit and kind of rare for a Log4j server to be running.12298855
How to test your apps for #log4shell vulnerability 1. Generate a DNS token 2. Wrap that token in Prefix: ${jndi:ldap:// Suffix: /a} 3. Use that value in search forms, profile data, settings etc. of your apps 4. Get notified when you triggered a reaction371.2K3.2K
I fell in love with #Log4Shell again; 4 P1s in a row. Its a simple recon and understanding where to spray the payload. This tweet is for you haters who made fun of my recent Log4Shell post. #BugBounty2181646
Stefan Stranger 🔍@sstrangerGet-Log4shellVuln.ps1 #PowerShell script scans all local drives for presence of log4j jar files and analyzes the contents of the jar file to determine if it is vulnerable to #log4shell (CVE-2021-44228) vulnerability260191
Red Hat@RedHatA critical zero-day flaw in Apache #Log4j 2 was made publicly known, which can allow a remote attacker to execute code on a target system with the same privileges as an app using Apache Log4j 2. Read Red Hat’s advisory on CVE-2021-44228 or #Log4Shell:06998
the patching will continue until morale improves #log4j #log4shell671446
Aziz ⚡@nXtExploitHow to test your apps for #log4shell vulnerability ? 1. Go to 2. Enter your email-ID and generate a Log4shell token. 3. Use that value in search forms, profile data, settings etc. of your target apps. 5. Get notified via #email after #payload triggered.476169
- Show more posts












