Linux Kernel up to 5.2.2 drivers/block/floppy.c set_geometry out-of-bounds

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Linux Kernel up to 5.2.2. Affected by this vulnerability is the function set_geometry of the file drivers/block/floppy.c. This manipulation causes out-of-bounds.
This vulnerability appears as CVE-2019-14283. The attack requires local access. There is no available exploit.
It is advisable to upgrade the affected component.
Details
A vulnerability classified as critical was found in Linux Kernel up to 5.2.2 (Operating System). Affected by this vulnerability is the function set_geometry of the file drivers/block/floppy.c. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel before 5.2.3, set_geometry in drivers/block/floppy.c does not validate the sect and head fields, as demonstrated by an integer overflow and out-of-bounds read. It can be triggered by an unprivileged local user when a floppy disk has been inserted. NOTE: QEMU creates the floppy device by default.
The weakness was presented 07/26/2019 (Website). The advisory is shared at seclists.org. This vulnerability is known as CVE-2019-14283 since 07/26/2019. An attack has to be approached locally. The successful exploitation needs a single authentication. Technical details are known, but no exploit is available.
Upgrading to version 5.2.3 eliminates this vulnerability.
See VDB-138338, VDB-138837, VDB-138838 and VDB-138839 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 6.0VulDB Meta Temp Score: 5.9
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.8
NVD Vector: 🔍
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: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kernel 5.2.3
Patch: git.kernel.org
Timeline
07/26/2019 🔍07/26/2019 🔍
07/26/2019 🔍
11/13/2023 🔍
Sources
Vendor: kernel.orgAdvisory: 154059
Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-14283 (🔍)
GCVE (CVE): GCVE-0-2019-14283
GCVE (VulDB): GCVE-100-138853
See also: 🔍
Entry
Created: 07/26/2019 20:46Updated: 11/13/2023 09:40
Changes: 07/26/2019 20:46 (60), 07/13/2020 16:33 (2), 11/13/2023 09:39 (5), 11/13/2023 09:40 (1)
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.