CVE-2025-3155 : Détail

CVE-2025-3155

7.4
/
Haute
A08-Soft and Data Integrity FailA01-Broken Access Control
0.06%V4
Network
2025-04-03
13h34 +00:00
2025-05-28
20h03 +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

Yelp: arbitrary file read

A flaw was found in Yelp. The Gnome user help application allows the help document to execute arbitrary scripts. This vulnerability allows malicious users to input help documents, which may exfiltrate user files to an external environment.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-829 Inclusion of Functionality from Untrusted Control Sphere
The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.
CWE-601 URL Redirection to Untrusted Site ('Open Redirect')
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.

Métriques

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

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.

Network

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).

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.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.

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.

Required

Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.

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.

Changed

An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.

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.

None

There is no loss of integrity within the impacted component.

Availability Impact

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

None

There is no impact to availability within the impacted component.

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

Gnome>>Yelp >> Version 42.2-8

    Configuraton 0

    Debian>>Debian_linux >> Version 11.0

    Configuraton 0

    Redhat>>Codeready_linux_builder >> Version 8.0

    Redhat>>Codeready_linux_builder >> Version 9.0

    Redhat>>Codeready_linux_builder_for_arm64 >> Version 8.0_aarch64

    Redhat>>Codeready_linux_builder_for_arm64 >> Version 9.0_aarch64

    Redhat>>Codeready_linux_builder_for_arm64_eus >> Version 8.8_aarch64

      Redhat>>Codeready_linux_builder_for_arm64_eus >> Version 9.2_aarch64

      Redhat>>Codeready_linux_builder_for_arm64_eus >> Version 9.4_aarch64

        Redhat>>Codeready_linux_builder_for_arm64_eus >> Version 9.6_aarch64

          Redhat>>Codeready_linux_builder_for_eus >> Version 8.8

            Redhat>>Codeready_linux_builder_for_eus >> Version 9.2

              Redhat>>Codeready_linux_builder_for_eus >> Version 9.4

                Redhat>>Codeready_linux_builder_for_ibm_z_systems >> Version 8.0_s390x

                Redhat>>Codeready_linux_builder_for_ibm_z_systems >> Version 9.0_s390x

                Redhat>>Codeready_linux_builder_for_ibm_z_systems_eus >> Version 8.8_s390x

                  Redhat>>Codeready_linux_builder_for_ibm_z_systems_eus >> Version 9.2_s390x

                  • Redhat>>Codeready_linux_builder_for_ibm_z_systems_eus >> Version 9.2_s390x (Open CPE detail)

                  Redhat>>Codeready_linux_builder_for_ibm_z_systems_eus >> Version 9.4_s390x

                    Redhat>>Codeready_linux_builder_for_ibm_z_systems_eus >> Version 9.6_s390x

                      Redhat>>Codeready_linux_builder_for_power_little_endian >> Version 8.0_ppc64le

                      • Redhat>>Codeready_linux_builder_for_power_little_endian >> Version 8.0_ppc64le (Open CPE detail)

                      Redhat>>Codeready_linux_builder_for_power_little_endian >> Version 9.0_ppc64le

                      • Redhat>>Codeready_linux_builder_for_power_little_endian >> Version 9.0_ppc64le (Open CPE detail)

                      Redhat>>Codeready_linux_builder_for_power_little_endian_eus >> Version 8.8_ppc64le

                        Redhat>>Codeready_linux_builder_for_power_little_endian_eus >> Version 9.2_ppc64le

                        • Redhat>>Codeready_linux_builder_for_power_little_endian_eus >> Version 9.2_ppc64le (Open CPE detail)

                        Redhat>>Codeready_linux_builder_for_power_little_endian_eus >> Version 9.4_ppc64le

                          Redhat>>Codeready_linux_builder_for_power_little_endian_eus >> Version 9.6_ppc64le

                            Redhat>>Enterprise_linux >> Version 8.0

                            Redhat>>Enterprise_linux >> Version 9.0

                            Redhat>>Enterprise_linux_eus >> Version 9.2

                            Redhat>>Enterprise_linux_eus >> Version 9.4

                            Redhat>>Enterprise_linux_eus >> Version 9.6

                              Redhat>>Enterprise_linux_for_arm_64 >> Version 8.0

                              Redhat>>Enterprise_linux_for_arm_64 >> Version 8.8_aarch64

                              Redhat>>Enterprise_linux_for_arm_64 >> Version 9.0_aarch64

                              Redhat>>Enterprise_linux_for_arm_64 >> Version 9.2_aarch64

                              Redhat>>Enterprise_linux_for_arm_64_eus >> Version 9.4_aarch64

                              Redhat>>Enterprise_linux_for_arm_64_eus >> Version 9.6_aarch64

                                Redhat>>Enterprise_linux_for_ibm_z_systems >> Version 8.0_s390x

                                Redhat>>Enterprise_linux_for_ibm_z_systems >> Version 9.0_s390x

                                Redhat>>Enterprise_linux_for_ibm_z_systems_eus >> Version 8.8_s390x

                                Redhat>>Enterprise_linux_for_ibm_z_systems_eus >> Version 9.2_s390x

                                Redhat>>Enterprise_linux_for_ibm_z_systems_eus >> Version 9.4_s390x

                                Redhat>>Enterprise_linux_for_ibm_z_systems_eus >> Version 9.6_s390x

                                  Redhat>>Enterprise_linux_for_power_little_endian >> Version 8.0_ppc64le

                                  Redhat>>Enterprise_linux_for_power_little_endian >> Version 9.0_ppc64le

                                  Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 8.8_ppc64le

                                  • Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 8.8_ppc64le (Open CPE detail)

                                  Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 9.2_ppc64le

                                  • Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 9.2_ppc64le (Open CPE detail)

                                  Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 9.4_ppc64le

                                  • Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 9.4_ppc64le (Open CPE detail)

                                  Redhat>>Enterprise_linux_for_power_little_endian_eus >> Version 9.6_ppc64le

                                    Redhat>>Enterprise_linux_server_aus >> Version 8.2

                                    Redhat>>Enterprise_linux_server_aus >> Version 8.4

                                    Redhat>>Enterprise_linux_server_aus >> Version 8.6

                                    Redhat>>Enterprise_linux_server_aus >> Version 9.2

                                    Redhat>>Enterprise_linux_server_aus >> Version 9.4

                                    Redhat>>Enterprise_linux_server_aus >> Version 9.6

                                      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_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)

                                      Redhat>>Enterprise_linux_update_services_for_sap_solutions >> Version 9.0

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

                                      Redhat>>Enterprise_linux_update_services_for_sap_solutions >> Version 9.2

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

                                      Redhat>>Enterprise_linux_update_services_for_sap_solutions >> Version 9.4

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

                                      Références

                                      https://access.redhat.com/errata/RHSA-2025:4450
                                      Tags : vendor-advisory, x_refsource_REDHAT
                                      https://access.redhat.com/errata/RHSA-2025:4451
                                      Tags : vendor-advisory, x_refsource_REDHAT
                                      https://access.redhat.com/errata/RHSA-2025:4455
                                      Tags : vendor-advisory, x_refsource_REDHAT
                                      https://access.redhat.com/errata/RHSA-2025:4456
                                      Tags : vendor-advisory, x_refsource_REDHAT
                                      https://access.redhat.com/errata/RHSA-2025:4457
                                      Tags : vendor-advisory, x_refsource_REDHAT
                                      https://access.redhat.com/errata/RHSA-2025:4505
                                      Tags : vendor-advisory, x_refsource_REDHAT
                                      https://access.redhat.com/errata/RHSA-2025:4532
                                      Tags : vendor-advisory, x_refsource_REDHAT
                                      https://access.redhat.com/errata/RHSA-2025:7430
                                      Tags : vendor-advisory, x_refsource_REDHAT
                                      https://access.redhat.com/errata/RHSA-2025:7569
                                      Tags : vendor-advisory, x_refsource_REDHAT
                                      https://access.redhat.com/security/cve/CVE-2025-3155
                                      Tags : vdb-entry, x_refsource_REDHAT
                                      https://bugzilla.redhat.com/show_bug.cgi?id=2357091
                                      Tags : issue-tracking, x_refsource_REDHAT
                                      Les informations affichées sur CVE Find proviennent de plusieurs sources de référence rigoureusement sélectionnées. Les données CVE sont fournies par MITRE Corporation et la National Vulnerability Database (NVD). Le catalogue des vulnérabilités activement exploitées (KEV) provient de la Cybersecurity and Infrastructure Security Agency (CISA), tandis que les scores EPSS sont issus de FIRST.org. Enfin, les données relatives aux faiblesses logicielles (CWE) et aux schémas d'attaque courants (CAPEC) sont maintenues par MITRE Corporation, et les informations sur les configurations logicielles et matérielles (CPE) proviennent du NVD.