The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsLearn about Insertion of Sensitive Information into Log File vulnerabilities in an interactive lesson.
Start learningUpgrade github.com/elastic/beats/v7/libbeat/processors/script/javascript to version 7.17.16 or higher.
This was deemed not a vulnerability.
github.com/elastic/beats/v7/libbeat/processors/script/javascript is a lightweight shippers for Elasticsearch & Logstash
Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File due to improper logging of sensitive information when handling failed event ingestions to Elasticsearch with certain HTTP status codes. An attacker can gain access to sensitive or private information by inducing the application to log events at the WARN or ERROR level.
Note: This vulnerability affects only the Beats application and Elastic Agent, when logging data from the Javascript runtime.
This log line is logged at the WARN level; changing the log level to ERROR will suppress these logs. For Beats and standalone Elastic Agent the log level can be changed in the configuration file, see:
https://www.elastic.co/guide/en/beats/filebeat/current/configuration-logging.html#level
https://www.elastic.co/guide/en/fleet/current/elastic-agent-standalone-logging-config.html