CVE-2018-9567
Last modified
CVE-2018-9567 is a vulnerability of currently unknown severity. On Pixel devices there is a bug causing verified boot to show the same certificate fingerprint despite using different signing keys. This may lead to local escalation of privilege if people are relying on those fingerprints to determine what version of the OS the device is running, with System execution privileges needed. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
On Pixel devices there is a bug causing verified boot to show the same certificate fingerprint despite using different signing keys. This may lead to local escalation of privilege if people are relying on those fingerprints to determine what version of the OS the device is running, with System execution privileges needed. User interaction is not needed for exploitation. Product: Android. Versions: Android kernel. Android ID: A-65543936.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Android | All versions |
References
- http://www.securityfocus.com/bid/106064Third Party Advisory, VDB Entry
- https://source.android.com/security/bulletin/2018-12-01Vendor Advisory
- http://www.securityfocus.com/bid/106064Third Party Advisory, VDB Entry
- https://source.android.com/security/bulletin/2018-12-01Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-9567?
How severe is CVE-2018-9567?
How do I fix CVE-2018-9567?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2018
- CVE-2018-9561In llcp_util_parse_connect of llcp_util.cc, there is a possi…
- CVE-2018-9562In bta_ag_do_disc of bta_ag_sdp.cc, there is a possible out-…7.5
- CVE-2018-9563In llcp_util_parse_cc of llcp_util.cc, there is a possible o…
- CVE-2018-9564In llcp_util_parse_link_params of llcp_util.cc, there is a p…
- CVE-2018-9565In readBytes of xltdecwbxml.c, there is a possible out of bo…7.5
- CVE-2018-9566In process_service_search_rsp of sdp_discovery.c, there is a…5.7
- CVE-2018-9568In sk_clone_lock of sock.c, there is a possible memory corru…7.8
- CVE-2018-9569In impd_init_drc_decode_post_config of impd_drc_gain_decoder…8.8
- CVE-2018-9570In impd_parse_drc_ext_v1 of impd_drc_dynamic_payload.c there…7.8
- CVE-2018-9571In impd_parse_loud_eq_instructions of impd_drc_dynamic_paylo…8.8
- CVE-2018-9572In impd_drc_parse_coeff of impd_drc_static_payload.c there i…8.8
- CVE-2018-9573In impd_parse_filt_block of impd_drc_dynamic_payload.c there…7.8
Are you affected by CVE-2018-9567?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
