Back to bug 2196090
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Sandipan Roy | 2023-05-08 04:14:58 UTC | Blocks | 2193421 | |
| Sandipan Roy | 2023-05-08 04:20:01 UTC | Doc Text | A vulnerability was found in FRRouting. The issue was discovered in bgpd in FRRouting (FRR). By crafting a BGP OPEN message with an option of type 0xff (Extended Length from RFC 9072), attackers may cause a denial of service (assertion failure and daemon restart, or out-of-bounds read). This is possible because of inconsistent boundary checks that do not account for reading 3 bytes (instead of 2) in this 0xff case. | |
| Sandipan Roy | 2023-05-08 04:23:41 UTC | Depends On | 2196093, 2196094 | |
| RaTasha Tillery-Smith | 2023-05-08 13:00:41 UTC | Doc Text | A vulnerability was found in FRRouting. The issue was discovered in bgpd in FRRouting (FRR). By crafting a BGP OPEN message with an option of type 0xff (Extended Length from RFC 9072), attackers may cause a denial of service (assertion failure and daemon restart, or out-of-bounds read). This is possible because of inconsistent boundary checks that do not account for reading 3 bytes (instead of 2) in this 0xff case. | A vulnerability was found in FRRouting. The issue occurs in bgpd in FRRouting (FRR). By crafting a BGP OPEN message with an option of type 0xff (Extended Length from RFC 9072), attackers may cause a denial of service (assertion failure and daemon restart or out-of-bounds read). This flaw is possible due to inconsistent boundary checks that do not account for reading 3 bytes (instead of 2) in this 0xff case. |
| FrantiĊĦek Hrdina | 2023-05-10 06:37:45 UTC | CC | fhrdina | |
| Sandipan Roy | 2023-05-10 09:08:01 UTC | Depends On | 2196093 | |
| Sandipan Roy | 2023-05-10 09:08:21 UTC | Depends On | 2196795 | |
| Red Hat Bugzilla | 2023-07-07 08:31:25 UTC | Assignee | security-response-team | nobody |
Back to bug 2196090