New CISO Hires at Uber, Square, SailPoint

Ride-sharing giant Uber has quietly snapped up veteran security leader Latha Maripuri to be its Chief Information Security Officer (CISO).

A formal announcement has not yet been made but Maripuri, a security leader with stints at IBM and NewsCorp, has shared the news on her LinkedIn profile.

Maripuri joins Uber from News Corp, where she spent the last six years holding the dual Global CISO and Deputy CTO titles.   

Uber has been without a formal security chief since the departure of John ‘Four’ Flynn in July 2020.  Flynn is now CISO at Amazon.

The CISO seat at Uber has seen its share of security-related controversies recently, including a data breach that eventually led to the ouster — and legal issues — surrounding former CISO Joe Sullivan.

Square Hires Google Veteran as New CISO

Separately, payment processor Square has tapped Google security veteran Jim Higgins to manage its security program.

Higgins, who spent the last 10 years managing security engineering, product security, and infrastructure protection teams at Google, will be tasked with securing Square’s financial transactions across mobile devices and in-store hardware terminals.

Square, which is owned and run by Twitter CEO Jack Dorsey, operates in the financial services space.  The company sells products — both software and hardware — to manage payments and transactions for third-party merchants.

Heather Gantt-Evans is New SailPoint CISO

Identity management and governance company SailPoint has given the keys to the CISO office to Home Depot security leader Heather Gantt-Evans.

The company said Gantt-Evans will design SailPoint’s cybersecurity strategy to decrease risk and exposure points across the business and increase collaboration between teams.

Gantt-Evans joins SailPoint from HomeDepot, where she acted as the company’s senior director of security operations and resilience. She was responsible for Home Depot’s security operations centers, network security operations, security engineering, application security and vulnerability management.

Prior to Home Depot, Gantt-Evans held strategic security roles at Ernst & Young, Booz Allen Hamilton supporting Air Force Cyber Command, and served in the U.S. Army Reserves for six years. 

Jameeka Green Aaron Joins Auth0 as CISO 

Auth0, a company that sells an identity platform for application teams, has tapped Jameeka Green Aaron to be its Chief Information Security Officer (CISO).

Aaron, who has held security leadership roles at Nike and Lockheed Martin, will be responsible for the holistic security and compliance of Auth0’s platform, products, and corporate environment, the company said in a statement.

Related:  Reddit Hires Allison Miller as CISO, VP of Trust

view counter

Ryan Naraine is Editor-at-Large at SecurityWeek and host of the popular Security Conversations podcast series. Ryan is a journalist and cybersecurity strategist with more than 20 years experience covering IT security and technology trends. He is a regular speaker at cybersecurity conferences around the world.
Ryan has built security engagement programs at major global brands, including Intel Corp., Bishop Fox and Kaspersky GReAT. He is a co-founder of Threatpost and the global SAS conference series. Ryan’s career as a journalist includes bylines at major technology publications including Ziff Davis eWEEK, CBS Interactive’s ZDNet, PCMag and PC World.
Follow Ryan on Twitter @ryanaraine.

Previous Columns by Ryan Naraine:
Tags:

http://feedproxy.google.com/~r/Securityweek/~3/waMqRyeIPQQ/new-ciso-hires-uber-square-sailpoint




Intel Paid Out $800,000 Per Year Through Bug Bounty Program

Over 230 Vulnerabilities Patched in Intel Products in 2020

Intel patched 231 vulnerabilities in its products last year, roughly the same as in the previous year, when it fixed 236 flaws.

The chipmaker on Wednesday published its 2020 Product Security Report, which reveals that nearly half of the vulnerabilities patched last year were discovered by its own employees, and the company claims that a vast majority of the addressed issues are the direct result of its investment in product security assurance.

According to Intel, 105 vulnerabilities were reported through the company’s bug bounty program, which saw a 33% increase in submissions compared to the previous year. The company also reported seeing a significant increase in the number of external security researchers it engaged with.

Intel vulnerability report 2020

Intel said it paid out an average of $800,000 per year through its bug bounty program since it was launched in 2018.

The report shows that 93 vulnerabilities were found in software, 66 in firmware, and 58 required both firmware and software updates to patch. Fourteen flaws were found to affect hardware.

In terms of severity, only 3% of the security holes patched last year were rated critical. Roughly one-third were rated high severity, and 57% were assigned a medium severity rating.

“The impact of most of the medium, high, and critical vulnerabilities is potential elevation of privilege,” Intel explained in its report. “In the case of medium severity issues, these require an authenticated user on the same physical network or who has physical access to a vulnerable system. These issues become high or critical, if an unauthenticated user can trigger the vulnerability and/or they can reach a vulnerable system from outside the local area network.”

Related: Intel Patches Tens of Vulnerabilities in Software, Hardware Products

Related: Intel Releases Firmware Updates to Patch Critical Vulnerability in AMT, ISM

Related: Vulnerability in Intel Chipsets Allows Hackers to Obtain Protected Data

Related: Load Value Injection: Intel CPUs Vulnerable to Reverse Meltdown Attack

view counter

Eduard Kovacs (@EduardKovacs) is a contributing editor at SecurityWeek. He worked as a high school IT teacher for two years before starting a career in journalism as Softpedia’s security news reporter. Eduard holds a bachelor’s degree in industrial informatics and a master’s degree in computer techniques applied in electrical engineering.

Previous Columns by Eduard Kovacs:
Tags:

http://feedproxy.google.com/~r/Securityweek/~3/NO1Lj45SGQM/intel-paid-out-800000-year-through-bug-bounty-program




Jetty Flaw Can Be Exploited to Inflate Target’s Cloud Bill, Cause Disruption

A vulnerability affecting Eclipse Jetty web servers can be exploited by an attacker to inflate a targeted organization’s cloud services bill or cause disruption, according to security researchers at tech company Synopsys.

Jetty is an open source Java web server and servlet container that has been used in a wide range of projects and products, including by major companies such as Facebook, Google and Yahoo.

Synopsys researchers discovered that Jetty versions 9.4.6 through 9.4.36, 10.0.0 and 11.0.0 are affected by a denial-of-service (DoS) vulnerability.

The issue was reported to Jetty developers on February 10 and it was patched a couple of weeks later in all impacted versions.

“When Jetty handles a request containing request headers with a large number of ‘quality’ (i.e. q) parameters (such as what are seen on the Accept, Accept-Encoding, and Accept-Language request headers), the server may enter a denial of service (DoS) state due to high CPU usage while sorting the list of values based on their quality values. A single request can easily consume minutes of CPU time before it is even dispatched to the application,” reads an advisory published by Jetty developers.

Travis Biehn, principal security consultant at Synopsys, told SecurityWeek that an attacker could exploit this vulnerability to “run up an organization’s bill or degrade service for other users.”

“Consider an organization that has some sort of auto-scaling Amazon infrastructure. For instance, overloading one server causes another to be provisioned and an attacker can run up a customers’ bill by leveraging this attack,” Biehn explained.

“The nuts and bolts of executing the attack are that the attacker just needs to be able to get HTTP requests to a vulnerable Jetty server with a malicious Accept header. No authentication is required,” he added. “It’s not typical to see Jetty serving the edge directly, so it’s possible that components like load balancers might make exploitation more difficult.”

Related: Hackers Scanning for VMware vCenter Servers Affected by Critical Vulnerability

Related: Vulnerability Allowing Full Server Takeover Found in Concrete5 CMS

Related: Hackers Scanning for Apache Tomcat Servers Vulnerable to Ghostcat Attacks

view counter

Eduard Kovacs (@EduardKovacs) is a contributing editor at SecurityWeek. He worked as a high school IT teacher for two years before starting a career in journalism as Softpedia’s security news reporter. Eduard holds a bachelor’s degree in industrial informatics and a master’s degree in computer techniques applied in electrical engineering.

Previous Columns by Eduard Kovacs:
Tags:

http://feedproxy.google.com/~r/Securityweek/~3/KSOYVcR_N68/jetty-flaw-can-be-exploited-inflate-targets-cloud-bill-cause-disruption




VMware Patches Remote Code Execution Vulnerability in View Planner

VMware this week announced the availability of a security patch for VMware View Planner, to address a vulnerability leading to remote code execution.

The benchmarking tool provides consistent methodology for the comparison of virtual desktop deployment platforms, measuring both the performance of application operations and the scalability of the deployment platform.

With the release of View Planner 4.6 Security Patch 1 on March 2, VMware fixes CVE-2021-21978, an issue that could allow an attacker to execute code remotely. The bug features a CVSS score of 8.6.

In its advisory, VMware explains that the bug is, in fact, rooted in improper input validation, complemented by lack of authorization.

Together, these issues could be abused for the upload of arbitrary files in the logupload web application, which could then lead to code execution.

According to the company, an attacker looking to exploit this bug needs to have already compromised the network in order to access View Planner Harness.

The attacker could then abuse the vulnerability to upload a specially crafted file and then execute it, which would essentially result in the execution of code remotely, within the logupload container.

The company also notes that it considers the vulnerability “to be in the Important severity range,” and that the bug was privately reported.

VMware recommends that all affected customers apply the security patch that was released this week, to ensure they are protected.

The issue was reported by Mikhail Klyuchnikov, a researcher with Positive Technologies. VMware makes no mention of the vulnerability being exploited in the wild.

Related: Hackers Scanning for VMware vCenter Servers Affected by Critical Vulnerability

Related: Vulnerability in VMware vSphere Replication Can Facilitate Attacks on Enterprises

Related: Hackers Can Compromise VMware vCenter Server Via Newly Patched Flaw

view counter

Ionut Arghire is an international correspondent for SecurityWeek.

Previous Columns by Ionut Arghire:
Tags:

http://feedproxy.google.com/~r/Securityweek/~3/tknD4uzspyg/vmware-patches-remote-code-execution-vulnerability-view-planner




Google Vows to Stop Tracking Individual Browsing for Ads

Google on Wednesday pledged to steer clear of tracking individual online activity when it begins implementing a new system for targeting ads without the use of so-called “cookies.”

The internet giant’s widely used Chrome browser this month will begin testing an alternative to the tracking practice that it believes could improve online privacy while still enabling advertisers to serve up relevant messages.

“We’re making explicit that once third-party cookies are phased out, we will not build alternate identifiers to track individuals as they browse across the web, nor will we use them in our products,” ads privacy and trust product management director David Temkin said in a blog post.

“Advances in aggregation, anonymization, and on-device process and other privacy-preserving technologies offer a clear path to replacing individual identifiers.”

The move comes with Google hammered by critics over user privacy, and increased scrutiny of privacy and protecting people’s data rights.

Growing fear of cookie-tracking has prompted support for internet rights legislation such as GDPR in Europe.

Temkin described the new Google system as “privacy-preserving… while still delivering results for advertisers and publishers.” 

Safari and Firefox browsers have already done away with third-party cookies, but they are still used at the world’s most popular browser, Chrome.

Chrome accounted for 63 percent of the global browser market last year, according to StatCounter.

Last month, Google unveiled the results of tests showing an alternative to cookies called Federated Learning of Cohorts (FLoC) which identifies groups of people with common interests without individualized tracking.

Some businesses have objected to the Google plan claiming it will force more advertisers into its “walled garden.”

view counter

© AFP 2020

Previous Columns by AFP:
Tags:

http://feedproxy.google.com/~r/Securityweek/~3/6gKGtTuhJ1E/google-vows-stop-tracking-individual-browsing-ads




Should You Be Concerned About the Recently Leaked Spectre Exploits?

A researcher revealed on Monday that some exploits for the notorious CPU vulnerability known as Spectre were uploaded recently to the VirusTotal malware analysis service. While some experts say this could increase the risk of exploitation for malicious purposes, others believe there is no reason for concern.

The Spectre and Meltdown vulnerabilities were disclosed in January 2018, when researchers warned that billions of devices powered by processors from Intel, AMD and other vendors were impacted. An attacker with access to the targeted system can exploit the flaws to obtain potentially sensitive data. Patches and mitigations have been released, but many devices likely remain vulnerable, including due to the impact of the patches on performance and the relatively low risk of exploitation in the wild.

Spectre exploit leakedIn a blog post titled Spectre exploits in the “wild”, researcher Julien Voisin shared a brief analysis of a Spectre exploit for Linux that had been uploaded to VirusTotal in early February. The exploit attempts to leverage CVE-2017-5753 — this is one of the two CVEs assigned to the Spectre flaw — for privilege escalation. A Windows exploit was also found on VirusTotal.

An analysis of the exploits spotted by Voisin showed that they came from offensive security firm Immunity and they were part of its CANVAS product, which includes hundreds of exploits, an automated exploitation system, and an exploit development framework for pentesters and researchers.

The Spectre exploit was developed by Immunity in 2018, shortly after the existence of the Spectre and Meltdown vulnerabilities came to light. However, a copy of CANVAS containing more than 800 exploits, including the Spectre exploits, started emerging recently on hacker forums, which is likely how they ended up on VirusTotal.

Voisin noted that the exploit still had a zero detection rate on VirusTotal when he had blogged about it. At the time of writing, it’s detected by 27 of 63 engines on VirusTotal.

Some members of the cybersecurity community have raised concerns about the availability of what some people described as “weaponized Spectre exploits.”

“More than three years after the discovery and publication of the Spectre vulnerability, there are signs that it could be weaponized, not just a POC. This new discovery has increased the potential risk,” Tal Morgenstern, co-founder and CPO of vulnerability remediation orchestration firm Vulcan Cyber, said via email.

However, he added, “We still need to consider that this is a local exploit, where an attacker would need to gain remote access by other means, making this a multistep attack.”

Chris Morgan, senior cyber threat intelligence analyst at Digital Shadows, a San Francisco-based provider of digital risk protection solutions, also believes the wider availability of exploits could increase the risk posed by the flaws, particularly in the case of users with older and unpatched operating systems, but he also admitted that “the technical requirements of a threat actor are still significant.”

Moritz Lipp, one of the researchers who discovered the Spectre vulnerability, told SecurityWeek that he does not believe the wider availability of the exploits makes a big difference now, pointing out that there are some conditions for the exploit to work, including the SMAP CPU feature to be disabled and the presence of an older version of the Linux kernel.

Lipp also suggested that it wouldn’t have been difficult for threat actors to create such exploits for Spectre given the proof-of-concepts (PoCs) that have been made available by the team that discovered Spectre and by researchers who found other similar CPU vulnerabilities.

Voisin told SecurityWeek that he published his blog post “to show that Spectre is a credible vector, but it doesn’t mean that everyone is able to write exploits for it.”

“Having a commercial-grade [exploit] shows that serious players have access to this kind of vectors,” the researcher explained. “It does increase a bit the chances of attacks of course, but only on the supported systems.”

He added that “there are better ways to escalate privileges on Linux, like the Baron Samedit exploit for sudo, or whatever privesc of the week on Windows.”

view counter

Eduard Kovacs (@EduardKovacs) is a contributing editor at SecurityWeek. He worked as a high school IT teacher for two years before starting a career in journalism as Softpedia’s security news reporter. Eduard holds a bachelor’s degree in industrial informatics and a master’s degree in computer techniques applied in electrical engineering.

Previous Columns by Eduard Kovacs:
Tags:

http://feedproxy.google.com/~r/Securityweek/~3/avXyl2V8Ytw/should-you-be-concerned-about-recently-leaked-spectre-exploits




Microsoft Expands Secured-core to Servers, IoT Devices

Microsoft this week announced Secured-core Server and Edge Secured-core, two solutions aimed at improving the security of servers and connected devices.

Initially announced in 2019, Secured-core is the result of a partnership between Microsoft and hardware manufacturers, and its goal is to add a security layer that combines identity, virtualization, operating system, hardware and firmware protection capabilities.

When it introduced Secured-core PCs, Microsoft said they were ideal for industries handling highly sensitive information, such as financial services, government, and healthcare. The company is now expanding coverage to servers and Internet of Things (IoT) devices, aiming to protect them against common attack vectors.

“Secured-core functionality helps proactively close the door on the many paths that attackers may try to exploit, and it allows IT and SecOps teams to optimize their time across other priorities,” the tech company says.

Secured-core Server aims to deliver not only advanced protection, but also simplified security and preventative defense. Thus, both hardware and firmware that manufacturers bring to market should satisfy specific security requirements.

Secured-core certified systems that feature secure hardware platforms are available for both Windows Server and validated Azure Stack HCI solutions, the company says.

The expanded coverage is accompanied by new functionality in the Windows Admin Center, allowing customers to configure the OS security features of Secured-core for Windows Server and Azure Stack HCI systems directly from a web browser. Manufacturers have the option to enable OS features for Azure Stack HCI systems.

Secured-core Servers feature hardware root-of-trust (courtesy of capabilities such as BitLocker, which leverages Trusted Platform Module 2.0), firmware protection (with support for Dynamic Root of Trust of Measurement (DRTM) technology), and support for virtualization-based security (VBS) and hypervisor-based code integrity (HVCI) to isolate parts of the OS and protect against entire classes of vulnerabilities.

Edge Secured-core, on the other hand, seeks to improve the built-in security of IoT devices running a full OS and also brings Secured-core to Linux.

Microsoft is also making Edge Secured-core public preview available within the Azure Certified Device program. Certified devices meet additional security requirements related to device identity, data protection, device updates, secure boot, OS hardening, and vulnerability disclosures.

Edge Secured-core devices feature a zero-trust attestation model, a built-in security agent, and security by default, to enforce system integrity, deliver hardware-based device identity, be remotely manageable, stay updated, and deliver protection for data.

Related: For Microsoft, Security is a $10 Billion Business

Related: Microsoft Defender ATP Gets UEFI Scanner

view counter

Ionut Arghire is an international correspondent for SecurityWeek.

Previous Columns by Ionut Arghire:
Tags:

http://feedproxy.google.com/~r/Securityweek/~3/B0mtInPi1E8/microsoft-expands-secured-core-servers-iot-devices




Microsoft: Multiple Exchange Server Zero-Days Under Attack by Chinese Hacking Group

Microsoft Exchange Vulnerabilities

Microsoft late Tuesday raised the alarm after discovering Chinese cyber-espionage operators chaining multiple zero-day exploits to siphon e-mail data from corporate Microsoft Exchange servers.

Redmond’s warning includes the release of emergency out-of-band patches for four distinct zero-day vulnerabilities that formed part of the threat actor’s arsenal.

Microsoft pinned the blame on a sophisticated Chinese APT operator called HAFNIUM that operates from leased VPS (virtual private servers) in the United States.

HAFNIUM primarily targets entities in the U.S. across a number of industry sectors, including infectious disease researchers, law firms, higher education institutions, defense contractors, policy think tanks, and NGOs.

The company said its analysts assess with high confidence that HAFNIUM is state-sponsored and operating out of China, based on observed victimology, tactics and procedures.

Supply Chain Security Summit

In all, Microsoft said the attacker chained four zero-days into a malware cocktail targeting its Exchange Server (Outlook Web App) product. The vulnerabilities exposed Microsoft’s customers to remote code excecution attacks, without requiring authentication.

“In the attacks observed, the threat actor used these vulnerabilities to access on-premises Exchange servers which enabled access to email accounts, and allowed installation of additional malware to facilitate long-term access to victim environments,” Microsoft said.

“We strongly urge customers to update on-premises systems immediately,” the company urged.

Here are the raw details on the vulnerabilities being exploited in the wild.

* CVE-2021-26855 is a server-side request forgery (SSRF) vulnerability in Exchange which allowed the attacker to send arbitrary HTTP requests and authenticate as the Exchange server.

* CVE-2021-26857 is an insecure deserialization vulnerability in the Unified Messaging service. Insecure deserialization is where untrusted user-controllable data is deserialized by a program. Exploiting this vulnerability gave HAFNIUM the ability to run code as SYSTEM on the Exchange server. This requires administrator permission or another vulnerability to exploit.

* CVE-2021-26858 is a post-authentication arbitrary file write vulnerability in Exchange. If HAFNIUM could authenticate with the Exchange server then they could use this vulnerability to write a file to any path on the server. They could authenticate by exploiting the CVE-2021-26855 SSRF vulnerability or by compromising a legitimate admin’s credentials.

* CVE-2021-27065 is a post-authentication arbitrary file write vulnerability in Exchange. If HAFNIUM could authenticate with the Exchange server then they could use this vulnerability to write a file to any path on the server. They could authenticate by exploiting the CVE-2021-26855 SSRF vulnerability or by compromising a legitimate admin’s credentials.

Enterprise defenders can find additional techincal details in this blog post from the Microsoft Server team.

Microsoft said the attacks included three steps. First, the group gained access to an Exchange Server either with stolen passwords or by using the previously undiscovered vulnerabilities to disguise as someone who should have access. Second, the attackers created a web shell to control the compromised server remotely. That remote access was then used – run from the U.S.-based private servers – to steal data from an organization’s network.

In campaigns unrelated to this new batch of zero-day vulnerabilities, Microsoft said it found HAFNIUM interacting with victim Office 365 tenants. “While they are often unsuccessful in compromising customer accounts, this reconnaissance activity helps the adversary identify more details about their targets’ environments,” the company explained.  

The attackers were also able to download the Exchange offline address book from compromised systems, which contains information about an organization and its users, Microsoft added.

Cybersecurity firm Volexity, which was credited by Microsoft for reporting different parts of the attack chain, has published a blog post with technical details and a video demonstrating exploitation in action, along with known attacker IP addresses connected to the attacks. Volexity said it detected anomalous activity from two of its customers’ Microsoft Exchange servers in January 2021, which led to discovery of the attacks.

view counter

Ryan Naraine is Editor-at-Large at SecurityWeek and host of the popular Security Conversations podcast series. Ryan is a journalist and cybersecurity strategist with more than 20 years experience covering IT security and technology trends. He is a regular speaker at cybersecurity conferences around the world.
Ryan has built security engagement programs at major global brands, including Intel Corp., Bishop Fox and Kaspersky GReAT. He is a co-founder of Threatpost and the global SAS conference series. Ryan’s career as a journalist includes bylines at major technology publications including Ziff Davis eWEEK, CBS Interactive’s ZDNet, PCMag and PC World.
Follow Ryan on Twitter @ryanaraine.

Previous Columns by Ryan Naraine:
Tags:

http://feedproxy.google.com/~r/Securityweek/~3/N3Tfx1nZPIk/microsoft-4-exchange-server-zero-days-under-attack-chinese-apt-group




Hackers Control Perl.com Domain Months Before Hijack

The Perl.com domain was hijacked in January 2021, but hackers seemingly took control of it four months prior, in September 2020.

Serving articles about the Perl programming language since 1997 and managed by The Perl Foundation, the domain started pointing to a parked site at the end of January, with evidence suggesting connections to sites distributing malware.

The issue, some of those involved with maintaining the site said at the time, was related to an account hijack that resulted in an unknown party being able to grab the domain for ten years.

In a post on Sunday, Brian Foy, senior editor of Perl.com and author of several books on Perl, explains that the account hijack appears to have been, in fact, an attack on the domain name registrar Network Solutions.

The attack, he explains, took place in September 2020 and might have resulted in several other domains being compromised.

“We think that there was a social engineering attack on Network Solutions, including phony documents and so on. There’s no reason for Network Solutions to reveal anything to me, but I did talk to other domain owners involved and this is the basic scheme they reported,” he notes.

In December, the hackers transferred the domain to the BizCN registrar. Although the domain was compromised in September, ICANN prohibits the transfer of a domain for 60 days following the updating of contact info.

The attackers also renewed the domain for two more years and, in January 2021, transferred it once again, this time to Key Systems, GmbH.

“This latency period avoids immediate detection, and bouncing the domain through a couple registrars makes the recovery much harder,” Foy says.

Following the transfer to Key Systems, however, the fraudulent registrant also listed the Perl.com on domain marketplace Afternic, for $190,000.

The domain was back in the hands of Tom Christiansen, the rightful owner, in early February. However, with security products quick to blacklist it and some DNS servers sinkholing it, it took a while longer for everything to be restored to normal.

“I think we’re fully back,” Foy notes, adding that the team is working on ensuring that such hijacking doesn’t happen again.

Related: Expired Domain Allowed Researcher to Hijack Country’s TLD

Related: Over 600 Microsoft Subdomains Can Be Hijacked: Researchers

view counter

Ionut Arghire is an international correspondent for SecurityWeek.

Previous Columns by Ionut Arghire:
Tags:

http://feedproxy.google.com/~r/Securityweek/~3/p9CJo1E5Kt8/hackers-control-perlcom-domain-months-hijack




Google Patches Critical Remote Code Execution Vulnerability in Android

Google this week announced the release of patches for 37 vulnerabilities as part of the Android security updates for March 2021, including a fix for a critical flaw in the System component.

Tracked as CVE-2021-0397 and affecting Android 8.1, 9, 10, and 11 releases, the security issue could allow an attacker to execute code remotely on a vulnerable device.

“The most severe of these issues is a critical security vulnerability in the System component that could enable a remote attacker using a specially crafted transmission to execute arbitrary code within the context of a privileged process,” Google explains.

The bug was addressed as part of the 2021-03-01 security patch level, which also brings patches for nine other issues, including six more in the System component, one affecting Android runtime, and two impacting Framework.

All of these flaws were rated high severity, with their exploitation leading to remote code execution (three bugs), elevation of privilege (five issues), and information disclosure (one vulnerability).

A total of 27 other security holes were addressed as part of the 2021-03-05 security patch level, including one in Kernel components, four in Qualcomm components, and 22 in Qualcomm closed-source components.

The issues were rated high severity, except for five bugs in the Qualcomm closed-source components, which feature a severity rating of critical.

Google’s March 2021 Android Security Bulletin also makes reference to a vulnerability included in Project Mainline components, namely CVE-2021-0390, which affects Wi-Fi.

This week, Google also announced the release of security patches for 43 vulnerabilities affecting Pixel devices. The bugs impact Framework (6), Media framework (5), System (11), Kernel components (19), Qualcomm components (1), and Qualcomm closed-source components (1).

The issues could lead to elevation of privilege, information disclosure, and denial of service. Eight of the bugs were rated high severity, with the remaining 35 considered moderate risk.

Pixel devices running a security patch level of 2021-03-05 or later have fixes for all bugs included in the March 2021 Android Security Bulletin and Pixel Update Bulletin.

Related: Google Patches Over a Dozen High-Severity Privilege Escalation Flaws in Android

Related: Google Releases January 2021 Security Updates for Android

Related: December 2020 Android Updates Patch 46 Vulnerabilities

view counter

Ionut Arghire is an international correspondent for SecurityWeek.

Previous Columns by Ionut Arghire:
Tags:

http://feedproxy.google.com/~r/Securityweek/~3/8eGhe7jHUx8/google-patches-critical-remote-code-execution-vulnerability-android