Bug 687908 - CVE-2011-0700 CVE-2011-0701 wordpress: multiple vulnerabilities corrected in 3.0.5 [epel-all]
Summary: CVE-2011-0700 CVE-2011-0701 wordpress: multiple vulnerabilities corrected in ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: wordpress
Version: el6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nick Bebout
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: CVE-2011-0700, CVE-2011-0701
TreeView+ depends on / blocked
 
Reported: 2011-03-15 17:25 UTC by Vincent Danen
Modified: 2018-04-11 07:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Release Note
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-12 20:35:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vincent Danen 2011-03-15 17:25:53 UTC
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected Fedora
versions.

For comments that are specific to the vulnerability please use bugs filed
against "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When creating a Bodhi update request, please include the bug IDs of the
respective parent bugs filed against the "Security Response" product.
Please mention CVE ids in the RPM changelog when available.

Bodhi update submission link:
https://admin.fedoraproject.org/updates/new/?type_=security&bugs=687906

Please note: this issue affects multiple supported versions of Fedora EPEL.
Only one tracking bug has been filed; please only close it when all
affected versions are fixed.


[bug automatically created by: add-tracking-bugs]

Comment 1 Matěj Cepl 2011-04-12 13:15:36 UTC
We have already wordpress-3.1-1.el6.noarch in EPEL-6. Shouldn't this be closed?

Comment 2 Vincent Danen 2011-04-12 20:35:16 UTC
Yes, it should have been.

This was corrected via wordpress-3.1-1.el5 and wordpress-3.1-1.el6.


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