Bug 1374481 - CVE-2016-7168 CVE-2016-7169 wordpress: two security issues fixed in 4.6.1 [epel-all]
Summary: CVE-2016-7168 CVE-2016-7169 wordpress: two security issues fixed in 4.6.1 [ep...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: wordpress
Version: el6
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Remi Collet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: CVE-2016-7168, CVE-2016-7169
TreeView+ depends on / blocked
 
Reported: 2016-09-08 19:18 UTC by Martin Prpič
Modified: 2016-09-27 03:51 UTC (History)
1 user (show)

Fixed In Version: wordpress-4.6.1-1.el5 wordpress-4.6.1-1.el6 wordpress-4.6.1-1.el7
Doc Type: Release Note
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-08 19:21:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Martin Prpič 2016-09-08 19:18:58 UTC
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora EPEL.

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

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

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

NOTE: this issue affects multiple supported versions of Fedora EPEL. While
only one tracking bug has been filed, please correct all affected versions
at the same time.  If you need to fix the versions independent of each
other, you may clone this bug as appropriate.
    
[bug automatically created by: add-tracking-bugs]

Comment 1 Martin Prpič 2016-09-08 19:19:04 UTC
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1374479,1374481

# Description of your update
notes=Security fix for 

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new

Comment 2 Martin Prpič 2016-09-08 19:21:15 UTC
Ah, I see the new release is already in Koji. Sorry for the noise.

Comment 3 Fedora Update System 2016-09-10 05:16:43 UTC
wordpress-4.6.1-1.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-eb5607d339

Comment 4 Fedora Update System 2016-09-10 05:16:51 UTC
wordpress-4.6.1-1.el5 has been submitted as an update to Fedora EPEL 5. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-b0f7448ed8

Comment 5 Fedora Update System 2016-09-10 05:17:10 UTC
wordpress-4.6.1-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-7e2d0ee701

Comment 6 Fedora Update System 2016-09-23 14:46:29 UTC
wordpress-4.6.1-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2016-09-27 03:47:51 UTC
wordpress-4.6.1-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2016-09-27 03:51:32 UTC
wordpress-4.6.1-1.el7 has been pushed to the Fedora EPEL 7 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.