自 2025 年 3 月 27 日起，我們建議您使用 android-latest-release 而非 aosp-main 建構及貢獻 AOSP。詳情請參閱「Android 開放原始碼計畫變更」。
Wear OS 安全性公告 - 2023 年 12 月
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
發布日期：2023 年 12 月 4 日
Wear OS 安全性公告列舉對 Wear OS 平台造成影響的安全漏洞，並說明相關細節。完整的 Wear OS 更新除了提供 2023 年 12 月 Android 安全性公告中的安全性修補程式等級 (2023-12-05 之後)，也解決了這個公告列出的所有問題。
我們建議所有客戶接受這些裝置更新。
本公告列出的問題，是系統元件中嚴重程度「高」的安全漏洞。這類漏洞可能讓攻擊者不必取得額外執行權限，即可提升本機權限，且過程中不必與使用者互動，就能達成濫用目的。嚴重程度評定標準是假設平台與服務的因應防護措施基於開發作業需求而關閉，或是遭到有心人士成功規避，然後推算當有人惡意運用漏洞時，使用者裝置會受到多大影響，並據此評定漏洞的嚴重程度。
公告事項
-
除了 2023 年 12 月 Android 安全性公告所述的安全漏洞外，2023 年 12 月的 Wear OS 安全性公告也針對下文列出的 Wear OS 安全漏洞提供修補程式。
2023-12-01 安全性修補程式等級安全漏洞詳情
以下各節將詳細說明 2023-12-01 安全性修補程式等級適用的各項安全漏洞。我們依照受影響的元件將安全漏洞分門別類，並將問題相關資訊列於下方的表格，包括 CVE ID、相關參考資料、安全漏洞類型、嚴重程度。在適用情況下，我們也會附上更新的 Android 開放原始碼計畫版本。假如有公開變更內容可以解決某錯誤，我們會連結相對應的錯誤 ID 和變更內容 (例如 Android 開放原始碼計畫變更清單)。如果某個錯誤有多筆相關的程式碼更改記錄，點選錯誤 ID 後面的編號連結即可查看其他參考資料。搭載 Android 10 以上版本的裝置可能會收到安全性更新和 Google Play 系統更新。
系統
本節中的安全漏洞可能讓攻擊者不必取得額外執行權限，即可提升本機權限，且過程中不必與使用者互動，就能達成濫用目的。
| CVE |
參考資料 |
類型 |
嚴重性 |
更新的 Android 開放原始碼計畫版本 |
|
CVE-2023-40094
|
A-307719731
|
EoP |
高 |
11、13 |
常見問題與解答
如果您在閱讀這篇公告後有任何疑問，可參考本節的常見問答。
1. 如何判斷目前的裝置軟體版本已修正這些問題？
請參閱 Google 裝置更新時間表中的說明，瞭解如何查看裝置的安全性修補程式等級。
- 如果是 2023-12-01 之後的安全性修補程式等級，代表 2023-12-01 安全性修補程式等級涵蓋的所有問題都已解決。
提供這些更新的裝置製造商應將修補程式字串等級設定為：
- [ro.build.version.security_patch]:[2023-12-01]
如果是搭載 Android 10 以上版本的裝置，Google Play 系統更新的日期字串應與 2023-12-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 |
2023 年 12 月 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,["# Wear OS Security Bulletin—December 2023\n\n*Published December 4, 2023*\n\n\nThe Wear OS Security Bulletin contains details of security vulnerabilities\naffecting the Wear OS platform.\nThe full Wear OS update comprises the security patch level of 2023-12-05 or\nlater from the [December 2023 Android Security Bulletin](/docs/security/bulletin/2023-12-01) in addition to\nall issues in this bulletin.\n\n\nWe encourage all customers to accept these updates to their devices.\n| **Note**: Please contact your device supplier for device firmware images.\n\n\nThe issue in this bulletin is a high security vulnerability in the System\ncomponent that could lead to local escalation of privilege with no additional\nexecution privileges needed. User interaction is not needed for exploitation.\nThe [severity assessment](/docs/security/overview/updates-resources#severity) is based on the effect that\nexploiting the vulnerability would possibly have on an affected device,\nassuming the platform and service mitigations are turned off for development\npurposes or if successfully bypassed.\n\nAnnouncements\n-------------\n\n- In addition to the security vulnerabilities described in the December 2023 Android Security Bulletin, the December 2023 Wear OS Security Bulletin also contains patches specifically for Wear OS vulnerabilities as described below.\n\n2023-12-01\nsecurity patch level vulnerability details\n-----------------------------------------------------\n\n\nIn the sections below, we provide details for each of the security\nvulnerabilities that apply to the 2023-12-01 patch level.\nVulnerabilities are grouped under the component they affect.\nIssues are described in the tables below and include CVE ID, associated\nreferences, [type of vulnerability](#type),\n[severity](/security/overview/updates-resources#severity),\nand updated AOSP versions (where applicable).\nWhen available, we link the public change that addressed the issue to the\nbug ID, like the AOSP change list.\nWhen multiple changes relate to a single bug, additional references are\nlinked to numbers following the bug ID.\nDevices with Android 10 and later may receive security updates as well as\n[Google\nPlay\nsystem updates](https://support.google.com/android/answer/7680439?).\n\n### System\n\nThe vulnerability in this section could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.\n\n| CVE | References | Type | Severity | Updated AOSP versions |\n|----------------|-------------|------|----------|-----------------------|\n| CVE-2023-40094 | A-307719731 | EoP | High | 11, 13 |\n\nCommon questions and answers\n----------------------------\n\nThis section answers common questions that may occur after reading this\nbulletin.\n\n**1. How do I determine if my device is updated to address these\nissues?**\n\nTo learn how to check a device's security patch level, read the\ninstructions on the\n[Google device update schedule](https://support.google.com/android/answer/7680439).\n\n- Security patch levels of 2023-12-01 or later address all issues associated with the 2023-12-01 security patch level.\n\nDevice manufacturers that include these updates should set the patch string\nlevel to:\n\n- \\[ro.build.version.security_patch\\]:\\[2023-12-01\\]\n\nFor some devices on Android 10 or later, the Google Play system update\nwill have a date string that matches the 2023-12-01\nsecurity patch level.\nPlease see [this article](https://support.google.com/android/answer/7680439?hl=en) for more details on how to\ninstall\nsecurity updates.\n\n\n**2. What do the entries in the *Type* column mean?**\n\nEntries in the *Type* column of the vulnerability details table\nreference the classification of the security vulnerability.\n\n| Abbreviation | Definition |\n|--------------|------------------------------|\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\nEntries under the *References* column of the vulnerability details\ntable may contain a prefix identifying the organization to which the\nreference\nvalue 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*\ncolumn mean?**\n\nIssues that are not publicly available have an \\* next to the corresponding\nreference ID. The update for that issue is generally contained in the latest\nbinary drivers for Pixel devices available from the\n[Google\nDeveloper site](https://developers.google.com/android/drivers).\n\n**5. Why are security vulnerabilities split between this bulletin and\ndevice / partner security bulletins, such as the\nPixel bulletin?**\n\nSecurity vulnerabilities that are documented in this security bulletin are\nrequired to declare the latest security patch level on Android\ndevices. Additional security vulnerabilities that are documented in the\ndevice / partner security bulletins are not required for\ndeclaring a security patch level. Android device and chipset manufacturers\nmay also publish security vulnerability details specific to their products,\nsuch as\n[Google](/docs/security/bulletin/pixel),\n[Huawei](https://consumer.huawei.com/en/support/bulletin/),\n[LGE](https://lgsecurity.lge.com/security_updates_mobile.html),\n[Motorola](https://motorola-global-portal.custhelp.com/app/software-security-page/g_id/6806),\n[Nokia](https://www.nokia.com/phones/en_int/security-updates),\nor\n[Samsung](https://security.samsungmobile.com/securityUpdate.smsb).\n\nVersions\n--------\n\n| Version | Date | Notes |\n|---------|------------------|--------------------|\n| 1.0 | December 4, 2023 | Bulletin published |"]]
