Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2023-31421 | First vendor Publication | 2023-10-26 |
| Vendor | Cve | Last vendor Modification | 2024-02-15 |
Security-Database Scoring CVSS v3
| Cvss vector : CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | |||
|---|---|---|---|
| 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 | High |
| Integrity Impact | None | Availability Impact | None |
| 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
| It was discovered that when acting as TLS clients, Beats, Elastic Agent, APM Server, and Fleet Server did not verify whether the server certificate is valid for the target IP address; however, certificate signature validation is still performed. More specifically, when the client is configured to connect to an IP address (instead of a hostname) it does not validate the server certificate's IP SAN values against that IP address and certificate validation fails, and therefore the connection is not blocked as expected. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-31421 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-295 | Certificate Issues |
CPE : Common Platform Enumeration
| Type | Description | Count |
|---|---|---|
| Application | 1 | |
| Application | 1 | |
| Application | 1 |
Sources (Detail)
| Source | Url |
|---|---|
| MISC | https://discuss.elastic.co/t/beats-elastic-agent-apm-server-and-fleet-server-... https://www.elastic.co/community/security |
Alert History
| Date | Informations |
|---|---|
| 2024-02-16 05:27:57 |
|
| 2023-12-22 02:32:42 |
|
| 2023-11-08 17:27:43 |
|
| 2023-10-27 02:35:46 |
|
| 2023-10-27 02:33:11 |
|
| 2023-10-26 17:27:21 |
|
| 2023-10-26 09:27:21 |
|
