CVE-2017-1000410 Detail
Modified
This vulnerability has been modified since it was last analyzed by the NVD. It is awaiting reanalysis which may result in further changes to the information provided.
Current Description
The Linux kernel version 3.3-rc1 and later is affected by a vulnerability lies in the processing of incoming L2CAP commands - ConfigRequest, and ConfigResponse messages. This info leak is a result of uninitialized stack variables that may be returned to an attacker in their uninitialized state. By manipulating the code flows that precede the handling of these configuration messages, an attacker can also gain some control over which data will be held in the uninitialized stack variables. This can allow him to bypass KASLR, and stack canaries protection - as both pointers and stack canaries may be leaked in this manner. Combining this vulnerability (for example) with the previously disclosed RCE vulnerability in L2CAP configuration parsing (CVE-2017-1000251) may allow an attacker to exploit the RCE against kernels which were built with the above mitigations. These are the specifics of this vulnerability: In the function l2cap_parse_conf_rsp and in the function l2cap_parse_conf_req the following variable is declared without initialization: struct l2cap_conf_efs efs; In addition, when parsing input configuration parameters in both of these functions, the switch case for handling EFS elements may skip the memcpy call that will write to the efs variable: ... case L2CAP_CONF_EFS: if (olen == sizeof(efs)) memcpy(&efs, (void *)val, olen); ... The olen in the above if is attacker controlled, and regardless of that if, in both of these functions the efs variable would eventually be added to the outgoing configuration request that is being built: l2cap_add_conf_opt(&ptr, L2CAP_CONF_EFS, sizeof(efs), (unsigned long) &efs); So by sending a configuration request, or response, that contains an L2CAP_CONF_EFS element, but with an element length that is not sizeof(efs) - the memcpy to the uninitialized efs variable can be avoided, and the uninitialized variable would be returned to the attacker (16 bytes).
Source:
MITRE
Description Last Modified:
12/07/2017
View Analysis Description
Analysis Description
The Linux kernel version 3.3-rc1 and later is affected by a vulnerability lies in the processing of incoming L2CAP commands - ConfigRequest, and ConfigResponse messages. This info leak is a result of uninitialized stack variables that may be returned to an attacker in their uninitialized state. By manipulating the code flows that precede the handling of these configuration messages, an attacker can also gain some control over which data will be held in the uninitialized stack variables. This can allow him to bypass KASLR, and stack canaries protection - as both pointers and stack canaries may be leaked in this manner. Combining this vulnerability (for example) with the previously disclosed RCE vulnerability in L2CAP configuration parsing (CVE-2017-1000251) may allow an attacker to exploit the RCE against kernels which were built with the above mitigations. These are the specifics of this vulnerability: In the function l2cap_parse_conf_rsp and in the function l2cap_parse_conf_req the following variable is declared without initialization: struct l2cap_conf_efs efs; In addition, when parsing input configuration parameters in both of these functions, the switch case for handling EFS elements may skip the memcpy call that will write to the efs variable: ... case L2CAP_CONF_EFS: if (olen == sizeof(efs)) memcpy(&efs, (void *)val, olen); ... The olen in the above if is attacker controlled, and regardless of that if, in both of these functions the efs variable would eventually be added to the outgoing configuration request that is being built: l2cap_add_conf_opt(&ptr, L2CAP_CONF_EFS, sizeof(efs), (unsigned long) &efs); So by sending a configuration request, or response, that contains an L2CAP_CONF_EFS element, but with an element length that is not sizeof(efs) - the memcpy to the uninitialized efs variable can be avoided, and the uninitialized variable would be returned to the attacker (16 bytes).
Source:
MITRE
Description Last Modified:
12/07/2017
Impact
CVSS v3.0 Severity and Metrics:
Base Score:
7.5 HIGH
Vector:
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
(V3 legend)
Impact Score:
3.6
Exploitability Score:
3.9
Attack Vector (AV):
Network
Attack Complexity (AC):
Low
Privileges Required (PR):
None
User Interaction (UI):
None
Scope (S):
Unchanged
Confidentiality (C):
High
Integrity (I):
None
Availability (A):
None
CVSS v2.0 Severity and Metrics:
Base Score:
5.0 MEDIUM
Vector:
(AV:N/AC:L/Au:N/C:P/I:N/A:N)
(V2 legend)
Impact Subscore:
2.9
Exploitability Subscore:
10.0
Access Vector (AV):
Network
Access Complexity (AC):
Low
Authentication (AU):
None
Confidentiality (C):
Partial
Integrity (I):
None
Availability (A):
None
Additional Information:
Allows unauthorized disclosure of information
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because
they may have information that would be of interest to you. No inferences should be drawn on account of other sites
being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose.
NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further,
NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about
this page to nvd@nist.gov.
Technical Details
Vulnerability Type
(View All)
- Information Leak / Disclosure (CWE-200)
Change History
8 change records found
- show changes
CVE Modified by MITRE -
5/9/2018 9:29:01 PM
| Action |
Type |
Old Value |
New Value |
| Added |
Reference |
|
https://access.redhat.com/errata/RHSA-2018:1319 [No Types Assigned] |
CVE Modified by MITRE -
4/18/2018 9:29:03 PM
| Action |
Type |
Old Value |
New Value |
| Added |
Reference |
|
https://access.redhat.com/errata/RHSA-2018:1130 [No Types Assigned] |
| Added |
Reference |
|
https://access.redhat.com/errata/RHSA-2018:1170 [No Types Assigned] |
CVE Modified by MITRE -
4/11/2018 9:29:01 PM
| Action |
Type |
Old Value |
New Value |
| Added |
Reference |
|
https://access.redhat.com/errata/RHSA-2018:0676 [No Types Assigned] |
| Added |
Reference |
|
https://access.redhat.com/errata/RHSA-2018:1062 [No Types Assigned] |
CVE Modified by MITRE -
4/10/2018 9:29:00 PM
| Action |
Type |
Old Value |
New Value |
| Added |
Reference |
|
https://access.redhat.com/errata/RHSA-2018:0654 [No Types Assigned] |
CVE Modified by MITRE -
1/10/2018 9:29:05 PM
| Action |
Type |
Old Value |
New Value |
| Added |
Reference |
|
https://www.debian.org/security/2018/dsa-4082 [No Types Assigned] |
CVE Modified by MITRE -
12/24/2017 9:29:12 PM
| Action |
Type |
Old Value |
New Value |
| Added |
Reference |
|
https://www.debian.org/security/2017/dsa-4073 [No Types Assigned] |
Initial Analysis -
12/21/2017 12:18:42 PM
| Action |
Type |
Old Value |
New Value |
| Added |
CPE Configuration |
|
OR
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 3.3 |
| Added |
CVSS V2 |
|
(AV:N/AC:L/Au:N/C:P/I:N/A:N) |
| Added |
CVSS V3 |
|
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| Added |
CWE |
|
CWE-200 |
| Changed |
Reference Type |
http://seclists.org/oss-sec/2017/q4/357 No Types Assigned |
http://seclists.org/oss-sec/2017/q4/357 Issue Tracking, Mailing List, Patch, Third Party Advisory |
| Changed |
Reference Type |
http://www.securityfocus.com/bid/102101 No Types Assigned |
http://www.securityfocus.com/bid/102101 Issue Tracking, Third Party Advisory, VDB Entry |
CVE Modified by MITRE -
12/8/2017 9:29:05 PM
| Action |
Type |
Old Value |
New Value |
| Added |
Reference |
|
http://www.securityfocus.com/bid/102101 [No Types Assigned] |
Quick Info
CVE Dictionary Entry:
CVE-2017-1000410
NVD Published Date:
12/07/2017
NVD Last Modified:
05/09/2018
|