Reverse Engineering the Apple Multipeer Connectivity Framework (2022)
1–10 of 36 posts
Re: Reverse Engineering the Apple Multipeer Connectivity Framework (2022)
#2> I’ve heard way too many negative stories about [Apple's] disclosure program and in general how they mistreat researchers.
Links?
Re: Reverse Engineering the Apple Multipeer Connectivity Framework (2022)
#3From a comment in the article:
> This gives me chills, the shared clipboard also uses this protocol, right? This means that everything we copy goes through the network via Bluetooth without encryption and can be captured by any Bluetooth sniffer?
The shared clipboard uses this protocol?... on what basis is this claim plausible?
Re: Reverse Engineering the Apple Multipeer Connectivity Framework (2022)
#4“Moreover, while sending crafted packets and attempting all sorts of things, I’ve discovered several vulnerabilities in the Apple custom made parsers. I will not discuss them here (exception made for the session spoofing) but at the same time I’m not interested in reporting them to Apple…”
Erm, hope they’re not super serious I guess?
Re: Reverse Engineering the Apple Multipeer Connectivity Framework (2022)
#5> I’ve heard way too many negative stories about [Apple's] disclosure program and in general how they mistreat researchers. Links?
I did some lazy searching and it seems it's a well known fact. I don't think the author has to back it up in this case.
Infosec researchers say Apple’s bug-bounty program needs work[0]
[0] https://arstechnica.com/information-technology/2021/09/infos...
Re: Reverse Engineering the Apple Multipeer Connectivity Framework (2022)
#6> I’ve heard way too many negative stories about [Apple's] disclosure program and in general how they mistreat researchers. Links?
Wait times over 8 months and they refused to give credit (but gave $).
Personal experience so I can’t say for others. They pay well though. My first year of college has been completely covered by them so no complaints.
Re: Reverse Engineering the Apple Multipeer Connectivity Framework (2022)
#7"custom (and as typical of Apple, undocumented) TCP protocol"
Pretty much all custom protocols are undocumented. Not sure why he feels the need to shit on Apple.
And any custom protocol parser will be riddled with errors, because they always expect values to be in range.
Re: Reverse Engineering the Apple Multipeer Connectivity Framework (2022)
#8"custom (and as typical of Apple, undocumented) TCP protocol" Pretty much all custom protocols are undocumented. Not sure why he feels the need to shit on Apple. And any custom protocol parser will be riddled with errors, because they always expect values to be in range.
Because when apple does it you can assume it only works on apple devices, such a bore. How people can get excited about vendor lock-in beyond me.
Re: Reverse Engineering the Apple Multipeer Connectivity Framework (2022)
#9From a comment in the article: > This gives me chills, the shared clipboard also uses this protocol, right? This means that everything we copy goes through the network via Bluetooth without encryption and can be captured by any Bluetooth sniffer? The shared clipboard uses this protocol?... on what basis is this claim plausible?
I thought it was clear it ran through iCloud: https://support.apple.com/en-au/HT209460
It only works between devices signed in with the same Apple ID
Re: Reverse Engineering the Apple Multipeer Connectivity Framework (2022)
#10“Moreover, while sending crafted packets and attempting all sorts of things, I’ve discovered several vulnerabilities in the Apple custom made parsers. I will not discuss them here (exception made for the session spoofing) but at the same time I’m not interested in reporting them to Apple…” Erm, hope they’re not super serious I guess?
Taken out of context it looks a bit weird, but it does explain the motivation:
"I’ve heard way too many negative stories about their disclosure program and in general how they mistreat researchers."