Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE.org to handle em-dashes gracefully #3137

Open
todb-cisa opened this issue Oct 7, 2024 · 0 comments
Open

CVE.org to handle em-dashes gracefully #3137

todb-cisa opened this issue Oct 7, 2024 · 0 comments
Assignees

Comments

@todb-cisa
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Needs Triage
Development

No branches or pull requests

2 participants