Elastic Beats vulnerabilitiesRanked by how likely they are to be used.
Elastic Beats is made by Elastic. We track 2 published vulnerabilities in it, across 2 versions. None of them is on the list of flaws known to be exploited today. If you run Elastic Beats, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Elastic Beats vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Elastic Beats's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Elastic Beats flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.7%CVE-2023-49922Medium
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...
- 0.3%CVE-2023-31421High
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...
Running Elastic Beats? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Elastic Beats on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 2 published vulnerabilities listed under the name Elastic Beats, across 2 versions.
None of Elastic Beats's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Elastic Beats. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.