{"id":4279,"date":"2014-11-11T12:49:19","date_gmt":"2014-11-11T17:49:19","guid":{"rendered":"http:\/\/me-en.kaspersky.com\/blog\/?p=4279"},"modified":"2020-02-26T18:59:08","modified_gmt":"2020-02-26T14:59:08","slug":"wirelurker_vulnerability_revealed","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/wirelurker_vulnerability_revealed\/4279\/","title":{"rendered":"iOS Vulnerability Behind WireLurker Apple Malware Revealed"},"content":{"rendered":"

Yesterday researchers said they discovered and disclosed to Apple, the vulnerability exploited by the WireLurker malware<\/a>, which targeted iOS mobile devices via infections through USB connections to Mac OS X and Windows machines.<\/p>\n

\"Masque-Attack-all-new-iOS-vulnerability_fb\"<\/a><\/p>\n

The vulnerability is called \u201cMasque<\/a>\u201d and it affects iOS 7.1.1, 7.1.2, 8.0, 8.1, and 8.1.1 beta. Perhaps most interestingly, while initial reports suggested that the malware could only infect iOS user-devices via USB connection, researchers from FireEye yesterday<\/a> said that the Masque bug is also exploitable by SMS text messages and email. However, in order to infect via SMS or email, the attacker would have to compel a victim to follow a link leading to the malicious apps.<\/p>\n

Researchers disclose a powerful #iOS vulnerability responsible for the #WireLurker Apple malware<\/p>Tweet<\/a><\/blockquote>\n

Technically, Masque gives attackers the ability to replace legitimate iOS apps with malicious ones without notification. In part, the flaw relates to an iOS enterprise provisioning failure to double check the identity of a given app against its digital certificate when the developer does not upload the application to the App Store. So in this case, iOS did not flag WireLurker\u2019s certificates, which were legitimately signed \u2013 albeit using a different certificate \u2013 because the malware merely uploaded the application directly to the user\u2019s phone from the infected desktop or laptop. This is why, unlike earlier iOS malware, WireLurker had the capacity to infect non-jailbroken devices.<\/p>\n

FireEye says that WireLurker is the only in the wild attack targeting the Masque vulnerability, but that it also appears to have been circulated among criminals. The Masque bug remains unpatched. To Apple\u2019s credit, they moved fast to invalidate the certificates used by the malicious malware.<\/p>\n

The need for anti-malware protection on Mac OS X devices cannot be overstated.<\/div>\n

Shortly after the security firm Palo Alto Networks published their WireLurker findings last week, the group responsible for the malware shut their operation down<\/a>. However, when it was still up and running, it aimed to infect Windows<\/a> and Mac machines, where it would lie dormant until the infected user attached an iPhone or iPod to his or her personal computer. When and if that occurred, the malware then searched the connected iOS device for the presence of a few popular applications. If present, WireLurker uninstalled those apps and replaced them with fake, trojanized replicas. It is not clear what data the malware ultimately sought.<\/p>\n

The only users that would have been impacted by WireLurker were users who had downloaded the Meitu photo app, the Taobao online auction app, or the AliPay payment application from a third-party application marketplace in China called Maiyadu.<\/p>\n

Palo Alto researchers said, 467 infected OS X apps have been found on Maiyadi and those apps have been downloaded more than 350,000 times as of Oct. 16, by more than 100,000 users.<\/p>\n

\u201cThe need for anti-malware protection on Mac OS X devices cannot be overstated,\u201d explained Kaspersky\u2019s global research and analysis team in a Securelist report<\/a>. \u201cIt\u2019s not only that your Mac OS X machine can get infected, but WireLurker showed us how the infection can move from your Mac to your iPhone. The good news is: there are plenty of options to chose from out there, including our own Kaspersky Internet Security for Mac<\/a>.\u201d<\/p>\n","protected":false},"excerpt":{"rendered":"

Yesterday, researchers disclosed a powerful iOS vulnerability that is responsible for the WireLurker Apple malware.<\/p>\n","protected":false},"author":42,"featured_media":4280,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[5],"tags":[14,656,838,34,837,836,835],"class_list":{"0":"post-4279","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-news","8":"tag-apple","9":"tag-apple-malware","10":"tag-ios-threats","11":"tag-mac","12":"tag-mac-malware","13":"tag-masque","14":"tag-wirelurker"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/wirelurker_vulnerability_revealed\/4279\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/wirelurker_vulnerability_revealed\/4350\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/wirelurker_vulnerability_revealed\/4805\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/wirelurker_vulnerability_revealed\/5043\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/wirelurker_vulnerability_revealed\/6062\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/wirelurker_vulnerability_revealed\/6628\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/wirelurker_vulnerability_revealed\/5413\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/wirelurker_vulnerability_revealed\/6062\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/wirelurker_vulnerability_revealed\/6628\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/wirelurker_vulnerability_revealed\/6628\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/apple\/","name":"apple"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/4279","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/42"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=4279"}],"version-history":[{"count":2,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/4279\/revisions"}],"predecessor-version":[{"id":15943,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/4279\/revisions\/15943"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/4280"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=4279"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=4279"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=4279"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}