以下に、パッチレベル 2022-01-01 に該当するセキュリティ脆弱性の各項目の詳細を示します。脆弱性は、影響を受けるコンポーネントごとに分類しています。下記の表に、問題の内容について説明し、CVE ID、関連する参照先、脆弱性のタイプ、重大度、更新対象の AOSP バージョン（該当する場合）を示します。問題の対処法として一般公開されている変更内容（AOSP の変更の一覧など）が参照可能な場合は、バグ ID の欄にその情報へのリンクがあります。複数の変更が同じバグに関係する場合は、バグ ID の後に続く番号で、追加の参照先へのリンクを示します。Android 10 以降を搭載したデバイスは、セキュリティ アップデートと Google Play システム アップデートを受信することがあります。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-08-08 UTC。"],[],[],null,["# Android Automotive OS Update Bulletin—January 2022\n\n*Published January 4, 2022*\n\n\nThe Android Automotive OS (AAOS) Update Bulletin contains details of security vulnerabilities affecting the Android Automotive OS platform. The full AAOS update comprises the security patch level of 2022-01-05 or later from the [January 2022 Android Security Bulletin](/security/bulletin/2022-01-01) in addition to all issues in this bulletin.\n\n\nWe encourage all customers to accept these updates to their devices.\n\n\n| **Note**: Please contact your device supplier for device firmware images.\n\n\nThe most severe of these issues is a high security vulnerability in the AAOS component that could enable a local malicious application to gain access to additional privileges due to a confused deputy. The [severity assessment](/security/overview/updates-resources#severity) is based on the effect that exploiting the vulnerability would possibly have on an affected device, assuming the platform and service mitigations are turned off for development purposes or if successfully bypassed.\n\n### **Announcements**\n\n- In addition to the security vulnerabilities described in the January 2022 Android Security Bulletin, the January 2022 Android Automotive OS Update Bulletin also contains patches specifically for AAOS vulnerabilities as described below.\n\n### **2022-01-01 security patch level vulnerability details**\n\n\nIn the sections below, we provide details for each of the security vulnerabilities that apply to the 2022-01-01 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, [type of vulnerability](#type), [severity](/docs/security/overview/updates-resources#severity), and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID. Devices with Android 10 and later may receive security updates as well as [Google Play system updates](https://support.google.com/android/answer/7680439?).\n\n#### **AAOS**\n\n\nThe most severe vulnerability in this section could enable a local malicious application to gain access to additional privileges due to a confused deputy.\n\n| CVE | References | Type | Severity | Updated AOSP versions |\n|---------------|-------------|------|----------|-----------------------|\n| CVE-2021-1035 | A-195668284 | EoP | High | 10, 12 |\n| CVE-2021-1036 | A-182812255 | EoP | High | 9, 10, 11, 12 |\n| CVE-2021-1037 | A-162951906 | ID | High | 9, 10, 11, 12 |\n\n### **Common questions and answers**\n\n\nThis section answers common questions that may occur after reading this bulletin.\n\n\n**1. How do I determine if my device is updated to address these issues?**\n\n\nTo learn how to check a device's security patch level, read the instructions on the [Google device update schedule](https://support.google.com/android/answer/7680439).\n\n- Security patch levels of 2022-01-01 or later address all issues associated with the 2022-01-01 security patch level.\n\n\nDevice manufacturers that include these updates should set the patch string level to:\n\n- \\[ro.build.version.security_patch\\]:\\[2022-01-01\\]\n\n\nFor some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2022-01-01 security patch level. Please see [this article](https://support.google.com/android/answer/7680439?hl=en) for more details on how to install security updates.\n\n\n**2. What do the entries in the *Type* column mean?**\n\n\nEntries in the *Type* column of the vulnerability details table reference the classification of the security vulnerability.\n\n|------------------|------------------------------|\n| **Abbreviation** | **Definition** |\n| RCE | Remote code execution |\n| EoP | Elevation of privilege |\n| ID | Information disclosure |\n| DoS | Denial of service |\n| N/A | Classification not available |\n\n\n**3. What do the entries in the *References* column mean?**\n\n\nEntries under the *References* column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.\n\n| Prefix | Reference |\n|--------|---------------------------|\n| A- | Android bug ID |\n| QC- | Qualcomm reference number |\n| M- | MediaTek reference number |\n| N- | NVIDIA reference number |\n| B- | Broadcom reference number |\n| U- | UNISOC reference number |\n\n\n**4. What does an \\* next to the Android bug ID in the *References* column mean?**\n\n\nIssues that are not publicly available have an \\* next to the corresponding reference ID. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the [Google Developer site](https://developers.google.com/android/drivers).\n\n\n**5. Why are security vulnerabilities split between this bulletin and device / partner security bulletins, such as the Pixel bulletin?**\n\n\nSecurity vulnerabilities that are documented in this security bulletin are required to declare the latest security patch level on Android devices. Additional security vulnerabilities that are documented in the device / partner security bulletins are not required for declaring a security patch level. Android device and chipset manufacturers may also publish security vulnerability details specific to their products, such as [Google](/security/bulletin/pixel), [Huawei](https://consumer.huawei.com/en/support/bulletin/), [LGE](https://lgsecurity.lge.com/security_updates_mobile.html), [Motorola](https://motorola-global-portal.custhelp.com/app/software-security-page/g_id/6806), [Nokia](https://www.nokia.com/phones/en_int/security-updates), or [Samsung](https://security.samsungmobile.com/securityUpdate.smsb).\n\n### **Versions**\n\n| Version | Date | Notes |\n|---------|-----------------|-------------------|\n| 1.0 | January 4, 2022 | Bulletin Released |"]]
