CVE Vulnerabilities

CVE-2020-12695

Incorrect Default Permissions

Published: Jun 08, 2020 | Modified: Nov 21, 2024
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:H
CVSS 2.x
7.8 HIGH
AV:N/AC:M/Au:N/C:P/I:N/A:C
RedHat/V2
RedHat/V3
7.5 MODERATE
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:H
Ubuntu
MEDIUM

The Open Connectivity Foundation UPnP specification before 2020-04-17 does not forbid the acceptance of a subscription request with a delivery URL on a different network segment than the fully qualified event-subscription URL, aka the CallStranger issue.

Weakness

During installation, installed file permissions are set to allow anyone to modify those files.

Affected Software

Name Vendor Start Version End Version
Unifi_controller Ui - (including) - (including)
Red Hat Enterprise Linux 8 RedHat gssdp-0:1.0.5-1.el8 *
Red Hat Enterprise Linux 8 RedHat gupnp-0:1.0.6-1.el8 *
Gupnp Ubuntu bionic *
Gupnp Ubuntu esm-apps/bionic *
Gupnp Ubuntu esm-apps/xenial *
Gupnp Ubuntu focal *
Gupnp Ubuntu trusty *
Gupnp Ubuntu upstream *
Gupnp Ubuntu xenial *
Libupnp Ubuntu bionic *
Libupnp Ubuntu esm-apps/bionic *
Libupnp Ubuntu esm-apps/xenial *
Libupnp Ubuntu trusty *
Libupnp Ubuntu xenial *
Minidlna Ubuntu bionic *
Minidlna Ubuntu focal *
Minidlna Ubuntu groovy *
Minidlna Ubuntu trusty *
Minidlna Ubuntu upstream *
Minidlna Ubuntu xenial *
Pupnp-1.8 Ubuntu bionic *
Pupnp-1.8 Ubuntu esm-apps/bionic *
Pupnp-1.8 Ubuntu esm-apps/focal *
Pupnp-1.8 Ubuntu esm-apps/jammy *
Pupnp-1.8 Ubuntu focal *
Pupnp-1.8 Ubuntu groovy *
Pupnp-1.8 Ubuntu hirsute *
Pupnp-1.8 Ubuntu impish *
Pupnp-1.8 Ubuntu jammy *
Pupnp-1.8 Ubuntu kinetic *
Pupnp-1.8 Ubuntu lunar *
Wpa Ubuntu bionic *
Wpa Ubuntu devel *
Wpa Ubuntu eoan *
Wpa Ubuntu focal *
Wpa Ubuntu groovy *
Wpa Ubuntu hirsute *
Wpa Ubuntu impish *
Wpa Ubuntu jammy *
Wpa Ubuntu kinetic *
Wpa Ubuntu lunar *
Wpa Ubuntu mantic *
Wpa Ubuntu noble *
Wpa Ubuntu oracular *
Wpa Ubuntu trusty *
Wpa Ubuntu trusty/esm *
Wpa Ubuntu xenial *

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References