LiveActive security incident?Get immediate response
CVE Record

CVE-2020-27352: When generating the systemd service units for the docker snap (and other similar snaps), snapd does not spe...

When generating the systemd service units for the docker snap (and other similar snaps), snapd does not specify Delegate=yes - as a result systemd will move processes from the containers created and managed by these snaps into the cgroup of the main daemon within the snap itself when reloading system units. This may grant additional privileges to a container within the snap that were not originally intended.

CriticalCVSS 9.3Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This flaw affects snapd’s generated systemd service units for the docker snap and similar snaps. During system unit reloads, container processes may be moved into the main snap daemon’s cgroup, potentially giving a container more privileges than intended.

Executive priority

Treat as high-priority where snapd-managed containers run production or sensitive workloads. The issue can weaken container isolation assumptions, but urgency should be scoped to confirmed snapd and docker-snap exposure.

Technical view

snapd omitted Delegate=yes when generating relevant systemd units. Without delegation, systemd can reassign managed container processes to the snap daemon cgroup during reloads. The CVE maps to CWE-269 and is scored CVSS 9.3 with local, low-complexity impact across confidentiality, integrity, and availability.

Likely exposure

Exposure is most relevant to systems using Canonical snapd with the docker snap or similar snaps that create and manage containers. The source bundle does not provide precise affected version ranges beyond the snapd package reference.

Exploitation context

The source bundle does not show KEV listing or other evidence of active exploitation. The weakness is local and container-related: risk depends on whether affected snap-managed container services are present and how privilege boundaries are relied upon.

Researcher notes

Evidence supports a privilege management flaw in snapd-generated systemd units. Version and fix details are incomplete in the provided bundle, so validation should rely on Canonical’s advisory and package metadata rather than assumed vulnerable ranges.

Mitigation direction

  • Review Canonical USN-4728-1 and apply vendor-recommended snapd updates.
  • Inventory hosts using snapd with docker or similar container-managing snaps.
  • Prioritize systems where containers handle sensitive workloads or untrusted code.
  • Check vendor guidance before applying compensating controls or configuration changes.

Validation and detection

  • Confirm whether snapd is installed on in-scope Linux hosts.
  • Identify snap-managed docker or similar container services.
  • Review generated systemd units for vendor-documented corrected behavior.
  • Verify remediation status against Canonical USN-4728-1.
Prepared
Confidence
medium
Sources
4

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.

cwe · medium confidence lookup

CWE-269: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-27352 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
Critical
CVSS
9.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.3CVSS 3.1CriticalCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H2.56Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.3Critical
CVSS 3.1 vector shape for CVE-2020-27352Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Canonical Ltd.snapdsnapd, 0Listed
Weakness

CWE details

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

CWE-269 · source CWE mapping

Improper Privilege Management

Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.