exploits | printfify | |
---|---|---|
15 | 1 | |
2,486 | 0 | |
- | - | |
0.0 | 5.2 | |
over 1 year ago | 3 months ago | |
C | Python | |
BSD 2-clause "Simplified" License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
exploits
Posts with mentions or reviews of exploits.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-04-12.
-
POV: you just wrote print("hello world") for the first time
If you still feel that's not "proper hacking", consider exploits that target the browser engine directly - those exploits are typically written in JavaScript. Here's an 0day from this week that gets code exec inside Chrome, written in JavaScript.
- Exploit for pwn2own Chrome zeroday released by third party researcher
- chrome 0day
-
Chrome zero-day released on GitHub (fixed on V8 but still works on latest)
Repo leads to this one from a few days ago, looks similar, maybe can help?
https://github.com/r4j0x00/exploits/tree/7ba55e5ab034d058774...
-
ELECTRIC CHROME: Exploiting CVE-2020-6418 on Tesla Model 3
Coincidentally, a Chromium 0day was released this morning that will very likely work out of the box on the latest Tesla software to get arbitrary code execution within the sandbox (tonight's little project, most likely).
- Chrome 0-Day
- Exploit of CVE-2020-16040 Google Chrome <= 87.0.4280.88 vulnerability
printfify
Posts with mentions or reviews of printfify.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-04-12.
-
Chrome zero-day released on GitHub (fixed on V8 but still works on latest)
I guess the newline that echo without -n would add is harmless.
OTOH -e, depending on your shell, is either necessary (e.g. bash), or unnecessary but harmless (e.g. zsh) or insufficient (e.g. dash). If you want to print stuff portably, you need to use printf(1).
(Shameless plug: you can use <https://github.com/jwilk/printfify> to generate printf commands for binary files.)
In this case, base64 encoding is much more efficient:
/EiD5PDowAAAAEFRQVBSUVZIMdJlSItSYEiLUhhIi1IgSItyUEgPt0pKTTHJSDHArDxhfAIs
What are some alternatives?
When comparing exploits and printfify you can also consider the following projects:
WHATWG HTML Standard - HTML Standard
wrangler-legacy - 🤠Home to Wrangler v1 (deprecated)
Metasploit - Metasploit Framework
disable-webassembly - Browser hacks to disable WebAssembly (WASM)
ios-RCE-Vulnerability - Latest ios RCE Vulnerability disclosed by Google Security Researcher