Posts Tagged ‘Google’
Thursday, September 17, 2015 @ 04:09 PM gHale
Google fixed a lockscreen bypass vulnerability for mobile devices running any Android 5 version, which an attacker could easily exploit, researchers said.
The attacker would need to have physical access to your device in order to execute the attack.
“By manipulating a sufficiently large string in the password field when the camera app is active an attacker is able to destabilize the lockscreen, causing it to crash to the home screen. At this point arbitrary applications can be run or adb developer access can be enabled to gain full access to the device and expose any data contained therein,” John Vernon Gordon III, a senior network security analyst at the University of Texas at Austin Information Security Office (ISO).
Google is aware of the flaw and fixed it in Android 5.1.1 build LMY48M pushed out a week ago.
The problem of other OEMs and device makers slowly shipping patches is not as big a problem because users can change their password into a PIN or pattern to be safe from such an attack.
Friday, September 4, 2015 @ 04:09 PM gHale
Google released Chrome 45 for Windows, Mac, and Linux this week, patching 29 vulnerabilities.
Ten of the 29 security issues ended up reported by external researchers.
Six of the vulnerabilities reported by external researchers ended up rated high severity, Google said.
The list includes cross-origin bypass flaws in DOM (CVE-2015-1291, CVE-2015-1293), a cross-origin bypass in Service Worker (CVE-2015-1292), use-after-free flaws in Skia (CVE-2015-1294) and Printing (CVE-2015-1295), and a character spoofing bug in the Omnibox address bar (CVE-2015-1296).
Google has paid out $7,500 for each of the cross-origin bypass vulnerabilities, $5,000 for the use-after-free in Skia, $3,000 for the use-after-free in Printing, and $1,000 for the Omnibox spoofing issue.
The medium impact flaws patched with the release of Chrome 45.0.2454.85 are a permission scoping error in WebRequests, a URL validation error in extensions, and information leak and use-after-free bugs in the Blink web browser engine.
The vulnerabilities fixed in Chrome 45 ended up reported by anonymous researchers, Mariusz Mlynski, Rob Wu, Alexander Kashev, and experts using the online monikers taro.suzuki.dev, cgvwzq, cloudfuzzer, and zcorpan.
The amount of money paid out by Google so far to those who contributed to making Chrome more secure is $40,500, but not all vulnerabilities underwent review by the search giant’s reward panel.
Google’s own security team has also identified many flaws through internal audits, fuzzing and other initiatives.
With the release of Chrome 45, Google has also started killing Flash ads. The company decided to pause certain plugin content, including Flash ads, in an effort to improve performance and reduce power consumption.
Thursday, April 16, 2015 @ 03:04 PM gHale
Chrome 42 for Windows, Mac and Linux is now up and running and this latest release fixes 45 security issues and removes NPAPI support, said Google officials.
The most serious vulnerability fixed in Chrome 42 is a cross-origin bypass flaw in the HTML parser (CVE-2015-1235). The discovery of this high severity bug earned an anonymous researcher $7,500.
The list of high severity vulnerabilities also includes a type confusion in V8 (CVE-2015-1242) reported by Cole Forrester of Onshape, a use-after-free in IPC (CVE-2015-1237) reported by Khalil Zhani, and an out-of-bounds write bug in the Skia graphics engine (CVE-2015-1238) identified by cloudfuzzer.
The medium severity security issues reported by external researchers are a cross-origin-bypass in the Blink web browser engine, an out-of-bounds read in WebGL, a use-after-free in PDFium, a tap-jacking flaw, an HSTS bypass in WebSockets, an out-of-bounds read in Blink, scheme issues in OpenSearch, and a SafeBrowsing bypass.
The researchers who contributed to making Chrome more secure gained $21,500, according to Google blog post.
“We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel,” said Alex Mineer of the Google Chrome team.
In September 2013, Google said it would phase out support for the Netscape Plugin API (NPAPI). The company noted at the time the API’s 90s-era architecture was causing crashes, security issues and other problems.
In January 2014, Google blocked web page-instantiated NPAPI plugins by default, but whitelisted some of the most popular applications, such as Silverlight, Unity, Google Earth, Google Talk, and Facebook Video. Java was also on the list of most popular plugins using NPAPI, but it ended up disabled earlier for security reasons.
Now, NPAPI support is out by default in Chrome and extensions requiring NPAPI plugins will end up removed from the Chrome Web Store. Advanced users and enterprises can temporarily re-enable NPAPI until the plugins they use transition to alternative technologies.
Starting with Chrome 45, scheduled to release in September, this override will end up removed and NPAPI support will go away forever.
Monday, March 16, 2015 @ 03:03 PM gHale
Google fixed two serious vulnerabilities with the release of Android 5.1 Lollipop.
The flaws, which affect all Android versions prior to 5.1, ended up uncovered and reported by Guang Gong, a security researcher at the Chinese internet security company Qihoo 360.
One of the vulnerabilities (CVE-2015-1474) is an integer overflow that leads to heap corruption. The high-severity flaw, which has a CVSS base score of 10, allows a remote attacker to gain elevated privileges or cause a denial-of-service (DoS) condition on the targeted system.
“Multiple integer overflows in the GraphicBuffer::unflatten function in platform/frameworks/native/libs/ui/GraphicBuffer.cpp in Android through 5.0 allow attackers to gain privileges or cause a denial of service (memory corruption) via vectors that trigger a large number of file descriptors or integer values,” Gong said in an advisory.
The second vulnerability (CVE-2015-1530) can also end up exploited for privilege escalation or DoS. The flaw is the result of an integer overflow in the Android media package.
“An Integer overflow in the BnAudioPolicyService::onTransact function in frameworks/av/media/libmedia/IAudioPolicyService.cpp in Android through 5.0 allows attackers to gain privileges or cause a denial of service (memory corruption) via vectors that trigger a large number of count value,” the advisory said.
Gong said malicious applications can exploit these vulnerabilities to surreptitiously carry out various tasks, including taking photos of the user and uploading them to a remote server, making phone calls, and sending messages.
Gong reported the vulnerabilities to Google in October and November 2014. In the case of CVE-2015-1474, the search giant had to release two patches because the first one was incomplete.
Google released Android 5.1 last Monday. The latest update introduces a new feature called Device Protection, which ensures lost or stolen devices remain locked until the owner signs in with their Google account.
Thursday, March 5, 2015 @ 01:03 PM gHale
Google’s latest version of its browser, Chrome 41, brings new apps and extension APIs, stability and performance improvements, and, of course, security fixes.
Fifty-one security issues ended up fixed in Chrome 41.0.2272.76, including 13 high-severity and six medium-severity vulnerabilities identified by external researchers.
Anonymous researchers earned $14,500 for identifying an out-of bounds write flaw in media (CVE-2015-1212), a use-after-free in v8 bindings (CVE-2015-1216), and a type confusion in v8 bindings (CVE-2015-1217).
The researcher who uses the online moniker Cloudfuzzer reported three out-of-bounds write vulnerabilities in skia filters (CVE-2015-1213, CVE-2015-1214, CVE-2015-1215), a use-after-free in DOM (CVE-2015-1218), and an out-of-bounds read in PDFium. Cloudfuzzer earned $19,000 for his work.
The list of high-severity vulnerabilities also includes an integer overflow in WebGL (CVE-2015-1219) reported by Chen Zhang of the NSFOCUS Security Team, use-after-free flaws in web databases and service workers (CVE-2015-1221, CVE-2015-1222) reported by Collin Payne, a use-after-free in the gif decoder (CVE-2015-1220) found by Aki Helin of OUSPG, a use-after-free in DOM (CVE-2015-1223) identified by Maksymillian Motyl, and a type confusion issue in v8 (CVE-2015-1230) reported by Skylined.
Medium-severity issues include an out-of-bounds read in vpxdecoder, a validation issue in the debugger, an uninitialized value in the Blink rendering engine, an uninitialized value in rendering, and a cookie injection via proxies.
Several vulnerabilities also ended up discovered by the Chrome Security Team.
So far, Google paid out $50,000 to those who contributed to making Chrome 41 more secure.
Google decided to turn the single-day Pwnium competition into a year-round program. Researchers who find a Pwnium-style bug chain in Chrome or Chrome OS and report it through the Chrome Vulnerability Reward Program (VRP) can get up to $50,000.
Thursday, January 15, 2015 @ 06:01 PM gHale
Google released details of a new privilege escalation vulnerability in Windows just as Microsoft was getting ready to send out a patch.
The issue is the vulnerability first came to Microsoft’s attention over 90 days ago and Google’s Project Zero automatically released the details when the Redmond software giant did not release a patch within the 90-day disclosure deadline.
“When a user logs into a computer the User Profile Service is used to create certain directories and mount the user hives (as a normal user account cannot do so),” Google said in its report. “In theory the only thing which needs to be done under a privileged account (other than loading the hives) is creating the base profile directory. This should be secure because c:\users requires administrator privileges to create. The configuration of the profile location is in HKLM so that can’t be influenced.”
“However, there seems to be a bug in the way it handles impersonation, the first few resources in the profile get created under the user’s token, but this changes to impersonating Local System part of the way through. Any resources created while impersonating Local System might be exploitable to elevate privilege. Note that this occurs every time the user logs in to their account, it isn’t something that only happens during the initial provisioning of the local profile,” Google said.
A proof-of-concept (PoC) demonstrating the attack on Windows 8.1 published, but researchers said the vulnerability also affects Windows 7.
In November, Microsoft informed Google of plans to address the issue in February 2015 and asked for an extension of the deadline. However, Google told Microsoft the 90 day deadline is “fixed for all vendors and bug classes and so cannot be extended.” Later, Microsoft promised to address the vulnerability in January, but Google still refused to extend its deadline even by two days.
In late December, Project Zero published the details and a proof-of-concept for a different Windows 8.1 privilege escalation flaw after the 90-day deadline expired.