CVE Vulnerabilities

CVE-2014-9513

Improper Access Control

Published: Aug 28, 2017 | Modified: Sep 08, 2017
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
7.5 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM

Insecure use of temporary files in xbindkeys-config 0.1.3-2 allows remote attackers to execute arbitrary code.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

Name Vendor Start Version End Version
Xbindkeys-config Debian 0.1.3-2 (including) 0.1.3-2 (including)
Xbindkeys-config Ubuntu artful *
Xbindkeys-config Ubuntu bionic *
Xbindkeys-config Ubuntu cosmic *
Xbindkeys-config Ubuntu disco *
Xbindkeys-config Ubuntu eoan *
Xbindkeys-config Ubuntu esm-apps/bionic *
Xbindkeys-config Ubuntu esm-apps/focal *
Xbindkeys-config Ubuntu esm-apps/jammy *
Xbindkeys-config Ubuntu esm-apps/xenial *
Xbindkeys-config Ubuntu focal *
Xbindkeys-config Ubuntu groovy *
Xbindkeys-config Ubuntu hirsute *
Xbindkeys-config Ubuntu impish *
Xbindkeys-config Ubuntu jammy *
Xbindkeys-config Ubuntu kinetic *
Xbindkeys-config Ubuntu lucid *
Xbindkeys-config Ubuntu lunar *
Xbindkeys-config Ubuntu mantic *
Xbindkeys-config Ubuntu precise *
Xbindkeys-config Ubuntu trusty *
Xbindkeys-config Ubuntu utopic *
Xbindkeys-config Ubuntu vivid *
Xbindkeys-config Ubuntu wily *
Xbindkeys-config Ubuntu xenial *
Xbindkeys-config Ubuntu yakkety *
Xbindkeys-config Ubuntu zesty *

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

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