ysoserial
Log4jAttackSurface
Our great sponsors
ysoserial | Log4jAttackSurface | |
---|---|---|
13 | 40 | |
7,291 | 2,085 | |
- | - | |
0.0 | 0.0 | |
30 days ago | over 2 years ago | |
Java | ||
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ysoserial
- anybody got ysoserial to work in kali 2022 running java v17?
-
Java deserialization payloads in log4j (Unified starting point)
So I've finished the unified box in stage 2 of the starting point and have tons of questions about the box. In the box they use veracode-research/rogue-jndi to exploit the log4j vulnerability. But when I test it with deserialize payload generated by frohoff/ysoserial it's not running. I've try to look at the java log in the challenge container but can't find anything that java complain or error out. Is it because the ysoserial payload too complex that it running but fail at some point and don't throw error or maybe the author just hard code so that only the payload from rogue-jndi work? can it's because of the java version/framework/library/weirdness? Do I need to test both kind of payload if I want to exploit log4j in the future or just stick with pimps/JNDI-Expoit-Kit or cckuailong/JNDI-Injection_Exploit-Plus (my senior recommendation when exploiting log4j).
-
An Unsafe Deserialization Vulnerability and Types of Deserialization
GitHub - Ysoserial
-
Great Time at JavaZone 2022
A gadget lets you run load a different class upon serialization. This will fail later when we downcast but during the read process we can load a different class where we can do arbitrary code execution. HashMap is a class that overrides the readObject and can be used as part of an exploit chain. ysoserial helps us create a chain of serialization to produce an exploit based on known serialization weaknesses. You can run this project and generate payload ser files that you can pass to exploit potential vulnerabilities.
- PoC tool for creating payloads that exploit unsafe Java object deserialization
-
Is Java as safe as we believe?
gadget chain attack: is a type of exploit where an attacker uses a series of "gadgets" — small pieces of code that perform a specific function — to execute a larger, more complex attack. By chaining together these gadgets, an attacker can gain control of a target system or perform other malicious actions. You can use ysoserial to create a serialize payload java -jar path/to/ysoserial.jar CommonsCollections4 'whoami'
-
Is Haskell a Good Choice for Software Security?
> A similar issue has occurred with Java (and other languages, see https://frohoff.github.io/appseccali-marshalling-pickles/). Java provided a suberbly user-friendly way of serializing any object to disk and recovering it back in its original form. The only unfortunate problem was that there was no way to say which object you are expecting! This allows attackers to send you objects that, upon deserialization in your program, become nasties that wreak havoc and steal data.
Not correct. You can certainly inspect before instantiation:
https://docs.oracle.com/javase/7/docs/platform/serialization...
-
Log4j 2.15.0 – Previously suggested mitigations may not be enough
Mmh, I don't think so. Beside logging most other libraries will already sanitize user input since it is a more commonly known attack vector for those kind of libraries. I would compare the vulnerability to https://github.com/frohoff/ysoserial.
-
Analysis of the 2nd Log4j CVE published earlier (CVE-2021-45046 / Log4Shell2)
Exactly. eg. https://github.com/frohoff/ysoserial#usage
Note the classes aren't at fault or doing anything wrong (even though you could imagine other mitigations they could use), they are just conveniently there to use if you have a vulnerability that lets you de-serialize untrusted data.
-
RCE 0-day exploit found in log4j, a popular Java logging package
This has been known for a zillion years and has caused a zillion CBEs, so at this point there are off-the-shelf tools like ysoserial that take your payload and wrap it into an object that kabooms when deserialized, with like 20 different choices of methods depending on what dangerous objects are available on the target's classpath for deserialization.
Log4jAttackSurface
-
Understanding and Exploiting Log4J Vulnerability
Checkout this link for knowing Log4j impact on manufacturers https://github.com/YfryTchsGD/Log4jAttackSurface
-
Dominion Voting wins key decision in lawsuit against Fox News
Just look at the currently ongoing insanity that is the log4j exploit, and how one single exploit has lead to a generic attack that can impact tons of companies. Imagine if a state decided to use voting machines, and someone found this style of exploit in the system.
-
Sustainable Open Source Software
Last week (Dec 9th) a major vulnerability was discovered in an open source logging project for Java called log4j. The vulnerability called Log4Shell would allow anyone to remotely run arbitrary code if they sent a message in the right format to the server. This is one of the worst attacks your system can be susceptible to and if you are interested in the technical details of the problem, here is an overview. The attack surface of Log4Shell is staggering, Amazon, Apple, Google, and the Apache Server are affected; it can almost not get bigger than this. We will see the real fallout of Log4Shell in the next weeks and months as right now servers worldwide are being scanned and prodded for this vulnerability.
-
Vulnerability Advisory: Apache Log Binary (Log4J)
Companies should verify they are not running any exposed Log4j Java code. Here is a list of impacted 3rd party software for your reference. If you find a server at risk, there are three potential ways to fix it as follows.
-
Using discovery to find devices with log4j installed
Looking for vendors/software on known lists like https://github.com/YfryTchsGD/Log4jAttackSurface
-
Schutz vor Log4j-Lücke – was hilft jetzt und was eher nicht
Blender ist nicht betroffen, #42
-
3 billion devices run log4j... including blender
It does and was also affected by log4j.
-
PSA: if you're hosting any public facing services make sure they're not vulnerable to the 0-day log4j RCE.
Thanks, sure it isn't complete but it does contain some scary and surprising (at least when first reading, of course the really aren't) things like: https://github.com/YfryTchsGD/Log4jAttackSurface/blob/master/pages/UniFi.md
- My feeds are full with the Log4j vulnerability, but let’s think about it for a moment…
-
Security Vulnerability in Minecraft: Java Edition
Apparently there's proof Steam along with many others are vulnerable.
What are some alternatives?
jsoniter - jsoniter (json-iterator) is fast and flexible JSON parser available in Java and Go
nimbus-eth2 - Nim implementation of the Ethereum Beacon Chain
log4shell-ldap - A tool for checking log4shell vulnerability mitigations
teku - Open-source Ethereum consensus client written in Java
log4shell-tools - Tool that runs a test to check whether one of your applications is affected by the recent vulnerabilities in log4j: CVE-2021-44228 and CVE-2021-45046
apache-log4j-rce-poc
Apache Log4j 2 - Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.
GDLauncher - GDLauncher is a simple, yet powerful Minecraft custom launcher with a strong focus on the user experience
PHP Serializer - A Java library for serializing objects as PHP serialization format.
Arthas - Alibaba Java Diagnostic Tool Arthas/Alibaba Java诊断利器Arthas
active-scan-plus-plus - ActiveScan++ Burp Suite Plugin