CVE Vulnerabilities

CVE-2020-12424

Incorrect Default Permissions

Published: Jul 09, 2020 | Modified: Nov 21, 2024
CVSS 3.x
6.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
CVSS 2.x
4.3 MEDIUM
AV:N/AC:M/Au:N/C:N/I:P/A:N
RedHat/V2
RedHat/V3
6.5 LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

When constructing a permission prompt for WebRTC, a URI was supplied from the content process. This URI was untrusted, and could have been the URI of an origin that was previously granted permission; bypassing the prompt. This vulnerability affects Firefox < 78.

Weakness

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

Affected Software

NameVendorStart VersionEnd Version
FirefoxMozilla*78.0 (excluding)
Red Hat Enterprise Linux 7RedHatfirefox-0:78.3.0-1.el7_9*
Red Hat Enterprise Linux 8RedHatfirefox-0:78.2.0-2.el8_2*
Red Hat Enterprise Linux 8.0 Update Services for SAP SolutionsRedHatfirefox-0:78.2.0-3.el8_0*
Red Hat Enterprise Linux 8.1 Extended Update SupportRedHatfirefox-0:78.2.0-3.el8_1*
FirefoxUbuntubionic*
FirefoxUbuntudevel*
FirefoxUbuntueoan*
FirefoxUbuntufocal*
FirefoxUbuntugroovy*
FirefoxUbuntuhirsute*
FirefoxUbuntuimpish*
FirefoxUbuntujammy*
FirefoxUbuntukinetic*
FirefoxUbuntulunar*
FirefoxUbuntumantic*
FirefoxUbuntunoble*
FirefoxUbuntutrusty*
FirefoxUbuntuupstream*
FirefoxUbuntuxenial*
Mozjs38Ubuntubionic*
Mozjs38Ubuntuesm-apps/bionic*
Mozjs38Ubuntuupstream*
Mozjs52Ubuntubionic*
Mozjs52Ubuntueoan*
Mozjs52Ubuntuesm-apps/focal*
Mozjs52Ubuntuesm-infra/bionic*
Mozjs52Ubuntufocal*
Mozjs52Ubuntugroovy*
Mozjs52Ubuntuupstream*
Mozjs60Ubuntueoan*
Mozjs60Ubuntuupstream*
Mozjs68Ubuntuesm-infra/focal*
Mozjs68Ubuntufocal*
Mozjs68Ubuntugroovy*
Mozjs68Ubuntuupstream*
ThunderbirdUbuntubionic*
ThunderbirdUbuntueoan*
ThunderbirdUbuntufocal*
ThunderbirdUbuntutrusty*
ThunderbirdUbuntuupstream*
ThunderbirdUbuntuxenial*

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