Bug 484811 (CVE-2009-0484) - CVE-2009-0484 bugzilla: CSRF vuln via buglist.cgi
Summary: CVE-2009-0484 bugzilla: CSRF vuln via buglist.cgi
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2009-0484
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL: http://nvd.nist.gov/nvd.cfm?cvename=C...
Whiteboard:
Depends On: 484756 484757 484758
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-10 00:38 UTC by Vincent Danen
Modified: 2019-09-29 12:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-09 19:59:43 UTC
Embargoed:


Attachments (Terms of Use)

Description Vincent Danen 2009-02-10 00:38:45 UTC
Name: CVE-2009-0484
URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0484
Assigned: 20090209
Reference: CONFIRM: http://www.bugzilla.org/security/2.22.6/
Reference: CONFIRM: https://bugzilla.mozilla.org/show_bug.cgi?id=466748

Cross-site request forgery (CSRF) vulnerability in Bugzilla 3.0 before
3.0.7, 3.2 before 3.2.1, and 3.3 before 3.3.2 allows remote attackers
to delete shared or saved searches via a link or IMG tag to
buglist.cgi.

Comment 1 Fedora Update System 2009-03-05 15:50:48 UTC
bugzilla-3.2.2-2.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/bugzilla-3.2.2-2.fc9

Comment 2 Fedora Update System 2009-03-05 15:53:06 UTC
bugzilla-3.2.2-2.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/bugzilla-3.2.2-2.fc10

Comment 4 Fedora Update System 2009-03-18 18:56:27 UTC
bugzilla-3.2.2-2.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2009-03-18 19:04:05 UTC
bugzilla-3.2.2-2.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.


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