红蟾蜍,蓝蟾蜍,黑蟾蜍?

L. Rizkallah, Nick Potter, Kyle Reed, Dylan Reynolds, Mohammed Salman, S. Bhunia
{"title":"红蟾蜍,蓝蟾蜍,黑蟾蜍?","authors":"L. Rizkallah, Nick Potter, Kyle Reed, Dylan Reynolds, Mohammed Salman, S. Bhunia","doi":"10.1109/aiiot54504.2022.9817361","DOIUrl":null,"url":null,"abstract":"Towards the end of 2012, it was announced by AntiSec, a small labeled sub-group of an anonymous hacktivists, that they leaked one million UDIDs of Apple users. AntiSec claimed the data were taken from a laptop that belonged to an agent who works for the authorities. However, it was later found that the trustworthy source of the leak was a small digital publishing company called BlueToad. In this paper, we investigate the motivation and methods of AntiSec by analyzing the data. There are many inconsistencies surrounding how the leak happened. As far as we know, there has never been a confirmed statement on how the data were accessed, but there are multiple theories. This paper examines the three main claims behind the data leak. We found that AntiSec was able to exploit the system through the vulnerability CVE-2012-0507. AntiSec could have used the UDIDs to track and collect Apple Users' private data; instead, they published the data to the public and blamed authorities for data collection. We analyzed the ramifications of AntiSec's decision. While it was never explicitly announced by BlueToad how they remedied the vulnerability, we provide the defense solutions they should have taken. We offer general tips for users to protect themselves from future attacks. We also detail some alternatives to using the UDID and which implementation Apple chose for their UDID replacement.","PeriodicalId":409264,"journal":{"name":"2022 IEEE World AI IoT Congress (AIIoT)","volume":"25 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2022-06-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":"{\"title\":\"Red Toad, Blue Toad, Hacked Toad?\",\"authors\":\"L. Rizkallah, Nick Potter, Kyle Reed, Dylan Reynolds, Mohammed Salman, S. Bhunia\",\"doi\":\"10.1109/aiiot54504.2022.9817361\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Towards the end of 2012, it was announced by AntiSec, a small labeled sub-group of an anonymous hacktivists, that they leaked one million UDIDs of Apple users. AntiSec claimed the data were taken from a laptop that belonged to an agent who works for the authorities. However, it was later found that the trustworthy source of the leak was a small digital publishing company called BlueToad. In this paper, we investigate the motivation and methods of AntiSec by analyzing the data. There are many inconsistencies surrounding how the leak happened. As far as we know, there has never been a confirmed statement on how the data were accessed, but there are multiple theories. This paper examines the three main claims behind the data leak. We found that AntiSec was able to exploit the system through the vulnerability CVE-2012-0507. AntiSec could have used the UDIDs to track and collect Apple Users' private data; instead, they published the data to the public and blamed authorities for data collection. We analyzed the ramifications of AntiSec's decision. While it was never explicitly announced by BlueToad how they remedied the vulnerability, we provide the defense solutions they should have taken. We offer general tips for users to protect themselves from future attacks. We also detail some alternatives to using the UDID and which implementation Apple chose for their UDID replacement.\",\"PeriodicalId\":409264,\"journal\":{\"name\":\"2022 IEEE World AI IoT Congress (AIIoT)\",\"volume\":\"25 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2022-06-06\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"1\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2022 IEEE World AI IoT Congress (AIIoT)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/aiiot54504.2022.9817361\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2022 IEEE World AI IoT Congress (AIIoT)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/aiiot54504.2022.9817361","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 1

摘要

2012年底,一个名为AntiSec的匿名黑客组织宣布,他们泄露了100万苹果用户的uid。AntiSec声称,这些数据是从一名为当局工作的特工的笔记本电脑上获取的。然而,后来发现,可信的泄密来源是一家名为BlueToad的小型数字出版公司。本文通过对数据的分析,探讨了反安全的动机和方法。关于泄漏是如何发生的,有很多不一致之处。据我们所知,关于数据是如何被访问的,从来没有一个确切的声明,但有多种理论。本文探讨了数据泄露背后的三个主要主张。我们发现AntiSec能够通过漏洞CVE-2012-0507来利用系统。反安全委员会本可以使用uid来跟踪和收集苹果用户的私人数据;相反,他们向公众公布了数据,并指责当局收集了数据。我们分析了反sec决定的后果。虽然BlueToad从未明确宣布他们如何修复该漏洞,但我们提供了他们应该采取的防御解决方案。我们为用户提供保护自己免受未来攻击的一般提示。我们还详细介绍了一些使用UDID的替代方案,以及苹果选择了哪些实现来替代UDID。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
Red Toad, Blue Toad, Hacked Toad?
Towards the end of 2012, it was announced by AntiSec, a small labeled sub-group of an anonymous hacktivists, that they leaked one million UDIDs of Apple users. AntiSec claimed the data were taken from a laptop that belonged to an agent who works for the authorities. However, it was later found that the trustworthy source of the leak was a small digital publishing company called BlueToad. In this paper, we investigate the motivation and methods of AntiSec by analyzing the data. There are many inconsistencies surrounding how the leak happened. As far as we know, there has never been a confirmed statement on how the data were accessed, but there are multiple theories. This paper examines the three main claims behind the data leak. We found that AntiSec was able to exploit the system through the vulnerability CVE-2012-0507. AntiSec could have used the UDIDs to track and collect Apple Users' private data; instead, they published the data to the public and blamed authorities for data collection. We analyzed the ramifications of AntiSec's decision. While it was never explicitly announced by BlueToad how they remedied the vulnerability, we provide the defense solutions they should have taken. We offer general tips for users to protect themselves from future attacks. We also detail some alternatives to using the UDID and which implementation Apple chose for their UDID replacement.
求助全文
通过发布文献求助,成功后即可免费获取论文全文。 去求助
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信