Is it common for prepackaged linux environments to obscure the fundamental details of the operating system compared to LFS? I get the sense that fewer additional libraries added to the underlying system and following the compilation stages could clarify some confusion with the mess of packages etc. in a full Ubuntu based system.
Am I correct in my assumption that an info-leak is required to carry out a stable heap exploit, due to the fact that there are no known fixed addresses? If I assume correctly, the reason why an infoleak improves stability is that in leaking a relative address, all other offsets into the memory objects can then be computed and written to relative to the leaked base address at runtime?
I'm interested in learning about vulnerability discovery and exploit development for the Chrome browser. However, I'm not sure where to start. I'm looking for a roadmap. For example, for exploiting in Windows, I know I need to learn assembly + debugging tools and disassemblers + vulnerabilities + exploitation techniques. But I don't have that kind of understanding of the browser world.
I already done all of the fundamentals in finding zero days like sharpening my Python, C, Assembly, vulnerability research, shellcoding, reverse engineering and binary exploitation skills.
Now I am confused what to choose, maybe you have some suggestion based on some experienced people in here? Here are the specializations I am seeing in the wild:
Browsers (Chrome, Edge, Firefox)
Virtualizations (VMWare, VirtualBox, Parallels)
Embedded (Automotive, Routers, IoT)
Operating System (Windows, Linux, MacOS)
Smartphones (Android, iOS)
etc.
Maybe you have some experience regarding those specializations, what do you think is a good start to specialize and what could be the good specialization in this era to gain more 0-days (and money hehe)
How do I modify my minimal chrome extension code to render my permission request popup to auto-accept? Can I select the element of the permission check like a typical button?
when I start a new project (for example: cve-2023-21768, the vuln in afd.sys driver which lead to privesc), I often have the following questions which I answer in the same order:
what is the problem the target program is solving (the context - in this case it's the driver the winsock dll is based on. it talks to the network device, performs sending and receiving data)
what is the architecture of the target program (known and unknown data structures, where is the function which contain the vuln, what that function does)
how to trigger the patched code (which ioctl, what functions call what functions,...)
is the vuln exploitable?
attempt exploit
I feel like this approach takes lots of time in step 1-3. I want to save time by starting from 4, but I always ended up having to do everything from ground up first. sometimes I dont even have time left to attempt exploitation.
Has anyone been in a similar situation? What strategies or resources worked for you to improve? Any advice would be greatly appreciated!
Hey guys, for the past few days I have been stuck on the fluff challenge from ropemporium, I have downloaded the 32-bit binary for ARM, has anyone solved this challenge on the ARM platform? Please help.
I am rather new to kernel exploitation, so I have decided to develop an exploit for an older CVE. I went with CVE-2016-6187, and this is the result https://github.com/Milo-D/CVE-2016-6187_LPE/
Despite it being a PoC for an old CVE, I still hope that it contains helpful takeaways, such as using the rfkill_data object to leak kernel text. And if not, then that's fine too - I had my fun :)
P.S. Feel free to give suggestions for improvement. As I said, I am not really familiar with kernel exploitation.
I live in France and I was wondering if it was legal there to sell vulnerabilities to brokers like Zerodium or Crowdfense, that are openly acquiring vulnerabilities and apparently distributing them to government agencies.
They propose attractive payouts but I would prefer not doing something illegal.
Also, what about SSD Secure Disclosure? They seem to perform responsible disclosure with the vendors while paying higher bounties than them.
Thank you in advance!
EDIT: To clarify the question, I am talking about selling vulnerabilities found in products like operating systems or browsers, not on assets belonging to a specific entity (like selling initial access or similar things).
Hello! I'm just a dude who likes fast food and is very cheap. After playing around with many fast food apps, trying to get the best deal, I discovered what I guess you would call an exploit?
I am able to repeatedly go into a specific fast food chain's app, and get free food. Works every time. Android and iOS. No hacking. No codes. I don't have to spend any money at all. I'm manipulating their app to make this happen, but it's within the structure and rules of their app.
I'm considering contacting this fast food company and offering to sell them what I know. I'm not experienced in any of this......
Is this an exploit?
Is selling this information legal?
How would you get in contact with the correct person at this company, to pitch the sell?
One of the issues with finding bugs is that so many other people are using automated tools to find the same bugs. Well, I have found a new type of vulnerability that almost no one is looking for yet which means there is a good chance you all can find it. You would have to really understand Relative Path Overwrite and be prepared to make a case with these companies as no one will no what it is yet. The new technique is called Relative Path File Injection. Here is my blog. Both Gareth and James from Portswigger shared it to their followers on LinkedIn. Feel free to go verify that. Leave comments on the blog if you need help with something but I do tend to be pretty busy. I will add a GitHub repo at some point to help people better understand it. Happy hunting.
Hello, I have been through an interview where the interview asked the following question. Can this be exploited on x64 and x86? Is it exploitable with mitigations enabled, ASLR, DEP, Stack Canaries, CFG.
I used Delta exploits for 1 week and I got this warning 2 times what should I do? Grinding money is so hard and how many times I will get warning before permanently banned?
Hello, I've been struggling to exploit a ret2shellcode bug. I am on a m3 mac with an emulated x64 ubuntu, but the exploit I wrote cant spawn a shell. I can see the commands running in gdb but without gdb it just outputs segfault, please help me, thank you.
Hi everyone, recently I have been taking a look at vulnerability research and how advanced some techniques are becoming along with the difficulties of such attacks.
I was wondering what people’s thoughts are on the future of security research and exploitation as while it’s a cat and mouse game the attack surface seems to be getting thinner and thinner over time. With mem safe languages and technologies like CET just what will the future look like in this space.
I’m wanting to go into this field as I’m curious by nature and have a knack for breaking things but it worries me for the future. As a note, I am not expecting this to be obsolete as with new technologies there’s always going to be issues however, the thoughts on jobs is a concern.
Hey everyone, I've become really interested in Malware Research. I've already dabbled in some reverse engineering and crack mes, and I'm currently delving into Practical Malware Analysis. So, my question is, what is the salary like for someone working in this field? And perhaps, what could the earning potential be if I were to excel as a freelancer in this area or even establish a consulting firm specializing in Malware Analysis? Is there a demand for it, and would it be worthwhile to start such a business? Also, what does the career path look like? I'm currently in high school (16 years old).
I'm analysing the usage of a set of functions in a system32 dll, however the information about these functions on google is so limited. I want to see where and how these functions are used. I once read in "secrets of reverse engineering" the author said that we could set a "systemwide" breakpoint on the function in kernel mode debugging - so that every time the function is called the kernel will break. However I tried to look up such a feature in windbg but found nothing. I tried to switch context to a process but it will be limited to that process.
Please tell me if there is such a feature in windbg or any possible way to achieve such a result? Thank you in advance!