cve,link,title,description,vendor,products,score,severity,epss,cisa,cisa_published,article,ransomware,exploited,exploited_date,poc,trended,trended_no_1,trended_no_1_date,published,trended_score
CVE-2023-49922,https://securityvulnerability.io/vulnerability/CVE-2023-49922,Beats Insertion of Sensitive Information into Log File,"An issue was discovered by Elastic whereby Beats and 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 Beats or Elastic Agent attempted to ingest, this could lead to the insertion of sensitive or private information in the Beats or 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.",Elastic,Beats,6.8,MEDIUM,0.0006300000241026282,false,,false,false,false,,,false,false,,2023-12-12T19:15:00.000Z,0
CVE-2023-31421,https://securityvulnerability.io/vulnerability/CVE-2023-31421,"Beats, Elastic Agent, APM Server, and Fleet Server Improper Certificate Validation issue","A vulnerability has been identified in which Beats, Elastic Agent, APM Server, and Fleet Server do not adequately verify server certificates when connecting to target IP addresses. While the signature of the certificate is checked, the validation process fails to confirm the server certificate's IP Subject Alternative Name (SAN) values against the actual IP being targeted. This lapse means that if configured to connect via an IP address instead of a hostname, the expected security checks are bypassed, potentially allowing unauthorized access.",Elastic,"Beats,Elastic Agent,APM Server,Fleet Server",7.5,HIGH,0.0009599999757483602,false,,false,false,false,,,false,false,,2023-10-26T04:15:00.000Z,0