github.com/elastic/beats v7.6.2+incompatible

Why

• warnVulnerability

  Buffer Overflow via Malformed Syslog Message or Malicious Tokenizer Pattern in github.com/elastic/beats

• warnVulnerability

  Elasticsearch Packetbeat has Excessive Allocation of Memory and CPU via Malicious IPv4 Fragments in github.com/elastic/beats

• warnVulnerability

  Metricbeat affected by multiple denial of service vulnerabilities in github.com/elastic/beats

• warnVulnerability

  Packetbeat does not properly validate an array index in multiple protocol parser components in github.com/elastic/beats

• warnVulnerability

  Metricbeat Allocates Memory with Excessive Size Value Leading to Denial of Service in github.com/elastic/beats

• warnVulnerability

  Filebeat Beats has Buffer Overflow via Malformed Syslog Message or Malicious Tokenizer Pattern in Dissect Configuration

• warnVulnerability

  Elastic Beats inserts sensitive information into log file (fixed in 7.17.16)

What the code does

On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.