Previous log4j patch insufficient in some situations. New CVE posted and new log4j released 2.16. Security News & Discussion |
- Previous log4j patch insufficient in some situations. New CVE posted and new log4j released 2.16.
- Security Analysis of the 2nd Log4j CVE published earlier (CVE-2021-45046 / Log4Shell2)
- Log4J – A Look into Threat Actors Exploitation Attempts
- log4j-jndi-be-gone: A simple mitigation for CVE-2021-44228 - log4j
- IPs exploiting the log4j2 CVE-2021-44228 detected by the crowdsec community
- Remote Deserialization Bug in Microsoft's RDP Client through Smart Card Extension (CVE-2021-38666)
- Exploiting CVE-2021-42278 and CVE-2021-42287 to impersonate DA from standard domain user
- log4jail - A firewall reverse proxy for preventing Log4J (Log4Shell aka CVE-2021-44228) attacks
- Yara rules to look for Log4J usage
- fully independent exploit does not require any 3rd party binaries. The exploit spraying the payload to all possible logged HTTP Headers such as
- Payload extracted from process dump of Trojan chrome installer. Can't find much info about this virus online other than its been around a long time.
- TCP reverse shell written in Rust
- Invoke-noPac - CVE-2021-42287/CVE-2021-42278 Scanner & Exploiter
You are subscribed to email updates from /r/netsec - Information Security News & Discussion. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States |
No comments:
Post a Comment