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 applicationsUpgrade trillium-client
to version 0.5.4 or higher.
Affected versions of this package are vulnerable to Improper Neutralization of CRLF Sequences in HTTP Headers via the outbound trillium_http::HeaderValue
and trillium_http::HeaderName
components. An attacker can manipulate the client-server synchronization and potentially control parts of requests or responses, leading to data exfiltration or server-side request forgery, by injecting \r\n
sequences into header values or names.
Notes:
This only affects use cases where attackers have control of outbound headers, and can insert "\r\n" sequences. Specifically, if untrusted and unvalidated input is inserted into header names or values.
trillium-http:
If a header name is invalid in server response headers, the specific header and any associated values are omitted from network transmission.
If a header value is invalid in server response headers, the individual header value is omitted from network transmission. Other headers values with the same header name will still be sent.
If any header name or header value is invalid in the client request headers, awaiting the client Conn returns an Error::MalformedHeader prior to any network access.