CVE-2023-3972 : Détail

CVE-2023-3972

7.8
/
Haute
A01-Broken Access Control
0.04%V3
Local
2023-11-01
15h54 +00:00
2024-11-23
01h25 +00:00
CVE.org
NVD
Notifications pour un CVE
Restez informé de toutes modifications pour un CVE spécifique.
Gestion des notifications

Descriptions du CVE

Insights-client: unsafe handling of temporary files and directories

A vulnerability was found in insights-client. This security issue occurs because of insecure file operations or unsafe handling of temporary files and directories that lead to local privilege escalation. Before the insights-client has been registered on the system by root, an unprivileged local user or attacker could create the /var/tmp/insights-client directory (owning the directory with read, write, and execute permissions) on the system. After the insights-client is registered by root, an attacker could then control the directory content that insights are using by putting malicious scripts into it and executing arbitrary code as root (trivially bypassing SELinux protections because insights processes are allowed to disable SELinux system-wide).

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-379 Creation of Temporary File in Directory with Insecure Permissions
The product creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file.
CWE-668 Exposure of Resource to Wrong Sphere
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V3.1 7.8 HIGH CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

Low

The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

Score EPSS

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Percentile EPSS

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.
EPSS First.org

Products Mentioned

Configuraton 0

Redhat>>Insights-client >> Version To (excluding) 3.2.2

Configuraton 0

Redhat>>Enterprise_linux >> Version 7.0

Redhat>>Enterprise_linux >> Version 8.0

Redhat>>Enterprise_linux >> Version 9.0

Redhat>>Enterprise_linux_aus >> Version 8.6

Redhat>>Enterprise_linux_desktop >> Version 7.0

Redhat>>Enterprise_linux_eus >> Version 8.6

Redhat>>Enterprise_linux_eus >> Version 8.8

Redhat>>Enterprise_linux_eus >> Version 9.0

Redhat>>Enterprise_linux_eus >> Version 9.2

Redhat>>Enterprise_linux_for_arm_64 >> Version 8.0

Redhat>>Enterprise_linux_for_arm_64_eus >> Version 8.6

Redhat>>Enterprise_linux_for_arm_64_eus >> Version 8.8

Redhat>>Enterprise_linux_for_arm_64_eus >> Version 9.0

Redhat>>Enterprise_linux_for_arm_64_eus >> Version 9.2

Redhat>>Enterprise_linux_for_ibm_z_systems >> Version 7.0

Redhat>>Enterprise_linux_for_ibm_z_systems >> Version 8.0

Redhat>>Enterprise_linux_for_ibm_z_systems >> Version 9.0

Redhat>>Enterprise_linux_for_ibm_z_systems_eus >> Version 8.6

Redhat>>Enterprise_linux_for_ibm_z_systems_eus >> Version 8.8

Redhat>>Enterprise_linux_for_ibm_z_systems_eus >> Version 9.0

Redhat>>Enterprise_linux_for_ibm_z_systems_eus >> Version 9.2

Redhat>>Enterprise_linux_for_power_big_endian >> Version 7.0

Redhat>>Enterprise_linux_for_power_little_endian >> Version 7.0

Redhat>>Enterprise_linux_for_power_little_endian >> Version 8.0

Redhat>>Enterprise_linux_for_power_little_endian >> Version 9.0

Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 8.6

Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 8.8

Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 9.2

Redhat>>Enterprise_linux_for_scientific_computing >> Version 7.0

Redhat>>Enterprise_linux_server >> Version 7.0

Redhat>>Enterprise_linux_server_aus >> Version 8.2

Redhat>>Enterprise_linux_server_aus >> Version 8.4

Redhat>>Enterprise_linux_server_aus >> Version 9.2

Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 8.1

  • Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 8.1 (Open CPE detail)

Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 8.2

  • Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 8.2 (Open CPE detail)

Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 8.4

  • Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 8.4 (Open CPE detail)

Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 8.6

  • Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 8.6 (Open CPE detail)

Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 8.8

  • Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 8.8 (Open CPE detail)

Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 9.0

  • Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 9.0 (Open CPE detail)

Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 9.2

  • Redhat>>Enterprise_linux_server_for_power_little_endian_update_services_for_sap_solutions >> Version 9.2 (Open CPE detail)

Redhat>>Enterprise_linux_server_tus >> Version 8.2

Redhat>>Enterprise_linux_server_tus >> Version 8.4

Redhat>>Enterprise_linux_server_tus >> Version 8.6

Redhat>>Enterprise_linux_server_tus >> Version 8.8

Redhat>>Enterprise_linux_server_update_services_for_sap_solutions >> Version 9.2

  • Redhat>>Enterprise_linux_server_update_services_for_sap_solutions >> Version 9.2 (Open CPE detail)

Redhat>>Enterprise_linux_update_services_for_sap_solutions >> Version 8.1

  • Redhat>>Enterprise_linux_update_services_for_sap_solutions >> Version 8.1 (Open CPE detail)

Redhat>>Enterprise_linux_update_services_for_sap_solutions >> Version 8.2

  • Redhat>>Enterprise_linux_update_services_for_sap_solutions >> Version 8.2 (Open CPE detail)

Redhat>>Enterprise_linux_update_services_for_sap_solutions >> Version 8.4

  • Redhat>>Enterprise_linux_update_services_for_sap_solutions >> Version 8.4 (Open CPE detail)

Redhat>>Enterprise_linux_update_services_for_sap_solutions >> Version 8.6

  • Redhat>>Enterprise_linux_update_services_for_sap_solutions >> Version 8.6 (Open CPE detail)

Redhat>>Enterprise_linux_update_services_for_sap_solutions >> Version 8.8

  • Redhat>>Enterprise_linux_update_services_for_sap_solutions >> Version 8.8 (Open CPE detail)

Références

https://access.redhat.com/errata/RHSA-2023:6264
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2023:6282
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2023:6283
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2023:6284
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2023:6795
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2023:6796
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2023:6798
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2023:6811
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/security/cve/CVE-2023-3972
Tags : vdb-entry, x_refsource_REDHAT
https://bugzilla.redhat.com/show_bug.cgi?id=2227027
Tags : issue-tracking, x_refsource_REDHAT