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. Impact: In body-parser versions prior to 1.20.6 (1.x line) and 2.3.0 (2.x line), when the parser is configured with an invalid limit option value such as an unparseable string or NaN, bytes.parse returns null and the request body size check is silently skipped. Applications that rely on limit as their primary safeguard against oversized request bodies will accept arbitrarily large payloads, leading to excessive memory and CPU usage and denial of service. Patches: This issue is fixed in body-parser 1.20.6 and 2.3.0. After the fix, invalid limit values throw a clear error at parser construction time instead of silently disabling enforcement, while null and undefined continue to fall back to the default limit of 100kb. Workarounds: Validate the limit value before passing it to body-parser. For example, parse the value at startup and reject any configuration where the result is null or a non-finite number.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle. Changing version to 45.
Addressed in 1.27 rebase $ jq '.packages."node_modules/body-parser".version' sgx-pccs-1.27-build/confidential-computing.tee.dcap.pccs-DCAP_1.27/service/package-lock.json "2.4.0"
FEDORA-2026-069bc15d81 (sgx-pccs-1.27-2.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-069bc15d81
FEDORA-2026-7277fc13ac (sgx-pccs-1.27-2.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-7277fc13ac
FEDORA-2026-d015d281d3 (sgx-pccs-1.27-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-d015d281d3
FEDORA-2026-069bc15d81 has been pushed to the Fedora 45 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-069bc15d81` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-069bc15d81 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-7277fc13ac has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-7277fc13ac` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-7277fc13ac See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-d015d281d3 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-d015d281d3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-d015d281d3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-069bc15d81 (sgx-pccs-1.27-2.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-7277fc13ac (sgx-pccs-1.27-2.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-d015d281d3 (sgx-pccs-1.27-2.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.