Coordinated CVE writeups
Root cause, impact, affected versions, remediation, and fix verification—published only after disclosure allows it.
Field notes
Writing built to outlast the platform.
Security research, lab walkthroughs, tooling notes, and personal field notes from Abdullah Kareem. The original Medium archive is unavailable, so selected work is being recovered, technically reviewed, and republished here with its original dates and context preserved.
Recover sourceVerify original dateReview technical claimsRepublish on CyberKareem
Selected inventory · 01
Recovered titles, honest status.
These representative records preserve known titles and original dates. Full article text will appear only after recovery and review.
- 01
Advanced lab walkthrough
HackTheBox ‘Atlas’ Walkthrough
A hard Windows lab covering source analysis, an XML and Java deserialization path, egress constraints, and credential recovery.
Recovery queuedOriginal platform unavailable - 02
Media sanitization tooling
Building a Boot-and-Nuke USB Tool: Secure Automated Purge
An automation and media-sanitization build note whose standards language and verification claims require revision before republication.
Technical review requiredOriginal platform unavailable - 03
Personal field note
Stoicism in Everyday Life
A reflection on resilience, anxiety, daily practice, and the practical use of ancient and modern ideas.
Recovery queuedOriginal platform unavailable - 04
Windows security tooling
Introducing the BitLocker Cryptographic Erase Utility
A BitLocker and TPM cryptographic-erasure utility note queued for a current technical and standards review.
Technical review requiredOriginal platform unavailable - 05
Lab walkthrough
HackTheBox ‘Tabby’ Walkthrough
A Linux attack path through local file inclusion, Tomcat deployment, credential reuse, and LXD privilege escalation.
Recovery queuedOriginal platform unavailable - 06
Lab walkthrough
HackTheBox ‘Access’ Walkthrough
A Windows lab involving anonymous FTP, stored credentials, Telnet access, and a local privilege path.
Recovery queuedOriginal platform unavailable
Coming home · 02
What the owned archive will publish.
The archive is organized by evidence and reader value, not by the order a platform happened to publish it.
Vulnerability patterns
Reusable lessons from authorization failures, trust-boundary mistakes, parser behavior, and incomplete fixes.
Labs and methodology
Walkthroughs that explain the decision path, failed hypotheses, and operational constraints—not only the final exploit chain.
Tools under evidence
Build notes that state assumptions, tested behavior, limitations, and standards context without overclaiming assurance.
Publishing standard · 03
Disclosure-safe. Version-aware. Correctable.
- 01
Primary evidence and affected-version context accompany security claims.
- 02
Embargoed, client-sensitive, and unfiled material remains private.
- 03
Original dates are preserved while technical revisions are clearly marked.
- 04
Corrections and changed registry states are dated instead of silently rewritten.
Published evidence first
Read the primary records while the archive is rebuilt.
The Research Ledger already links every published Finder credit to its primary public source. Future CVE writeups will connect back to those records.
Open research ledger