CVE Vulnerabilities

CVE-2021-39184

Exposure of Resource to Wrong Sphere

Published: Oct 12, 2021 | Modified: Nov 21, 2024
CVSS 3.x
8.6
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
Ubuntu

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. A vulnerability in versions prior to 11.5.0, 12.1.0, and 13.3.0 allows a sandboxed renderer to request a thumbnail image of an arbitrary file on the users system. The thumbnail can potentially include significant parts of the original file, including textual data in many cases. Versions 15.0.0-alpha.10, 14.0.0, 13.3.0, 12.1.0, and 11.5.0 all contain a fix for the vulnerability. Two workarounds aside from upgrading are available. One may make the vulnerability significantly more difficult for an attacker to exploit by enabling contextIsolation in ones app. One may also disable the functionality of the createThumbnailFromPath API if one does not need it.

Weakness

The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

Affected Software

Name Vendor Start Version End Version
Electron Electronjs 10.1.0 (including) 11.5.0 (excluding)
Electron Electronjs 12.0.0 (including) 12.1.0 (excluding)
Electron Electronjs 13.0.0 (including) 13.3.0 (excluding)
Electron Electronjs 14.0.0-beta1 (including) 14.0.0-beta1 (including)
Electron Electronjs 14.0.0-beta10 (including) 14.0.0-beta10 (including)
Electron Electronjs 14.0.0-beta11 (including) 14.0.0-beta11 (including)
Electron Electronjs 14.0.0-beta12 (including) 14.0.0-beta12 (including)
Electron Electronjs 14.0.0-beta13 (including) 14.0.0-beta13 (including)
Electron Electronjs 14.0.0-beta14 (including) 14.0.0-beta14 (including)
Electron Electronjs 14.0.0-beta15 (including) 14.0.0-beta15 (including)
Electron Electronjs 14.0.0-beta16 (including) 14.0.0-beta16 (including)
Electron Electronjs 14.0.0-beta17 (including) 14.0.0-beta17 (including)
Electron Electronjs 14.0.0-beta18 (including) 14.0.0-beta18 (including)
Electron Electronjs 14.0.0-beta19 (including) 14.0.0-beta19 (including)
Electron Electronjs 14.0.0-beta2 (including) 14.0.0-beta2 (including)
Electron Electronjs 14.0.0-beta20 (including) 14.0.0-beta20 (including)
Electron Electronjs 14.0.0-beta21 (including) 14.0.0-beta21 (including)
Electron Electronjs 14.0.0-beta22 (including) 14.0.0-beta22 (including)
Electron Electronjs 14.0.0-beta23 (including) 14.0.0-beta23 (including)
Electron Electronjs 14.0.0-beta24 (including) 14.0.0-beta24 (including)
Electron Electronjs 14.0.0-beta25 (including) 14.0.0-beta25 (including)
Electron Electronjs 14.0.0-beta3 (including) 14.0.0-beta3 (including)
Electron Electronjs 14.0.0-beta4 (including) 14.0.0-beta4 (including)
Electron Electronjs 14.0.0-beta5 (including) 14.0.0-beta5 (including)
Electron Electronjs 14.0.0-beta6 (including) 14.0.0-beta6 (including)
Electron Electronjs 14.0.0-beta7 (including) 14.0.0-beta7 (including)
Electron Electronjs 14.0.0-beta8 (including) 14.0.0-beta8 (including)
Electron Electronjs 14.0.0-beta9 (including) 14.0.0-beta9 (including)
Electron Electronjs 15.0.0-alpha1 (including) 15.0.0-alpha1 (including)
Electron Electronjs 15.0.0-alpha2 (including) 15.0.0-alpha2 (including)
Electron Electronjs 15.0.0-alpha3 (including) 15.0.0-alpha3 (including)
Electron Electronjs 15.0.0-alpha4 (including) 15.0.0-alpha4 (including)
Electron Electronjs 15.0.0-alpha5 (including) 15.0.0-alpha5 (including)
Electron Electronjs 15.0.0-alpha6 (including) 15.0.0-alpha6 (including)
Electron Electronjs 15.0.0-alpha7 (including) 15.0.0-alpha7 (including)
Electron Electronjs 15.0.0-alpha8 (including) 15.0.0-alpha8 (including)
Electron Electronjs 15.0.0-alpha9 (including) 15.0.0-alpha9 (including)

Extended Description

Resources such as files and directories may be inadvertently exposed through mechanisms such as insecure permissions, or when a program accidentally operates on the wrong object. For example, a program may intend that private files can only be provided to a specific user. This effectively defines a control sphere that is intended to prevent attackers from accessing these private files. If the file permissions are insecure, then parties other than the user will be able to access those files. A separate control sphere might effectively require that the user can only access the private files, but not any other files on the system. If the program does not ensure that the user is only requesting private files, then the user might be able to access other files on the system. In either case, the end result is that a resource has been exposed to the wrong party.

References