41554 blogs · 4,417,066 posts Claim your blog

Record · corpus.blog/posts/01a087ab-1382-710b-9c09-a58531af332a

1000 third parties could have stolen RIPE NCC session tokens - by design

mxsasha.eu · published 6 May 2026

A record is what was published and who pointed at it. The text of the post is not held here: read it at the source, or at its Wayback capture.

Read the post at mxsasha.eu Wayback capture

0blogs citing

First cited: —
Most recent: —
Rank this month: not ranked
Links from this post: 13
Words captured: 1,759

Cited by

No blog we hold has cited this post yet.

Links from this post

Link

Host

Taking down a European network with a TLS certificate: my RIPE NCC RPKI exploit chain Read at the source ↗

https://datatracker.ietf.org/doc/html/rfc8659

datatracker.ietf.org

Inside a 14-month responsible disclosure with the RIPE NCC Read at the source ↗

https://www.ripe.net/about-us/support/contact/responsible-disclosure-policy/

ripe.net

https://crt.sh/?q=mtg.ripe.net

crt.sh

https://crt.sh/?q=anchors.atlas.ripe.net

crt.sh

https://letsencrypt.org/docs/caa/

letsencrypt.org

https://cheatsheetseries.owasp.org/cheatsheets/Subdomain_Takeover_Prevention_Cheat_Sheet.html

cheatsheetseries.owasp.org

https://labs.ripe.net/author/eleonora-petridou/what-we-learned-from-a-multi-service-vulnerability-disclosure/

labs.ripe.net

RIPE NCC session fixation: poaching logins with an Atlas probe Read at the source ↗

Root from the parking lot: OpenWrt XSS through SSID scanning (CVE-2026-32721) Read at the source ↗

Taking down a European network with a TLS certificate: my RIPE NCC RPKI exploit chain Read at the source ↗

Rooting Home Assistant through MeshCore: XSS attacks with a LoRa node name Read at the source ↗