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 @opentelemetry/instrumentation-http to version 0.222.0 or higher.
@opentelemetry/instrumentation-http is an OpenTelemetry instrumentation for node:http and node:https http client and server modules
Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File in the server-span path of getIncomingRequestAttributes(), which writes the raw query string verbatim into the url.query span attribute for incoming requests. Credentials embedded in inbound request URLs - AWS presigned-URL signatures, Azure SAS tokens (sig), and GCS signed-URL signatures - are exported in plaintext to the configured tracing backend. The redactedQueryParams configuration option has no effect on server spans, making the documented mitigation silently inert, so any party with span-read access to the observability backend can retrieve still-valid credentials.
Note: This is only exploitable when inbound requests carry credentials in the query string and the attacker has read access to the telemetry backend.