Hide Forgot
when doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was used to issue a `PUT` request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the subsequent `POST` request. Reference: https://curl.se/docs/CVE-2022-32221.html
Created curl tracking bugs for this issue: Affects: fedora-all [bug 2137780] Created mingw-curl tracking bugs for this issue: Affects: fedora-all [bug 2137781]
This issue has been addressed in the following products: JBoss Core Services on RHEL 7 JBoss Core Services for RHEL 8 Via RHSA-2022:8840 https://access.redhat.com/errata/RHSA-2022:8840
This issue has been addressed in the following products: Red Hat JBoss Core Services Via RHSA-2022:8841 https://access.redhat.com/errata/RHSA-2022:8841
Created davix tracking bugs for this issue: Affects: epel-all [bug 2153064] Affects: fedora-all [bug 2153065]
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2023:0333 https://access.redhat.com/errata/RHSA-2023:0333
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2022-32221