Tuesday, May 3, 2016
Thursday, January 23, 2014
Monday, October 7, 2013
Max will give an overview of Android’s device protection mechanisms in 4.0+ and how they can be circumvented or unintentionally undermined by device manufacturers, 'cause each device manufacturer or carrier can add or modify code from the Android Open Source Project (AOSP). This can include access to device memory, exploitable processes which run as the root user, initialization scripts which perform privileged actions without proper validation, or APKs which leak access to otherwise-protected information sources. The talk will also detail /boot and /recovery differences between OEMs, how signature checks are performed, and demonstrate some of our tools to examine new devices and find potential security flaws.
"At this time, we do not believe the attackers removed decrypted credit or debit card numbers from our systems". Question, why is that information not encrypted in the first place. What is the need to store them unencrypted.
In all, Adobe says that the breach impacts some 2.9 million customers worldwide, and that they're in the process of sending out notifications to those who had credit or debit card details compromised. Further, Adobe has alerted the banks processing customer payments, in order for them to help protect accounts upstream.
Adobe admitted that source code was breached during the incident. It wouldn't comment which product lines were breached. Adobe is the most commonly used product in almost every system out there. In theory this could mean, that their software could have more 0-days than what we are aware of. It could also mean that the current versions may have been altered, and backdoored already.
The earliest known date of discovery is September 17, but Adobe hasn't said how long the attackers have had possession of the stolen source code, nor can they comment on how far it's spread online. Last week, reporter Brian Krebs, found 40 GB worth of Adobe's proprietary data on a server used by criminals, but by the time he found it, Adobe was already investigating its theft.
In an advisory to customers, Adobe confirmed that the source code theft impacted Adobe Acrobat, ColdFusion, ColdFusion Builder and "other Adobe products." As to what those other products are, Adobe didn't say. And why would they !!!!
Adobe recommends that customers update to the latest supported software versions, and that they download the newest releases when they're made available on October 8.
Hong Kong-based PureVPN faced problems this weekend, after someone used a Zero-Day vulnerability in WHMCS to send the networking firm's customers an alarming message. The rogue email stated that the VPN service was going to shutdown due to legal issues, and that customer information was handed over to the authorities.
Addressed simply as "Dear Customer" the letter said that due to an incident, PureVPN would be closing accounts and were no longer able to run an anonymization service. In addition, it said the company "had to handover all [customer] information to the authorities."
The letter was signed by Uzair Gadit, the co-Founder of PureVPN, who took to his company's blog and Twitter on Saturday to dispute the claims it made. According to a second email delivered to customers, the cause for the letter was a vulnerability in WHMCS — a platform used by many service providers like PureVPN, to manage user registrations and accounts, as well as billing and support.
"Preliminary reports suggest that we are hit with a zero day exploit, found in [WHMCS]...We are able to confirm that the breach is limited to a subset of registered users Email IDs and names," a blog post by PureVPN explained.
The WHMCS vulnerability was disclosed last week in versions 5.2.7 and 5.1.9. Moreover, proof-of-concept code for launching an SQL Injection attack spread to a few different exploitation-based forums and places like Pastebin. The flaw itself resides in dbfunctions.php (update_query), and requires that the attacker have an account on the system; something that is easily done considering the nature of WHMCS.
At issue is the fact that the script trusts any SQL update that has a value starting with AES_ENCRYPT. As it was explained to CSO, this was a case of missing input validation checks, a common (yet risky) coding error.
It's unclear if there are any other websites targeted by those responsible for the PureVPN compromise. CSO asked PureVPN, since given the nature of the vulnerability itself, if it can be disproved that the entire email database was accessed, but the company didn't respond to questions.
A recent series of customer studies by mobile management firm Fiberlink shows a pattern of risky behavior, and widespread usage of a soon to be dead operating system
Friday, August 2, 2013
The security nightmare corporations face with the bring-your-own-device (BYOD) trend just got worse with the release of Google's new Moto X. With the Android smartphone unveiled Thursday, Google is hoping to lure customers with a personal digital assistant that's easy to use and can guess what information or services people want by reading emails and schedules and tracking search queries. While all this data collection may make the device invaluable, it also should make corporations very nervous. "It's engineers gone wild," said Roger Entner, principal analyst for Recon Analytics. "The engineers are [saying], 'Oh, wouldn't this be a really cool idea,' but don't think through the repercussions." The ease-of-use features in the Moto X, designed and built by Google-owned Motorola, are likely to tickle consumers while haunting IT security pros. First is the always-on microphone, which a person can use to activate the device using trigger words, such as "OK Google Now," to make phone calls or access services and features. The feature is possible through a special, low-power chip developed by Motorola that keeps the microphone on without draining the battery. The always-ready microphone, coupled with the massive amount of data collection, makes the Moto X a valuable target for cybercriminals and cyberspies, who are already heavily focused on developing malware to take control of Android devices. Security researchers say tools for building and distributing Android malware are getting progressively better in the criminal underground. In 2012, the number of Android malware rose more than 2,500% and accounted for 95% of mobile threats on the Internet, according to Cisco's 2013 Annual Security Report. Malware exists today that can take control of an Android device, if a user can be tricked into installing in infected app from an online store or clicking a malicious link on a text message. "Once that happens, all bets are off, and all these lovely sensors become a continuous sound and video information-gathering tool on your designated target," said Kurt Stammberger, vice president of market development for mobile security vendor Mocana. [Also see: Next iPhone's possible fingerprint reader unlikely to excite buyers | Pentagon nod shows Android can be as secure as Blackberry] Motorola will also provide hands-free authentication with the Moto X, through a plastic token that can be clipped onto clothing that will communicate via near-field communication (NFC). As long as the token is a few feet away, a password won't be necessary to unlock the device. The token will be sold separately, reports said. "I'm sure someone at Black Hat or Defcon will figure out a workaround," William Stofega, analyst for IDC, said, referrring to the two security conferences now under way in Las Vegas. The Moto X is not the first Android phone to have these security-troubling features. The Motorola Droid that debuted last week also has them, industry observers say. However, Google has already proclaimed the Moto X its flagship smartphone and Motorola Mobility is reported to be set to spend as much as $500 million in marketing. Such a push gives the phone a better chance of becoming a success. Google's strategy of making its smartphones as useful as possible is what's needed to drive sales in the consumer market. A phone that can automatically notify the user about traffic conditions before heading to a meeting is certain to please many people. But the data collection necessary to provide such services, as well as the microphone, camera and NFC needed for ease of use, are making it increasingly difficult for companies to have a liberal BYOD policy. "Bring-your-own-device is a security nightmare in general," Entner said. Whether an employee can use their own device to access the corporate network should depend on their job, Stofega said. A chief research officer may not want his location known or to communicate with staff and bosses without strict security controls. "At some point [companies] have to have control at some level of the person and also the intellectual capital that's invested in that person," Stofega said. In the meantime, companies are better offer steering away from the Moto X for now, experts say. "I would not recommend the Moto X to corporate clients until we have a really good understanding and assurances from Google and Motorola on how to combat potential mischief being done with these capabilities," Entner said.