CVE-2018-1063: Context relabeling of filesystems is vulnerable to symbolic link attack, allowing a local, unprivileged malicious entity to change the…
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.40% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: policycoreutils (Debian:12) 2.7-1; coreutils (openSUSE:Tumbleweed) 3.2-1.4; policycoreutils (Red Hat:enterprise_linux:7::client) 0:2.5-22.el7.
Low priority for now. Upgrade to policycoreutils (Debian:12) 2.7-1; coreutils (openSUSE:Tumbleweed) 3.2-1.4; policycoreutils (Red Hat:enterprise_linux:7::client) 0:2.5-22.el7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 2, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 34th percentile
- CWE
- CWE-59
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| selinux project | selinux | cpe:2.3:a:selinux_project:selinux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
SELinux Project policycoreutils
- 2.5-11 and neweraffected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat enterprise linux7.0
- selinux project selinuxall versions
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | policycoreutils | before 2.7-1 | 2.7-1 |
| openSUSE:Tumbleweed | coreutils | before 3.2-1.4 | 3.2-1.4 |
| Red Hat:enterprise_linux:7::client | policycoreutils | before 0:2.5-22.el7 | 0:2.5-22.el7 |
| Red Hat:enterprise_linux:7::client | policycoreutils-debuginfo | before 0:2.5-22.el7 | 0:2.5-22.el7 |
| Red Hat:enterprise_linux:7::client | policycoreutils-devel | before 0:2.5-22.el7 | 0:2.5-22.el7 |
| Red Hat:enterprise_linux:7::client | policycoreutils-gui | before 0:2.5-22.el7 | 0:2.5-22.el7 |
| Red Hat:enterprise_linux:7::client | policycoreutils-newrole | before 0:2.5-22.el7 | 0:2.5-22.el7 |
| Red Hat:enterprise_linux:7::client | policycoreutils-python | before 0:2.5-22.el7 | 0:2.5-22.el7 |
| Red Hat:enterprise_linux:7::client | policycoreutils-restorecond | before 0:2.5-22.el7 | 0:2.5-22.el7 |
| Red Hat:enterprise_linux:7::client | policycoreutils-sandbox | before 0:2.5-22.el7 | 0:2.5-22.el7 |
| SUSE:Linux Enterprise Server 11 SP4 | policycoreutils | before 2.0.79-4.9.3.3 | 2.0.79-4.9.3.3 |
| SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | policycoreutils | before 2.5-10.3.1 | 2.5-10.3.1 |
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-3246libuser before 0.56.13-8 and 0.60 before 0.60-7, as used in the userhelper program in the usermode package, directly modifies /etc/passwd…KEV62This week
- CVE-2023-50387Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of…60This week
- CVE-2017-5456A mechanism to bypass file system access protections in the sandbox using the file system request constructor through an IPC message.40Plan
Published before and after this one in the same product
- ← EarlierCVE-2015-7837Sep 19, 2017 · The Linux kernel, as used in Red Hat Enterprise Linux 7, kernel-rt, and Enterprise MRG 2 and when booted with UEFI Secure Boot enabled…22Monitor
- ← EarlierCVE-2017-15121Dec 6, 2017 · A non-privileged user is able to mount a fuse filesystem on RHEL 6 or 7 and crash a system if an application punches a hole in a file that…22Monitor
- Later →CVE-2017-5428Jun 11, 2018 · An integer overflow in "createImageBitmap()" was reported through the Pwn2Own contest.40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:policycoreutils | 2.7-1 · Debian:12 | Package registry (OSV) |
| opensuse:coreutils | 3.2-1.4 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:policycoreutils | 0:2.5-22.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:policycoreutils-debuginfo | 0:2.5-22.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:policycoreutils-devel | 0:2.5-22.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:policycoreutils-gui | 0:2.5-22.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:policycoreutils-newrole | 0:2.5-22.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:policycoreutils-python | 0:2.5-22.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:policycoreutils-restorecond | 0:2.5-22.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:policycoreutils-sandbox | 0:2.5-22.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| suse:policycoreutils | 2.5-10.3.1 · SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-59 · Improper Link Resolution Before File Access ('Link Following')CVSS vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
- Obfuscated Files or Information: HTML SmugglingT1027.006
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Autostart Execution:Shortcut ModificationT1547.009
- Hide Artifacts: Resource ForkingT1564.009
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: Services File Permissions WeaknessT1574.010
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.