In some cases, vulnerability names are too long and actually descriptions - not names.
Problem:
In some cases, vulnerability names are too long and are actually a description of the vulnerability.
This vulnerability Name:
Check when opening files - can an attacker redirect it (via symlinks), force the opening of special file type (e.g., device files), move things around to create a race condition, control its ancestors, or change its contents? (CWE-362)
Is in actuality a description of the vulnerability. The problem this causes is that when a user goes to create an issue, they get an error since there is a character limit on issue names. The other issue is that it is not a name but a description, leading to a discontinuity in the security reports and dashboards.
Solution:
How might we shorten or create more accurate names from the information we receive from identifiers?