# CVE-2012-2693: Missing authorization in n/a > Local users can access unintended USB devices due to incorrect device assignment logic in libvirt when multiple devices share IDs. - **Severity:** Low 3.7 (`AV:L/AC:H/Au:N/C:P/I:P/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 Jun 2012 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2012-2693, GHSA-p575-v2mx-34m6, RHSA-2012:0748, RHSA-2013:0127 ## What is CVE-2012-2693? CVE-2012-2693 is a low-severity missing authorization vulnerability in Redhat Libvirt, published on 17 Jun 2012. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description libvirt, possibly before 0.9.12, does not properly assign USB devices to virtual machines when multiple devices have the same vendor and product ID, which might cause the wrong device to be associated with a guest and might allow local users to access unintended USB devices. Weakness: CWE-264 ## Which versions are affected by CVE-2012-2693? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libvirt` | Red Hat:enterprise_linux:6::client | All versions | 0:0.9.10-21.el6 | | `libvirt-client` | Red Hat:enterprise_linux:6::client | All versions | 0:0.9.10-21.el6 | | `libvirt-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:0.9.10-21.el6 | | `libvirt-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.9.10-21.el6 | | `libvirt-lock-sanlock` | Red Hat:enterprise_linux:6::client | All versions | 0:0.9.10-21.el6 | | `libvirt-python` | Red Hat:enterprise_linux:6::client | All versions | 0:0.9.10-21.el6 | | `libvirt` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.9.10-21.el6 | | `libvirt-client` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.9.10-21.el6 | | `libvirt-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.9.10-21.el6 | | `libvirt-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.9.10-21.el6 | | `libvirt-lock-sanlock` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.9.10-21.el6 | | `libvirt-python` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.9.10-21.el6 | | `libvirt` | Red Hat:enterprise_linux:6::server | All versions | 0:0.9.10-21.el6 | | `libvirt-client` | Red Hat:enterprise_linux:6::server | All versions | 0:0.9.10-21.el6 | | `libvirt-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:0.9.10-21.el6 | | `libvirt-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:0.9.10-21.el6 | | `libvirt-lock-sanlock` | Red Hat:enterprise_linux:6::server | All versions | 0:0.9.10-21.el6 | | `libvirt-python` | Red Hat:enterprise_linux:6::server | All versions | 0:0.9.10-21.el6 | | `libvirt` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.9.10-21.el6 | | `libvirt-client` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.9.10-21.el6 | | `libvirt-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.9.10-21.el6 | | `libvirt-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.9.10-21.el6 | | `libvirt-lock-sanlock` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.9.10-21.el6 | | `libvirt-python` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.9.10-21.el6 | | `libvirt` | Red Hat:rhel_virtualization:5::client | All versions | 0:0.8.2-29.el5 | | `libvirt-debuginfo` | Red Hat:rhel_virtualization:5::client | All versions | 0:0.8.2-29.el5 | | `libvirt-devel` | Red Hat:rhel_virtualization:5::client | All versions | 0:0.8.2-29.el5 | | `libvirt-python` | Red Hat:rhel_virtualization:5::client | All versions | 0:0.8.2-29.el5 | | `libvirt` | Red Hat:rhel_virtualization:5::server | All versions | 0:0.8.2-29.el5 | | `libvirt-debuginfo` | Red Hat:rhel_virtualization:5::server | All versions | 0:0.8.2-29.el5 | | `libvirt-devel` | Red Hat:rhel_virtualization:5::server | All versions | 0:0.8.2-29.el5 | | `libvirt-python` | Red Hat:rhel_virtualization:5::server | All versions | 0:0.8.2-29.el5 | | `libvirt-lock-sanlock` | Red Hat:storage:3:server:el6 | All versions | 0:0.9.10-21.el6 | Products: Redhat Libvirt. ## How do I fix CVE-2012-2693? Upgrade to a fixed version. ## Is CVE-2012-2693 being exploited? There is no known exploitation of CVE-2012-2693 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Libvirt - [CVE-2013-4401](https://insights.sbomify.com/CVE-2013-4401/): Missing authorization in n/a (high 8.5) - [CVE-2017-2635](https://insights.sbomify.com/CVE-2017-2635/): Null dereference in libvirt (high 7.7) - [CVE-2013-4400](https://insights.sbomify.com/CVE-2013-4400/): Privilege escalation in n/a (high 7.2) - [CVE-2013-4291](https://insights.sbomify.com/CVE-2013-4291/): Privilege escalation in n/a (medium 6.9) - [CVE-2011-1146](https://insights.sbomify.com/CVE-2011-1146/): Missing authorization in n/a (medium 6.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2012-2693 and fix it if it is affected. What it is: CVE-2012-2693 is a low-severity missing authorization vulnerability in Redhat Libvirt, published on 17 Jun 2012. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2012-2693 in the wild and no public exploit code. Affected product: Redhat Libvirt. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2012-2693/ (Markdown: https://insights.sbomify.com/CVE-2012-2693/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2012-2693 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-2693 - OSV: https://osv.dev/vulnerability/CVE-2012-2693 --- From sbomify Insights: https://insights.sbomify.com/CVE-2012-2693/ Summaries are generated and may contain mistakes; the official description above is the record.