Back to bug 2035081
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Pedro Sampaio | 2021-12-22 20:27:09 UTC | Depends On | 2035082 | |
| Pedro Sampaio | 2021-12-22 20:33:48 UTC | Blocks | 2035089 | |
| Sandipan Roy | 2021-12-23 10:06:35 UTC | Depends On | 2035218, 2035217 | |
| Sandipan Roy | 2021-12-23 10:07:28 UTC | Comment | 2 | updated |
| Sandipan Roy | 2021-12-23 10:10:33 UTC | Comment | 2 | updated |
| Sandipan Roy | 2021-12-23 10:10:59 UTC | Comment | 2 | updated |
| Sandipan Roy | 2021-12-23 10:13:19 UTC | Comment | 2 | updated |
| Sandipan Roy | 2021-12-29 06:25:44 UTC | Doc Text | A flaw was found in the patch. A possible memory corruption vulnerability could allow an attacker to input a specially crafted patch file leading to a crash or code execution. The highest threat from this vulnerability is to system availability. | |
| Eric Christensen | 2022-01-05 19:30:04 UTC | Doc Text | A flaw was found in the patch. A possible memory corruption vulnerability could allow an attacker to input a specially crafted patch file leading to a crash or code execution. The highest threat from this vulnerability is to system availability. | A flaw was found in patch. A possible memory corruption vulnerability could allow an attacker to input a specially crafted patch file leading to a crash or code execution. |
| Red Hat Bugzilla | 2022-02-22 06:37:27 UTC | CC | jnakfour | |
| Red Hat Bugzilla | 2023-07-07 08:35:09 UTC | Assignee | security-response-team | nobody |
Back to bug 2035081