Bug 2296979 - CVE-2024-38517 rapidjson: privilege escalation via integer underflow in GenericReader::ParseNumber() [fedora-all]
Summary: CVE-2024-38517 rapidjson: privilege escalation via integer underflow in Gener...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rapidjson
Version: 40
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Tom Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["6bb6d607-b1f7-4991-a951-0...
Depends On:
Blocks: CVE-2024-38517
TreeView+ depends on / blocked
 
Reported: 2024-07-10 01:01 UTC by Robb Gatica
Modified: 2024-07-19 02:21 UTC (History)
3 users (show)

Fixed In Version: rapidjson-1.1.0-41.fc41 rapidjson-1.1.0-41.fc40 rapidjson-1.1.0-41.fc39
Clone Of:
Environment:
Last Closed: 2024-07-10 18:45:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Robb Gatica 2024-07-10 01:01:49 UTC
More information about this security flaw is available in the following bug:

https://bugzilla.redhat.com/show_bug.cgi?id=2296854

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.

Comment 1 Tom Hughes 2024-07-10 14:26:38 UTC
For the benefit of people that aren't psychic https://nvd.nist.gov/vuln/detail/CVE-2024-38517 is the issue in question.

That in turn links to https://github.com/Tencent/rapidjson/pull/1261 which is the actual upstream report/fix and which is six years old so I'm not sure why somebody has decided it's a pants-on-fire matter now.

Sadly because upstream are a complete pain in the arse that still hasn't been released as there have been no new releases for eight years now.

Comment 2 Fedora Update System 2024-07-10 18:41:13 UTC
FEDORA-2024-5e0da8577a (rapidjson-1.1.0-41.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-5e0da8577a

Comment 3 Fedora Update System 2024-07-10 18:45:26 UTC
FEDORA-2024-5e0da8577a (rapidjson-1.1.0-41.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2024-07-10 20:01:45 UTC
FEDORA-2024-a3c1b2629e (rapidjson-1.1.0-41.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-a3c1b2629e

Comment 5 Fedora Update System 2024-07-10 20:01:45 UTC
FEDORA-2024-fb1e912d0e (rapidjson-1.1.0-41.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-fb1e912d0e

Comment 6 Fedora Update System 2024-07-11 01:29:03 UTC
FEDORA-2024-fb1e912d0e has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-fb1e912d0e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-fb1e912d0e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2024-07-11 01:44:47 UTC
FEDORA-2024-a3c1b2629e has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-a3c1b2629e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-a3c1b2629e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2024-07-19 01:45:50 UTC
FEDORA-2024-fb1e912d0e (rapidjson-1.1.0-41.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2024-07-19 02:21:43 UTC
FEDORA-2024-a3c1b2629e (rapidjson-1.1.0-41.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.