The following Fedora EPEL 5 Security updates need testing:
Age URL
795
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2014-3849
sblim-sfcb-1.3.8-2.el5
438
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-edbea40516
mcollective-2.8.4-1.el5
410
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-582c8075e6
thttpd-2.25b-24.el5
20
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-ce45574ab6
libbsd-0.8.3-2.el5
0
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-e541856e99
wordpress-4.7.1-1.el5
The following builds have been pushed to Fedora EPEL 5 updates-testing
prosody-0.9.12-1.el5
wordpress-4.7.1-1.el5
Details about builds:
================================================================================
prosody-0.9.12-1.el5 (FEDORA-EPEL-2017-d29ce64182)
Flexible communications server for Jabber/XMPP
--------------------------------------------------------------------------------
Update Information:
Prosody 0.9.12 ============== A summary of changes in this release: *
Dependencies: Fix certificate verification failures when using LuaSec 0.6 (fixes
#781) * mod_s2s: Lower log message to 'warn' level, standard for remotely-
triggered protocol issues * certs/Makefile: Remove -c flag from chmod call (a
GNU extension) * Networking: Prevent writes after a handler is closed (fixes
#783)
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #1412102 - prosody-0.9.12 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1412102
--------------------------------------------------------------------------------
================================================================================
wordpress-4.7.1-1.el5 (FEDORA-EPEL-2017-e541856e99)
Blog tool and publishing platform
--------------------------------------------------------------------------------
Update Information:
**WordPress 4.7.1** Security and Maintenance Release This is a security release
for all previous versions and we strongly encourage you to update your sites
immediately. WordPress versions 4.7 and earlier are affected by eight security
issues: * Remote code execution (RCE) in PHPMailer ��� No specific issue
appears to affect WordPress or any of the major plugins we investigated but, out
of an abundance of caution, we updated PHPMailer in this release. This issue was
reported to PHPMailer by Dawid Golunski and Paul Buonopane. * The REST API
exposed user data for all users who had authored a post of a public post type.
WordPress 4.7.1 limits this to only post types which have specified that they
should be shown within the REST API. Reported by Krogsgard and Chris Jean. *
Cross-site scripting (XSS) via the plugin name or version header on update-
core.php. Reported by Dominik Schilling of the WordPress Security Team. *
Cross-site request forgery (CSRF) bypass via uploading a Flash file. Reported by
Abdullah Hussam. * Cross-site scripting (XSS) via theme name fallback.
Reported by Mehmet Ince. * Post via email checks
mail.example.com if default
settings aren���t changed. Reported by John Blackbourn of the WordPress Security
Team. * A cross-site request forgery (CSRF) was discovered in the
accessibility mode of widget editing. Reported by Ronnie Skansing. * Weak
cryptographic security for multisite activation key. Reported by Jack. Thank
you to the reporters for practicing responsible disclosure. In addition to the
security issues above, WordPress 4.7.1 fixes 62 bugs from 4.7. For more
information, see the [release
notes](https://codex.wordpress.org/Version_4.7.1)
or consult the [list of
changes](https://core.trac.wordpress.org/query?milestone=4.7.1).
--------------------------------------------------------------------------------