Dell BIOS Value rbu_packet.pktNum/rbu_packet.pktSize memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Dell BIOS. This issue affects the function rbu_packet.pktNum/rbu_packet.pktSize of the component Value Handler. Performing a manipulation results in memory corruption.
This vulnerability is identified as CVE-2013-3582. Additionally, an exploit exists.
It is recommended to upgrade the affected component.
Details
A vulnerability classified as critical has been found in Dell BIOS (version now known). This affects the function rbu_packet.pktNum/rbu_packet.pktSize of the component Value Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was released 07/31/2013 by Corey Kallenberg, John Butterworth and Xeno Kovah with MITRE as Copernicus: Question Your Assumptions about BIOS Security as not defined posting (Blog). The advisory is shared at mitre.org. The public release happened without involvement of Dell. The posting contains:
As a result of this research, the MITRE team, consisting of Sam Cornwell, Corey Kallenberg, Xeno Kovah, and myself, contributed to the creation of a tool we have dubbed Copernicus. Copernicus dumps the BIOS so inspection (such as comparing against a clean copy) is possible, and also checks the status of the configuration to determine if the BIOS can be modified. (…) How does it work? The tool is implemented as a kernel driver that creates a file containing the BIOS dump and a file containing the raw configuration information. When deployed in enterprise environments, scripts can send the raw BIOS dump and configuration information to a server for post-processing. This processing can indicate whether a given BIOS differs from an expected baseline, and it can also indicate whether the BIOS or the computer's System Management RAM (where some code loaded by BIOS continues running after boot).This vulnerability is uniquely identified as CVE-2013-3582 since 05/21/2013. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details and a public exploit are known. The advisory points out:
During the course of MITRE's Trusted Firmware Measurement research project, we determined the exact methods by which computers' firmware (BIOS) protects itself from modification. Subsequent experiments revealed that many older BIOSes still in use today, do not adequately protect themselves.
A public exploit has been developed by Xeno Kovah and been published immediately after the advisory. The exploit is shared for download at mitre.org. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 370593 (Dell Products BIOS Buffer Overflow Vulnerability).
Upgrading eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (96353†). Further details are available at kb.cert.org. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.dell.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.3VulDB Meta Temp Score: 8.4
VulDB Base Score: 9.3
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Xeno Kovah
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
05/21/2013 🔍07/16/2013 🔍
07/31/2013 🔍
07/31/2013 🔍
08/20/2013 🔍
08/28/2013 🔍
08/14/2024 🔍
Sources
Vendor: dell.comAdvisory: Copernicus: Question Your Assumptions about BIOS Security
Researcher: Corey Kallenberg, John Butterworth, Xeno Kovah
Organization: MITRE
Status: Not defined
Confirmation: 🔍
CVE: CVE-2013-3582 (🔍)
GCVE (CVE): GCVE-0-2013-3582
GCVE (VulDB): GCVE-100-9981
CERT: 🔍
OSVDB: 96353
scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
Entry
Created: 08/20/2013 16:22Updated: 08/14/2024 21:11
Changes: 08/20/2013 16:22 (62), 09/16/2017 10:23 (6), 08/14/2024 21:11 (17)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.