Elastic Agent up to 7.17.15/8.11.2 HTTP Status Code log file
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Elastic Agent up to 7.17.15/8.11.2. It has been classified as problematic. This affects an unknown part of the component HTTP Status Code Handler. Performing a manipulation results in log file. This vulnerability was named CVE-2023-6687. The attack needs to be approached within the local network. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability was found in Elastic Agent up to 7.17.15/8.11.2. It has been classified as problematic. This affects an unknown code block of the component HTTP Status Code Handler. The manipulation with an unknown input leads to a log file vulnerability. CWE is classifying the issue as CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. This is going to have an impact on confidentiality. The summary by CVE is:
An issue was discovered by Elastic whereby Elastic Agent would log a raw event in its own logs at the WARN or ERROR level if ingesting that event to Elasticsearch failed with any 4xx HTTP status code except 409 or 429. Depending on the nature of the event that Elastic Agent attempted to ingest, this could lead to the insertion of sensitive or private information in the Elastic Agent logs. Elastic has released 8.11.3 and 7.17.16 that prevents this issue by limiting these types of logs to DEBUG level logging, which is disabled by default.
The weakness was presented 12/12/2023. It is possible to read the advisory at discuss.elastic.co. This vulnerability is uniquely identified as CVE-2023-6687 since 12/11/2023. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
Upgrading to version 7.17.16 or 8.11.3 eliminates this vulnerability.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
- 7.17.0
- 7.17.1
- 7.17.2
- 7.17.3
- 7.17.4
- 7.17.5
- 7.17.6
- 7.17.7
- 7.17.8
- 7.17.9
- 7.17.10
- 7.17.11
- 7.17.12
- 7.17.13
- 7.17.14
- 7.17.15
- 8.11.0
- 8.11.1
- 8.11.2
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.6
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CNA Base Score: 6.8
CNA Vector (Elastic): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Log fileCWE: CWE-532 / CWE-200 / CWE-284
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Agent 7.17.16/8.11.3
Timeline
12/11/2023 🔍12/12/2023 🔍
12/12/2023 🔍
01/04/2024 🔍
Sources
Advisory: discuss.elastic.coStatus: Confirmed
CVE: CVE-2023-6687 (🔍)
GCVE (CVE): GCVE-0-2023-6687
GCVE (VulDB): GCVE-100-247623
Entry
Created: 12/12/2023 19:55Updated: 01/04/2024 08:02
Changes: 12/12/2023 19:55 (49), 01/04/2024 08:02 (12)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.