Skip to content
KitploitKITPLOIT
工具漏洞利用博客
Log in
提交
工具漏洞利用博客
提交

黑客、渗透测试和网络安全工具,武装您的安全武器库!

Kitploit 是一个黑客、网络安全和渗透测试工具的目录。发现最新的项目更新,查找漏洞、分析系统、自动化测试并加强你的安全。

··订阅源·联系·隐私·© 2026 Kitploit

工具目录

分类

查看所有分类
Loading categories
android-gadget — CVE-2022-20009 - Android USB Gadgets 的描述和示例漏洞利用代码 | Kitploit
工具/GitHubGitHub/szymonh/android-gadget
Android安全嵌入式系统安全漏洞分析漏洞利用硬件安全二进制利用
GitHubszymonh/android-gadget

android-gadget

CVE-2022-20009 - Android USB Gadgets 的描述和示例漏洞利用代码

查看仓库
53183年前尚未审核

最受欢迎

查看全部 →

发现我们社区最常用的工具。

探索所有工具

浏览我们的工具集合

查看所有工具 →
分享

android-gadget

摘要

Android 使用的某些 Linux 内核版本受到 CVE-2021-39685 问题的影响。有关 CVE-2021-39685 的详细信息和 POC 可在 inspector-gadget 仓库中找到。

本仓库包含了针对多个 Android 特定 USB gadget 的 POC,包括:

  • f_accessory
  • f_audio_source
  • f_gsi
  • f_mtp
  • f_qc_rndis
  • f_rmnet

描述

a) f_accessory

  • 在 composite.c 中分配的 EP0 缓冲区大小为 USB_COMP_EP0_BUFSIZ (4096) 字节
  • 函数的控制传输处理程序 acc_ctrlrequest 读取 ctrl->wLength 到 w_length
  • 对于 bRequest 为 ACCESSORY_SEND_STRING 或 ACCESSORY_SEND_HID_EVENT,将 value 设置为 w_length
  • 数据传输阶段长度设置为 cdev->req->length = value;
  • 数据传输导致缓冲区溢出,溢出量为 wLength - 4096 字节
  • 写入到 EP0 缓冲区及其之后的数据量由攻击者控制
int acc_ctrlrequest(struct usb_composite_dev *cdev,
				const struct usb_ctrlrequest *ctrl)
{
	struct acc_dev	*dev = get_acc_dev();
	int	value = -EOPNOTSUPP;
	struct acc_hid_dev *hid;
	int offset;
	u8 b_requestType = ctrl->bRequestType;
	u8 b_request = ctrl->bRequest;
	u16	w_index = le16_to_cpu(ctrl->wIndex);
	u16	w_value = le16_to_cpu(ctrl->wValue);
	u16	w_length = le16_to_cpu(ctrl->wLength);
	unsigned long flags;
    ...
	if (b_requestType == (USB_DIR_OUT | USB_TYPE_VENDOR)) {
        ...
        } else if (b_request == ACCESSORY_SEND_STRING) {
			dev_info(&cdev->gadget->dev, "%s: got ACCESSORY_SEND_STRING(52) request\n",
				__func__);
			schedule_work(&dev->sendstring_work);
			dev->string_index = w_index;
			cdev->gadget->ep0->driver_data = dev;
			cdev->req->complete = acc_complete_set_string;
			value = w_length;
            ...
		} else if (b_request == ACCESSORY_SEND_HID_EVENT) {
			spin_lock_irqsave(&dev->lock, flags);
			hid = acc_hid_get(&dev->hid_list, w_value);
			spin_unlock_irqrestore(&dev->lock, flags);
			if (!hid) {
				value = -EINVAL;
				goto err;
			}
			cdev->req->context = hid;
			cdev->req->complete = acc_complete_send_hid_event;
			value = w_length;
		}
...
	if (value >= 0) {
		cdev->req->zero = 0;
		cdev->req->length = value;
		value = usb_ep_queue(cdev->gadget->ep0, cdev->req, GFP_ATOMIC);
		if (value < 0)
			ERROR(cdev, "%s setup response queue error\n",
				__func__);
	}

b) f_audio_source

  • 在 composite.c 中分配的 EP0 缓冲区大小为 USB_COMP_EP0_BUFSIZ (4096) 字节
  • 函数的控制传输处理程序 audio_setup 读取 ctrl->wLength 到 w_length
  • 对于 bRequestType 匹配条件 USB_DIR_OUT | USB_TYPE_CLASS | USB_RECIP_ENDPOINT,value 变量被赋值为 audio_set_endpoint_req 的返回值
  • 当 bRequest 等于 UAC_SET_CUR、UAC_SET_MIN、UAC_SET_MAX 或 UAC_SET_RES 时,audio_set_endpoint_req 返回 wLength
  • 数据传输阶段长度设置为 value;req->length = value;
  • 数据传输导致缓冲区溢出,溢出量为 wLength - 4096 字节
  • 写入到 EP0 缓冲区及其之后的数据量由攻击者控制
static int
audio_setup(struct usb_function *f, const struct usb_ctrlrequest *ctrl)
{
	struct usb_composite_dev *cdev = f->config->cdev;
	struct usb_request *req = cdev->req;
	int value = -EOPNOTSUPP;
	u16 w_index = le16_to_cpu(ctrl->wIndex);
	u16 w_value = le16_to_cpu(ctrl->wValue);
	u16 w_length = le16_to_cpu(ctrl->wLength);

    /* composite driver infrastructure handles everything; interface
	 * activation uses set_alt().
	 */
	switch (ctrl->bRequestType) {
	case USB_DIR_OUT | USB_TYPE_CLASS | USB_RECIP_ENDPOINT:
		value = audio_set_endpoint_req(f, ctrl);
		break;
	case USB_DIR_IN | USB_TYPE_CLASS | USB_RECIP_ENDPOINT:
		value = audio_get_endpoint_req(f, ctrl);
		break;
	}
	/* respond with data transfer or status phase? */
	if (value >= 0) {
		pr_debug("audio req%02x.%02x v%04x i%04x l%d\n",
			ctrl->bRequestType, ctrl->bRequest,
			w_value, w_index, w_length);
		req->zero = 0;
		req->length = value;
		req->complete = audio_control_complete;
		value = usb_ep_queue(cdev->gadget->ep0, req, GFP_ATOMIC);
		if (value < 0)
			pr_err("audio response on err %d\n", value);
	}
static int audio_set_endpoint_req(struct usb_function *f,
		const struct usb_ctrlrequest *ctrl)
{
	int value = -EOPNOTSUPP;
	u16 ep = le16_to_cpu(ctrl->wIndex);
	u16 len = le16_to_cpu(ctrl->wLength);
	u16 w_value = le16_to_cpu(ctrl->wValue);
	pr_debug("bRequest 0x%x, w_value 0x%04x, len %d, endpoint %d\n",
			ctrl->bRequest, w_value, len, ep);
	switch (ctrl->bRequest) {
	case UAC_SET_CUR:
	case UAC_SET_MIN:
	case UAC_SET_MAX:
	case UAC_SET_RES:
		value = len;
		break;
	default:
		break;
	}
	return value;
}

c) f_gsi

  • 在 composite.c 中分配的 EP0 缓冲区大小为 USB_COMP_EP0_BUFSIZ (4096) 字节
  • 函数的控制传输处理程序 gsi_setup 读取 ctrl->wLength 到 w_length 变量
  • 对于 bRequest 设置为 USB_CDC_SEND_ENCAPSULATED_COMMAND,value 被设置为 w_length
  • 数据传输阶段长度设置为 value;req->length = value;
  • 数据传输导致缓冲区溢出,溢出量为 wLength - 4096 字节
  • 写入到 EP0 缓冲区及其之后的数据量由攻击者控制
static int
gsi_setup(struct usb_function *f, const struct usb_ctrlrequest *ctrl)
{
	struct f_gsi *gsi = func_to_gsi(f);
	struct usb_composite_dev *cdev = f->config->cdev;
	struct usb_request *req = cdev->req;
	int id, value = -EOPNOTSUPP;
	u16 w_index = le16_to_cpu(ctrl->wIndex);
	u16 w_value = le16_to_cpu(ctrl->wValue);
	u16 w_length = le16_to_cpu(ctrl->wLength);
	struct gsi_ctrl_pkt *cpkt;
	u8 *buf;
	u32 n;
	bool line_state;
    ...
    switch ((ctrl->bRequestType << 8) | ctrl->bRequest) {
    ...
	case ((USB_DIR_OUT | USB_TYPE_CLASS | USB_RECIP_INTERFACE) << 8)
			| USB_CDC_SEND_ENCAPSULATED_COMMAND:
		log_event_dbg("USB_CDC_SEND_ENCAPSULATED_COMMAND");
		if (w_value || w_index != id)
			goto invalid;
		/* read the request; process it later */
		value = w_length;
		req->context = gsi;
		if (gsi->prot_id == IPA_USB_RNDIS)
			req->complete = gsi_rndis_command_complete;
		else
			req->complete = gsi_ctrl_cmd_complete;
		/* later, rndis_response_available() sends a notification */
		break;
    ...
    ...
    /* respond with data transfer or status phase? */
	if (value >= 0) {
		log_event_dbg("req%02x.%02x v%04x i%04x l%d",
			ctrl->bRequestType, ctrl->bRequest,
			w_value, w_index, w_length);
		req->zero = (value < w_length);
		req->length = value;
		value = usb_ep_queue(cdev->gadget->ep0, req, GFP_ATOMIC);
		if (value < 0)
			log_event_err("response on err %d", value);
	}

d) f_mtp

  • 在 composite.c 中分配的 EP0 缓冲区大小为 USB_COMP_EP0_BUFSIZ (4096) 字节
  • 函数的控制传输处理程序 mtp_ctrlrequest 读取 ctrl->wLength 到 w_length
  • 对于 bRequest 设置为 MTP_REQ_CANCEL,value 被设置为 w_length
  • 数据传输阶段长度设置为 value;req->length = value;
  • 数据传输导致缓冲区溢出,溢出量为 wLength - 4096 字节
  • 写入到 EP0 缓冲区及其之后的数据量由攻击者控制
static int mtp_ctrlrequest(struct usb_composite_dev *cdev,
				const struct usb_ctrlrequest *ctrl)
{
	struct mtp_dev *dev = _mtp_dev;
	int	value = -EOPNOTSUPP;
	u16	w_index = le16_to_cpu(ctrl->wIndex);
	u16	w_value = le16_to_cpu(ctrl->wValue);
	u16	w_length = le16_to_cpu(ctrl->wLength);
	unsigned long	flags;
    ...
    	} else if ((ctrl->bRequestType & USB_TYPE_MASK) == USB_TYPE_CLASS) {
		mtp_log("class request: %d index: %d value: %d length: %d\n",
			ctrl->bRequest, w_index, w_value, w_length);
		if (ctrl->bRequest == MTP_REQ_CANCEL && w_index == 0
				&& w_value == 0) {
			mtp_log("MTP_REQ_CANCEL\n");
			spin_lock_irqsave(&dev->lock, flags);
			if (dev->state == STATE_BUSY) {
				dev->state = STATE_CANCELED;
				wake_up(&dev->read_wq);
				wake_up(&dev->write_wq);
			}
			spin_unlock_irqrestore(&dev->lock, flags);
			/* We need to queue a request to read the remaining
			 *  bytes, but we don't actually need to look at
			 * the contents.
			 */
			value = w_length;
    ...
    /* respond with data transfer or status phase? */
	if (value >= 0) {
		int rc;
		cdev->req->zero = value < w_length;
		cdev->req->length = value;
		rc = usb_ep_queue(cdev->gadget->ep0, cdev->req, GFP_ATOMIC);
		if (rc < 0)
			pr_err("%s: response queue error\n", __func__);
	}

e) f_qc_rndis

  • 在 composite.c 中分配的 EP0 缓冲区大小为 USB_COMP_EP0_BUFSIZ (4096) 字节
  • 函数的控制传输处理程序 rndis_qc_setup 读取 ctrl->wLength 到 w_length
  • 对于 bRequest 设置为 USB_CDC_SEND_ENCAPSULATED_COMMAND,value 被设置为 w_length
  • 数据传输阶段长度设置为 value;req->length = value;
  • 数据传输导致缓冲区溢出,溢出量为 wLength - 4096 字节
  • 写入到 EP0 缓冲区及其之后的数据量由攻击者控制
下载工具