# CVE-2017-11565: Security feature bypass in n/a

> Attackers can bypass AppArmor restrictions on Tor by exploiting a flawed init script path assumption in specific Debian configurations.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-11565, GHSA-v9q4-769r-h63j, UBUNTU-CVE-2017-11565

## What is CVE-2017-11565?

CVE-2017-11565 is a high-severity vulnerability in n/a, published on 23 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

## Which versions are affected by CVE-2017-11565?

It affects 1 product.


Products: Debian Tor.

## How do I fix CVE-2017-11565?

Apply the vendor's patch.

## Is CVE-2017-11565 being exploited?

There is no known exploitation of CVE-2017-11565 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-11565 and fix it if it is affected.

What it is: CVE-2017-11565 is a high-severity vulnerability in n/a, published on 23 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-11565 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-11565/ (Markdown: https://insights.sbomify.com/CVE-2017-11565/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-11565
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-11565
- OSV: https://osv.dev/vulnerability/CVE-2017-11565

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-11565/
Summaries are generated and may contain mistakes; the official description above is the record.