News for hackers. Stuff that matters.
Re:We abused Slack's TURN servers to gain access to internal... by russellbeattie on Tuesday April 07, 2020 @02:53PM (#22806254)
So Slack's VoIP uses WebRTC, which connects via UDP/TCP to always send SRTP packets through a TURN proxy (which extends STUN via ICE) to work around usual NAT problems. These guys scanned the TURN and found an SSRF which allowed them to connect to Slack's VPC on AWS using IAM temporary credentials. Interesting.

For fun, read that last paragraph out loud to a non-techy near by and watch their eyes...

Re:We abused Slack's TURN servers to gain access to internal... by tandr on Tuesday April 07, 2020 @03:27PM (#22806588)
This is a nice summary actually. (btw, you can read it to techy-but-not-in-the-field and still get the same look. I am not sure if I should be sad or proud from the fact that I understood 90% of what you have said without google-fu...)
Re:We abused Slack's TURN servers to gain access to internal... by anthk on Wednesday April 08, 2020 @02:33AM (#22810548)
If you are into SIP this is pretty well known.
Re:We abused Slack's TURN servers to gain access to internal... by tandr on Wednesday April 15, 2020 @07:35PM (#22884431)
I am not :)
Re:We abused Slack's TURN servers to gain access to internal... by jedberg on Tuesday April 07, 2020 @04:00PM (#22806912)
I understood every word of that and my eyes still glazed over. :)
Re:We abused Slack's TURN servers to gain access to internal... by bitwize on Tuesday April 07, 2020 @05:02PM (#22807433)
Could be a line on CSI: Los Angeles.
Re:We abused Slack's TURN servers to gain access to internal... by pottertheotter on Tuesday April 07, 2020 @03:35PM (#22806659)
Do you mean this paragraph?

"Our recommendation here is to make use of the latest coturn which by default, no longer allows peering with 127.0.0.1 or ::1. In some older versions, you might also want to use the no-loopback-peers."

Re:We abused Slack's TURN servers to gain access to internal... by topher200 on Tuesday April 07, 2020 @04:07PM (#22806982)
I believe GP means this paragraph:

> So Slack's VoIP uses WebRTC, which connects via UDP/TCP to always send SRTP packets through a TURN proxy (which extends STUN via ICE) to work around usual NAT problems. These guys scanned the TURN and found an SSRF which allowed them to connect to Slack's VPC on AWS using IAM temporary credentials. Interesting.

Re:We abused Slack's TURN servers to gain access to internal... by pottertheotter on Tuesday April 07, 2020 @04:42PM (#22807255)
Thanks! I don't know where my head was.
Re:We abused Slack's TURN servers to gain access to internal... by keanebean86 on Tuesday April 07, 2020 @05:14PM (#22807537)
Sounds like you're STUNned. Try not to TURN you head and maybe put some ICE on it.
Re:We abused Slack's TURN servers to gain access to internal... by jedberg on Tuesday April 07, 2020 @03:58PM (#22806894)
OP means they paragraph they just wrote.
Re:We abused Slack's TURN servers to gain access to internal... by pottertheotter on Tuesday April 07, 2020 @04:42PM (#22807259)
Thanks! I don't know where my head was.
Re:We abused Slack's TURN servers to gain access to internal... by bigdict on Tuesday April 07, 2020 @06:23PM (#22808088)
Hey I thought he was referring to the last paragraph in the article too…
Re:We abused Slack's TURN servers to gain access to internal... by weavie on Tuesday April 07, 2020 @04:43PM (#22807264)
Read it to myself and my eyes glaze over, and I've spent the past couple of weeks trying to decipher all the acronyms involved in WebRTC!
Re:We abused Slack's TURN servers to gain access to internal... by userbinator on Tuesday April 07, 2020 @09:56PM (#22809377)
I've worked with SIP and H323 but not WebRTC so I knew about STUN/TURN/ICE, but you're right about the acronym-soup, even to those who have networking experience --- VoIP is its own little niche. (Along the same lines, I've been a bystander to a group of GSM developers' meetings and it's just as incomprehensible.)
Re:We abused Slack's TURN servers to gain access to internal... by lwb on Tuesday April 07, 2020 @03:24PM (#22806572)
Even a techy who isn't familiar with networking protocols would start to glaze over!
Re:We abused Slack's TURN servers to gain access to internal... by ct520 on Tuesday April 07, 2020 @04:19PM (#22807078)
Not so much networking protocols but WebRTC maybe? I did a hello world type of implementation of WEBRTC awhile back and it made perfect sense to me.
Re:We abused Slack's TURN servers to gain access to internal... by dep_b on Wednesday April 08, 2020 @03:52AM (#22810880)
Yeah there's the WebRTC you can hack in an afternoon and there's the WebRTC that covers the most common edge cases. The problem that the solution to one problem (for example your websocket going disconnecting mid call while WebRTC still soldiers on) can create three new problems when a different edge case arises.
Re:We abused Slack's TURN servers to gain access to internal... by m463 on Wednesday April 08, 2020 @04:54AM (#22811204)
I recall Elon Musk's Acronyms Seriously Suck memo
Re:We abused Slack's TURN servers to gain access to internal... by kalium_xyz on Wednesday April 08, 2020 @12:59AM (#22810212)
Heh, reminds me of neuromancer
Re:We abused Slack's TURN servers to gain access to internal... by saagarjha on Wednesday April 08, 2020 @01:47AM (#22810387)
I read your paragraph and almost didn’t read the actual article :(
Re:We abused Slack's TURN servers to gain access to internal... by ddrt on Wednesday April 08, 2020 @01:19AM (#22810287)
Acronym city right here.