DOCSLIB.ORG

Release Notes for Android

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

BlackBerry UEM Client for Android Release Notes 12.38.2.156999 2021-06-18Z | | 2 Contents What's new in BlackBerry UEM Client for Android............................................. 4 Fixed issues...................................................................................................... 5 Known issues....................................................................................................7 Legal notice...................................................................................................... 9 | | iii What's new in BlackBerry UEM Client for Android What's New in BlackBerry UEM Client for Android 12.38.2.156999 • Bug fixes only. What's New in BlackBerry UEM Client for Android 12.38.1.156983 • Support for updates: Updating from UEM Client version 12.34.x and earlier is no longer supported. You must be running UEM Client version 12.35.x or later to update to the latest version. Devices running an older version must be reactivated. • Device reporting: Changes were made to how the UEM Client reports MEID or IMEI values of devices to UEM. What's new in BlackBerry UEM Client for Android 12.38.0.156961 • New activation method: You can now activate a device using your organization’s identity provider such as Okta or Ping Identity. Administrators must configure this option in the BlackBerry UEM and Enterprise Identity administration console. This feature requires UEM 12.14. • Password change: On Samsung devices, changing your password is now easier when your administrator resets it. • Certificate enrollment: Administrators can now enable a setting in the user credential profiles that allows you to dismiss certificate enrollment and complete it later. • Android support: Devices running Android 7 are no longer supported. | What's new in BlackBerry UEM Client for Android | 4 Fixed issues Fixed issues in BlackBerry UEM Client for Android 12.38.2.156999 On Samsung devices running Android 10 or 11, users could access other apps even though the device was assigned an App Lock mode profile with the Work space only (Android Enterprise) activation type. (EMA-16445) On some devices that were activated with a Samsung Knox workspace, users were prompted to enter the certificate password to install the certificate from the shared certificate profile. (EMA-16419) Fixed issues in BlackBerry UEM Client for Android 12.38.1.156983 On BlackBerry devices powered by Android, the Bluetooth capabilities may have been disabled even though it was allowed by the IT policy. (EMA-16397) When you tried to activate an Android 11 device with the Work space only or Work and personal - full control (Android Enterprise) activation type, but the Work and personal - user privacy activation type was ranked with highest priority, the “Unable to activate device - Unsupported activation type" error message displayed. (EMA-16382) On Android 10 devices, users were not prompted to select a certificate for authentication when trying to access the intranet in a browser. (EMA-16162) After activating an Android 11 device with the Work and personal - full control (Android Enterprise) activation type, you could not install apps from Google Play in the personal space. (EMA-16113) Fixed issues in BlackBerry UEM Client for Android 12.38.0.156961 When you tried to activate Samsung Knox device, sometimes the "Error 102" message displayed and activation was not successful. (EMA-16339) You could not install an app if an administrator set an app config payload with an empty itemListValue. (EMA-16250) On some Android 11 devices, the UEM Client got stuck on the loading screen after trying to unlock the app. (GD-54473) On devices running Android 11, you could not unlock the work space using the facial recognition feature even though the IT policy allowed it. Note that after upgrading to Android 11, you must manually enable facial recognition for the workspace through the device settings. (EMA-16201) On Android 11 devices activated with the Work space only (Android Enterprise) activation type, device logs could not be gathered. (EMA-16120) The status of the "Trust agent inactivity timeout" IT policy setting incorrectly displayed as "Password expiration timeout" on the Assigned IT Policy screen. (EMA-16026) | Fixed issues | 5 On some devices running Android 11, during activation with the Work and personal - user privacy (Android Enterprise) activation type, the device App Info screen of the UEM Client appeared after setting the work space password. (EMA-16021) On BlackBerry devices running Android 8.1, after setting a device password during activation, the UEM Client was minimized. (EMA-16012) When activating a Samsung Knox device with the Work and personal - full control (Android Enterprise) activation type, after setting the work space password and device password, the device password screen persisted in a second app window. (EMA-15930) On Android devices that are activated with the Work space only (Android Enterprise) activation type and assigned an app lock mode profile, the UEM Client and Google Play store did not appear on the home screen. (EMA-14214) | Fixed issues | 6 Known issues Issues that are new in this release are noted with an asterisk (*). * On BlackBerry UEM dark site servers, users cannot activate their devices using the alternate FQDN if it resolves to another FQDN. (EMA-16474) * On Android 11 devices activated with the Work and personal - full control (Android Enterprise) activation type, the user cannot configure Smart Lock settings on the device even though the IT policy rules allow it. (EMA-16454) * If you try to take a screenshot of the UEM Client activation screens (for example, for training purposes), the "Can't take screenshot due to security policy" error message displays even though the device is not activated yet. (EMA-16439) If an administrator changes the password policy rule for the workspace of Samsung Knox devices and the workspace password that was set on a device is no longer compliant, the error message (“Device password does not meet requirements set by the administrator or it’s expired”) displays on the Compliance Report screen in UEM Client. The error message should refer to the “Workspace password” instead. (EMA-16425) When the IT policy rule requires a workspace password and a device password is already set prior to activating a device using the Work and personal - full control (Android Enterprise) activation type, the user is not prompted to set a work space password during activation. (EMA-16279) During activation, the user must set a complex password for the work space even though the IT policy is set to numeric or alphanumeric. (EMA-16254) When trying to activate Samsung Galaxy S20 model devices that are running Android 11, an “Error 3006” message appears and activation is not successful when using the Work and personal - full control (Android Enterprise fully managed device with a work profile) activation type with the ‘When activating Android Enterprise devices, enable premium UEM functionality such as BlackBerry Secure Connect Plus’ and ‘Enable Samsung Knox DualDar Workspace’ options selected in the activation profile. (EMA-16075) When activating a Samsung Knox device, if the screen times out at the Knox license activation screen, the activation is not successful when you try to continue. (EMA-16046) On some European models of Samsung devices running Android 11, the device Welcome screen appears during activation when using the Work and personal - full control (Android Enterprise fully managed device with a work profile) activation type. The device is activated correctly and the user can follow device setup screens. (EMA-16014) On some Samsung devices that are activated using the Work and personal - full control (Android Enterprise fully managed device with a work profile) activation type, after upgrading to Android 11, the compliance profile incorrectly restricts apps in the personal space. (EMA-15960) On Samsung OneUI Core devices that are activated with an Android Enterprise activation type and the premium option enabled, the device may not work correctly when it calls any Samsung Knox APIs because it is not a Samsung Knox device. For a list of Samsung Knox devices, visit the Samsung website. (EMA-15736) | Known issues | 7 On devices running Android 11 that are activated with Work space only and Work and personal - full control (Android Enterprise) activation types, the "Set time automatically" and "Obtain time zone from network" IT policy rules are not enforced. (EMA-15649) On Samsung devices activated with the Work and personal - full control (Android Enterprise fully managed device) non-premium activation type, when an administrator unassigns an app, the app isn’t uninstalled but is instead grayed out and cannot be opened. (EMA-14851) Workaround: On the device, manually uninstall the app. On Samsung Knox devices that are activated with the Work space only (Android Enterprise fully managed device) activation type, the device does not establish a BlackBerry Secure Connect Plus connection if the administrator disables the “Allow user-configured VPN in workspace” IT policy rule. For more information about this issue, visit support.blackberry.com/community to read article 58735. (BSCP-789) When activating a Samsung device running Android 8 with the Work space only or Work space only (Premium) activation types, the facial recognition feature on the device is not available. (EMA-9819) On Samsung Knox 3.0+ devices activated with the Work space only (Samsung Knox) activation type, when the “Disable work space” command is sent to the device, the user sees the password entry screen when trying to access the workspace instead of a locked screen. Later, when the “Enable work space” command is sent to the device, the keyboard does not appear correctly when the user tries to enter the password. (EMA-9809) Workaround: If the keyboard doesn’t appear correctly, press the Power button twice. For Samsung Knox 3.0+ devices activated with the Work space only (Samsung Knox) activation type, when the "Reset workspace password" command is sent to the device, the password reset screen does not display if the device is locked. The user can not access their work space until they set a new password.
Recommended publications
  • Benyamin Kohanim, Et Al. V. Blackberry Limited, Et Al. 13-CV

    Benyamin Kohanim, Et Al. V. Blackberry Limited, Et Al. 13-CV

    Case 1:13-cv-07132-TPG Document 12 Filed 03/25/14 Page 1 of 5 tPDCSDNY DOCUMENT UNITED STATES DISTRICT COURT ELECmONICA:ix P1St) SOUTHERN DISTRICT OF NEW YORK i _Jl ---------------------------------x jDATEF1LED:ZV('t I - MARVIN PEARLSTEIN, individually and on behalf of all others similarly situated, 13 Civ. 7060 (TPG) Plaintiff, - against - BLACKBERRY LIMITED (formerly known as RESEARCH IN MOTION LIMITED), THORSTEN HEINS, and BRIAN BIDUKKA, Defendants. ---------------------------------x BENYAMIN KOHANIM, individually and on behalf of all others similarly situated, 13 Civ. 7132 (TPG) Plaintiff, - against - BLACKBERRY LIMITED, et al., Defendants. ---------------------------------x VU TRAN, individually and on behalf of all others similarly situated, 13 Civ. 7972 (TPG) Plaintiff, - against - BLACKBERRY LIMITED, et al., ORDER Defendants. ---------------------------------x - Case 1:13-cv-07132-TPG Document 12 Filed 03/25/14 Page 2 of 5 Before the court are three separate but related class-action lawsuits against BlackBerry Limited, the telecommunications company known best for its line of BlackBerry mobile devices. Plaintiffs allege that Blackberry published a series of materially false and misleading statements regarding the company's financial projections and the new BlackBerry 10 device. Pursuant to Federal Rule of Civil Procedure 42(a), plaintiffs now move to consolidate the cases and to appoint a lead plaintiff and lead counsel pursuant to the Private Securities Litigation Reform Act ("PSLRA"), 15 U.S.C. § 78u-4. For the reasons stated more fully in court on March 14, 2014, the court (1) grants the motion to consolidate the actions filed as 13 Civ. 7060 (TPG), 13 Civ. 7132 (TPG), and 13 Civ. 7972 (TPG); appoints Todd Cox and Mary Dinzik as lead plaintiff; and appoints Kahn, Swick & Foti, LLC as lead counsel.
  • Android (Operating System) 1 Android (Operating System)

    Android (Operating System) 1 Android (Operating System)

    Android (operating system) 1 Android (operating system) Android Home screen displayed by Samsung Nexus S with Google running Android 2.3 "Gingerbread" Company / developer Google Inc., Open Handset Alliance [1] Programmed in C (core), C++ (some third-party libraries), Java (UI) Working state Current [2] Source model Free and open source software (3.0 is currently in closed development) Initial release 21 October 2008 Latest stable release Tablets: [3] 3.0.1 (Honeycomb) Phones: [3] 2.3.3 (Gingerbread) / 24 February 2011 [4] Supported platforms ARM, MIPS, Power, x86 Kernel type Monolithic, modified Linux kernel Default user interface Graphical [5] License Apache 2.0, Linux kernel patches are under GPL v2 Official website [www.android.com www.android.com] Android is a software stack for mobile devices that includes an operating system, middleware and key applications.[6] [7] Google Inc. purchased the initial developer of the software, Android Inc., in 2005.[8] Android's mobile operating system is based on a modified version of the Linux kernel. Google and other members of the Open Handset Alliance collaborated on Android's development and release.[9] [10] The Android Open Source Project (AOSP) is tasked with the maintenance and further development of Android.[11] The Android operating system is the world's best-selling Smartphone platform.[12] [13] Android has a large community of developers writing applications ("apps") that extend the functionality of the devices. There are currently over 150,000 apps available for Android.[14] [15] Android Market is the online app store run by Google, though apps can also be downloaded from third-party sites.
  • What's New in BES12 Cloud 711-60712-123 Published: 2016-06-20 SWD-20160620151902701 Contents

    What's New in BES12 Cloud 711-60712-123 Published: 2016-06-20 SWD-20160620151902701 Contents

    Reference Guide What's New in BES12 Cloud 711-60712-123 Published: 2016-06-20 SWD-20160620151902701 Contents What's new in BES12 Cloud ...........................................................................5 Supported features by device type.......................................................................................................5 Compatibility and requirements.........................................................................................................11 BES12 Cloud Architecture and data flows.....................................................12 Architecture: BES12 Cloud solution................................................................................................... 12 Architecture: BES12 Cloud and BlackBerry Secure Connect Plus.......................................................14 Architecture: BES12 Cloud and the BlackBerry Gatekeeping Service................................................. 15 Architecture: Android for Work.......................................................................................................... 16 Architecture: KNOX Workspace......................................................................................................... 17 Activating devices........................................................................................ 19 Data flow: Activating a BlackBerry 10, iOS, Android, or Windows device............................................. 19 Data flow: Activating an OS X device.................................................................................................
  • A Comparative Analysis of Mobile Operating Systems Rina

    A Comparative Analysis of Mobile Operating Systems Rina

    International Journal of Computer Sciences and Engineering Open Access Research Paper Vol.-6, Issue-12, Dec 2018 E-ISSN: 2347-2693 A Comparative Analysis of mobile Operating Systems Rina Dept of IT, GGDSD College, Chandigarh ,India *Corresponding Author: [email protected] Available online at: www.ijcseonline.org Accepted: 09/Dec/2018, Published: 31/Dec/2018 Abstract: The paper is based on the review of several research studies carried out on different mobile operating systems. A mobile operating system (or mobile OS) is an operating system for phones, tablets, smart watches, or other mobile devices which acts as an interface between users and mobiles. The use of mobile devices in our life is ever increasing. Nowadays everyone is using mobile phones from a lay man to businessmen to fulfill their basic requirements of life. We cannot even imagine our life without mobile phones. Therefore, it becomes very difficult for the mobile industries to provide best features and easy to use interface to its customer. Due to rapid advancement of the technology, the mobile industry is also continuously growing. The paper attempts to give a comparative study of operating systems used in mobile phones on the basis of their features, user interface and many more factors. Keywords: Mobile Operating system, iOS, Android, Smartphone, Windows. I. INTRUDUCTION concludes research work with future use of mobile technology. Mobile operating system is the interface between user and mobile phones to communicate and it provides many more II. HISTORY features which is essential to run mobile devices. It manages all the resources to be used in an efficient way and provides The term smart phone was first described by the company a user friendly interface to the users.
  • Blackberry UEM + Android Tailor Solutions to Your Business with Android

    Blackberry UEM + Android Tailor Solutions to Your Business with Android

    Data Sheet BlackBerry UEM + Android Tailor solutions to your business with Android Android powers more smartphones in the enterprise than any mobile OS1 and most organizations around the world are using Android to get work done. Together, BlackBerry UEM and Android allow you to deploy and manage devices securely and consistently across all users in your organization. From corporate owned to employee enabled devices, BlackBerry gives you the ability to support all Android users in your enterprise. Stronger Together BlackBerry UEM brings comprehensive Unified Endpoint Management to Android. The BlackBerry UEM Advantage BlackBerry UEM offers a rich set of integrations that allow IT to manage any Android device including smartphones, tablets and task specific devices such as wearable computers in a simple consistent manner leveraging the core enterprise features found in the Android platform. Through the unified endpoint management console, policy control can be enforced across diverse and growing fleets of devices and apps. Coupled with BlackBerry’s trusted end-to-end security model, BlackBerry UEM provides the flexibility and security you need to keep your employees connected and protected. • Simplified Management: BlackBerry UEM provides a unified management console designed to simplify IT administration. • Full Breadth of Android Configuration and Deployment Options: BlackBerry UEM provides a comprehensive set of tools to provisionand manage devices and apps using Android enterprise features and services. • Networking Enhancements: BlackBerry Connectivity, powered by BlackBerry's global secure communications infrastructure, securely extends mobile access to work resources located behind the firewall, without the requirement for separate VPN infrastructure. • Familiar Environments for Users: End-users benefit from a familiar and intuitive Android user experience for mobile work applications.
  • A Detailed Guide to Android 11

    A Detailed Guide to Android 11

    International Research Journal of Engineering and Technology (IRJET) e-ISSN: 2395-0056 Volume: 08 Issue: 01 | Jan 2021 www.irjet.net p-ISSN: 2395-0072 A Detailed Guide to Android 11 Mr. Shubham Randive Student, Semester-III, MSC(I.T.), Keraleeya Samajam’s Model College, Dombivali East, Thane, Maharashtra, India ---------------------------------------------------------------------***---------------------------------------------------------------------- Abstract - Android 11 is shaping the leading edge of mobile Settings selections on top of the display. We expect this innovation with advanced machine-learning. Android 11 feature to make it to the final version this time around. contains a various features such as Live option, foldables, 5G networks, smart reply in notifications, Dark Theme, Gesture Chat Bubbles in Android 11 Navigation, Setting panels, sharing shortcut, focus mode, family link, location restrictions, protection from device Bubbles are basically like Facebook Messenger chat heads tracking, limiting application access to external storage, but for the other applications. The feature was actually enterprise security, Device-specific security measures. Android launched with Android 10. Google is finally bringing it to the 11 is better in performance as compared to android 10 and in forefront. It works with applications like Telegram and some parts to IOS 14. WhatsApp just fine. Key Words: Features; Android 11 vs Android 10;Android 11 Share menu pinning vs 1OS 14; Pros and Cons; The feature was introduced with Android 7 Nougat. 1. INTRODUCTION However, the current Android sharing menu has been a mess. Android 11 will allow you to pin 4 apps you share to Android is software platform and operating system for the most frequently, to the top of share menu.
  • Blackberry Limited

    Blackberry Limited

    UNITED STATES SECURITIES AND EXCHANGE COMMISSION Washington, D.C. 20549 __________________________________________________________ FORM 40-F REGISTRATION STATEMENT PURSUANT TO SECTION 12 OF THE SECURITIES EXCHANGE ACT OF 1934 or ANNUAL REPORT PURSUANT TO SECTION 13(a) OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 For the fiscal year ended February 28, 2017 Commission File Number 0-29898 __________________________________________________________ BlackBerry Limited (Exact name of Registrant as specified in its charter) Ontario 3661 Not Applicable (Province or other Jurisdiction (Primary Standard Industrial (I.R.S. Employer of Incorporation or Organization) Classification Code Number) Identification No) 2200 University Ave East Waterloo, Ontario, Canada, N2K 0A7 (519) 888-7465 (Address and telephone number of Registrant’s principal executive offices) BlackBerry Corporation 3001 Bishop Drive, Suite 400 San Ramon, California, USA 94583 (925) 242-5660 (Name, address and telephone number of agent for service in the United States) __________________________________________________________ Securities registered or to be registered pursuant to Section 12(b) of the Act: Title of each class Name of each exchange where registered Common Shares, without par value Toronto Stock Exchange Common Shares, without par value NASDAQ Stock Market, LLC Securities registered or to be registered pursuant to Section 12(g) of the Act: None Securities for which there is a reporting obligation pursuant to Section 15(d) of the Act: None For annual reports, indicate by check mark the information filed with this Form: Annual information form Audited annual financial statements Indicate the number of outstanding shares of each of the Registrant’s classes of capital or common stock as of the close of the period covered by this annual report.
  • Blackberry Limited (Exact Name of Registrant As Specified in Its Charter)

    Blackberry Limited (Exact Name of Registrant As Specified in Its Charter)

    UNITED STATES SECURITIES AND EXCHANGE COMMISSION Washington, D.C. 20549 __________________________________________________________ FORM 40-F REGISTRATION STATEMENT PURSUANT TO SECTION 12 OF THE SECURITIES EXCHANGE ACT OF 1934 or ANNUAL REPORT PURSUANT TO SECTION 13(a) OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 For the fiscal year ended March 1, 2014 Commission File Number 0-29898 __________________________________________________________ BlackBerry Limited (Exact name of Registrant as specified in its charter) Ontario 3,661 Not Applicable (Province or other Jurisdiction (Primary Standard Industrial (I.R.S. Employer of Incorporation or Organization) Classification Code Number) Identification No) 2200 University Ave East Waterloo, Ontario, Canada, N2K 0A7 (519) 888-7465 (Address and telephone number of Registrant’s principal executive offices) BlackBerry Corporation 5000 Riverside Drive, Suite 100E, Irving, Texas, USA 75039 (972) 650-6126 (Name, address and telephone number of agent for service in the United States) __________________________________________________________ Securities registered or to be registered pursuant to Section 12(b) of the Act: Common Shares, without par value Securities registered or to be registered pursuant to Section 12(g) of the Act: None Securities for which there is a reporting obligation pursuant to Section 15(d) of the Act: None For annual reports, indicate by check mark the information filed with this Form: Annual information form Audited annual financial statements Indicate the number of outstanding shares of each of the Registrant’s classes of capital or common stock as of the close of the period covered by this annual report. The Registrant had 526,551,953 Common Shares outstanding as at March 1, 2014.
  • Marvin Pearlstein, Et Al. V. Blackberry Limited, Et Al. 13-CV-07060-Class

    Marvin Pearlstein, Et Al. V. Blackberry Limited, Et Al. 13-CV-07060-Class

    Case 1:13-cv-07060-TPG Document 1 Filed 10/04/13 Page 1 of 35 JUDGEGR1SA UNITED STATES DISTRICT COURT C1 7O6O S1)ITTI-IF1N 1UST121CT (W NkW vnuic IPA, MARVIN PEARLSTEIN, Individually And CIVIL ACTI NO. On Behalf of All Others Similarly Situated, Plaintiff, vs. CLASS ACTION COMPLAINT FOR VIOLATIONS OF FEDERAL SECURITIES LAWS BLACKBERRY LIMITED (formerly known as RESEARCH IN MOTION LIMITED), THORSTEN HEINS, and BRIAN BIDULKA, Defendants. JURY TRIAL DEMANDED NATURE OF THE ACTION Plaintiff Marvin Pearistein ("Plaintiff'), alleges the following based upon the investigation of Plaintiff's counsel, which included a review of United States Securities and Exchange Commission ("SEC") filings by BlackBerry Limited ("BlackBerry" or the "Company")', securities analysts' reports and advisories about the Company, press releases and other public statements issued by the Company and its executives, and media reports about BlackBerry. Plaintiff believes that substantial additional evidentiary support will exist for the allegations set forth herein after a reasonable opportunity for discovery. 1 On July 10, 2013, the Company changed its name from Research in Motion Limited ("RIM") to BlackBerry Limited. Case 1:13-cv-07060-TPG Document 1 Filed 10/04/13 Page 2 of 35 1. This is a securities class action brought on behalf of the purchasers of BlackBerry common stock between September 27, 2012 and September 20, 2013 (the "Class Period"), against BlackBerry and certain of its officers and/or directors (collectively, "Defendants") for violations of the Securities and Exchange Act of 1934 (the "Exchange Act"). The claims asserted herein arise from Defendants' publicly issued materially false and/or misleading during the Class Period.

  • Keep Your Business Driving Forward

    BLACKBERRY SOFTWARE ASSURANCE Keep Your Business Driving Forward Retain your investment with BlackBerry® Software Assurance. Upgrade your existing perpetual BES Client Access Licenses (CALs) and receive perpetual Enterprise Mobility Management (EMM) Corporate licenses1. Software Assurance provides Upgrade2 and Update3 rights, so you always have access to the latest software. Now you can easily support a multi-platform environment with EMM tools that enable you to manage iOS, Android® and BlackBerry® 10 devices. And, with full Upgrade and Update rights, you can effectively maximize the value of your multi-platform environment. This offer will be available January, 2014 with annual subscriptions starting upon purchase. You can purchase BlackBerry Software Assurance directly from BlackBerry or through an Authorized BlackBerry Partner. To order, use Global part Number SRV-00015-380, BlackBerry Software Assurance. What’s included with BlackBerry Software Assurance? 4 • Upgrade your existing BES perpetual licenses and receive BES 10 perpetual EMM Corporate licenses • Leverage BES10 Tools to securely manage your multi-platform environment, including iOS, Android and BlackBerry devices • Incrementally add Software licenses as needed according to your roll-out schedule in order to make the move to BES10 • Benefit from all future major Upgrades and Updates If you purchase Advantage Support or higher levels of support, BlackBerry Software Assurance is included. For more information on BlackBerry Software Assurance and BlackBerry Technical Support Services, visit www.blackberry.com/softwareassurance 1 Cannot be used to Upgrade BES Client Access Licenses (CALs) to other perpetual licenses such as EMM Regulated or Secure Work Space for iOS or Android. 2 An Upgrade is a new major version release of the covered software that provides functional enhancements at the platform-level which materially advance the software’s capabilities.
  • PIP Vulnerability in Android 11

    PIP Vulnerability in Android 11

    PIP Vulnerability in Android 11 TANMAY TYAGI AKSHAY SHARMA ABHINAV 1 Table of Contents ● Introduction ● Key Terms ● Definitions ○ PIP ( Picture-in-Picture ) ○ Android Manifest File ○ Local Privilege Escalation ● Affected Android Versions ● Unaffected Versions ● CVSS Score : CVE-2021 -0485 ● Virtual Environment ● Exploitation ● Mitigation ● References 2 PIP Vulnerability in Android 11 Introduction From 2017, Android imposed certain background execution limitations so that the applications in the background won’t be able to access the camera, microphone and other sensors. This reduced - ❏ notification pop-ups ❏ Advertisements (As apps can’t use microphones to listen for user interests) and improved - ❏ Battery ❏ Performance ❏ Security In PiP mode, there is no special permission required to control the minimum allowed window size so it is possible to create an arbitrary small window which won’t be visible to the user. Using this window, it is possible for an unprivileged application to maintain its foreground stage and bypass security restrictions which were introduced in Android Oreo and later for better performance, health and security. NIST DEF - In getMinimalSize of PipBoundsAlgorithm.java, there is a possible bypass of restrictions on background processes due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. In this paper we will exploit this vulnerability in a virtual lab environment with a Proof of Concept. Confidential Document © Copyright of Safe Security 2021 3 PIP Vulnerability in Android 11 Key terms PIP ( Picture-in-Picture), Android Manifest File, Local Privilege Escalation Definitions PIP ( Picture-in-Picture) It is a Multi Window solution, generally used for video playback and extensively used in Gmaps.
  • The Android Platform Security Model∗

    The Android Platform Security Model∗

    The Android Platform Security Model∗ RENÉ MAYRHOFER, Google and Johannes Kepler University Linz JEFFREY VANDER STOEP, Google CHAD BRUBAKER, Google NICK KRALEVICH, Google Android is the most widely deployed end-user focused operating system. With its growing set of use cases encompassing communication, navigation, media consumption, entertainment, finance, health, and access to sensors, actuators, cameras, or microphones, its underlying security model needs to address a host of practical threats in a wide variety of scenarios while being useful to non-security experts. The model needs to strike a difficult balance between security, privacy, and usability for end users, assurances for app developers, and system performance under tight hardware constraints. While many of the underlying design principles have implicitly informed the overall system architecture, access control mechanisms, and mitigation techniques, the Android security model has previously not been formally published. This paper aims to both document the abstract model and discuss its implications. Based on a definition of the threat model and Android ecosystem context in which it operates, we analyze how the different security measures in past and current Android implementations work together to mitigate these threats. There are some special cases in applying the security model, and we discuss such deliberate deviations from the abstract model. CCS Concepts: • Security and privacy → Software and application security; Domain-specific security and privacy architectures; Operating systems security; • Human-centered computing → Ubiquitous and mobile devices. Additional Key Words and Phrases: Android, security, operating system, informal model 1 INTRODUCTION Android is, at the time of this writing, the most widely deployed end-user operating system.