Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2022-3643 | First vendor Publication | 2022-12-07 |
| Vendor | Cve | Last vendor Modification | 2023-11-29 |
Security-Database Scoring CVSS v3
| Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H | |||
|---|---|---|---|
| Overall CVSS Score | 6.5 | ||
| Base Score | 6.5 | Environmental Score | 6.5 |
| impact SubScore | 4 | Temporal Score | 6.5 |
| Exploitabality Sub Score | 2 | ||
| Attack Vector | Local | Attack Complexity | Low |
| Privileges Required | Low | User Interaction | None |
| Scope | Changed | Confidentiality Impact | None |
| Integrity Impact | None | Availability Impact | High |
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : | |||
|---|---|---|---|
| Cvss Base Score | N/A | Attack Range | N/A |
| Cvss Impact Score | N/A | Attack Complexity | N/A |
| Cvss Expoit Score | N/A | Authentication | N/A |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| Guests can trigger NIC interface reset/abort/crash via netback It is possible for a guest to trigger a NIC interface reset/abort/crash in a Linux based network backend by sending certain kinds of packets. It appears to be an (unwritten?) assumption in the rest of the Linux network stack that packet protocol headers are all contained within the linear section of the SKB and some NICs behave badly if this is not the case. This has been reported to occur with Cisco (enic) and Broadcom NetXtrem II BCM5780 (bnx2x) though it may be an issue with other NICs/drivers as well. In case the frontend is sending requests with split headers, netback will forward those violating above mentioned assumption to the networking core, resulting in said misbehavior. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3643 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-74 | Failure to Sanitize Data into a Different Plane ('Injection') |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2024-03-12 13:28:56 |
|
| 2024-02-02 02:37:58 |
|
| 2024-02-01 12:27:43 |
|
| 2024-01-12 02:30:13 |
|
| 2023-12-29 02:27:52 |
|
| 2023-11-29 21:27:50 |
|
| 2023-11-22 02:27:13 |
|
| 2023-09-29 13:21:42 |
|
| 2023-09-05 13:32:36 |
|
| 2023-09-05 01:27:08 |
|
| 2023-09-02 13:30:49 |
|
| 2023-09-02 01:27:33 |
|
| 2023-08-12 13:37:57 |
|
| 2023-08-12 01:26:50 |
|
| 2023-08-11 13:28:33 |
|
| 2023-08-11 01:27:40 |
|
| 2023-08-06 13:26:18 |
|
| 2023-08-06 01:26:33 |
|
| 2023-08-04 13:26:43 |
|
| 2023-08-04 01:26:54 |
|
| 2023-07-14 13:26:42 |
|
| 2023-07-14 01:26:38 |
|
| 2023-06-06 13:16:44 |
|
| 2023-05-17 13:10:03 |
|
| 2023-05-08 21:27:33 |
|
| 2023-03-29 02:27:18 |
|
| 2023-03-28 12:26:39 |
|
| 2023-01-25 02:14:10 |
|
| 2023-01-11 00:27:28 |
|
| 2022-12-24 09:27:26 |
|
| 2022-12-22 21:27:27 |
|
| 2022-12-12 21:27:22 |
|
| 2022-12-08 02:08:47 |
|
| 2022-12-08 02:07:56 |
|
| 2022-12-08 00:27:11 |
|
| 2022-12-07 09:27:13 |
|
