| 1 |
A boilerplate for tracking the status of patches across Debian Kernel trees. |
Candidate: CVE-2004-0587 |
| 2 |
dannf> should anything go above this line? |
References: |
| 3 |
dannf> should we use debian-style rfc822 for this for machine readability? |
FEDORA:FEDORA-2004-186 |
| 4 |
====================================================== |
URL:http://lwn.net/Articles/91155/ |
| 5 |
Candidate: (##NEEDED## | CAN-XXXX-XXXX | N/A) |
MANDRAKE:MDKSA-2004:066 |
| 6 |
URL: dannf> What makes a URL different than a Reference? Is it always mitre's? |
URL:http://www.mandrakesecure.net/en/advisories/advisory.php?name=MDKSA-2004:066 |
| 7 |
Reference: CONFIRM:##URL## dannf> what does CONFIRM mean? |
REDHAT:RHSA-2004:413 |
| 8 |
Reference: MISC:##URL## dannf> what does MISC mean? |
URL:http://www.redhat.com/support/errata/RHSA-2004-413.html |
| 9 |
|
REDHAT:RHSA-2004:418 |
| 10 |
Description: ##NEEDED## dannf> can a single description work for the cve, |
URL:http://www.redhat.com/support/errata/RHSA-2004-418.html |
| 11 |
dannf> the changelog, and the DSA? |
SGI:20040804-01-U |
| 12 |
dannf> should this use debian/control style multiline? |
URL:ftp://patches.sgi.com/support/free/security/advisories/20040804-01-U.asc |
| 13 |
dannf> should we have a short description? |
SUSE:SuSE-SA:2004:010 |
| 14 |
upstream: comma separated versions(s) of upstream kernel that first included this patch |
URL:http://www.novell.com/linux/security/advisories/2004_10_kernel.html |
| 15 |
2.6.13: (pending|released|already included|N/A)(backported)?(patch-name-used.diff)? |
BID:10279 |
| 16 |
2.6.12: (added to svn|released)(backported)?(patch-name-used.diff)? |
URL:http://www.securityfocus.com/bid/10279 |
| 17 |
2.6.8-sarge: (added to svn|released)(backported)?(patch-name-used.diff)? |
SECTRACK:1010057 |
| 18 |
... |
URL:http://securitytracker.com/id?1010057 |
| 19 |
one line for each currently maintained tree |
XF:suse-hbaapinode-dos(16062) |
| 20 |
|
URL:http://xforce.iss.net/xforce/xfdb/16062 |
| 21 |
dannf> what does backported mean? the patch didn't apply & needed munging, |
Description: |
| 22 |
dannf> or just that we used a patch intended for a newer tree, that may have |
Insecure permissions for the /proc/scsi/qla2300/HbaApiNode file in Linux |
| 23 |
dannf> applied cleanly? |
allows local users to cause a denial of service. |
| 24 |
|
Notes: |
| 25 |
|
2.4.26-3 has the note: |
| 26 |
|
CVE-2004-0587 code is not present, not vulnerable |
| 27 |
|
So the question is, did the code get added when we moved to 2.4.27, and |
| 28 |
|
was it still vulnerable? |
| 29 |
|
Bugs: |
| 30 |
|
upstream: |
| 31 |
|
2.6.14: |
| 32 |
|
2.6.8-sarge-security: |
| 33 |
|
2.4.27-sarge-security: |
| 34 |
|
2.6.8: |
| 35 |
|
2.4.19-woody-security: |
| 36 |
|
2.4.18-woody-security: |
| 37 |
|
2.4.17-woody-security: |
| 38 |
|
2.4.16-woody-security: |
| 39 |
|
2.4.17-woody-security-hppa: |
| 40 |
|
2.4.17-woody-security-ia64: |
| 41 |
|
2.4.18-woody-security-hppa: |