4 ms·
I was unfamiliar with request smuggling; here's an explainer: https://portswigger.net/web-security/request-smuggling https://portswigger.net/web-security/reques
by wpietri 7y ago
I was unfamiliar with request smuggling; here's an explainer: https://portswigger.net/web-security/request-smuggling https://portswigger.net/web-security/request-smuggling
The first in-band signalling attack I came across was the blue box [1], invented in the late 1960s. It still occasionally worked in the 1980s on older phone systems. It amazes me that we're still creating new systems vulnerable to in-band attacks.
[1] https://en.wikipedia.org/wiki/Blue_box https://en.wikipedia.org/wiki/Blue_box
- sixstringtheory 7y agoWow, I was fascinated by phreaking when I was younger and first getting into programming. Been working on mac/iOS for years and never knew that the guys responsible for the most enjoyable part of my career, the Steves, built and sold a blue box!
- at-fates-hands 7y agoOf all the stories I heard, Woz was way more interested in using them. When Jobs found it out it was illegal, he dropped selling them and distanced himself from the other phreakers he was hanging out with, too afraid of the legal ramifications of getting caught with this equipment. Most of the books I've read basically paint Jobs as a goody-two-shoes type who cringed at the illegality of phreaking - while saying he probably was thinking ahead, knowing he already wanted to start his own company and didn't want stuff like this to come back and haunt him. It was an interesting dichotomy to me.
- abhishekjha 7y agoIs it what Steve Jobs and his friend used to hijack telephone lines and call the pope, free of cost?
- acruns 7y agoYes. https://www.inc.com/glenn-leibowitz/in-a-rare-23-year-old-interview-steve-jobs-said-this-1-pivotal-experience-inspired-him-to-start-apple-computer.html https://www.inc.com/glenn-leibowitz/in-a-rare-23-year-old-in...
- AnIdiotOnTheNet 7y agoOf all the places on the internet to hear Steve Wozniak referred to simply as Steve Jobs's friend...
- abhishekjha 7y agoSorry, I didn't realise that other friend in this incient was Steve Wozniak specifically. I saw his interview after his return to Apple.
- JangoSteve 7y agoCan someone explain the redirect/cookie-stealing part of this? I read through the post explaining request smuggling, and then re-read their exploit description, and the request smuggling part all makes sense. However, I don't fully understand the significance of the 301 in relation to the browser sending the attacker's server the cookie with the request. If the back-end server is already proxying whatever request it receives from the front-end proxy server, why was it necessary to first get it to redirect an HTTP 1.1 header to an https request? The only thing I could think of was that maybe it has something to do with getting the unencrypted cookie, but according to their description, the forwarded request with the cookie doesn't happen until after the redirect to https anyway. I know I'm missing something obvious here.
- tptacek 7y agoWhat's subtle is that the middlebox is being tricked into parsing the body of an HTTP request as the envelope, or vice versa. The requests hitting the backend are being scrambled. The browser is doing what it can to ensure cookies only go to the right domain, but the servers are chopping those careful requests up and sending them to random places.
- jorams 7y ago> the servers are chopping those careful requests up and sending them to random places. I understand that the backend is parsing different requests than the frontend, but I don't see how the cookies ever get sent to the attacker's domain. I understand three requests as moving like this: 1. attacker -> frontend -> backend (partially) -> frontend -> attacker 2. victim -> frontend -> backend (including a bit of 1) -> frontend -> victim 3. (after 301) victim -> malicious server The second request results in a 301, causing the victim's client to make a new request to the target of the 301. This new request does not include cookies, because it is to a different domain. What am I misunderstanding? When do the cookies get sent to the malicious server?
- tptacek 7y agoAlongside a legitimate request with cookies, there is queued an evil request that uses mismatched Content-Length and chunked encoding headers to graft the body of the evil request to the envelope of the legitimate request. The evil body becomes the envelope for the entire legitimate request, and the evil envelope generates the redirect. Skip down to the "Explanation of malicious request" section.
- lonelappde 7y agoHow can you avoid in-band attacks? I'm not going to send a postcard to a webserver with metadata about every HTTP request.
- wpietri 7y agoThe phone system switched call routing from in-band signalling (that is, tones you could hear on the wire) to out-of-band signalling (where control information went over separate channels to content). Another approach is reliable encapsulation. Ethernet and TCP/IP, for example, are technically all in one channel. But packet content won't be mistaken for protocol information. You could also look at things like SSH and how it has multiple channels: https://tools.ietf.org/html/rfc4254 https://tools.ietf.org/html/rfc4254 I'm sure there are other approaches, too, and I hope people will mention them.