Fedora Account System
Red Hat Associate
Red Hat Customer
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to 1.1.21, 2.1.7, 3.0.9, and 5.0.12, the expand function handles untrusted {a},b}-shaped patterns with many trailing closing braces by restarting its scan once for each trailing closing brace. The successive full-input rescans with linear working-string growth cause quadratic CPU time and memory pressure that can block the Node.js event loop. The process eventually recovers, making the impact a recoverable CPU denial of service. This issue is fixed in versions 1.1.21, 2.1.7, 3.0.9, and 5.0.12.
As I have said repeatedly: The CVE does not affect Boost. The Node modules are only used to generate HTML files during preparation of the release tarball, and are not used during the RPM build and are not part of the installed RPMs. I checked this with upstream and was told "The npm packages are only required at doc build time, so it makes sense to not include them in the release tarball." https://lists.boost.org/archives/list/boost@lists.boost.org/thread/APKJIASXU2DLQMGYIQR4JOMJE5CB56KB/ The Boost 1.92.0 release will not include those files in the release tarball at all, due to https://github.com/boostorg/release-tools/pull/111 which was already changed in March. That PR says "Remove "doc/node_modules" from libraries after the build. Since that directory adds extra MBs, and isn't needed."