# CVE-2013-4282: Memory corruption in n/a > Remote attackers can crash the SPICE server by sending a long password in a ticket, causing a denial of service. - **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 2 Nov 2013 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2013-4282, GHSA-wr45-fcg3-r672, MGASA-2014-0022, RHSA-2013:1460, RHSA-2013:1473, RHSA-2013:1474, SUSE-SU-2015:0884-1, SUSE-SU-2015:0884-2, UBUNTU-CVE-2013-4282 ## What is CVE-2013-4282? CVE-2013-4282 is a medium-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 2 Nov 2013. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Stack-based buffer overflow in the reds_handle_ticket function in server/reds.c in SPICE 0.12.0 allows remote attackers to cause a denial of service (crash) via a long password in a SPICE ticket. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2013-4282? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `qspice` | Red Hat:enterprise_linux:5::client | All versions | 0:0.3.0-56.el5_10.1 | | `qspice-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:0.3.0-56.el5_10.1 | | `qspice-libs` | Red Hat:enterprise_linux:5::client | All versions | 0:0.3.0-56.el5_10.1 | | `qspice` | Red Hat:enterprise_linux:5::server | All versions | 0:0.3.0-56.el5_10.1 | | `qspice-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:0.3.0-56.el5_10.1 | | `qspice-libs` | Red Hat:enterprise_linux:5::server | All versions | 0:0.3.0-56.el5_10.1 | | `spice-server` | Red Hat:enterprise_linux:6::client | All versions | 0:0.12.0-12.el6_4.5 | | `spice-server-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:0.12.0-12.el6_4.5 | | `spice-server-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.12.0-12.el6_4.5 | | `spice-server` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.12.0-12.el6_4.5 | | `spice-server-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.12.0-12.el6_4.5 | | `spice-server-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.12.0-12.el6_4.5 | | `rhev-hypervisor6` | Red Hat:enterprise_linux:6::hypervisor | All versions | 0:6.4-20131016.0.el6_4 | | `spice-server` | Red Hat:enterprise_linux:6::server | All versions | 0:0.12.0-12.el6_4.5 | | `spice-server-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:0.12.0-12.el6_4.5 | | `spice-server-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:0.12.0-12.el6_4.5 | | `spice-server` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.12.0-12.el6_4.5 | | `spice-server-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.12.0-12.el6_4.5 | | `spice-server-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.12.0-12.el6_4.5 | | `qspice` | Red Hat:rhel_virtualization:5::client | All versions | 0:0.3.0-56.el5_10.1 | | `qspice-debuginfo` | Red Hat:rhel_virtualization:5::client | All versions | 0:0.3.0-56.el5_10.1 | | `qspice-libs-devel` | Red Hat:rhel_virtualization:5::client | All versions | 0:0.3.0-56.el5_10.1 | | `qspice` | Red Hat:rhel_virtualization:5::server | All versions | 0:0.3.0-56.el5_10.1 | | `qspice-debuginfo` | Red Hat:rhel_virtualization:5::server | All versions | 0:0.3.0-56.el5_10.1 | | `qspice-libs-devel` | Red Hat:rhel_virtualization:5::server | All versions | 0:0.3.0-56.el5_10.1 | | `spice` | SUSE:Linux Enterprise Desktop 12 | All versions | 0.12.4-6.1 | | `spice` | SUSE:Linux Enterprise Server 12 | All versions | 0.12.4-6.1 | | `spice` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 0.12.4-6.1 | | `spice` | SUSE:Linux Enterprise Software Development Kit 12 | All versions | 0.12.4-6.1 | Products: Redhat Enterprise Linux, Redhat Enterprise Virtualization, Spice Project Spice. ## How do I fix CVE-2013-4282? Apply the vendor's patch. ## Is CVE-2013-4282 being exploited? There is no known exploitation of CVE-2013-4282 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Enterprise Linux - [CVE-2018-14667](https://insights.sbomify.com/CVE-2018-14667/): Red Hat JBoss RichFaces Framework Expression Language Injection (critical 9.8, exploited in the wild) - [CVE-2021-20325](https://insights.sbomify.com/CVE-2021-20325/): Missing fixes for CVE-2021-40438 and CVE-2021-26691 in the versions of httpd, as shipped in Red Hat Enterprise Linux 8.5.0, causes a securit (critical 9.8) - [CVE-2018-25011](https://insights.sbomify.com/CVE-2018-25011/): Memory corruption in libwebp (critical 9.8) - [CVE-2018-25014](https://insights.sbomify.com/CVE-2018-25014/): Other in libwebp (critical 9.8) - [CVE-2014-3585](https://insights.sbomify.com/CVE-2014-3585/): Supply chain in redhat-upgrade-tool (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2013-4282 and fix it if it is affected. What it is: CVE-2013-4282 is a medium-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 2 Nov 2013. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2013-4282 in the wild and no public exploit code. Affected product: Redhat Enterprise Linux. 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-2013-4282/ (Markdown: https://insights.sbomify.com/CVE-2013-4282/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2013-4282 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-4282 - OSV: https://osv.dev/vulnerability/CVE-2013-4282 --- From sbomify Insights: https://insights.sbomify.com/CVE-2013-4282/ Summaries are generated and may contain mistakes; the official description above is the record.