QID 610451

Date Published: 2022-12-13

QID 610451: Google Pixel Android December 2022 Security Patch Missing

Android is a mobile operating system based on a modified version of the Linux kernel and other open source software, designed primarily for touchscreen mobile devices such as smartphones and tablets.

Following security issues were discovered:
CVE-2022-20509,CVE-2022-20508,CVE-2022-20503,CVE-2022-20505,CVE-2022-20504,CVE-2022-20507,CVE-2022-20506,CVE-2022-20581,CVE-2022-20580,CVE-2022-20583,CVE-2022-20582,CVE-2022-20585,CVE-2022-20584,CVE-2022-20587,CVE-2022-20586,CVE-2022-20589,CVE-2022-20588,CVE-2022-42501,CVE-2022-42503,CVE-2022-42502,CVE-2022-42505,CVE-2022-42504,CVE-2022-42507,CVE-2022-42506,CVE-2022-42509,CVE-2022-42508,CVE-2022-20535,CVE-2022-20536,CVE-2022-20537,CVE-2022-20530,CVE-2022-20531,CVE-2021-39771,CVE-2022-20533,CVE-2022-20538,CVE-2022-20539,CVE-2022-1852,CVE-2022-42534,CVE-2022-42535,CVE-2022-42530,CVE-2022-42531,CVE-2022-42532,CVE-2022-20523,CVE-2022-20522,CVE-2022-20521,CVE-2022-20520,CVE-2022-20527,CVE-2022-20526,CVE-2022-20525,CVE-2022-20524,CVE-2022-20529,CVE-2022-20528,CVE-2022-42529,CVE-2022-42523,CVE-2022-42522,CVE-2022-42521,CVE-2022-42520,CVE-2022-42527,CVE-2022-42526,CVE-2022-42525,CVE-2022-42524,CVE-2022-1419,CVE-2022-20600,CVE-2022-20556,CVE-2022-20557,CVE-2022-20554,CVE-2022-20555,CVE-2022-20552,CVE-2022-20553,CVE-2022-20550,CVE-2022-20558,CVE-2022-20559,CVE-2022-20498,CVE-2022-28390,CVE-2022-20545,CVE-2022-20544,CVE-2022-20547,CVE-2022-20546,CVE-2022-20541,CVE-2022-20540,CVE-2022-20543,CVE-2022-20549,CVE-2022-20548,CVE-2022-20569,CVE-2022-42542,CVE-2022-20593,CVE-2022-0500,CVE-2022-20570,CVE-2022-20571,CVE-2022-20572,CVE-2022-20574,CVE-2022-20575,CVE-2022-20576,CVE-2022-20577,CVE-2022-20578,CVE-2022-20579,CVE-2020-0465,CVE-2022-25675,CVE-2022-25677,CVE-2022-20599,CVE-2022-1116,CVE-2022-20568,CVE-2022-20567,CVE-2022-20566,CVE-2022-20564,CVE-2022-20563,CVE-2022-20562,CVE-2022-20561,CVE-2022-20560,CVE-2022-20602,CVE-2022-20603,CVE-2022-34494,CVE-2022-34495,CVE-2022-20606,CVE-2022-20607,CVE-2022-20604,CVE-2022-20605,CVE-2022-20608,CVE-2022-20609,CVE-2022-20518,CVE-2022-20519,CVE-2022-20512,CVE-2022-20513,CVE-2022-20510,CVE-2022-20511,CVE-2022-20516,CVE-2022-20517,CVE-2022-20514,CVE-2022-20515,CVE-2021-30348,CVE-2022-20601,CVE-2022-20199,CVE-2022-20592,CVE-2022-20610,CVE-2022-20590,CVE-2022-20591,CVE-2022-20596,CVE-2022-20597,CVE-2022-20594,CVE-2022-20595,CVE-2022-20598,CVE-2022-30594,CVE-2022-42512,CVE-2022-42513,CVE-2022-42510,CVE-2022-42511,CVE-2022-42516,CVE-2022-42517,CVE-2022-42514,CVE-2022-42515,CVE-2022-42518,CVE-2022-42519

Affected Products :
Pixel 4 XL, Pixel 4, Pixel 3a XL, Pixel 3a, Pixel 3 XL, Pixel 3, Pixel 2 XL, Pixel 2

On successful exploitation, it could allow an attacker to execute code.

  • CVSS V3 rated as Critical - 9.8 severity.
  • CVSS V2 rated as High - 7.2 severity.
    • Solution
    Refer to Google Pixel advisory Google Pixel Android December2022 to address this issue and obtain more information.
    Vendor References

    CVEs related to QID 610451

    CVE-2022-20509 | CVE-2022-20508 | CVE-2022-20503 | CVE-2022-20505 | CVE-2022-20504 | CVE-2022-20507 | CVE-2022-20506 | CVE-2022-20581 | CVE-2022-20580 | CVE-2022-20583 | CVE-2022-20582 | CVE-2022-20585 | CVE-2022-20584 | CVE-2022-20587 | CVE-2022-20586 | CVE-2022-20589 | CVE-2022-20588 | CVE-2022-42501 | CVE-2022-42503 | CVE-2022-42502 | CVE-2022-42505 | CVE-2022-42504 | CVE-2022-42507 | CVE-2022-42506 | CVE-2022-42509 | CVE-2022-42508 | CVE-2022-20535 | CVE-2022-20536 | CVE-2022-20537 | CVE-2022-20530 | CVE-2022-20531 | CVE-2021-39771 | CVE-2022-20533 | CVE-2022-20538 | CVE-2022-20539 | CVE-2022-1852 | CVE-2022-42534 | CVE-2022-42535 | CVE-2022-42530 | CVE-2022-42531 | CVE-2022-42532 | CVE-2022-20523 | CVE-2022-20522 | CVE-2022-20521 | CVE-2022-20520 | CVE-2022-20527 | CVE-2022-20526 | CVE-2022-20525 | CVE-2022-20524 | CVE-2022-20529 | CVE-2022-20528 | CVE-2022-42529 | CVE-2022-42523 | CVE-2022-42522 | CVE-2022-42521 | CVE-2022-42520 | CVE-2022-42527 | CVE-2022-42526 | CVE-2022-42525 | CVE-2022-42524 | CVE-2022-1419 | CVE-2022-20600 | CVE-2022-20556 | CVE-2022-20557 | CVE-2022-20554 | CVE-2022-20555 | CVE-2022-20552 | CVE-2022-20553 | CVE-2022-20550 | CVE-2022-20558 | CVE-2022-20559 | CVE-2022-20498 | CVE-2022-28390 | CVE-2022-20545 | CVE-2022-20544 | CVE-2022-20547 | CVE-2022-20546 | CVE-2022-20541 | CVE-2022-20540 | CVE-2022-20543 | CVE-2022-20549 | CVE-2022-20548 | CVE-2022-20569 | CVE-2022-42542 | CVE-2022-20593 | CVE-2022-0500 | CVE-2022-20570 | CVE-2022-20571 | CVE-2022-20572 | CVE-2022-20574 | CVE-2022-20575 | CVE-2022-20576 | CVE-2022-20577 | CVE-2022-20578 | CVE-2022-20579 | CVE-2020-0465 | CVE-2022-25675 | CVE-2022-25677 | CVE-2022-20599 | CVE-2022-1116 | CVE-2022-20568 | CVE-2022-20567 | CVE-2022-20566 | CVE-2022-20564 | CVE-2022-20563 | CVE-2022-20562 | CVE-2022-20561 | CVE-2022-20560 | CVE-2022-20602 | CVE-2022-20603 | CVE-2022-34494 | CVE-2022-34495 | CVE-2022-20606 | CVE-2022-20607 | CVE-2022-20604 | CVE-2022-20605 | CVE-2022-20608 | CVE-2022-20609 | CVE-2022-20518 | CVE-2022-20519 | CVE-2022-20512 | CVE-2022-20513 | CVE-2022-20510 | CVE-2022-20511 | CVE-2022-20516 | CVE-2022-20517 | CVE-2022-20514 | CVE-2022-20515 | CVE-2021-30348 | CVE-2022-20601 | CVE-2022-20199 | CVE-2022-20592 | CVE-2022-20610 | CVE-2022-20590 | CVE-2022-20591 | CVE-2022-20596 | CVE-2022-20597 | CVE-2022-20594 | CVE-2022-20595 | CVE-2022-20598 | CVE-2022-30594 | CVE-2022-42512 | CVE-2022-42513 | CVE-2022-42510 | CVE-2022-42511 | CVE-2022-42516 | CVE-2022-42517 | CVE-2022-42514 | CVE-2022-42515 | CVE-2022-42518 | CVE-2022-42519 |
    Software Advisories
    Advisory ID Software Component Link
    December 2022 Android URL Logo source.android.com/security/bulletin/pixel/2022-12-01
    By selecting these links, you may be leaving CVEreport webspace. We have provided these links to other websites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other websites that are more appropriate for your purpose. CVEreport does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, CVEreport does not endorse any commercial products that may be mentioned on these sites. Please address comments about any linked pages to [email protected].