/explore
|
You are here 
|
zhero-web-sec.github.io | ||
| | | | |
tom.vg
[AI summary] This article explains cross-site and browser-based timing attacks that allow attackers to infer sensitive information from response sizes using side-channel leaks in web browsers. |
|
| | | | | ||
| | | | |
labanskoller.se
During 2021 I had access to a facility equipped with an alarm system from Securitas Direct. I had access as a regular user to Securitas Direct's My Pages at mypages-pro.securitas-direct.com, which is used to administer some aspects of one's security alarm installation. That web application suffered a CWE-384 Session Fixation vulnerability which can be used by an attacker in a so-called Man-In-The-Middle (MiTM) position. Home page of Securitas Direct My Pages In summary, if an attacker is on the same netw... |
|
| | | | | ||
| | | | |
positive.security
Using a still unpatched vulnerability in the PHP library dompdf (used for rendering PDFs from HTML), we achieved RCE on a web server with merely a reflected XSS vulnerability as entry point. |
|
| | | | | ||
| | | | |
tricht.eu
I like using Caddy as a HTTPS server with automatic SSL certificates using Let's Encrypt. With a few configuration lines you can get up and running in no time. Recently I switched VPS providers and ended up having to migrate Caddy from v1 to v2. The documentation for Caddy is wonderful and chockful with emojis. The getting started tutorial starts by telling you how a Caddyfile looks like in v2, where my confusion started. As I mostly need reverse proxies, the very first example there looks like this: |
|
| | | |||
