CVE Vulnerabilities

CVE-2016-4486

Exposure of Sensitive Information to an Unauthorized Actor

Published: May 23, 2016 | Modified: Sep 12, 2023
CVSS 3.x
3.3
LOW
Source:
NVD
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CVSS 2.x
2.1 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
Ubuntu

The rtnl_fill_link_ifmap function in net/core/rtnetlink.c in the Linux kernel before 4.5.5 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel stack memory by reading a Netlink message.

Weakness

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affected Software

Name Vendor Start Version End Version
Suse_linux_enterprise_software_development_kit Novell 11.0-sp4 (including) 11.0-sp4 (including)
Suse_linux_enterprise_software_development_kit Novell 12.0 (including) 12.0 (including)
Suse_linux_enterprise_software_development_kit Novell 12.0-sp1 (including) 12.0-sp1 (including)
Suse_linux_enterprise_debuginfo Novell 11.0-sp4 (including) 11.0-sp4 (including)
Suse_linux_enterprise_desktop Novell 12.0 (including) 12.0 (including)
Suse_linux_enterprise_desktop Novell 12.0-sp1 (including) 12.0-sp1 (including)
Suse_linux_enterprise_live_patching Novell 12.0 (including) 12.0 (including)
Suse_linux_enterprise_module_for_public_cloud Novell 12.0 (including) 12.0 (including)
Suse_linux_enterprise_real_time_extension Novell 12.0-sp1 (including) 12.0-sp1 (including)
Suse_linux_enterprise_server Novell 11.0-extra (including) 11.0-extra (including)
Suse_linux_enterprise_server Novell 11.0-sp4 (including) 11.0-sp4 (including)
Suse_linux_enterprise_server Novell 12.0 (including) 12.0 (including)
Suse_linux_enterprise_server Novell 12.0-sp1 (including) 12.0-sp1 (including)
Suse_linux_enterprise_workstation_extension Novell 12.0 (including) 12.0 (including)
Suse_linux_enterprise_workstation_extension Novell 12.0-sp1 (including) 12.0-sp1 (including)

Extended Description

There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:

Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:

Information exposures can occur in different ways:

It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References