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.19, 2.1.5, 3.0.7, and 5.0.10, crafted brace patterns can exhaust the native stack in parseCommaParts because parseCommaParts recursively processes the remainder once per brace group and uses push.apply to pass every element of a very large comma-part array as a function argument. Patterns containing many comma-separated brace groups trigger the recursive path, while the large array triggers the argument-array path without deep recursion. These paths cause recursive and argument-array native stack exhaustion before max or maxLength can limit output, potentially terminating the Node.js process in a process-terminating denial of service. This issue is fixed in versions 1.1.19, 2.1.5, 3.0.7, and 5.0.10.
Is there any way to stop ProdSec from reporting these? I've explained 20 times why there are no Node.js or NPM CVEs affecting Boost, see the replies to every bug you've filed for them: https://bugzilla.redhat.com/buglist.cgi?columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cbug_severity&component=boost&list_id=13700574&order=severity%2C%20&product=Fedora&query_format=advanced&short_desc=CVE-2026-&short_desc_type=casesubstring
To report myself, again: 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."
(In reply to Jonathan Wakely from comment #2) > To report myself, again: Oops, "repeat"