Bug 1624909
| Summary: | CVE number above 9999 are rejected as invalid | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Alicja Kario <hkario> |
| Component: | command line | Assignee: | Dan Callaghan <dcallagh> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | develop | CC: | dcallagh, kvolny |
| Target Milestone: | 26.0 | Keywords: | Patch, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-08 02:16:44 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Alicja Kario
2018-09-03 14:54:14 UTC
Dear Hubert,
thank you for your bug report. Yes it seems that the length of the CVE number is restricted:
RegExpCVE = re.compile("^\d{4}-\d{4}$")
Perhaps changing it to:
re.compile("^\d{4}-\d{4,7}$")
according to: https://cve.mitre.org/cve/identifiers/syntaxchange.html
will still validate, but give room for the change?
from the article:
> CVE IDs can now have four or more digits in the sequence number portion of the ID.
so, no, limit to 7 digits is not ok, it needs to be unlimited or some very high limit
Ah dang... yes. I guess for whatever reason I missed the arbitrary in:
CVE prefix + Year + Arbitrary Digits
I guess then the regexp becomes just:
re.compile("^\d{4}-\d+$")
It should reject CVEs with < 4 digits in the final section as they are not valid. So the regex should be:
^\d{4}-\d{4,}$
Hah of course. Good point Matt! This bug was fixed on the release-25 branch, but the next release will be Beaker 26.0. Beaker 26.0 has been released. *** Bug 1555256 has been marked as a duplicate of this bug. *** |