Title: EdgeX <title> Technical Advisory
created by EdgeX Product team <link to full document> <date>
Description:
Issue description and its ramifications.
Affected Releases:
Could be a set of releases, perhaps releases in a range, or all releases before a specific release
Criticality:
An edgeX provided score. Could score lower than a dependent CVE score by virtue of its use in EdgeX.
Workaround/Fix:
...
Title: EdgeX Security Advisory: <ID> <Brief Description>
Date: <date>
ID: (same as in title)
Affects: One or more releases, specified as a range, or prior to a given release. Example Fuji or Edinburgh:Fuji. Sub-projects in the same.
Description: Issue description and its ramifications.
Score: Severity, Risk
The associated risk could be lower than the severity by virtue of mitigation factors in the usage context.
Workaround/Fix: Typically release specific patch sets, one per affected release.
Credit: Who spotted the issue ! and their affiliation. Thank you!
References: to the reported issue, patch sets, related issues etc
==============
The above issue report would also be sent to those subscribing to EdgeX security issue updates.
Footer of the email message:
You are receiving the above EdgeX security issue information as a registered subscriber to the EdgeX <subscription-list> list. Click to This email was sent by EdgeX to <subscription-list> because you are a registered user.
You may unsubscribe.