CVE Vulnerabilities

CVE-2019-3866

Incorrect Permission Assignment for Critical Resource

Published: Nov 08, 2019 | Modified: Aug 04, 2021
CVSS 3.x
5.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
2.1 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
5.9 MODERATE
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N
Ubuntu
MEDIUM

An information-exposure vulnerability was discovered where openstack-mistrals undercloud log files containing clear-text information were made world readable. A malicious system user could exploit this flaw to access sensitive user information.

Weakness

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

Affected Software

Name Vendor Start Version End Version
Openstack-mistral Redhat - (including) - (including)
Red Hat OpenStack Platform 16.0 (Train) RedHat openstack-mistral-0:9.0.2-0.20191125120837.6651519.el8ost *
Red Hat Quay 3 RedHat quay/clair-rhel8:v3.4.0-25 *
Red Hat Quay 3 RedHat quay/quay-bridge-operator-bundle:v3.4.0-3 *
Red Hat Quay 3 RedHat quay/quay-bridge-operator-rhel8:v3.4.0-17 *
Red Hat Quay 3 RedHat quay/quay-builder-qemu-rhcos-rhel8:v3.4.0-17 *
Red Hat Quay 3 RedHat quay/quay-builder-rhel8:v3.4.0-18 *
Red Hat Quay 3 RedHat quay/quay-container-security-operator-bundle:v3.4.0-2 *
Red Hat Quay 3 RedHat quay/quay-container-security-operator-rhel8:v3.4.0-2 *
Red Hat Quay 3 RedHat quay/quay-openshift-bridge-rhel8-operator:v3.4.0-17 *
Red Hat Quay 3 RedHat quay/quay-operator-bundle:v3.4.0-89 *
Red Hat Quay 3 RedHat quay/quay-operator-rhel8:v3.4.0-132 *
Red Hat Quay 3 RedHat quay/quay-rhel8:v3.4.0-51 *
Mistral Ubuntu bionic *
Mistral Ubuntu disco *
Mistral Ubuntu eoan *
Mistral Ubuntu groovy *
Mistral Ubuntu hirsute *
Mistral Ubuntu impish *
Mistral Ubuntu kinetic *
Mistral Ubuntu lunar *
Mistral Ubuntu mantic *
Mistral Ubuntu trusty *
Mistral Ubuntu xenial *

Potential Mitigations

  • Run the code in a “jail” or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
  • OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.
  • This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.
  • Be careful to avoid CWE-243 and other weaknesses related to jails.

References