You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On CVE.org, it's quite normal to search for CVEs in the following format:
CVE-2024-27394
However, sometimes I end up copy-pasting a string like this from a blog post or other resource:
CVE-2024–27394
Note the second em-dash.
It would be nice if the search string was passed to the search function with a normalized dash character. There are many choices for dash.
Maybe a regex that just takes:
/^CVE.(\d{4}).(\d{4,10}).*$/
and turns it into
CVE-\1-\2
and goes with that.
That would save minutes a day, I'm sure. Maybe you're logging searches and can find out how often people put well-meaning garbage in this search field.
On CVE.org, it's quite normal to search for CVEs in the following format:
CVE-2024-27394
However, sometimes I end up copy-pasting a string like this from a blog post or other resource:
CVE-2024–27394
Note the second em-dash.
It would be nice if the search string was passed to the search function with a normalized dash character. There are many choices for dash.
Maybe a regex that just takes:
/^CVE.(\d{4}).(\d{4,10}).*$/
and turns it into
CVE-\1-\2
and goes with that.
That would save minutes a day, I'm sure. Maybe you're logging searches and can find out how often people put well-meaning garbage in this search field.
This was first opened at CVEProject/Ideas#28
The text was updated successfully, but these errors were encountered: