Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2023-4128 | First vendor Publication | 2023-08-10 |
| Vendor | Cve | Last vendor Modification | 2023-11-14 |
Security-Database Scoring CVSS v3
| Cvss vector : N/A | |||
|---|---|---|---|
| Overall CVSS Score | NA | ||
| Base Score | NA | Environmental Score | NA |
| impact SubScore | NA | Temporal Score | NA |
| Exploitabality Sub Score | NA | ||
| 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
| Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2023-4206, CVE-2023-4207, CVE-2023-4208. Reason: This record is a duplicate of CVE-2023-4206, CVE-2023-4207, CVE-2023-4208. Notes: All CVE users should reference CVE-2023-4206, CVE-2023-4207, CVE-2023-4208 instead of this record. All references and descriptions in this record have been removed to prevent accidental usage. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-4128 |
Alert History
| Date | Informations |
|---|---|
| 2023-11-14 17:28:18 |
|
| 2023-11-08 02:52:41 |
|
| 2023-11-08 02:50:48 |
|
| 2023-11-07 21:28:11 |
|
| 2023-11-05 13:27:41 |
|
| 2023-10-27 21:27:48 |
|
| 2023-10-20 09:27:59 |
|
| 2023-10-18 00:27:50 |
|
| 2023-10-17 21:27:39 |
|
| 2023-10-12 00:27:47 |
|
| 2023-10-11 00:27:41 |
|
| 2023-09-29 13:29:40 |
|
| 2023-09-19 21:27:40 |
|
| 2023-09-10 17:27:29 |
|
| 2023-09-05 13:42:11 |
|
| 2023-09-05 01:29:51 |
|
| 2023-09-02 13:40:17 |
|
| 2023-09-02 01:30:16 |
|
| 2023-08-20 00:27:26 |
|
| 2023-08-17 00:27:21 |
|
| 2023-08-14 09:27:21 |
|
| 2023-08-11 05:27:23 |
|
| 2023-08-10 21:27:18 |
|
