CVE-2017-11565: n/a vulnerability

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

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

UnknownCVSS not scoredNot KEV-listedUpdatedAug 5, 2024, 18:12 UTC (UTC+00:00)

Security readout for executives and security teams

This issue can leave Tor running without the AppArmor confinement that operators expected on certain Debian package setups. It is not a remote Tor protocol flaw; it is an operating-system packaging and startup problem. The CVE notes default Debian stretch systems using systemd unit startup are not affected. Exposure appears limited to Debian Tor installations using the affected tor.init startup path with AppArmor expected. Default Debian stretch installations that start Tor through systemd are explicitly described as unaffected. Treat this as a targeted hardening issue, not an internet-wide emergency. Prioritize Debian Tor hosts where AppArmor confinement is part of risk control or compliance assumptions. Mitigation focus: Check Debian guidance for the fixed Tor package or maintainer recommendation.; Confirm Tor starts through systemd where applicable, not the affected init script.; Ensure AppArmor confinement is actually active for Tor after startup..

Prepared: Jun 13, 2026, 04:25 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-11565 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jul 23, 2017, 20:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://bugs.debian.org/869153CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.