Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/mein-0/knockgiga
Privilege EscalationVulnerability AnalysisExploitationReverse EngineeringHardware SecurityBinary Exploitation
GitHubmein-0/knockgiga

KnockGiga

Proof-of-concept local privilege escalation exploiting Gigabyte gdrv3.sys IOCTLs to write the SYSTEM token into a user process via an unchecked physical memory read.

View Repository
136881 month agoNot yet reviewed
Share

hi hackers.

gdrv3.sys is the signed kernel driver that ships with Gigabyte App Center and EasyTune. It creates \.\GIOV3 with no security descriptor, so any local user can open it no admin, no UAC. Two of its IOCTLs are the whole story.

The first one (0xC3502019) says it reads physical memory. You give it a physical address, a length and an output pointer, and it copies the bytes there. The output pointer is the problem: the driver never checks that it is user space. No ProbeForWrite, no boundary check, nothing. So a "read" is really a write-what-where, you just pick where the answer lands. Read the SYSTEM process token out of physical memory, then point the output straight at your own EPROCESS token field. The driver writes the SYSTEM token into your process for you.

That is the entire exploit. No memory corruption, no shellcode in kernel mode. SMEP, SMAP, KVAS, CET and CFG never enter the picture because nothing runs at CPL0 that is not supposed to. It is data only, and it worked every run. The second IOCTL pair (0xC3502584 read, 0xC3502580 write) is the classic one. Arbitrary MSR, no index whitelist. Reading IA32_LSTAR already breaks KASLR on its own, and writing it hijacks the syscall entry. It needs SMEP/SMAP work so I kept it as a secondary path, but even alone it is bad.

Build and run from a normal user account:

gcc -O2 -o poc.exe poc.c -lpsapi
poc.exe

Tested on Windows 10 x64 22H2 (build 19045). The driver ships with Gigabyte App Center, so on a lot of Gigabyte boards it is already loaded.

I reported it to Gigabyte in June 2026 and they fixed it. The newer builds put an SDDL on the device that locks it down to admins, and add a whitelist on the MSR write. The current gdrv3 is no longer exploitable this way.

SYSTEM shell

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    871
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    548
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    383
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    361
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    305
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    280

Explore all tools

Browse our collection of tools

View all tools →