Bug 2498736

Summary: CVE-2026-12590 sgx-pccs: body-parser: Denial of Service via invalid limit option [fedora-all]
Product: [Fedora] Fedora Reporter: Jon Moroney <jmoroney>
Component: sgx-pccsAssignee: Daniel Berrangé <berrange>
Status: ON_QA --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 45CC: berrange
Target Milestone: ---Keywords: Reopened, Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["dc39e583-bec8-4630-928f-e2bb7c99e74f"]}
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-09-07 05:57:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2498472    

Description Jon Moroney 2026-07-09 20:28:31 UTC
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.

Comment 1 Aoife Moloney 2026-08-17 15:16:57 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle.
Changing version to 45.

Comment 2 Daniel Berrangé 2026-11-09 17:12:43 UTC
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"

Comment 3 Fedora Update System 2026-11-09 17:35:50 UTC
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

Comment 4 Fedora Update System 2026-11-09 18:12:01 UTC
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

Comment 5 Fedora Update System 2026-11-09 19:52:26 UTC
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

Comment 6 Fedora Update System 2026-11-10 02:18:36 UTC
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.

Comment 7 Fedora Update System 2026-11-10 02:53:30 UTC
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.

Comment 8 Fedora Update System 2026-11-10 03:15:50 UTC
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.