自 2025 年 3 月 27 日起，我們建議您使用 android-latest-release 而非 aosp-main 建構及貢獻 AOSP。詳情請參閱「Android 開放原始碼計畫變更」。
Android Automotive OS 更新公告 - 2022 年 1 月
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
發布日期：2022 年 1 月 4 日
Android Automotive OS (AAOS) 更新公告列舉對 Android Automotive OS 平台造成影響的安全性漏洞，並說明相關細節。完整的 AAOS 更新除了提供 2022 年 1 月 Android 安全性公告中的安全性修補程式等級 (2022-01-05 之後)，也解決了這個公告列出的所有問題。
我們建議所有客戶接受這些裝置更新。
在這些問題中，最嚴重的就是 AAOS 元件中嚴重程度「高」的安全性漏洞。本機惡意應用程式可藉由混淆代理問題取得額外權限。嚴重程度評定標準是假設平台與服務的因應防護措施基於開發作業需求而關閉，或是遭到有心人士成功規避，然後推算當有人惡意運用漏洞時，使用者裝置會受到多大影響，並據此評定漏洞的嚴重程度。
公告事項
- 除了修補 2022 年 1 月 Android 安全性公告列出的安全性漏洞外，2022 年 1 月 Android Automotive OS 更新公告也專為下文列出的 AAOS 安全性漏洞提供修補程式。
2022-01-01 安全性修補程式等級 - 資安漏洞詳情
下列各節針對 2022-01-01 安全性修補程式等級適用的各項安全性漏洞提供了詳細資訊。我們依照資安問題影響的元件將各項漏洞分門別類，並將問題相關資訊列於下方的表格，包括 CVE ID、相關參考資料、安全漏洞類型、嚴重程度。在適用情況下，我們也會附上更新的 Android 開放原始碼計畫版本。假如有公開變更可以解決某錯誤，該錯誤 ID 會連結到相對應的變更，例如 Android 開放原始碼計畫變更清單。如果單一錯誤有多項相關變更，您可以透過該錯誤 ID 後面的編號連結開啟額外的參考資料。搭載 Android 10 以上版本的裝置可能會收到安全性更新和 Google Play 系統更新。
AAOS
本節中最嚴重的漏洞可能會造成混淆代理問題，讓本機惡意應用程式因而取得額外權限。
| CVE |
參考資料 |
類型 |
嚴重性 |
更新的 Android 開放原始碼計畫版本 |
| CVE-2021-1035
|
A-195668284
|
EoP
|
高
|
10、12
|
| CVE-2021-1036
|
A-182812255
|
EoP
|
高
|
9、10、11、12
|
| CVE-2021-1037
|
A-162951906
|
ID
|
高
|
9、10、11、12
|
常見問題與解答
如果您在閱讀這篇公告後有任何疑問，可參考本節的常見問答。
1. 如何判斷我的裝置軟體版本是否更新並修正問題？
請參閱 Google 裝置更新時間表中的操作說明，瞭解如何查看裝置的安全性修補程式等級。
- 2022-01-01 之後的安全性修補程式等級已解決了所有與 2022-01-01 安全性修補程式等級相關的問題。
提供這些更新的裝置製造商應將修補程式字串等級設定為：
- [ro.build.version.security_patch]:[2022-01-01]
如果是搭載 Android 10 以上版本的裝置，Google Play 系統更新的日期字串應與 2022-01-01 安全性修補程式等級相同。如要進一步瞭解如何安裝安全性更新，請參閱這篇文章。
2. 「類型」欄中的項目代表什麼意義？
在資安漏洞詳情表格中，「類型」欄中的項目代表的是安全性漏洞的類別。
| 縮寫
|
定義
|
| RCE
|
遠端程式碼執行
|
| EoP
|
權限升級
|
| ID
|
資訊外洩
|
| DoS
|
阻斷服務
|
| 無
|
未分類
|
3. 「參考資料」欄中的項目代表什麼意思？
在資安漏洞詳情表格中，「參考資料」欄底下的項目可能會包含一個前置字串，用以表示該參考資料值所屬的機構。
| 前置字串 |
參考資料 |
| A-
|
Android 錯誤 ID
|
| QC-
|
Qualcomm 參考編號
|
| M-
|
MediaTek 參考編號
|
| N-
|
NVIDIA 參考編號
|
| B-
|
Broadcom 參考編號
|
| U-
|
UNISOC 參考編號
|
4. 「參考資料」欄中，Android 錯誤 ID 旁的星號 (*) 代表什麼？
在對應的參考資料 ID 旁邊標上星號 (*) 代表該問題並未公開，用於解決問題的更新通常會直接整合在 Pixel 裝置的最新二進位驅動程式。您可以前往 Google Developers 網站下載這些驅動程式。
5. 為什麼安全性漏洞會分別刊載在這份安全性公告和裝置/合作夥伴安全性公告 (例如 Pixel 公告)？
刊載在此安全性公告的安全漏洞，都是宣告 Android 裝置最新安全性修補程式等級時，必須修正的問題。但裝置/合作夥伴安全性公告所刊載的其他安全漏洞，對於宣告安全性修補程式等級並非必要。Android 裝置和晶片組製造商也可能會針對該公司的產品發布安全漏洞詳細資料，例如：Google、Huawei、LGE、Motorola、Nokia 或 Samsung。
版本
| 版本 |
日期 |
附註 |
| 1.0
|
2022 年 1 月 4 日
|
發布公告
|
這個頁面中的內容和程式碼範例均受《內容授權》中的授權所規範。Java 與 OpenJDK 是 Oracle 和/或其關係企業的商標或註冊商標。
上次更新時間：2025-08-05 (世界標準時間)。
[[["容易理解","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-05 (世界標準時間)。"],[],[],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 |"]]
