CVE-2018-1063
CVSS V2 Low 3.3
CVSS V3 Medium 4.4
Description
Context relabeling of filesystems is vulnerable to symbolic link attack, allowing a local, unprivileged malicious entity to change the SELinux context of an arbitrary file to a context with few restrictions. This only happens when the relabeling process is done, usually when taking SELinux state from disabled to enable (permissive or enforcing). The issue was found in policycoreutils 2.5-11.
Overview
- CVE ID
- CVE-2018-1063
- Assigner
- secalert@redhat.com
- Vulnerability Status
- Modified
- Published Version
- 2018-03-02T15:29:00
- Last Modified Date
- 2023-02-12T23:32:32
Weakness Enumerations
CPE Configuration (Product)
CPE | Vulnerable | Operator | Version Start | Version End |
---|---|---|---|---|
cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:* | 1 | OR | ||
cpe:2.3:a:selinux_project:selinux:-:*:*:*:*:*:*:* | 1 | OR |
CVSS Version 2
- Version
- 2.0
- Vector String
- AV:L/AC:M/Au:N/C:P/I:P/A:N
- Access Vector
- LOCAL
- Access Compatibility
- MEDIUM
- Authentication
- NONE
- Confidentiality Impact
- PARTIAL
- Integrity Impact
- PARTIAL
- Availability Impact
- NONE
- Base Score
- 3.3
- Severity
- LOW
- Exploitability Score
- 3.4
- Impact Score
- 4.9
CVSS Version 3
- Version
- 3.0
- Vector String
- CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- Attack Vector
- LOCAL
- Attack Compatibility
- LOW
- Privileges Required
- LOW
- User Interaction
- NONE
- Scope
- UNCHANGED
- Confidentiality Impact
- LOW
- Availability Impact
- NONE
- Base Score
- 4.4
- Base Severity
- MEDIUM
- Exploitability Score
- 1.8
- Impact Score
- 2.5
References
Reference URL | Reference Tags |
---|---|
https://access.redhat.com/errata/RHSA-2018:0913 | |
https://access.redhat.com/security/cve/CVE-2018-1063 | |
https://bugzilla.redhat.com/show_bug.cgi?id=1550122 | Issue Tracking Mitigation Vendor Advisory |
Sources
Source Name | Source URL |
---|---|
NIST | https://nvd.nist.gov/vuln/detail/CVE-2018-1063 |
MITRE | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1063 |
History
Created | Old Value | New Value | Data Type | Notes |
---|---|---|---|---|
2022-05-10 18:45:45 | Added to TrackCVE | |||
2022-12-03 02:56:08 | 2018-03-02T15:29Z | 2018-03-02T15:29:00 | CVE Published Date | updated |
2022-12-03 02:56:08 | 2018-04-12T01:29:10 | CVE Modified Date | updated | |
2022-12-03 02:56:08 | Modified | Vulnerability Status | updated | |
2023-02-02 17:07:17 | 2023-02-02T16:18:39 | CVE Modified Date | updated | |
2023-02-02 17:07:18 | Context relabeling of filesystems is vulnerable to symbolic link attack, allowing a local, unprivileged malicious entity to change the SELinux context of an arbitrary file to a context with few restrictions. This only happens when the relabeling process is done, usually when taking SELinux state from disabled to enable (permissive or enforcing). The issue was found in policycoreutils 2.5-11. | Context relabeling of filesystems is vulnerable to symbolic link attack, allowing a local, unprivileged malicious entity to change the SELinux context of an arbitrary file to a context with few restrictions. This only happens when the relabeling process is done, usually when taking SELinux state from disabled to enable (permissive or enforcing). | Description | updated |
2023-02-02 17:07:18 | References | updated | ||
2023-02-13 01:07:42 | 2023-02-12T23:32:32 | CVE Modified Date | updated | |
2023-02-13 01:07:42 | Weakness Enumeration | update | ||
2023-02-13 01:07:43 | Context relabeling of filesystems is vulnerable to symbolic link attack, allowing a local, unprivileged malicious entity to change the SELinux context of an arbitrary file to a context with few restrictions. This only happens when the relabeling process is done, usually when taking SELinux state from disabled to enable (permissive or enforcing). | Context relabeling of filesystems is vulnerable to symbolic link attack, allowing a local, unprivileged malicious entity to change the SELinux context of an arbitrary file to a context with few restrictions. This only happens when the relabeling process is done, usually when taking SELinux state from disabled to enable (permissive or enforcing). The issue was found in policycoreutils 2.5-11. | Description | updated |