Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2022-3786 | First vendor Publication | 2022-11-01 |
Vendor | Cve | Last vendor Modification | 2024-11-21 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | |||
---|---|---|---|
Overall CVSS Score | 7.5 | ||
Base Score | 7.5 | Environmental Score | 7.5 |
impact SubScore | 3.6 | Temporal Score | 7.5 |
Exploitabality Sub Score | 3.9 | ||
Attack Vector | Network | Attack Complexity | Low |
Privileges Required | None | User Interaction | None |
Scope | Unchanged | 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
A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed a malicious certificate or for an application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a certificate to overflow an arbitrary number of bytes containing the `.' character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service). In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3786 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-120 | Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') (CWE/SANS Top 25) |
CPE : Common Platform Enumeration
Sources (Detail)
Source | Url |
---|
Alert History
Date | Informations |
---|---|
2024-11-28 14:14:30 |
|
2024-08-02 13:40:26 |
|
2024-08-02 01:30:24 |
|
2024-03-01 13:26:19 |
|
2024-02-02 02:38:13 |
|
2024-02-01 12:27:48 |
|
2023-11-07 21:31:20 |
|
2023-09-05 13:32:53 |
|
2023-09-05 01:27:13 |
|
2023-09-02 13:31:05 |
|
2023-09-02 01:27:37 |
|
2023-08-12 13:38:11 |
|
2023-08-12 01:26:55 |
|
2023-08-11 13:28:47 |
|
2023-08-11 01:27:45 |
|
2023-08-09 02:16:54 |
|
2023-08-06 13:26:32 |
|
2023-08-06 01:26:38 |
|
2023-08-04 13:26:56 |
|
2023-08-04 01:26:59 |
|
2023-07-14 13:26:56 |
|
2023-07-14 01:26:42 |
|
2023-07-12 02:17:23 |
|
2023-03-29 02:27:30 |
|
2023-03-28 12:26:44 |
|
2023-01-19 21:27:26 |
|
2022-12-09 09:27:28 |
|
2022-11-05 02:08:12 |
|
2022-11-05 02:07:43 |
|
2022-11-04 17:27:20 |
|
2022-11-04 09:27:18 |
|
2022-11-04 02:08:42 |
|
2022-11-04 02:08:15 |
|
2022-11-04 00:27:16 |
|
2022-11-03 21:27:39 |
|
2022-11-03 17:27:23 |
|
2022-11-03 09:27:18 |
|
2022-11-03 05:27:19 |
|
2022-11-03 02:09:54 |
|
2022-11-03 02:09:05 |
|
2022-11-03 00:27:19 |
|
2022-11-02 21:28:08 |
|
2022-11-02 17:27:16 |
|
2022-11-02 09:27:17 |
|
2022-11-02 00:27:13 |
|
2022-11-01 21:27:11 |
|