Back to bug 2214914

Who When What Removed Added
Sandipan Roy 2023-06-14 04:51:21 UTC CC security-response-team
Sandipan Roy 2023-06-14 04:51:46 UTC CC zdohnal
Sandipan Roy 2023-06-14 04:53:12 UTC Depends On 2214915
Sandipan Roy 2023-06-14 04:53:31 UTC Blocks 2214604
Sandipan Roy 2023-06-14 04:55:24 UTC Depends On 2214917
Guilherme de Almeida Suckevicz 2023-06-19 15:00:36 UTC Deadline 2023-06-22
Sandipan Roy 2023-06-22 11:05:26 UTC Summary EMBARGOED CVE-2023-34241 cups: use-after-free in cupsdAcceptClient() in scheduler/client.c CVE-2023-34241 cups: use-after-free in cupsdAcceptClient() in scheduler/client.c
Deadline 2023-06-22
Group qe_staff, security
Sandipan Roy 2023-06-22 11:06:40 UTC Depends On 2216717, 2216718
Sandipan Roy 2023-06-22 11:09:25 UTC Doc Text A vulnerability was found in CPUS. This security vulnerability due to cups logs data of free memory to the logging service AFTER the connection has been closed, when it should have logged the data right before. This resulting a use-after-free vulnerability in cupsdAcceptClient() in scheduler/client.c
RaTasha Tillery-Smith 2023-06-22 13:01:18 UTC Doc Text A vulnerability was found in CPUS. This security vulnerability due to cups logs data of free memory to the logging service AFTER the connection has been closed, when it should have logged the data right before. This resulting a use-after-free vulnerability in cupsdAcceptClient() in scheduler/client.c A vulnerability was found in CUPS. This issue occurs due to logging data of free memory to the logging service AFTER the connection has been closed, when it should have logged the data immediately before the connection closed, resulting in a use-after-free in cupsdAcceptClient() in scheduler/client.c
Rodrigo A B Freire 2023-06-26 18:14:06 UTC Flags needinfo?(chazlett)
CC chazlett, rfreire
Rodrigo A B Freire 2023-06-26 18:24:20 UTC Flags needinfo?(chazlett) needinfo?(rfreire)
Rodrigo A B Freire 2023-06-26 19:46:22 UTC CC rfreire
Flags needinfo?(rfreire)
Red Hat Bugzilla 2023-07-07 08:33:06 UTC Assignee security-response-team nobody
CC security-response-team

Back to bug 2214914