CVE Vulnerabilities

CVE-2020-15664

Incorrect Authorization

Published: Oct 01, 2020 | Modified: Oct 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 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Ubuntu
MEDIUM

By holding a reference to the eval() function from an about:blank window, a malicious webpage could have gained access to the InstallTrigger object which would allow them to prompt the user to install an extension. Combined with user confusion, this could result in an unintended or malicious extension being installed. This vulnerability affects Firefox < 80, Thunderbird < 78.2, Thunderbird < 68.12, Firefox ESR < 68.12, Firefox ESR < 78.2, and Firefox for Android < 80.

Weakness

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.

Affected Software

Name Vendor Start Version End Version
Firefox Mozilla * 80.0 (excluding)
Firefox Mozilla 78.0 (including) 78.2 (excluding)
Firefox_esr Mozilla * 68.12 (excluding)
Thunderbird Mozilla * 68.12 (excluding)
Thunderbird Mozilla 78.0 (including) 78.2 (excluding)
Red Hat Enterprise Linux 6 RedHat firefox-0:68.12.0-1.el6_10 *
Red Hat Enterprise Linux 6 RedHat thunderbird-0:68.12.0-1.el6_10 *
Red Hat Enterprise Linux 7 RedHat firefox-0:68.12.0-1.el7_8 *
Red Hat Enterprise Linux 7 RedHat thunderbird-0:68.12.0-1.el7_8 *
Red Hat Enterprise Linux 8 RedHat firefox-0:78.2.0-2.el8_2 *
Red Hat Enterprise Linux 8 RedHat thunderbird-0:68.12.0-1.el8_2 *
Red Hat Enterprise Linux 8.0 Update Services for SAP Solutions RedHat firefox-0:78.2.0-3.el8_0 *
Red Hat Enterprise Linux 8.0 Update Services for SAP Solutions RedHat thunderbird-0:68.12.0-1.el8_0 *
Red Hat Enterprise Linux 8.1 Extended Update Support RedHat firefox-0:78.2.0-3.el8_1 *
Red Hat Enterprise Linux 8.1 Extended Update Support RedHat thunderbird-0:68.12.0-1.el8_1 *
Firefox Ubuntu bionic *
Firefox Ubuntu devel *
Firefox Ubuntu focal *
Firefox Ubuntu groovy *
Firefox Ubuntu hirsute *
Firefox Ubuntu impish *
Firefox Ubuntu jammy *
Firefox Ubuntu kinetic *
Firefox Ubuntu lunar *
Firefox Ubuntu mantic *
Firefox Ubuntu noble *
Firefox Ubuntu trusty *
Firefox Ubuntu upstream *
Firefox Ubuntu xenial *
Firefox-esr Ubuntu trusty *
Firefox-esr Ubuntu upstream *
Mozjs38 Ubuntu bionic *
Mozjs38 Ubuntu esm-apps/bionic *
Mozjs38 Ubuntu upstream *
Mozjs52 Ubuntu bionic *
Mozjs52 Ubuntu esm-apps/focal *
Mozjs52 Ubuntu esm-infra/bionic *
Mozjs52 Ubuntu focal *
Mozjs52 Ubuntu groovy *
Mozjs52 Ubuntu upstream *
Mozjs60 Ubuntu upstream *
Mozjs68 Ubuntu focal *
Mozjs68 Ubuntu groovy *
Mozjs68 Ubuntu upstream *
Thunderbird Ubuntu bionic *
Thunderbird Ubuntu focal *
Thunderbird Ubuntu trusty *
Thunderbird Ubuntu upstream *
Thunderbird Ubuntu xenial *

Extended Description

Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user’s privileges and any permissions or other access-control specifications that apply to the resource. When access control checks are incorrectly applied, users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.

Potential Mitigations

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
  • Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
  • For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
  • One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.

References