This template is for public disclosure of CVE details on Envoy's GitHub. It should be filed with the public release of a security patch version, and will be linked to in the announcement sent to [email protected]. The title of this issue should be the CVE identifier and it should have the
security
label applied.
Brief description used when filing CVE.
$CVSSSTRING($CVSSSCORE, $SEVERITY)
Envoy x.y.z and before.
List affected internal components and features.
How would an attacker use this?
Individual and optional organization.
If there is proof-of-concept or example, provide a concrete example.
Deep dive into the defect. This should be detailed enough to maintain a record for posterity while being clear and concise.
Are there configuration or CLI options that can be used to mitigate?
How can exploitation of this bug be detected in existing and future Envoy versions? E.g. access logs.
- CVE: $CVEURL
Any other public information.