Linux Kernel up to 4.17.4 fs/inode.c inode_init_owner access control

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.
6.3$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in Linux Kernel up to 4.17.4. Affected by this vulnerability is the function inode_init_owner of the file fs/inode.c. Performing a manipulation results in access control. This vulnerability was named CVE-2018-13405. The attack needs to be approached locally. In addition, an exploit is available. To fix this issue, it is recommended to deploy a patch.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel up to 4.17.4 (Operating System). This affects the function inode_init_owner of the file fs/inode.c. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

The inode_init_owner function in fs/inode.c in the Linux kernel through 4.17.4 allows local users to create files with an unintended group ownership, in a scenario where a directory is SGID to a certain group and is writable by a user who is not a member of that group. Here, the non-member can trigger creation of a plain file whose group ownership is that group. The intended behavior was that the non-member can trigger creation of a directory (but not a plain file) whose group ownership is that group.

The bug was discovered 07/13/2018. The weakness was presented 07/06/2018 as confirmed git commit (GIT Repository). It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2018-13405 since 07/06/2018. The exploitability is told to be easy. Attacking locally is a requirement. No form of authentication is needed for exploitation. Technical details and a public exploit are known. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 111329 (SUSE SLED12 / SLES12 Security Update : kernel (SUSE-SU-2018:2051-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 157849 (Oracle Enterprise Linux Security Update for kernel (ELSA-2018-3083)).

Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. A possible mitigation has been published 3 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Exploit-DB (45033), Tenable (111329) and SecurityFocus (BID 104685†). See VDB-81153, VDB-87616, VDB-105605 and VDB-109511 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.3

VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 111329
Nessus Name: SUSE SLED12 / SLES12 Security Update : kernel (SUSE-SU-2018:2051-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
Exposure Time: 🔍

Patch: git.kernel.org

Timelineinfo

07/06/2018 🔍
07/06/2018 +0 days 🔍
07/06/2018 +0 days 🔍
07/06/2018 +0 days 🔍
07/06/2018 +0 days 🔍
07/13/2018 +7 days 🔍
07/24/2018 +11 days 🔍
07/25/2018 +1 days 🔍
11/27/2024 +2317 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: RHSA-2018:2948
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2018-13405 (🔍)
GCVE (CVE): GCVE-0-2018-13405
GCVE (VulDB): GCVE-100-120483

OVAL: 🔍

SecurityFocus: 104685 - Linux Kernel 'drivers/video/fbdev/uvesafb.c' Local Integer Overflow Vulnerability

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 07/06/2018 22:05
Updated: 11/27/2024 04:24
Changes: 07/06/2018 22:05 (80), 05/07/2020 14:22 (8), 04/03/2023 19:53 (4), 11/27/2024 04:24 (14)
Complete: 🔍
Cache ID: 216:236:103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!