Can't link to CVE number in the form of YYYY-NNNNN
Bug #1750473 reported by
Tristan Cacqueray
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
When the CVE number is 5 digits long, the form is failing with:
There is 1 error.
2017-18191 is not a known CVE sequence number.
CVE References
Revision history for this message
| Colin Watson (cjwatson) wrote | #1 |
| Changed in launchpad: | |
| status: | New → Incomplete |
| tags: | added: lp-bugs |
Revision history for this message
| Tristan Cacqueray (tristan-cacqueray) wrote | #2 |
| Changed in launchpad: | |
| status: | Incomplete → Invalid |
To post a comment you must log in.
That just means that our system hadn't scanned that CVE number from Mitre's database yet - we scan it daily. We seem to have picked up that CVE now, judging from our logs:
2018-02-20 08:47:42 INFO CVE-2017-18191 created
2018-02-20 08:47:42 INFO Creating new CONFIRM reference for 2017-18191
2018-02-20 08:47:42 INFO Creating new CONFIRM reference for 2017-18191
... so could you please try again?