# CVE-2013-3582: Memory corruption in n/a

> Local administrators can bypass BIOS signing requirements to install arbitrary firmware images via a buffer overflow in Dell BIOS.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6486-j487-828h

## What is CVE-2013-3582?

CVE-2013-3582 is a high-severity memory corruption vulnerability in n/a, published on 28 Aug 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in Dell BIOS on Dell Latitude D###, E####, XT2, and Z600 devices, and Dell Precision M#### devices, allows local users to bypass intended BIOS signing requirements and install arbitrary BIOS images by leveraging administrative privileges and providing a crafted rbu_packet.pktNum value in conjunction with a crafted rbu_packet.pktSize value.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2013-3582?

It affects 22 products.


Products: Dell Latitude D530, Dell Latitude D531, Dell Latitude D630, Dell Latitude D631, Dell Latitude D830, Dell Latitude E4200, Dell Latitude E4300, Dell Latitude E5400, Dell Latitude E5500, Dell Latitude E6400, Dell Latitude E6400 Atg, Dell Latitude E6400 Atg Xfr, Dell Latitude E6500, Dell Latitude Xt2, Dell Latitude Z600, Dell Precision M2300, Dell Precision M2400, Dell Precision M4300, Dell Precision M4400, Dell Precision M6300 and 2 more.

## How do I fix CVE-2013-3582?

No fix has been published for CVE-2013-3582 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-3582 being exploited?

There is no known exploitation of CVE-2013-3582 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3582 and fix it if it is affected.

What it is: CVE-2013-3582 is a high-severity memory corruption vulnerability in n/a, published on 28 Aug 2013. 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-2013-3582 in the wild and no public exploit code.

Affected product: n/a. 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-3582/ (Markdown: https://insights.sbomify.com/CVE-2013-3582/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-3582
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-3582
- OSV: https://osv.dev/vulnerability/CVE-2013-3582

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-3582/
Summaries are generated and may contain mistakes; the official description above is the record.