Linux Kernel 3.2/3.4/3.10/3.12/3.13 Floppy Device /drivers/block/floppy.c raw_cmd_copyout access control

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Linux Kernel 3.2/3.4/3.10/3.12/3.13. Affected by this vulnerability is the function raw_cmd_copyout of the file /drivers/block/floppy.c of the component Floppy Device Handler. This manipulation causes access control.
The identification of this vulnerability is CVE-2014-1738. There is no exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability has been found in Linux Kernel 3.2/3.4/3.10/3.12/3.13 (Operating System) and classified as critical. Affected by this vulnerability is the function raw_cmd_copyout of the file /drivers/block/floppy.c of the component Floppy Device Handler. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device.
The weakness was shared 04/28/2014 by Matthew Daley as floppy: don't write kernel-only members to FDRAWCMD ioctl output as confirmed git commit (GIT Repository). The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2014-1738 since 01/29/2014. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue. Responsible for the vulnerability is the following code:
ret = copy_to_user(param, ptr, sizeof(*ptr));The advisory points out:
Do not leak kernel-only floppy_raw_cmd structure members to userspace. This includes the linked-list pointer and the pointer to the allocated DMA space.
The vulnerability scanner Nessus provides a plugin with the ID 73971 (Debian DSA-2926-1 : linux - security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 167228 (SUSE Enterprise Linux Security Update for Linux Kernel (SUSE-SU-2014:0807-1)).
Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. A possible mitigation has been published 1 weeks after the disclosure of the vulnerability. The vulnerability will be addressed with the following lines of code:
struct floppy_raw_cmd cmd = *ptr; cmd.next = NULL; cmd.kernel_data = NULL; ret = copy_to_user(param, &cmd, sizeof(cmd));
The vulnerability is also documented in the databases at X-Force (93049), Tenable (73971), SecurityFocus (BID 67302†), Secunia (SA59309†) and Vulnerability Center (SBV-44418†). Additional details are provided at bugzilla.redhat.com. The entries VDB-11302, VDB-11315, VDB-11755 and VDB-12214 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Not Affected
- Red Hat Enterprise Linux 5/6
- Red Hat Enterprise MRG 2
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.4VulDB Meta Temp Score: 7.3
VulDB Base Score: 8.4
VulDB Temp Score: 7.3
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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 73971
Nessus Name: Debian DSA-2926-1 : linux - security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
OpenVAS ID: 702926
OpenVAS Name: Debian Security Advisory DSA 2926-1 (linux - security update
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: git.kernel.org
Timeline
01/29/2014 🔍04/28/2014 🔍
05/05/2014 🔍
05/07/2014 🔍
05/09/2014 🔍
05/11/2014 🔍
05/11/2014 🔍
05/13/2014 🔍
07/01/2014 🔍
06/19/2021 🔍
Sources
Vendor: kernel.orgAdvisory: floppy: don't write kernel-only members to FDRAWCMD ioctl output
Researcher: Matthew Daley
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2014-1738 (🔍)
GCVE (CVE): GCVE-0-2014-1738
GCVE (VulDB): GCVE-100-13189
OVAL: 🔍
X-Force: 93049 - Linux Kernel raw_cmd_copyout() privilege escalation, High Risk
SecurityFocus: 67302 - Linux Kernel CVE-2014-1738 Local Privilege Escalation Vulnerability
Secunia: 59309 - Red Hat update for kernel, Less Critical
SecurityTracker: 1030474
Vulnerability Center: 44418 - Linux Kernel Before 3.8.13.23 Local Privilege Escalation and DoS in raw_cmd_copyout Function, Medium
Misc.: 🔍
See also: 🔍
Entry
Created: 05/13/2014 14:32Updated: 06/19/2021 13:17
Changes: 05/13/2014 14:32 (89), 05/27/2017 10:48 (6), 06/19/2021 13:12 (3), 06/19/2021 13:17 (1)
Complete: 🔍
Cache ID: 216:242: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.