Bug 156316 - Add links for CVE id's to appropriate CVE id (TEST CAN-2005-0001)
Add links for CVE id's to appropriate CVE id (TEST CAN-2005-0001)
Status: CLOSED DUPLICATE of bug 624597
Product: Bugzilla
Classification: Community
Component: Bugzilla General (Show other bugs)
All Linux
medium Severity medium (vote)
: ---
: ---
Assigned To: Simon Green
Kevin Baker
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2005-04-28 16:48 EDT by Josh Bressers
Modified: 2014-12-01 18:08 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-14 20:55:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Josh Bressers 2005-04-28 16:48:13 EDT
When we file security bugs, we usually have a CVE ID in the Summary (sometimes
there are ID's in the Description and comments).  It would be nice if the CVE
id's could be a link to MITRE's site.


Comment 1 David Lawrence 2005-04-29 15:13:17 EDT
Testing CVE-1234-1234 CAN-1234-1234
Comment 2 Josh Bressers 2005-04-29 15:14:19 EDT
That is awesome.  Will it work if the id is in the Summary?
Comment 3 David Lawrence 2005-04-29 15:36:43 EDT
Not sure, at first it doesnt seem so beacuase the summary is html filtered to
prevent cross site scripting attacks. I will need to look deeper and see if it
can be done. Comments are easy cause there is already a nice interface for
adding additional recipes for auto linking things.
Comment 4 Josh Bressers 2005-04-29 15:40:31 EDT
If not, don't worry about it too much.  I'll just make sure I put the CVE ID in
a comment as well as the summary.
Comment 5 David Lawrence 2008-09-16 12:52:33 EDT
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code.
Updating bug version to 3.2.
Comment 6 David Lawrence 2010-01-15 12:33:29 EST
Red Hat Bugzilla is now using version 3.4 of the Bugzilla codebase and
therefore this feature will need to be implemented against the new release.
Updating bug version to 3.2.
Comment 7 David Lawrence 2010-08-25 17:41:57 EDT
Red Hat has now upgraded to Bugzilla 3.6 and this bug will now be reassigned to that version. It would be helpful to the Bugzilla Development Team if this bug is verified to still be an issue with the latest version. If it is no longer an issue, then feel free to close, otherwise please comment that it is still a problem and we will try to address the issue as soon as we can.

Bugzilla Development Team
Comment 9 Jeff Fearn 2012-05-30 00:42:01 EDT
As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time.

If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically.

Thanks, the Bugzilla team.
Comment 10 Simon Green 2012-06-14 20:55:47 EDT

*** This bug has been marked as a duplicate of bug 624597 ***

Note You need to log in before you can comment on or make changes to this bug.