Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

http://www.cs.ucdavis.edu/~rogaway/papers/draft-rogaway-ipse... If you could provide some more information on responses, perhaps emails dismissing it, I think we can figure out what went wrong.


sort by: page size:

paper: https://ieeexplore.ieee.org/abstract/document/8721270 (lack of authentication allows DoS, spoofing)

Admittedly low-value comment: Can we appreciate the amazing vulnerability name? Confluenza.

https://censys.io/blog/cve-2021-26084-confluenza/


https://tailscale.com/security-bulletins/#ts-2022-004

It was a pretty severe issue, but tailscale did respond quickly to it.



the original link is not responding...

Here is a copy of the paper hosted on usenix,

https://www.usenix.org/system/files/conference/usenixsecurit...




https://www.zdnet.com/article/apple-update-kills-off-zoom-we...

This was a seriously exploitable issue that was a problem every time it was run.

I agree that this certificate mechanism is absurdly problematic.

That doesn’t justify dismissing the security risks it was intended to prevent.


https://labs.integrity.pt/articles/the-curious-case-of-apple...

That's a post from April 2019 showing a very similar issue with IKEv2 VPNs leaking traffic on iOS. I wonder if the two issues are related. Back then, Apple was made aware under responsible disclosure but apparently nothing was done about it.


https://www.zdnet.com/article/apple-removes-feature-that-all...

"The bugs were related to Apple deprecating network kernel extensions (NKEs) in Big Sur and introducing a new system called Network Extension Framework, and Apple engineers not having enough time to iron out all the bugs before the Big Sur launch last fall."





https://github.com/Netflix/security-bulletins/blob/master/ad... is the advisory by the party that discovered the issue. (Disclosure: I have met Jonathan Looney and know some of the Netflix engineering staff, but I don't work for Netflix.)


https://habr.com/en/post/579714/

thunderspy.io/

Those are my favorite recent examples, but specifically Apple has huge issues with turnaround time. They also don't communicate with or assist the researchers who found these exploits either, which makes things particularly frustrating for people who ultimately both want to secure Apple's systems. Their overt hostility, history of poor communication, and frankly pathetic bug bounties are all contributors to how people perceive Apple's relationship with security experts.


https://xenproject.org/2012/06/13/the-intel-sysret-privilege...

I can only speculate as to the types of vulnerabilities not disclosed.


http://slackhq.com/post/114696167740/march-2015-security-inc...

http://valleywag.gawker.com/slack-is-letting-anyone-peek-at-... https://news.ycombinator.com/item?id=8425799

Tbh, at this point I wouldn't be surprised if these "problems" occurred after someone discovered the bug and reported it.


next

Legal | privacy