Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
New Attack Method Can Hit 95% Of iOS Devices
Newest First  |  Oldest First  |  Threaded View
SenseCyBlog
SenseCyBlog,
User Rank: Apprentice
11/26/2014 | 3:39:02 AM
An Increasing Tendency Toward Smartphone-Based Attacks
We have recently seen the development and publishing of hack applications for smartphones on underground forums. Most tools are only available for Android smartphones, and many require root permissions. The most popular tool for cookie theft is DroidSheep. For details visit our blog / follow our twitter account.
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
11/12/2014 | 8:13:45 AM
Re: Doesn't make much sense
I don't think you are being cynical at all, @aws0513. Vendors who aren't responsive to issues about the security of their products don't deserve to be in business..
aws0513
aws0513,
User Rank: Ninja
11/11/2014 | 10:37:51 AM
Re: Doesn't make much sense
My cynicism, in all cases, is on the vendor side of the equation.
In my opinion, all product vendors must be intentionally responsive to any legitimate claims of security vulnerabilities of any kind that are relevant to their products.
AnonymousMan
AnonymousMan,
User Rank: Moderator
11/11/2014 | 8:49:40 AM
Re: Doesn't make much sense
I guess I'm more cynical than you, or at least in a different way.  I believe the details are left out because they make the attack less practical and relevant to the vast majority of iOS users.  Just like WireLurker.
aws0513
aws0513,
User Rank: Ninja
11/11/2014 | 8:40:50 AM
Re: Doesn't make much sense
I think the details are left out intentionally in order to prevent copy-cat activites.
However, what I find more disturbing is that Apple has yet (as of this posting) to release any official statement specific to the threat.  Part of me wants to believe that Apple is investigating the claim in detail.
AnonymousMan
AnonymousMan,
User Rank: Moderator
11/10/2014 | 6:03:37 PM
Doesn't make much sense
how does one pull down apps from 3rd parties on an iPhone that is not jailbroken?  I'm confused about how this attack would work in reality, and it seems to me the FireEye is leaving out some important details.  
aws0513
aws0513,
User Rank: Ninja
11/10/2014 | 3:26:54 PM
Re: Protection is vital
Other than the three recommendations noted in the last paragraph, not much more can be done.
The first point in the recommendations crucial.  As long as users are not pulling down apps from 3rd party sources, the risk is likely mitigated.  For many organizations, it looks like there should be little "pants on fire" reaction as long as they have a good handle on how their users use the iOS devices that they manage.

To me, the bigger concern would be with end users and organizations that are not aware of this attack.  This concern is especially enhanced for organizations that have embraced BYOD for iOS devices on a broad scale.
SecOpsSpecialist
SecOpsSpecialist,
User Rank: Moderator
11/10/2014 | 2:35:37 PM
Protection is vital
So I'm going to ask the million dollar question that is probably swimming through everyone's mind as they read this: How do we protect against it?

Obviously in a non-commercial environment, it is easier because we as consumers can easily put protection on our phones, laptops etc to prevent this kind of thing. But, for the commercial environment, how would a business go about protecting its end users and so on?


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Creating an Effective Incident Response Plan
Security teams are realizing their organizations will experience a cyber incident at some point. An effective incident response plan that takes into account their specific requirements and has been tested is critical. This issue of Tech Insights also includes: -a look at the newly signed cyber-incident law, -how organizations can apply behavioral psychology to incident response, -and an overview of the Open Cybersecurity Schema Framework.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-37016
PUBLISHED: 2022-12-01
Symantec Endpoint Protection (Windows) agent may be susceptible to a Privilege Escalation vulnerability, which is a type of issue whereby an attacker may attempt to compromise the software application to gain elevated access to resources that are normally protected from an application or user.
CVE-2022-37017
PUBLISHED: 2022-12-01
Symantec Endpoint Protection (Windows) agent, prior to 14.3 RU6/14.3 RU5 Patch 1, may be susceptible to a Security Control Bypass vulnerability, which is a type of issue that can potentially allow a threat actor to circumvent existing security controls. This CVE applies narrowly to the Client User I...
CVE-2022-28607
PUBLISHED: 2022-12-01
An issue was discovered in asith-eranga ISIC tour booking through version published on Feb 13th 2018, allows attackers to gain sensitive information via the action parameter to /system/user/modules/mod_users/controller.php.
CVE-2022-30528
PUBLISHED: 2022-12-01
SQL Injection vulnerability in asith-eranga ISIC tour booking through version published on Feb 13th 2018, allows attackers to execute arbitrary commands via the username parameter to /system/user/modules/mod_users/controller.php.
CVE-2022-1471
PUBLISHED: 2022-12-01
SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization.