If all you need is a simple way to serve static files that minimizes resource consumption and is reliably secure, what is the state of the art these days? In the past I would probably reach for Nginx, but I wonder if a more focused/less configurable tool would be preferable from a security standpoint.
Hunting for Nginx alias traversals in the wild
11–20 of 165 posts
Re: Hunting for Nginx alias traversals in the wild
#12At risk of asking a dumb question, is there any good reason that you’d want nginx to allow traversing into “..” from a URL path? It just seems like problems waiting to happen. Edit: Actually, I’m a bit lost as to what’s happening in the original vuln. http://localhost/foo../secretfile.txt gets interpreted as /var/www/foo/../secretfile.txt or whatever… but why wouldn’t a server without the vulnerability interpret http…
Re: Hunting for Nginx alias traversals in the wild
#13Note that this leaks the vault with secrets encrypted - a leak of the cyphertext. > This vulnerability has been disclosed to Bitwarden and has since then been fixed. Bitwarden issued a US$6000 bounty, which is the highest bounty they issued on their HackerOne program. That's a ridiculously low payout.
Re: Hunting for Nginx alias traversals in the wild
#14Earlier quoted context omitted.
I don’t know enough about bounty programs to comment on the amount, but my understanding is that leaking encrypted secrets isn’t really dangerous?
It's generally a question of time. If you want to play the long game and collect a lot of encrypted data now, you can simply wait until it is possible to trivially decrypt, and/or start cracking now and let the years work on it. Most encryption decisions are framed as a tradeoff of the time and resources it would currently take to brute-force your way through it, and how many years before a simple attack becomes feas…
Re: Hunting for Nginx alias traversals in the wild
#15At risk of asking a dumb question, is there any good reason that you’d want nginx to allow traversing into “..” from a URL path? It just seems like problems waiting to happen. Edit: Actually, I’m a bit lost as to what’s happening in the original vuln. http://localhost/foo../secretfile.txt gets interpreted as /var/www/foo/../secretfile.txt or whatever… but why wouldn’t a server without the vulnerability interpret http…
https://book.hacktricks.xyz/network-services-pentesting/pent...
Re: Hunting for Nginx alias traversals in the wild
#16Re: Hunting for Nginx alias traversals in the wild
#17Note that this leaks the vault with secrets encrypted - a leak of the cyphertext. > This vulnerability has been disclosed to Bitwarden and has since then been fixed. Bitwarden issued a US$6000 bounty, which is the highest bounty they issued on their HackerOne program. That's a ridiculously low payout.
Small companies can't just give out $50k bounties, even if it would be deserved.
https://siliconangle.com/2022/09/06/bitwarden-reels-100m-ope...
Re: Hunting for Nginx alias traversals in the wild
#18Re: Hunting for Nginx alias traversals in the wild
#19As an aside, I didn't know Github code search accepted regex.