Inefficient Regular Expression Complexity Affecting opensearch-dashboards-2-fips package, versions <2.19.1-r1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Inefficient Regular Expression Complexity vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-CHAINGUARDLATEST-OPENSEARCHDASHBOARDS2FIPS-9404500
- published14 Mar 2025
- disclosed11 Mar 2025
Introduced: 11 Mar 2025
NewCVE-2025-27789 (opens in a new tab)How to fix?
Upgrade Chainguard opensearch-dashboards-2-fips to version 2.19.1-r1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream opensearch-dashboards-2-fips package and not the opensearch-dashboards-2-fips package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
Babel is a compiler for writing next generation JavaScript. When using versions of Babel prior to 7.26.10 and 8.0.0-alpha.17 to compile regular expression named capturing groups, Babel will generate a polyfill for the .replace method that has quadratic complexity on some specific replacement pattern strings (i.e. the second argument passed to .replace). Generated code is vulnerable if all the following conditions are true: Using Babel to compile regular expression named capturing groups, using the .replace method on a regular expression that contains named capturing groups, and the code using untrusted strings as the second argument of .replace. This problem has been fixed in @babel/helpers and @babel/runtime 7.26.10 and 8.0.0-alpha.17. It's likely that individual users do not directly depend on @babel/helpers, and instead depend on @babel/core (which itself depends on @babel/helpers). Upgrading to @babel/core 7.26.10 is not required, but it guarantees use of a new enough @babel/helpers version. Note that just updating Babel dependencies is not enough; one will also need to re-compile the code. No known workarounds are available.