News for hackers. Stuff that matters.
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…