CVE-2017-1000410

High

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).

Package Linux Kernel
Published 2017-12-07
Last modified 2026-05-13
CVSS version 3.0
Patch available
Awaiting data

CVSS 3.0 score

7.5

out of 10
High
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
Vector string
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Weakness type

CWE-200

CVE-2017-1000410 is a Information Exposure vulnerability

What is Information Exposure?

The product exposes sensitive information to an actor not authorised to see it. Learn more on MITRE CWE

References

The following references provide additional information about CVE-2017-1000410 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

Frequently asked questions

  • What is CVE-2017-1000410?

    CVE-2017-1000410 is a High severity Linux kernel vulnerability with a CVSS score of 7.5 out of 10 , classified as an Information Exposure flaw (CWE-200) . CVE-2017-1000410 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • What is the CVSS score for CVE-2017-1000410?

    CVE-2017-1000410 has a CVSS score of 7.5 out of 10, rated High severity (CVSS 3.0). The vector string is CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N .

  • Is there a patch available for CVE-2017-1000410?

    No patch is currently available for CVE-2017-1000410. Monitor the NIST NVD and your Linux distribution's security advisories for updates.

  • Is CVE-2017-1000410 actively exploited?

    No — CVE-2017-1000410 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.

  • What is Information Exposure (CWE-200)?

    The product exposes sensitive information to an actor not authorised to see it. View CWE-200 on MITRE CWE →

Back to
All CVEs
View on
NVD / NIST