Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
CVE-2020-15368, aka "How to exploit a vulnerable driver"
| Date | Stars |
|---|---|
| 2026-07-24 | 514 |
| 2026-07-25 | 514 |
| 2026-07-28 | 514 |
| 2026-07-30 | 514 |
| 2026-08-06 | 514 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
# How to exploit a vulnerable windows driver Exploit and Proof of Concept (PoC) for [CVE-2020-15368](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15368). Asrock repackaged rweverything driver for their RGB controller configuration tool and signed it. They "protect" it by encrypting their ioctls...lol. We found this CVE by accident last summer, and afaik the driver still isn't patched. The impact is of course arbitrary code execution in kernel, etc. So enjoy this "0day" lol. If you want to argue with me on whether it's a REAL BONA FIDE CVE, please feel free to reach out to me on Twitter, we can have a huge fight on public social media and it will be really exciting for everyone involved! I will even buy a domain for this bug if you are so inclined. it's all about marketing!!!! **Anyways, this bug is pretty shit, so I'm going to use it as a tutorial on how to pwn your typical vuln driver. So this post is aimed towards beginners.** You'll learn how to exploit a vulnerable driver. There are tons of other shitty drivers out there like this. The world is your oyster. Have fun **DISCLAIMER: This publication is provided for educational purposes only. It is the reader's responsibility to obey all applicable local, state and federal laws. The author(s) of this publication assume no liability and are not responsible for any misuse or damage caused by the software contained in this publication.** ## Backstory Stuck in quarantine, my roomates ([Pear0](https://github.com/Pear0), [Codetector](https://github.com/codetector1374)) and I were fooling around on Pear0's new Asrock motherboard. The bright red LEDs were extremely annoying and it was not possible to configure them on Linux. Thus our plan was to reverse the Windows driver that controlled it and replicate the I/O operations on Linux. Long story short, it didn't take long until we realized the driver is literally just a generic driver granting arbitrary read/write access to anything. This includes control registers like CR3, CR4, physical memory, etc. Drivers like this are [intended for use as a debugging tool](http://rweverything.com/) and the vendor's website clearly states so.  We thought this was extremely funny. It's quite exciting the first time you make a computer triple fault and hard reboot from userspace. (Maybe less exciting the 20th time.) Anyways, we reported the bug then forgot about it for a year. ## Setup As a kernel noob, I was wondering how to actually load and interact with the driver. Turns out it is extremely easy. You can just create a service for the driver in [Process Hacker](https://processhacker.sourceforge.io/) (obviously, requires admin to load drivers). Then you can just right click and start it. Yes it's really that simple.  We can view our Device object in [WinObjEx64](https://github.com/hfiref0x/WinObjEx64).  We can even play with the device in [FileTest](http://www.zezula.net/en/fstools/filetest.html).   All of these 3 tools are amazing, especially PH and FileTest. They are like a Swiss army knife and they ought to be in every Windows reverser's toolbox. For example, from my understanding [Jonas L](https://twitter.com/jonasLyk) has found countless Windows LPE vulnerabilities just dicking around in FileTest. So Windows really has some great tools for fucking around. I wish there was this shit on Linux. ## "Security" bypass Rweverything has an ioctl that takes an ioctl as a parameter, which controls what operation to perform (read mem, write mem, read msr, etc.), and a union of some operation-specific parameters like src address, dst addr, etc. When we compare the two drivers' code:  🤔🤔🤔🤔🤔🤔🤔🤔🤔 Nevertheless, the driver makes a shoddy attempt at security by obscurity by requiring t
Excerpt of 13,821 characters
Read on GitHub
9
1
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:5ed768d2254b2b08, topic:tutorial, readme:tutorial, readme:course