Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-39480 | First vendor Publication | 2024-07-05 |
Vendor | Cve | Last vendor Modification | 2024-11-21 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | |||
---|---|---|---|
Overall CVSS Score | 7.8 | ||
Base Score | 7.8 | Environmental Score | 7.8 |
impact SubScore | 5.9 | Temporal Score | 7.8 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | High |
Integrity Impact | High | Availability Impact | High |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
In the Linux kernel, the following vulnerability has been resolved: kdb: Fix buffer overflow during tab-complete Currently, when the user attempts symbol completion with the Tab key, kdb will use strncpy() to insert the completed symbol into the command buffer. Unfortunately it passes the size of the source buffer rather than the destination to strncpy() with predictably horrible results. Most obviously if the command buffer is already full but cp, the cursor position, is in the middle of the buffer, then we will write past the end of the supplied buffer. Fix this by replacing the dubious strncpy() calls with memmove()/memcpy() calls plus explicit boundary checks to make sure we have enough space before we start moving characters around. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-39480 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-120 | Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') (CWE/SANS Top 25) |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-06-26 02:32:31 |
|
2025-06-25 12:31:50 |
|
2025-06-24 02:37:10 |
|
2025-05-27 02:41:37 |
|
2025-03-29 03:37:54 |
|
2025-03-28 13:43:14 |
|
2025-03-28 03:16:31 |
|
2025-03-19 03:11:56 |
|
2025-03-18 03:24:48 |
|
2025-03-14 03:12:10 |
|
2025-03-06 14:08:34 |
|
2025-02-22 03:22:04 |
|
2025-01-08 03:03:25 |
|
2025-01-07 03:02:59 |
|
2024-12-25 03:01:36 |
|
2024-12-12 03:04:34 |
|
2024-11-25 09:24:16 |
|
2024-11-22 21:23:18 |
|
2024-11-21 21:22:55 |
|
2024-11-20 02:58:13 |
|
2024-11-14 02:58:31 |
|
2024-11-09 02:58:32 |
|
2024-10-26 02:55:56 |
|
2024-10-25 02:57:51 |
|
2024-10-23 02:57:03 |
|
2024-10-03 02:52:24 |
|
2024-10-02 02:50:48 |
|
2024-09-15 02:48:37 |
|
2024-09-12 02:48:10 |
|
2024-09-07 02:47:11 |
|
2024-09-06 02:46:22 |
|
2024-09-04 02:49:36 |
|
2024-08-22 00:28:01 |
|
2024-08-21 13:27:45 |
|
2024-08-02 13:56:35 |
|
2024-08-02 01:35:48 |
|
2024-07-09 00:27:31 |
|
2024-07-05 17:27:24 |
|
2024-07-05 13:27:27 |
|