Skip to content
KitploitKITPLOIT
工具漏洞利用博客
Log in
提交
工具漏洞利用博客
提交

黑客、渗透测试和网络安全工具,武装您的安全武器库!

Kitploit 是一个黑客、网络安全和渗透测试工具的目录。发现最新的项目更新,查找漏洞、分析系统、自动化测试并加强你的安全。

··订阅源·联系·隐私·© 2026 Kitploit

工具目录

分类

查看所有分类
Loading categories
security-writeups — CTF writeups and teaching scripts for web security, bug bounty techniques, and network forensics, with blank-value versions for active practice. | Kitploit
工具/GitHubGitHub/alzeaty1/security-writeups
Network ForensicsWeb Application ExploitationWeb SecurityCTFPenetration TestingLearning & EducationLearning Paths & CoursesLabs & Practice
GitHubalzeaty1/security-writeups

security-writeups

CTF writeups and teaching scripts for web security, bug bounty techniques, and network forensics, with blank-value versions for active practice.

查看仓库
304天前尚未审核

最受欢迎

查看全部 →

发现我们社区最常用的工具。

探索所有工具

浏览我们的工具集合

查看所有工具 →
分享
内容在请求的语言中不可用。显示英文版本。

Security Writeups

Lab write-ups from self-directed work, mostly TryHackMe, plus a PortSwigger SQLi practical. The reasoning lives on the site — the full methodology, the payloads, the parts where I went wrong first — and this repo is the index and the scripts.

Nine rooms, and they are not nine unrelated things. What they share is that almost none of them needed a novel exploit. What they have in common:

  • Misconfiguration did most of the work. A .git directory on a web root. A password in a daemon's command-line arguments. A Cognito guest role with dynamodb:Scan on everything. A loopback-bound inspector that only looked safe.
  • The boring ones needed patience more than tools. Boolean and time-based blind SQLi are one character per request. CryptoCabana was not a crypto problem at all — the secret was never the value, it was the version history.
  • The chaining is the content. None of these rooms are solved in one step, and the write-ups spend most of their length on how step two was even possible after step one.

Coverage across the set: web exploitation (SQLi, XSS, SSTI, deserialization), cloud credential abuse on both AWS and Azure, network forensics, and OSINT that never touched a server at all.

The teaching-script convention

Some folders ship a Python script. In every case it is a teaching version: the key values, targets, and query templates are left blank or as obvious placeholders on purpose.

The reasoning is simple. A script that works out of the box against a live instance teaches you the invocation, not the mechanism, and it ages badly. If you open beachbar_rce.py and it runs, you have learned nothing about why the payload works. Fill in the blanks from your own traffic, or you have skipped the part that mattered.

Rooms

RoomWhat it actually wasDifficulty
Beach BarPyYAML deserialization RCE, then a root daemon that leaked its own password via /procEasy
ComplimentaryAn unauthenticated Cognito role allowed to Scan every tableEasy
CryptoCabanaAzure SAS token to service principal to Key Vault — and a rotated secret's version historyMedium
Do Not Disturb{"$ne": ""} login bypass, EJS template injection, loopback Node inspector, two escalationsMedium
Overheard at BreakfastAn email as an MD5 input to Gravatar, and no server to attack at allEasy
Packed LightA keylogger exfiltrating keystrokes one XOR'd cookie at a timeEasy
Room 404The repository served to anyone who asked for itEasy
SQL InjectionFour oracles, one endpointEasy
XSS IntroductionOne encoding bug in four shapes, ending with blindEasy

Elsewhere

  • Write-ups: alzeaty1.github.io
  • ctf-crypto-analysis-tool — modular crypto analysis CLI (XOR, entropy, ECB detection)
  • TryHackMe: tryhackme.com/p/ALZeaty
  • LinkedIn: Ahmed Abdalrhman

About

Junior penetration tester. Self-directed lab work across web application security, network analysis, and cloud credential abuse (AWS and Azure). Certified through NTI/NTRA (Cybersecurity Academy) and TryHackMe Advent of Cyber 2025 (24 challenges).

License

MIT

下载工具