Linux Kernel up to 4.13.4 x86 FPU Subsystem regset.c ptrace Header information disclosure

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.3$0-$5k0.00

Summaryinfo

A vulnerability described as problematic has been identified in Linux Kernel up to 4.13.4. The affected element is the function ptrace of the file arch/x86/kernel/fpu/regset.c of the component x86 FPU Subsystem. Executing a manipulation as part of Header can lead to information disclosure. This vulnerability appears as CVE-2017-15537. The attack requires local access. There is no available exploit. A patch should be applied to remediate this issue.

Detailsinfo

A vulnerability classified as problematic was found in Linux Kernel up to 4.13.4 (Operating System). This vulnerability affects the function ptrace of the file arch/x86/kernel/fpu/regset.c of the component x86 FPU Subsystem. The manipulation as part of a Header leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. CVE summarizes:

The x86/fpu (Floating Point Unit) subsystem in the Linux kernel before 4.13.5, when a processor supports the xsave feature but not the xsaves feature, does not correctly handle attempts to set reserved bits in the xstate header via the ptrace() or rt_sigreturn() system call, allowing local users to read the FPU registers of other processes on the system, related to arch/x86/kernel/fpu/regset.c and arch/x86/kernel/fpu/signal.c.

The bug was discovered 10/17/2017. The weakness was presented 10/17/2017 as confirmed git commit (GIT Repository). The advisory is available at git.kernel.org. This vulnerability was named CVE-2017-15537 since 10/17/2017. Local access is required to approach this attack. The requirement for exploitation is a single authentication. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.

The vulnerability scanner Nessus provides a plugin with the ID 104737 (Ubuntu 17.10 : linux, linux-raspi2 vulnerabilities (USN-3487-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Ubuntu Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 196961 (Ubuntu Security Notification for Linux, Linux-aws, Linux-gke, Linux-kvm, Linux-raspi2, Linux-snapdragon (USN-3469-1)).

Upgrading to version 4.13.5 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be patching the affected component. A possible mitigation has been published 2 months after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (104737). See VDB-102883, VDB-102882, VDB-107418 and VDB-107763 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.4
VulDB Meta Temp Score: 4.3

VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 104737
Nessus Name: Ubuntu 17.10 : linux, linux-raspi2 vulnerabilities (USN-3487-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 841810
OpenVAS Name: Ubuntu Update for linux-lts-xenial USN-3469-2
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Kernel 4.13.5
Patch: git.kernel.org

Timelineinfo

10/17/2017 🔍
10/17/2017 +0 days 🔍
10/17/2017 +0 days 🔍
10/17/2017 +0 days 🔍
10/18/2017 +1 days 🔍
11/21/2017 +34 days 🔍
11/22/2017 +1 days 🔍
01/03/2023 +1868 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: USN-3487-1
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-15537 (🔍)
GCVE (CVE): GCVE-0-2017-15537
GCVE (VulDB): GCVE-100-107938
See also: 🔍

Entryinfo

Created: 10/18/2017 08:56
Updated: 01/03/2023 18:30
Changes: 10/18/2017 08:56 (80), 11/25/2019 16:24 (3), 01/03/2023 18:23 (4), 01/03/2023 18:30 (1)
Complete: 🔍
Cache ID: 216:6A7:103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!