CVE-2025-15039 : Chi tiết

CVE-2025-15039

9.4
/
Nghiêm trọng
2026-08-06
08h16 +00:00
Network
2026-09-29
14h10 +00:00
CVE.org
NVD
Thông báo cho một CVE
Luôn được thông báo về mọi thay đổi đối với một CVE cụ thể.
Quản lý thông báo

Mô tả CVE

The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of all required authentication steps when a specific multi-step pattern involving certain authenticators is configured. This allows an attacker to bypass intermediate authentication challenges by exploiting how the script handles callbacks and re-execution of authentication steps. Successful exploitation allows a malicious actor to gain unauthorized access to a targeted user account. This vulnerability can only be exploited when all of the following conditions are met: the application login flow contains a specific secondary authenticator, the Conditional Authentication script is configured with particular event callbacks and re-executes an authentication step, the targeted user has one of the impacted authenticators enrolled, and the attacker successfully completes any preceding authentication steps.

Thông tin CVE

Điểm yếu liên quan

CWE-ID Tên điểm yếu Nguồn
CWE-693 Protection Mechanism Failure
The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

Số liệu

Số liệu Điểm Mức độ nghiêm trọng CVSS Vector Nguồn
V3.1 9.4 CRITICAL CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

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.

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.

Low

Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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.

 ed10eef1-636d-4fbe-9993-6890dfa878f8

Sản phẩm được đề cập

Cấu hình 0

Wso2>>Api_control_plane >> Version Từ (bao gồm) 4.5.0 Đến (không bao gồm) 4.5.0.45

Wso2>>Api_control_plane >> Version Từ (bao gồm) 4.6.0 Đến (không bao gồm) 4.6.0.9

Wso2>>Api_manager >> Version Từ (bao gồm) 2.6.0 Đến (không bao gồm) 2.6.0.150

Wso2>>Api_manager >> Version Từ (bao gồm) 3.0.0 Đến (không bao gồm) 3.0.0.180

Wso2>>Api_manager >> Version Từ (bao gồm) 3.1.0 Đến (không bao gồm) 3.1.0.356

Wso2>>Api_manager >> Version Từ (bao gồm) 3.2.0 Đến (không bao gồm) 3.2.0.460

Wso2>>Api_manager >> Version Từ (bao gồm) 3.2.1 Đến (không bao gồm) 3.2.1.79

Wso2>>Api_manager >> Version Từ (bao gồm) 4.0.0 Đến (không bao gồm) 4.0.0.381

Wso2>>Api_manager >> Version Từ (bao gồm) 4.1.0 Đến (không bao gồm) 4.1.0.244

Wso2>>Api_manager >> Version Từ (bao gồm) 4.2.0 Đến (không bao gồm) 4.2.0.184

Wso2>>Api_manager >> Version Từ (bao gồm) 4.3.0 Đến (không bao gồm) 4.3.0.95

Wso2>>Api_manager >> Version Từ (bao gồm) 4.4.0 Đến (không bao gồm) 4.4.0.59

Wso2>>Api_manager >> Version Từ (bao gồm) 4.5.0 Đến (không bao gồm) 4.5.0.44

Wso2>>Api_manager >> Version Từ (bao gồm) 4.6.0 Đến (không bao gồm) 4.6.0.8

Wso2>>Identity_server >> Version Từ (bao gồm) 5.7.0 Đến (không bao gồm) 5.7.0.130

Wso2>>Identity_server >> Version Từ (bao gồm) 5.8.0 Đến (không bao gồm) 5.8.0.133

Wso2>>Identity_server >> Version Từ (bao gồm) 5.9.0 Đến (không bao gồm) 5.9.0.173

Wso2>>Identity_server >> Version Từ (bao gồm) 5.10.0 Đến (không bao gồm) 5.10.0.385

Wso2>>Identity_server >> Version Từ (bao gồm) 5.11.0 Đến (không bao gồm) 5.11.0.432

Wso2>>Identity_server >> Version Từ (bao gồm) 6.0.0 Đến (không bao gồm) 6.0.0.259

Wso2>>Identity_server >> Version Từ (bao gồm) 6.1.0 Đến (không bao gồm) 6.1.0.260

Wso2>>Identity_server >> Version Từ (bao gồm) 7.0.0 Đến (không bao gồm) 7.0.0.138

Wso2>>Identity_server >> Version Từ (bao gồm) 7.1.0 Đến (không bao gồm) 7.1.0.49

Wso2>>Identity_server >> Version Từ (bao gồm) 7.2.0 Đến (không bao gồm) 7.2.0.7

Wso2>>Identity_server_as_key_manager >> Version Từ (bao gồm) 5.7.0 Đến (không bao gồm) 5.7.0.129

Wso2>>Identity_server_as_key_manager >> Version Từ (bao gồm) 5.9.0 Đến (không bao gồm) 5.9.0.179

Wso2>>Identity_server_as_key_manager >> Version Từ (bao gồm) 5.10.0 Đến (không bao gồm) 5.10.0.376

Wso2>>Open_banking_am >> Version Từ (bao gồm) 1.4.0 Đến (không bao gồm) 1.4.0.143

Wso2>>Open_banking_am >> Version Từ (bao gồm) 1.5.0 Đến (không bao gồm) 1.5.0.144

Wso2>>Open_banking_am >> Version Từ (bao gồm) 2.0.0 Đến (không bao gồm) 2.0.0.405

Wso2>>Open_banking_iam >> Version Từ (bao gồm) 2.0.0 Đến (không bao gồm) 2.0.0.425

Wso2>>Open_banking_km >> Version Từ (bao gồm) 1.4.0 Đến (không bao gồm) 1.4.0.137

Wso2>>Open_banking_km >> Version Từ (bao gồm) 1.5.0 Đến (không bao gồm) 1.5.0.127

Wso2>>Traffic_manager >> Version Từ (bao gồm) 4.5.0 Đến (không bao gồm) 4.5.0.43

Wso2>>Traffic_manager >> Version Từ (bao gồm) 4.6.0 Đến (không bao gồm) 4.6.0.8

Wso2>>Universal_gateway >> Version Từ (bao gồm) 4.5.0 Đến (không bao gồm) 4.5.0.44

Wso2>>Universal_gateway >> Version Từ (bao gồm) 4.6.0 Đến (không bao gồm) 4.6.0.8

Tài liệu tham khảo

Thông tin trình bày trên CVE Find đến từ nhiều nguồn tham chiếu được chọn lọc cẩn thận. Dữ liệu CVE được cung cấp bởi MITRE Corporation và Cơ sở dữ liệu lỗ hổng quốc gia (NVD). Danh mục lỗ hổng đã bị khai thác đã biết (KEV) có nguồn từ Cơ quan An ninh mạng và Cơ sở hạ tầng (CISA), trong khi điểm EPSS đến từ FIRST.org. Ngoài ra, dữ liệu về điểm yếu phần mềm (CWE) và mẫu tấn công phổ biến (CAPEC) được duy trì bởi MITRE Corporation, và thông tin về cấu hình phần cứng và phần mềm (CPE) được cung cấp bởi NVD.