Security — Pingiskokhttps://rmrf.tips/en/tags/security/Bugs, vulnerabilities and security research. Web2, Web3, Bug BountyHugoenrmrf_0rmrf_0© 2026 PingiskokSat, 24 Oct 2026 00:00:00 +0300Web servers, Part 2: what happens to a request inside nginx and Apachehttps://rmrf.tips/en/series/web-servers/web-servers-anatomy/Sat, 24 Oct 2026 00:00:00 +0300https://rmrf.tips/en/series/web-servers/web-servers-anatomy/How nginx and Apache select a site, process the path and forward a request to the application, and what you can test from the outside.Web servers, Part 1: where HTTP actually breakshttps://rmrf.tips/en/series/web-servers/web-servers-why-broken/Sat, 24 Oct 2026 00:00:00 +0300https://rmrf.tips/en/series/web-servers/web-servers-why-broken/How proxies and applications interpret the same request differently: body boundaries, paths, forwarding headers and cache keys.JWT, Part 20: Post-Quantum JWT and the Future of Tokenshttps://rmrf.tips/en/series/jwt/jwt-post-quantum/Fri, 03 Apr 2026 20:20:00 +0300https://rmrf.tips/en/series/jwt/jwt-post-quantum/The series finale. Shor's algorithm breaks every asymmetric JWT algorithm. ML-DSA signatures at 2.4 KB don't fit in a cookie. SD-JWT for selective disclosure. Harvest Now, Decrypt Later — why migrating JWE to post-quantum cryptography is needed now.JWT, Part 19: RFC 8725 - the checklist nobody readshttps://rmrf.tips/en/series/jwt/jwt-rfc8725/Fri, 03 Apr 2026 20:19:00 +0300https://rmrf.tips/en/series/jwt/jwt-rfc8725/RFC 8725 — fifteen JWT security rules from the standard's authors. For each — which attack from the series it prevents, which CVEs exist, and why ~65% of applications don't check aud. Plus three new rules from the 2026 bis update.JWT, Part 18: What Instead of JWT - PASETO, Macaroons, Opaque Tokens, and Server-Side Sessionshttps://rmrf.tips/en/series/jwt/jwt-alternatives/Fri, 03 Apr 2026 20:18:00 +0300https://rmrf.tips/en/series/jwt/jwt-alternatives/JWT isn't perfect — 70+ CVEs over ten years. We break down the alternatives: PASETO without the alg field, Macaroons with unique attenuation, opaque tokens with instant revocation, Google/Netflix server-side sessions. For each — what to break on a pentest.JWT, Part 17: Hardcoded Secrets - When the Key Is Sitting in the Source Codehttps://rmrf.tips/en/series/jwt/jwt-hardcoded-secrets/Fri, 03 Apr 2026 20:17:00 +0300https://rmrf.tips/en/series/jwt/jwt-hardcoded-secrets/CVE-2025-20188 (CVSS 10.0): eight characters 'notfound' in a Cisco IOS XE Lua script = root RCE on enterprise equipment. 17% of JWT CVEs in 2024-2026 are hardcoded secrets. Where to look: git history, Docker layers, JS bundles, source maps, firmware.JWT, Part 14: Advanced Crypto Attacks - Lattices, Side-Channels, and Fault Injectionhttps://rmrf.tips/en/series/jwt/jwt-advanced-crypto/Sat, 28 Mar 2026 10:14:00 +0300https://rmrf.tips/en/series/jwt/jwt-advanced-crypto/Leak three bits of the nonce from each ECDSA signature — and after 100 signatures you have the full private key. Minerva, TPM-FAIL, EUCLEAK: real attacks on real devices, and what's actually applicable on a web pentest right now.JWT, Part 13: XSS + JWT = Full Account Takeoverhttps://rmrf.tips/en/series/jwt/jwt-xss/Sat, 28 Mar 2026 10:13:00 +0300https://rmrf.tips/en/series/jwt/jwt-xss/Found a Reflected XSS? If the app stores JWTs in localStorage, that's not just alert(1) — it's a full takeover of every account. We cover theft from every storage type, CSP bypass via WebRTC and CSS injection, and the only defenses that actually work.JWT, Part 12: JWT in OAuth 2.0 and OIDC - where it breaks in the real worldhttps://rmrf.tips/en/series/jwt/jwt-oauth-oidc/Sat, 28 Mar 2026 10:12:00 +0300https://rmrf.tips/en/series/jwt/jwt-oauth-oidc/At the seams between OAuth and OIDC components, attacks emerge that don't exist in isolation: token confusion, cross-service relay, ALBeast in AWS, and DPoP bypass — with real CVEs and step-by-step pentest checks.JWT, Part 11: JWT Libraries - a Leakiness Rankinghttps://rmrf.tips/en/series/jwt/jwt-libraries/Sat, 28 Mar 2026 10:11:00 +0300https://rmrf.tips/en/series/jwt/jwt-libraries/Which library is running on the backend determines which attacks will actually land: a ranked breakdown of the most vulnerable JWT libraries, a tier classification from recommended to dangerous, and passive fingerprinting techniques that identify the stack from the token header alone.JWT, Part 10: JWE - encrypted tokens and how to break themhttps://rmrf.tips/en/series/jwt/jwt-jwe/Sat, 28 Mar 2026 10:10:00 +0300https://rmrf.tips/en/series/jwt/jwt-jwe/JWE is the encrypted side of JWT that almost nobody talks about: five parts, two encryption layers, and a full zoo of attacks - Invalid Curve on ECDH-ES, Bleichenbacher on RSA1_5, Padding Oracle on AES-CBC, PBES2 DoS with one request, and the forbidden attack on AES-GCM.JWT, Part 9: JWT Cryptography for Hackershttps://rmrf.tips/en/series/jwt/jwt-crypto/Sat, 28 Mar 2026 10:09:00 +0300https://rmrf.tips/en/series/jwt/jwt-crypto/The math behind HMAC, RSA, and ECDSA from an attacker's perspective: why Sony lost the PlayStation 3 to a single repeated number, and how leaking just a few nonce bits is enough to recover a private key.JWT, Part 8: Psychic Signatures - zero signature on Javahttps://rmrf.tips/en/series/jwt/jwt-psychic-signatures/Sat, 21 Mar 2026 18:07:00 +0300https://rmrf.tips/en/series/jwt/jwt-psychic-signatures/A signature of all zeros passes ECDSA verification on Java 15-18. For any message, with any key. Five lines of Python - and you're admin.JWT, Part 7: Brute-forcing JWT secrets on GPUhttps://rmrf.tips/en/series/jwt/jwt-bruteforce/Sat, 21 Mar 2026 18:06:00 +0300https://rmrf.tips/en/series/jwt/jwt-bruteforce/JWT contains everything for an offline attack: message and signature. Hashcat on GPU runs through 150 million HS256 per second. The secret 'secret' is cracked in 2 seconds.JWT, Part 6: jku/x5u/jwk/x5c - the entire JWT header is an attack surfacehttps://rmrf.tips/en/series/jwt/jwt-header-injection/Sat, 21 Mar 2026 18:05:00 +0300https://rmrf.tips/en/series/jwt/jwt-header-injection/The JWT header can contain a URL, and the server will go to that URL to download the key for signature verification. This isn't a bug - it's RFC 7515.JWT, Part 5: kid injection - SQL Injection via token headerhttps://rmrf.tips/en/series/jwt/jwt-kid-injection/Sat, 21 Mar 2026 18:04:00 +0300https://rmrf.tips/en/series/jwt/jwt-kid-injection/The RFC doesn't define the structure of kid. Developers use it as a file path, SQL parameter, or command argument. Each option is a separate class of vulnerability.JWT, Part 4: Algorithm Confusion - public key as passwordhttps://rmrf.tips/en/series/jwt/jwt-algorithm-confusion/Sat, 21 Mar 2026 18:03:00 +0300https://rmrf.tips/en/series/jwt/jwt-algorithm-confusion/Take the server's public key from open access, sign a token with it - and the server accepts it. The signature exists, the signature is correct, but the token is forged.JWT, Part 3: alg:none - one line and you're adminhttps://rmrf.tips/en/series/jwt/jwt-alg-none/Sat, 21 Mar 2026 18:02:00 +0300https://rmrf.tips/en/series/jwt/jwt-alg-none/The RFC requires every JWT library to support the none algorithm. Change one field in the header - and the server skips signature verification.JWT, Part 2: JWT Anatomy - dissecting the token byte by bytehttps://rmrf.tips/en/series/jwt/jwt-anatomy/Fri, 20 Mar 2026 18:01:00 +0300https://rmrf.tips/en/series/jwt/jwt-anatomy/Taking a real token and dissecting it like a pathologist: header, payload, signature, Base64url, claims, edge cases.JWT, Part 1: Why JWT is the most broken standard on the webhttps://rmrf.tips/en/series/jwt/jwt-why-broken/Fri, 20 Mar 2026 18:00:00 +0300https://rmrf.tips/en/series/jwt/jwt-why-broken/70+ CVEs over ten years. A bug from 2015 still fires in 2026. Let's figure out why JWT stubbornly remains broken.