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/zbyszkok/cve-2025-49844-redishell-ai-made-revshell
Vulnerability AnalysisExploitationCTFPapers & ResearchLearning & EducationBinary Exploitation
GitHubzbyszkok/cve-2025-49844-redishell-ai-made-revshell

CVE-2025-49844-RediShell-AI-made-Revshell

Untested completition of the Redishell PoC made by AI

View Repository
391 year agoNot yet reviewed

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.

    962
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    558
  • 3

    redforge

    cybersecurity91/redforge

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

    348
  • 4

    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.

    344
  • 5

    ARTEX

    baarai/artex

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

    324
  • 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.

    297

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2025-49844 RediShell

AI-made Revshell PoC

Untested completition of the Redishell PoC made by AI.

Original PoC:
https://github.com/raminfp/redis_exploit/blob/main/exploit_poc.py

Korean Piece:
https://github.com/dwisiswant0/CVE-2025-49844/blob/master/CVE-2025-49844.lua

Progress ?

We later went ahead and plugged in GDB - we managed to get the Base address and find out a few more things, but most of it all, it appears this isn't a simple Heap vuln. No matter what we tried, it was impossible to get code execution. Crashing? Yes. Commands? No.

We're no longer firm in reversing, so we can't be sure, but from all we found over hours with the help of some of the strongest AI models, it's not possible to get code execution through this vuln (or it's one out of a thousand attempts but that's just pure guesswork).

Through numerous attempts, we always landed somewhere here at best:

Script attempted to access nonexistent global variable 'print' script: 67dfac1cecac4f99df897c7a0713f1d6fcef69a4, on @user_script:21.

Curious to see the real PoC with code execution.

READ PROPERLY PLEASE: We said, FROM ALL WE KNOW / HAVE SEEN YET. That's not an absolute statement, there may be a trick or treat we haven't considered, there's way better BinExers out there.

Other attempts

Note that Redis Server remained stable - we pulled it out of docker for testing. You can trigger the crash by firing the exploit a couple thousand times and we haven't yet tried to combine this bruteforce method with attempts of code execution, it may be the solution.

Original PoC

As you see, the original PoC seems to struggle from the same issues, it claims to be "simplified" while it's not entirely clear, what the result is supposed to be.

Korean Puzzle Piece

Nothin yet...

$ while redis-cli -h localhost -p 6380 --eval korean.lua; do printf '.'; done

The saga continues...

Mysteriously, in Redis patch notes, a completely different CVE is listed - also supposedly a Binary Exploit, but a much simpler one, a stack-based Buffer Overflow with supposed RCE:

CVE-2025-62507 - Bug in XACKDEL may lead to stack overflow and potential RCE

https://github.com/redis/redis/compare/8.2.2...8.2

We found even less information on this. It's already challenging to find a non-backported version without self-compile but maybe that's the route we'll have to take then.

All these POTENTIALS - I got potential. Now I got 2 potentials.

Boing - Indeed a crash, sir!

62507 is the way to go... don't have RCE yet, but it looks easy and promissing...

Final Words

So was CVE-2025-49844 just a ruse? The Korean Puzzle still hasnt produced a crash - but it produces completely different output against our self-compiled 8.2.2. Having to admit, even I tapped into thinking "yeah, crash, more than plausible, probably easy..." and just assumed, the crash part of CVE-2025-49844 would be working. But it never did. Sorry for saying it wrong before, but it's cleared now, hopefully. CVE-2025-49844 doesn't crash, CVE-2025-62507 does crash.

.(error) ERR user_script:16: Script attempted to access nonexistent global variable 'newproxy' script: 859491190bfb66357ec83aee16eb0554967c9c38, on @user_script:16.

Looks familiar? IDK What they did there... or if nobody checked other than me? The world has become a rather strange place lately.

Download Tool