CVE-2025-48059 – com.powsybl:powsybl-contingency-api

Package

Manager: maven
Name: com.powsybl:powsybl-contingency-api
Vulnerable Version: >=5.0.0 <6.3.0

Severity

Level: Low

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L/E:U/RL:O/RC:R

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U

EPSS: 0.00059 pctl0.18749

Details

PowSyBl Core Contains a Polynomial ReDoS in RegexCriterion ### Impact _What kind of vulnerability is it? Who is impacted?_ This is an advisory for a **potential polynomial Regular Expression Denial of Service (ReDoS)** vulnerability in the `RegexCriterion` class. This class compiles and evaluates an unvalidated, user-supplied regular expression against the identifier of an `Identifiable` object via `Pattern.compile(regex).matcher(id).find()`. To trigger **polynomial ReDoS** in `RegexCriterion`, **two attacker-controlled conditions** must be met: - **Control over the regex input** passed into the constructor: - _Example:_ An attacker supplies a malicious pattern such as `(.*a){10000}`. - **Control or influence over the output of `Identifiable.getId()`**: - _Example:_ A long string like `"aaaa...!"` that forces excessive backtracking. If both conditions are satisfied, a malicious actor can cause **significant CPU exhaustion** through repeated or recursive `filter(...)` calls — especially if performed over large network models or filtering operations. While this class does not handle file or memory data directly, its reliance on untrusted regular expressions and potentially attacker-controlled identifiers makes it vulnerable to **polynomial ReDoS** under the right conditions. This risk is amplified when the library is used in dynamic or scriptable environments where external users control either criterion construction or network object identifiers. Although not as dangerous as _catastrophic exponential ReDoS_, the polynomial pattern still induces significant performance degradation as input size increases. #### Am I impacted? Since `RegexCriterion` are used to define contingencies or limit reductions, you are vulnerable if: - you allow untrusted users to define contingency lists or limit reductions using this criterion; - OR you load untrusted contingencies or limit reductions files AND use them with a network containing untrusted identifiers. ### Patches com.powsybl:powsybl-iidm-criteria:6.7.2 and higher ### References [powsybl-core v6.7.2](https://github.com/powsybl/powsybl-core/releases/tag/v6.7.2)

Metadata

Created: 2025-06-19T16:19:48Z
Modified: 2025-06-20T22:20:47Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/06/GHSA-8qjw-9xgm-c9ff/GHSA-8qjw-9xgm-c9ff.json
CWE IDs: ["CWE-1333"]
Alternative ID: GHSA-8qjw-9xgm-c9ff
Finding: F211
Auto approve: 1