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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
Apple: Majority Of Mac OS X Users Not At Risk To 'Shellshock'
Threaded  |  Newest First  |  Oldest First
Robert McDougal
Robert McDougal,
 User Rank: Ninja
9/28/2014 | 12:48:25 PM
Apple is attempting to minimize.
True, in order to be vulnerable to a remote execution you need to enable some inbound service, such as SSH.  However, the fact is that ALL versions of OSX have the vulnerability.  In my testing, every version of OSX, including the beta of Yosemite, have proved to be vulnerable.

I know Apple hasn't had to deal with major vulnerabilities routinely in the past, but this isn't the way to address it.  Apple should admit that all versions of OSX have the vulnerability but, users are not exposed unless they enable X, Y or Z.  They shouldn't leave the subject up for debate by making a nebulous statement such as "systems are safe by default and not exposed to remote exploits of Bash unless users configure advanced UNIX services".  This doesn't actually explain to users how they might currently be vulnerable, or what they may do for a work around.

Apple gets an F for this response in my book.

 
RyanSepe
RyanSepe,
 User Rank: Ninja
9/29/2014 | 9:12:11 AM
Re: Apple is attempting to minimize.
Very good point Robert. I think even if there is the possibility of a vulnerable configuration within your hardware that you need to account for it. How difficult would it be for Apple to design a quick app to check if the system settings you have on your Mac are vulnerable? 

The answer is not very difficult at all if it is just a series of enables/disables. If enabled true if not than false. A quick scan should be made available for all OSX users. I think it isn't too lofty of a request considered that this vulnerability was given the highest severity rating possible by NIST.
securityaffairs
securityaffairs,
 User Rank: Ninja
9/29/2014 | 11:02:09 AM
Re: Apple is attempting to minimize.
I agree, OS X is anyway affected by the Bash bug flaw and its announcement is giving a fake sense of security to many people that aren't able to check their systems.
theb0x
theb0x,
 User Rank: Ninja
9/29/2014 | 9:26:22 PM
Re: Apple is attempting to minimize.
The following conditions must be true in OSX to exploit the system:

1) Root must be enabled. The setting is pretty well hidden and the user must knowly access it. (System default is disabled in latest OSX.)

2) A local terminal session must be spawned with the following command followed by root password:

sudo systemsetup -setremotelogin on

This enables the SSH Daemon. How many average Apple users do you think have configured their systems this way? At this point I see this as nothing more than a social engineering attack for these system conditions to be true for most users. Unless they know what SSH is because they're a Sys Admin. I am not taking sides with Apple. Their security responses are a joke and always make me chuckle.
securityaffairs
securityaffairs,
 User Rank: Ninja
9/30/2014 | 2:38:52 AM
Re: Apple is attempting to minimize.
I agree theb0x!


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
Incorporating a Prevention Mindset into Threat Detection and Response
Threat detection and response systems, by definition, are reactive because they have to wait for damage to be done before finding the attack. With a prevention-mindset, security teams can proactively anticipate the attacker's next move, rather than reacting to specific threats or trying to detect the latest techniques in real-time. The report covers areas enterprises should focus on: What positive response looks like. Improving security hygiene. Combining preventive actions with red team efforts.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-1809
PUBLISHED: 2022-05-21
Access of Uninitialized Pointer in GitHub repository radareorg/radare2 prior to 5.7.0.
CVE-2022-31267
PUBLISHED: 2022-05-21
Gitblit 1.9.2 allows privilege escalation via the Config User Service: a control character can be placed in a profile data field, such as an emailAddress%3Atext '[email protected]\n\trole = "#admin"' value.
CVE-2022-31268
PUBLISHED: 2022-05-21
A Path Traversal vulnerability in Gitblit 1.9.3 can lead to reading website files via /resources//../ (e.g., followed by a WEB-INF or META-INF pathname).
CVE-2022-31264
PUBLISHED: 2022-05-21
Solana solana_rbpf before 0.2.29 has an addition integer overflow via invalid ELF program headers. elf.rs has a panic via a malformed eBPF program.
CVE-2022-31259
PUBLISHED: 2022-05-21
The route lookup process in beego through 1.12.4 and 2.x through 2.0.2 allows attackers to bypass access control. When a /p1/p2/:name route is configured, attackers can access it by appending .xml in various places (e.g., p1.xml instead of p1).