This is the simple request form for a single CVE ID in an Open Source product or software for an issue that is public. If you need more than one CVE ID either fill this form out multiple times, or you need an embargoed CVE ID this is NOT the form to use, please email kurt@seifried.org directly for details and a template to submit an embargoed request (please note due to email volume these may take a while).

For closed source and other CNA's (CVE Numbering Authority) please check with MITRE at https://cve.mitre.org/cve/cna.html or use the CVE request form at https://cve.mitre.org/cve/request_id.html.

Requestor email address:
Your contact email address:
Your answer
Product name:
Product Name - please use the full name the vendor/project uses (so we can search for it if need be)
Your answer
Vendor or project name:
Name of project vendor/owner (if it exists) - needed if the project name isn't unique/well known
Your answer
Version affected:
Please put an affected version (e.g. 1.2.3) or range (e.g. 1.2.3 and older)
Your answer
Version fixed (if known):
If you know the fixed version please put it here, this is not mandatory as CVE's can be assigned to issues that have not been fixed yet
Your answer
Affected component (if known):
Affected function name, line of code, functionality (e.g. image upload)
Your answer
Has the project confirmed or acknowledged the vulnerability?
Has the upstream project been contacted and replied yet
Vulnerability type (if unknown use "other" and explain):
Vulnerability type if other:
Your answer
Impact of issue (select more than one if needed):
Impact of issue if other:
Your answer
Attack vector / exploitation:
If known please provide information on how this issue is exploited or what the attack vector is
Your answer
Suggested Description of issue for CVE database:
Example format: [Vendor name] [product name] version [version info] is vulnerable to a [single flaw type] in the [component] resulting [some impact].
Your answer
Short title of issue:
If the description is very long please provide a short title such as "Buffer overflow in Foo version 1.2"
Your answer
Additional notes:
Please add any additional notes
Your answer
Reference URL (must be public, e.g. no login) required):
Please provide a SINGLE link to where the advisory/security report/ChangeLog/etc is or will be regarding this CVE
Your answer
Other reference URL(s) (must be public, e.g. no login) required):
Please provide any additional links to where the advisory/security report/ChangeLog/etc is or will be regarding this CVE
Your answer
Person/People/Organization that helped discover or process this vulnerability:
Your answer
Never submit passwords through Google Forms.
This form was created inside of Seifried. Report Abuse - Terms of Service - Additional Terms