Red Hat would like to thank Mike O'Connor for bringing this issue to our attention. Red Hat would like to thank the rsync team for their rapid response and quick fix for this issue. Red Hat would like to thank Ulf Härnhammar for discovering and alerting us to this issue. Red Hat would like to thank Paul Starzetz from ISEC for disclosing this issue as well as Andrea Arcangeli and Solar Designer for working on the patch. Red Hat would like to thank Steffan Esser for finding and reporting these issues and Jacques A. Vidrine for providing initial patches. Red Hat would like to thank Steffan Esser for finding and reporting this issue and Jacques A. Vidrine for providing the initial patch. Red Hat would like to thank Steffan Esser for finding and reporting this issue and Jacques A. Vidrine for providing the initial patch. Red Hat would like to thank Paul Starzetz from ISEC for reporting this issue. Red Hat would like to thank Niels Heinen for reporting this issue. Red Hat would like to thank the Samba team for reporting this issue and providing us with a patch. Red Hat would like to thank David Dawes from XFree86 and iDefense for reporting and working on this issue. Red Hat would like to thank David Dawes from XFree86 and iDefense for reporting and working on this issue. Red Hat would like to thank Craig Southeren of the OpenH323 project for providing the fixes for these issues. Red Hat would like to thank David Dawes from XFree86 for the patches and notification of these issues. Red Hat would like to thank the MIT Kerberos Development Team for their responsible disclosure of this issue. Red Hat would like to thank Ulf Härnhammar for disclosing and providing test cases and patches for these issues. Red Hat would like to thank Ulf Härnhammar for disclosing and providing test cases and patches for these issues. Red Hat would like to thank Stefan Esser for notifying us of this issue and Derek Price for providing an updated patch. Red Hat would like to thank Derek Price for auditing, disclosing, and providing a patch for this issue. Red Hat would like to thank iSEC Security Research for disclosing this issue and a number of vendor-sec participants for reviewing and working on the patch to this issue. Red Hat would like to thank Stefan Esser and Sebastian Krahmer for auditing, disclosing, and providing a patch for this issue. Red Hat would like to thank Stefan Esser and Sebastian Krahmer for auditing, disclosing, and providing a patch for this issue. Red Hat would like to thank Stefan Esser and Sebastian Krahmer for auditing, disclosing, and providing a patch for this issue. Red Hat would like to thank Chris Evans for discovering these issues. Red Hat would like to thank Chris Evans for discovering this issue. Red Hat would like to thank Chris Evans for discovering these issues. Red Hat would like to thank Sebastian Krahmer for auditing, disclosing, and providing a patch for this issue. Red Hat would like to thank iDefense for their responsible disclosure of this issue. Red Hat would like to thank iDefense for their responsible disclosure of this issue. Red Hat would like to thank the MIT Kerberos Development Team and Gaël Delalleau for their responsible disclosure of this issue. Red Hat would like to thank the MIT Kerberos Development Team and Daniel Wachdorf for their responsible disclosure of this issue. Red Hat would like to thank the MIT Kerberos Development Team and Daniel Wachdorf for their responsible disclosure of this issue. Red Hat would like to thank the MIT Kerberos Development Team for their responsible disclosure of this issue. Red Hat would like to thank Derek B. Noonburg for reporting this issue and providing a patch. Red Hat would like to thank Derek B. Noonburg for reporting this issue and providing a patch. Red Hat would like to thank Derek B. Noonburg for reporting this issue and providing a patch. Red Hat would like to thank Chris Evans for reporting this issue. Red Hat would like to thank Chris Evans for reporting this issue. Red Hat would like to thank Chris Evans for reporting this issue. Red Hat would like to thank Chris Evans for reporting this issue. Red Hat would like to thank Dirk Mueller for reporting this issue. Red Hat would like to thank iDefense for reporting this issue. Red Hat would like to thank Solar Designer for reporting this issue. Red Hat would like to thank Dirk Mueller for reporting this issue and providing a patch. Red Hat would like to thank Tavis Ormandy of the Google Security Team for reporting this issue. Red Hat would like to thank Kirill Korotaev for reporting this issue. Red Hat would like to thank Barry Warsaw for disclosing this vulnerability. Red Hat would like to thank Barry Warsaw for disclosing these vulnerabilities. Red Hat would like to thank Stephane Eranian for reporting this issue. Red Hat would like to thank Wei Wang of McAfee Avert Labs for reporting this issue. Red Hat would like to thank Olof Johansson for reporting this issue. Red Hat would like to thank Dmitriy Monakhov for reporting this issue. Red Hat would like to thank Kostantin Khorenko for reporting this issue. Red Hat would like to thank Glenn Randers-Pehrson, Mats Palmgren, and Tavis Ormandy for supplying details and patches for this issue. Red Hat would like to thank Kostantin Khorenko for reporting this issue. Red Hat would like to thank Ludwig Nussel for reporting this issue. Red Hat would like to thank Ludwig Nussel for reporting this issue. Red Hat would like to thank Ludwig Nussel for reporting this issue. Red Hat would like to thank Fridrich Štrba and iDefense for alerting us to this issue. Red Hat would like to thank Daniel Roethlisberger for reporting this issue. Red Hat would like to thank John Heasman for reporting this issue. Red Hat would like to thank the SWsoft Virtuozzo/OpenVZ Linux kernel team for reporting this issue. Red Hat would like to thank MIT for reporting this issue. Red Hat would like to thank MIT and iDefense for reporting this issue. Red Hat would like to thank Ulf Härnhammar of Secunia Research for reporting this issue. Red Hat would like to thank MIT for reporting this issue. Red Hat would like to thank Core Security Technologies for reporting this issue. Red Hat would like to thank iDefense for reporting this issue. Red Hat would like to thank Ilja van Sprundel for reporting this issue. Red Hat would like to thank Fridrich Štrba and iDefense for alerting us to this issue. Red Hat would like to thank Tavis Ormandy and Will Drewry for properly disclosing these issues. Red Hat would like to thank Tavis Ormandy and Will Drewry for properly disclosing these issues. Red Hat would like to thank Glenn Randers-Pehrson, Mats Palmgren, and Tavis Ormandy for supplying details and patches for this issue. Red Hat would like to thank the Samba developers, TippingPoint, and iDefense for reporting these issues. Red Hat would like to thank the Samba developers, TippingPoint, and iDefense for reporting these issues. Red Hat would like to thank JLANTHEA for reporting this issue. Red Hat would like to acknowledge Tim Brown of Portcullis Computer Security and Dirk Mueller for these issues. Red Hat would like to thank Dmitry V. Levin for reporting this issue. Red Hat would like to thank Robert Buchholz for reporting this issue. Red Hat would like to thank Rick King for responsibly disclosing this issue. Red Hat would like to thank Alin Rad Pop for reporting this issue. Red Hat would like to credit iDefense and Neil Kettle for reporting this issue. Red Hat would like to thank the Samba developers for responsibly disclosing this issue. Red Hat would like to thank Wojciech Purczynski for reporting this issue. Red Hat would like to credit Chris Evans for reporting this issue. Red Hat would like to thank Tavis Ormandy and Will Drewry for properly disclosing this issue. Red Hat would like to thank Alin Rad Pop of Secunia Research for responsibly disclosing this issue. Red Hat would like to thank Rafal Wojtczuk of McAfee Avert Research for responsibly disclosing these issues. Red Hat would like to thank Josh Lange for reporting this issue. Red Hat would like to thank Alin Rad Pop of Secunia Research for responsibly disclosing this issue. Red Hat would like to thank the Google Security Team for responsibly disclosing this issue. Red Hat would like to thank Tim Baum for reporting this issue. Red Hat would like to thank Nick Piggin for responsibly disclosing this issue. Red Hat would like to thank "regenrecht" for reporting this issue. Red Hat would like to thank MIT for reporting this issue. Red Hat would like to thank MIT for reporting this issue. Red Hat would like to thank Ulf Härnhammar of Secunia Research for finding and reporting this issue. Red Hat would like to thank Will Drewry for reporting these issues. Red Hat would like to thank Will Drewry for reporting these issues. Red Hat would like to thank Tavis Ormandy of the Google Security Team for reporting this issue. Red Hat would like to thank MIT and Jeff Altman of Secure Endpoints for reporting this issue. Red Hat would like to thank MIT for reporting this issue. Red Hat would like to thank Alin Rad Pop of Secunia Research for responsibly disclosing this issue. Red Hat would like to thank Alin Rad Pop of Secunia Research for responsibly disclosing this issue. Red Hat would like to thank Alin Rad Pop of Secunia Research for responsibly disclosing this issue. Red Hat would like to thank Aleksander Adamowski for reporting this issue. Red Hat would like to thank Dan Kaminsky for reporting this issue. Red Hat would like to thank David Remahl of the Apple Product Security team for responsibly reporting these issues. Red Hat would like to thank David Remahl of the Apple Product Security team for responsibly reporting these issues. Red Hat would like to thank Drew Yao of the Apple Product Security team for reporting this issue. Red Hat would like to thank Drew Yao of the Apple Product Security team for reporting this issue. Red Hat would like to thank Drew Yao of the Apple Product Security team for reporting this issue. Red Hat would like to thank Drew Yao of the Apple Product Security team for reporting this issue. Red Hat would like to thank Drew Yao of the Apple Product Security team for reporting this issue. Red Hat would like to thank Drew Yao of the Apple Product Security team for reporting this issue. Red Hat would like to thank Chris Evans and oCERT for reporting this vulnerability. Red Hat would like to thank Sebastian Krahmer for responsibly disclosing this issue. Red Hat would like to thank Sebastian Krahmer of the SuSE Security Team for reporting this issue. Red Hat would like to thank Justin Cappos and Justin Samuel for discussing various package update mechanism flaws which led to our discovery of this issue. Red Hat would like to thank Andreas Solberg for responsibly disclosing this issue. Red Hat would like to thank "regenrecht" for reporting this issue. Red Hat would like to thank "regenrecht" for reporting this issue. Red Hat would like to thank "regenrecht" for reporting this issue. Red Hat would like to thank Stéphane Bertin for responsibly disclosing this issue. Red Hat would like to thank Drew Yao of the Apple Product Security team for reporting this issue. Red Hat would like to thank Drew Yao of the Apple Product Security team for reporting this issue. Credit: Google Security Team (for the original OpenSSL issue), Florian Weimer for spotting that BIND9 was vulnerable. Red Hat would like to thank Braden Thomas and Drew Yao of the Apple Product Security team for responsibly reporting these flaws. Red Hat would like to thank Braden Thomas and Drew Yao of the Apple Product Security team for responsibly reporting these flaws. Red Hat would like to thank Aaron Sigel of the Apple Product Security team and iDefense for responsibly reporting this flaw. Red Hat would like to thank Braden Thomas and Drew Yao of the Apple Product Security team for responsibly reporting this flaw. Red Hat would like to thank Alin Rad Pop of Secunia Research for responsibly reporting this flaw. Red Hat would like to thank Ludwig Nussel for reporting this flaw responsibly. Red Hat would like to thank Ludwig Nussel for reporting this flaw responsibly. Red Hat would like to thank Chris Evans from the Google Security Team for reporting this issue. Red Hat would like to thank Chris Evans from the Google Security Team for reporting these issues. Red Hat would like to thank Chris Evans from the Google Security Team for reporting these issues. Red Hat would like to thank Erik Sjölund for reporting this issue. Red Hat would like to thank Will Dormann of the CERT/CC for responsibly reporting this flaw. Red Hat would like to thank Will Dormann of the CERT/CC for responsibly reporting these flaws. Red Hat would like to thank Anibal Sacco from Core Security Technologies for reporting this issue. Red Hat would like to thank Will Dormann of the CERT/CC for responsibly reporting this flaw. Red Hat would like to thank Will Dormann of the CERT/CC for responsibly reporting this flaw. Red Hat would like to thank Will Dormann of the CERT/CC for responsibly reporting these flaws. Red Hat would like to thank Will Dormann of the CERT/CC for responsibly reporting these flaws. Red Hat would like to thank Will Dormann of the CERT/CC for responsibly reporting this flaw. Red Hat would like to thank Sebastian Krahmer of the SUSE Security Team for responsibly reporting this flaw. Red Hat would like to thank Will Dormann of the CERT/CC for responsibly reporting this flaw. Red Hat would like to thank Will Dormann of the CERT/CC for responsibly reporting this flaw. Red Hat would like to thank Will Drewry for reporting this issue. Red Hat would like to thank Swen van Brussel for reporting this issue. Red Hat would like to thank Tavis Ormandy of the Google Security Team for responsibly reporting this flaw. Red Hat would like to thank Stefan Cornelius of Secunia Research for responsibly reporting this flaw. Red Hat would like to thank Ramon de C. Valle for reporting this issue. Red Hat would like to thank Ramon de C. Valle for reporting this issue. Red Hat would like to thank Tavis Ormandy and Julien Tinnes of the Google Security Team for responsibly reporting this flaw. Red Hat would like to thank Tavis Ormandy and Julien Tinnes of the Google Security Team for responsibly reporting this flaw. Red Hat would like to thank Aaron Sigel of Apple Product Security for responsibly reporting this issue. Red Hat would like to thank Adam Zabrocki for reporting this issue. Red Hat would like to thank Chris Rohlf for reporting this issue. Red Hat would like to thank Simon Vallet for responsibly reporting this issue. Red Hat would like to thank Stefan Cornelius of Secunia Research for reporting this flaw. Red Hat would like to thank Rafael Dominguez Vega for reporting this issue. Red Hat would like to thank Christian Johansson of Bitsec AB and Thomas Biege of the SUSE Security Team for independently reporting this issue. Red Hat would like to thank Tavis Ormandy of Google Security Team for reporting this issue. Red Hat would like to thank STMicroelectronics for responsibly reporting this issue. Red Hat would like to thank Aki Helin of the Oulu University Secure Programming Group for responsibly reporting this flaw. Red Hat would like to thank Telesys Software for responsibly reporting this issue. Red Hat would like to thank CERT-FI for responsibly reporting this flaw, who credit Ilkka Mattila and Tuomas Salomäki for the discovery of the issue. Red Hat would like to thank CERT-FI for responsibly reporting this flaw, who credit Ilkka Mattila and Tuomas Salomäki for the discovery of the issue. Red Hat would like to thank Mathias Krause for reporting this issue. Red Hat would like to thank Sebastian Krahmer for reporting this issue. Red Hat would like to thank Ramon de C. Valle for reporting this issue. Red Hat would like to thank Sadrul Habib Chowdhury of the Pidgin project for responsibly reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Sebastian Krahmer of SuSE Security Team for responsibly reporting this issue. Red Hat would like to thank the Apple Product Security team for responsibly reporting this issue. Upstream acknowledges Adrian 'pagvac' Pastor of GNUCITIZEN and Tim Starling as the original reporters. Red Hat would like to thank Drew Yao of the Apple Product Security team for reporting this issue. Red Hat would like to thank the Apple Product Security team for responsibly reporting this issue. Upstream acknowledges regenrecht as the original reporter. Red Hat would like to thank Jakob Lell for responsibly reporting this issue. Red Hat would like to thank Daniel Stenberg for responsibly reporting this issue. Upstream acknowledges Wesley Miaw as the original reporter. Red Hat would like to thank Stefano Di Paola and Giorgio Fedon of Minded Security for responsibly reporting this issue. Red Hat would like to thank the Debian Security Team for reporting this issue. The Debian Security Team acknowledges Ronald Volgers as the original reporter. Red Hat would like to thank Dan Rosenberg for responsibly reporting these flaws. Red Hat would like to thank Dan Rosenberg for responsibly reporting these flaws. Red Hat would like to thank the Ubuntu Security Team for reporting this issue. The Ubuntu Security Team acknowledges Dan Rosenberg as the original reporter. Red Hat would like to thank Marcus Meissner for reporting this issue. Red Hat would like to thank Neil Brown for reporting this issue. Red Hat would like to thank Ang Way Chuang for reporting this issue. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges Ralf Philipp Weinmann working with TippingPoint's Zero Day Initiative as the original reporter. Red Hat would like to thank John Sullivan for responsibly reporting this flaw. Red Hat would like to thank Todd C. Miller, the upstream sudo maintainer, for responsibly reporting this issue. Upstream acknowledges Valerio Costamagna as the original reporter. Red Hat would like to thank Tim Bunce for responsibly reporting this issue. Upstream acknowledges Nick Cleaton as the original reporter. Red Hat would like to thank Tim Bunce for responsibly reporting this issue. Red Hat would like to thank Jukka Taimisto and Olli Jarva of Codenomicon Ltd, Nokia Siemens Networks, and Wind River on behalf of their customer, for reporting this issue. Red Hat would like to thank the MIT Kerberos Team for responsibly reporting this issue. Upstream acknowledges Shawn Emery of Oracle as the original reporter. Red Hat would like to thank the MIT Kerberos Team for reporting this issue. Upstream acknowledges Mike Roszkowski as the original reporter. Red Hat would like to thank the MIT Kerberos Team for reporting this issue. Red Hat would like to thank the MIT Kerberos Team for reporting this issue. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges Matthieu Bonetti of VUPEN Vulnerability Research Team as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges wushi of team509, working with TippingPoint's Zero Day Initiative as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges wushi of team509, working with TippingPoint's Zero Day Initiative as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges wushi of team509, working with TippingPoint's Zero Day Initiative as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges wushi of team509, working with TippingPoint's Zero Day Initiative as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges regenrecht working with iDefense as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges wushi of team509, working with TippingPoint's Zero Day Initiative as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges wushi of team509, working with TippingPoint's Zero Day Initiative as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges wushi of team509, working with TippingPoint's Zero Day Initiative, as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges wushi of team509, working with TippingPoint's Zero Day Initiative, as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges Ojan Vafai of Google Inc. as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges Aki Helin of OUSPG as the original reporter. Red Hat would like to thank Apple Product Security for responsibly reporting this flaw, who credit Kevin Finisterre of digitalmunition.com for the discovery of the issue. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges Dave Bowker of davebowker.com as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges Mark Dowd of Azimuth Security as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges Aki Helin of OUSPG as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges wushi of team509 as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges kuzzcc, and Skylined of Google Chrome Security Team, as the original reporters. Red Hat would like to thank Mario Mikocevic for responsibly reporting this issue. Red Hat would like to thank Tim Bunce for responsibly reporting this flaw. Upstream credits also Rafaël Garcia-Suarez for discovering of this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Pierre Noguès of Meta Security as the original reporter. Red Hat would like to thank Dan Rosenberg for responsibly reporting this issue. Red Hat would like to thank Dan Rosenberg for responsibly reporting this issue. Red Hat would like to thank Anders Kaseorg and Evan Broder of Ksplice, Inc. for responsibly reporting this issue. Red Hat would like to thank the Apple Product Security team for responsibly reporting this flaw. Upstream acknowledges Luca Carettoni as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges wushi of team509, working with TippingPoint's Zero Day Initiative, as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges Yaar Schnitman of Google Inc. as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges Mark Dowd as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges James Robinson of Google Inc. as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges Skylined of Google Chrome Security Team as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges wushi of team509, working with TippingPoint's Zero Day Initiative, as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges Justin Schuh as the original reporter. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Red Hat would like to thank Drew Yao of Apple Product Security for responsibly reporting this issue. Upstream acknowledges wushi of team509 as the original reporter. Red Hat would like to thank Braden Thomas of the Apple Product Security team for reporting these issues. Red Hat would like to thank Rodrigo Rubira Branco of Check Point Vulnerability Discovery Team for responsibly reporting this issue. Red Hat would like to thank Meder Kydyraliev of Google Security Team for responsibly reporting this issue. Red Hat would like to thank the Samba team for responsibly reporting this issue. Upstream acknowledges Jun Mao as the original reporter. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank the Vulnerability Research Team at TELUS Security Labs and Fujita Tomonori for responsibly reporting these flaws. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Doug Knight of University of Alaska for reporting this issue. Red Hat would like to thank the X.Org security team for reporting this issue. Upstream acknowledges Rafal Wojtczuk as the original reporter. Red Hat would like to thank Jeremy Nickurak for reporting this issue. Red Hat would like to thank Andre Osterhues for reporting this issue. Red Hat would like to thank Robert Święcki of the Google Security Team for the discovery of this issue. Red Hat would like to thank Robert Święcki of the Google Security Team for the discovery of this issue. Red Hat would like to thank Robert Święcki of the Google Security Team for the discovery of this issue. Red Hat would like to thank Robert Święcki of the Google Security Team for the discovery of this issue. Red Hat would like to thank Robert Święcki of the Google Security Team for the discovery of these issues. Red Hat would like to thank Dan Rosenberg for responsibly reporting this issue. Red Hat would like to thank Dan Rosenberg for responsibly reporting this issue. Red Hat would like to thank the Evince development team for reporting this issue. Upstream acknowledges Jon Larimer of IBM X-Force as the original reporter. Red Hat would like to thank the Evince development team for reporting this issue. Upstream acknowledges Jon Larimer of IBM X-Force as the original reporter. Red Hat would like to thank the Evince development team for reporting this issue. Upstream acknowledges Jon Larimer of IBM X-Force as the original reporter. Red Hat would like to thank the Evince development team for reporting this issue. Upstream acknowledges Jon Larimer of IBM X-Force as the original reporter. Red Hat would like to thank Grant Diffey of CenITex for reporting this issue. Red Hat would like to thank Kees Cook for reporting this issue. Red Hat would like to thank Ted Brunell for reporting this issue. Red Hat would like to thank Emmanuel Bouillon of NATO C3 Agency for reporting this issue. Red Hat would like to thank Tavis Ormandy for reporting this issue. Red Hat would like to thank Markus Wuethrich of Swiss Post - PostFinance for reporting this issue. Red Hat would like to thank Tavis Ormandy for reporting this issue. Red Hat would like to thank Kees Cook for reporting this issue. Red Hat would like to thank Kees Cook for reporting this issue. Red Hat would like to thank Toshiyuki Okajima for reporting this issue. Red Hat would like to thank Tavis Ormandy for reporting this issue. Red Hat would like to thank Tavis Ormandy for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Robert Swiecki of Google Security Team for reporting this issue. Red Hat would like to thank Tavis Ormandy for reporting this issue. Red Hat would like to thank Ben Hawkes for reporting this issue. Red Hat would like to thank Tavis Ormandy for reporting this issue. Red Hat would like to thank Mark Sapiro for reporting these flaws. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Ben Hawkes for reporting this issue. Red Hat would like to thank the Openswan project for reporting this issue. Upstream acknowledges D. Hugh Redelmeier and Paul Wouters as the original reporters. Red Hat would like to thank the Openswan project for reporting this issue. Upstream acknowledges D. Hugh Redelmeier and Paul Wouters as the original reporters. Red Hat would like to thank Raphael Geissert for reporting this issue. Red Hat would like to thank Sebastian Krahmer of the SuSE Security Team for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank OpenOffice.org for reporting this issue. Upstream acknowledges Dan Rosenberg of Virtual Security Research as the original reporter. Red Hat would like to thank OpenOffice.org for reporting this issue. Upstream acknowledges Dan Rosenberg of Virtual Security Research as the original reporter. Red Hat would like to thank OpenOffice.org for reporting this issue. Upstream acknowledges Dan Rosenberg of Virtual Security Research as the original reporter. Red Hat would like to thank OpenOffice.org for reporting this issue. Upstream acknowledges Dan Rosenberg of Virtual Security Research as the original reporter. Red Hat would like to thank Dmitri Gribenko for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank the Pidgin project for reporting these issues. Upstream acknowledges Daniel Atallah as the original reporter. Red Hat would like to thank the Openswan project for reporting this issue. Upstream acknowledges D. Hugh Redelmeier and Paul Wouters as the original reporters. Red Hat would like to thank the Openswan project for reporting this issue. Upstream acknowledges D. Hugh Redelmeier and Paul Wouters as the original reporters. Red Hat would like to thank Ralph Loader for reporting this issue. Red Hat would like to thank Tavis Ormandy for reporting this issue. Red Hat would like to thank Ben Hawkes and Tavis Ormandy for reporting this issue. Red Hat would like to thank Brad Spengler for reporting this issue. Red Hat would like to thank Kees Cook for reporting this issue. Red Hat would like to thank Ole Husgaard of eXerp.com for reporting this issue. Red Hat would like to thank Rob Hulswit for reporting this issue. Red Hat would like to thank Thomas Pollet for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Nelson Elhage for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Dan Rosenberg of Virtual Security Research for reporting this issue. Red Hat would like to thank the Google Security Team for reporting this issue. Upstream acknowledges Bui Quang Minh from Bkis as the original reporter. Red Hat would like to thank Geoff Keating of the Apple Product Security team for reporting this issue. Red Hat would like to thank the MIT Kerberos Team for reporting this issue. Red Hat would like to thank the MIT Kerberos Team for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall and Kees Cook for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Steve Chen for reporting this issue. Red Hat would like to thank Tavis Ormandy for reporting this issue. Red Hat would like to thank Tavis Ormandy for reporting this issue. Red Hat would like to thank Leif Nixon for reporting this issue. Red Hat would like to thank Vladymyr Denysov for reporting this issue. Red Hat would like to thank Alan Cox for reporting this issue. Red Hat would like to thank Brad Spengler for reporting this issue. Red Hat would like to thank Vegard Nossum for reporting this issue. Red Hat would like to thank Vegard Nossum for reporting this issue. Red Hat would like to thank Nelson Elhage for reporting this issue. Red Hat would like to thank Kosuke Tatsukawa for reporting this issue. Red Hat would like to thank Sebastian Krahmer of the SuSE Security Team for reporting this issue. Red Hat would like to thank Sebastian Krahmer for reporting this issue. Red Hat would like to thank the TippingPoint Zero Day Initiative project for reporting this issue. The original issue reporter wishes to stay anonymous. Red Hat would like to thank Stephan Mueller of atsec information security for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Stu Tomlinson as the original reporter. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank OpenOffice.org for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Kees Cook for reporting this issue. Red Hat would like to thank Kees Cook for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Nadav Amit for reporting this issue. Red Hat would like to thank Emmanuel Bouillon of NATO C3 Agency for reporting this issue. Red Hat would like to thank Phil Pennock for reporting this issue. Red Hat would like to thank Mozilla Security Team for reporting this issue. Red Hat would like to thank Drew Yao of the Apple Product Security team for reporting this issue. Red Hat would like to thank Apple Product Security for reporting this issue. Red Hat would like to thank the MIT Kerberos project for reporting this issue. Upstream acknowledges Kevin Longfellow of Oracle Corporation as the original reporter. Red Hat would like to thank the MIT Kerberos project for reporting this issue. Red Hat would like to thank the CERT/CC for reporting CVE-2011-0411. The CERT/CC acknowledges Wietse Venema as the original reporter. Red Hat would like to thank Internet Systems Consortium for reporting this issue. Red Hat would like to thank Maksymilian Arciemowicz for reporting this issue. Red Hat would like to thank Nico Golde of Debian Security Team for reporting this issue. Debian Security Team acknowledges 'Teeed' as the original issue reporter. Red Hat would like to thank Matthieu Herrb for reporting this issue. Upstream acknowledges Sebastian Krahmer of the SuSE Security Team as the original reporter. This issue was discovered by Huzaifa Sidhpurwala of the Red Hat Security Response Team. Red Hat would like to thank Andrew Kerr for reporting this issue. Red Hat would like to thank Mark Sapiro for reporting these flaws. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Rafael Dominguez Vega for reporting this issue. Red Hat would like to thank Adam Prince for reporting this issue. Red Hat would like to thank Hyrum Wright of the Apache Subversion project for reporting this issue. Upstream acknowledges Philip Martin, WANdisco, Inc. as the original reporter. Red Hat would like to thank Thomas Biege of the SuSE Security Team for reporting this issue. Red Hat would like to thank Thomas Biege of the SuSE Security Team for reporting this issue. Red Hat would like to thank the Samba team for reporting this issue. Upstream acknowledges Volker Lendecke of SerNet as the original reporter. Red Hat would like to thank Kees Cook for reporting this issue. Red Hat would like to thank Sebastian Krahmer of the SUSE Security Team for reporting this issue. Red Hat would like to thank Sebastian Krahmer of the SuSE Security Team for reporting this issue. Red Hat would like to thank Nelson Elhage for reporting this issue. Red Hat would like to thank Timo Warns for reporting this issue. Red Hat would like to thank Tavis Ormandy for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Kees Cook for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Nelson Elhage for reporting this issue. Red Hat would like to thank Nelson Elhage for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank the Pidgin project for reporting these issues. Upstream acknowledges Marius Wachtler as the original reporter. Red Hat would like to thank Juraj Somorovsky of Ruhr-University Bochum for reporting this issue. Red Hat would like to thank Wayne Davison and Matt McCutchen for reporting this issue. This issue was discovered by Huzaifa Sidhpurwala of the Red Hat Security Response Team. Red Hat would like to thank Peter Huewe for reporting this issue. Red Hat would like to thank Peter Huewe for reporting this issue. Red Hat would like to thank Timo Warns for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Julien Tinnes of Google Security Team for reporting this issue. Red Hat would like to thank Nicolas Grégoire and Aleksey Sanin for reporting this issue. Red Hat would like to thank Ryan Sweat for reporting this issue. Red Hat would like to thank Martin Kouba from IT SYSTEMS a.s. for reporting this issue. Red Hat would like to thank Neel Mehta of Google for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank the MIT Kerberos project for reporting this issue. Upstream acknowledges Tim Zingelman as the original reporter. Red Hat would like to thank the MIT Kerberos project for reporting this issue. Upstream acknowledges Andrej Ota as the original reporter. Red Hat would like to thank the MIT Kerberos project for reporting this issue. Red Hat would like to thank Ryan Sweat for reporting this issue. Red Hat would like to thank Timo Warns for reporting this issue. Red Hat would like to thank Robert Swiecki for reporting this issue. Red Hat would like to thank Thomas Biege of the SuSE Security Team for reporting this issue. Red Hat would like to thank Cendio AB for reporting this issue. Cendio AB acknowledges an anonymous contributor working with the SecuriTeam Secure Disclosure program as the original reporter. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank the CERT/CC for reporting CVE-2011-1720. Upstream acknowledges Thomas Jarosch of Intra2net AG as the original reporter. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Oliver Hartkopp for reporting this issue. Red Hat would like to thank Nelson Elhage for reporting this issue. Red Hat would like to thank the Apache Subversion project for reporting this issue. Upstream acknowledges Joe Schaefer of Apache Software Foundation as the original reporter. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Timo Warns for reporting this issue. Red Hat would like to thank the Apache Subversion project for reporting this issue. Upstream acknowledges Ivan Zhakov of VisualSVN as the original reporter. Red Hat would like to thank the Ubuntu Security Team for reporting these issues. The Ubuntu Security Team acknowledges Vasiliy Kulikov of Openwall and Dan Rosenberg as the original reporters. Red Hat would like to thank the Ubuntu Security Team for reporting these issues. The Ubuntu Security Team acknowledges Vasiliy Kulikov of Openwall and Dan Rosenberg as the original reporters. Red Hat would like to thank the Ubuntu Security Team for reporting this issue. The Ubuntu Security Team acknowledges Vasiliy Kulikov of Openwall and Dan Rosenberg as the original reporters. Red Hat would like to thank the Ubuntu Security Team for reporting this issue. The Ubuntu Security Team acknowledges Dan Rosenberg and Marc Deslauriers as the original reporters. Red Hat would like to thank the Ubuntu Security Team for reporting this issue. The Ubuntu Security Team acknowledges Marc Deslauriers as the original reporter. Red Hat would like to thank the Ubuntu Security Team for reporting this issue. The Ubuntu Security Team acknowledges Vasiliy Kulikov of Openwall as the original reporter. Red Hat would like to thank the Apache Subversion project for reporting this issue. Upstream acknowledges Kamesh Jayachandran of CollabNet, Inc. as the original reporter. Red Hat would like to thank the CERT/CC for reporting this issue. The CERT/CC acknowledges Billy Bob Brumley and Nicola Tuveri as the original reporters. This issue was discovered by Huzaifa Sidhpurwala of the Red Hat Security Response Team. This issue was discovered by Huzaifa Sidhpurwala of the Red Hat Security Response Team. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. This issue was discovered by Huzaifa Sidhpurwala of the Red Hat Security Response Team. Red Hat would like to thank Andrea Righi for reporting this issue. Red Hat would like to thank the ObjectWorks+ Development Team at Nomura Research Institute for reporting this issue. Red Hat would like to thank Clement Lecigne for reporting this issue. Red Hat would like to thank Nelson Elhage for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. This issue was discovered by Huzaifa Sidhpurwala of the Red Hat Security Response Team. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Mark Doliner as the original reporter. Red Hat would like to thank Juraj Somorovsky of Ruhr-University Bochum for reporting this issue. Red Hat would like to thank Vasily Averin for reporting this issue. Red Hat would like to thank Marek Kroemeke and Filip Palian for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Robert Swiecki for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Peter Robinson for reporting this issue. Red Hat would like to thank Marco Slaviero of SensePost for reporting this issue. Red Hat would like to thank Li Yu for reporting this issue. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Yoshihiro Ishikawa of LAC Co., Ltd. as the original reporter. Red Hat would like to thank the Apache Tomcat project for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Nobuhiro Tsuji of NTT DATA SECURITY CORPORATION as the original reporter. Red Hat would like to thank Fernando Gont for reporting this issue. This issue was discovered by Huzaifa Sidhpurwala of the Red Hat Security Response Team. Red Hat would like to thank Brent Meshier for reporting this issue. Red Hat would like to thank Daniel Karanja Muturi for reporting this issue. Red Hat would like to thank Nils Juenemann and The Bearded Warriors for independently reporting this issue. Red Hat would like to thank Nils Juenemann for reporting this issue. Red Hat would like to thank Christopher Hartley of The Ohio State University for reporting this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mateusz Jurczyk of the Google Security Team as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ken Russell of Google as the original reporter. Red Hat would like to thank the Ubuntu Security Team for reporting this issue. The Ubuntu Security Team acknowledges Sauli Pahlman as the original reporter. Red Hat would like to thank Kees Cook of Google ChromeOS Team for reporting this issue. Red Hat would like to thank Kees Cook of Google ChromeOS Team for reporting this issue. Red Hat would like to thank Dan Kaminsky for reporting this issue. Red Hat would like to thank Darren Lavender for reporting this issue. Red Hat would like to thank Matt McCutchen for reporting this issue. Red Hat would like to thank Greg Banks for reporting this issue. Red Hat would like to thank Yasuaki Ishimatsu for reporting this issue. Red Hat would like to thank CERT-FI for reporting this issue. CERT-FI acknowledges Riku Hietamäki, Tuomo Untinen and Jukka Taimisto of the Codenomicon CROSS project as the original reporters. Red Hat would like to thank CERT-FI for reporting this issue. CERT-FI acknowledges Riku Hietamäki, Tuomo Untinen and Jukka Taimisto of the Codenomicon CROSS project as the original reporters. Red Hat would like to thank CERT-FI for reporting this issue. CERT-FI acknowledges Riku Hietamäki, Tuomo Untinen and Jukka Taimisto of the Codenomicon CROSS project as the original reporters. Red Hat would like to thank CERT-FI for reporting this issue. CERT-FI acknowledges Riku Hietamäki, Tuomo Untinen and Jukka Taimisto of the Codenomicon CROSS project as the original reporters. Red Hat would like to thank CERT-FI for reporting this issue. CERT-FI acknowledges Riku Hietamäki, Tuomo Untinen and Jukka Taimisto of the Codenomicon CROSS project as the original reporters. Red Hat would like to thank Sylvain Maes for reporting this issue. Red Hat would like to thank Somnath Kotur for reporting this issue. Red Hat would like to thank Yogesh Sharma for reporting this issue. Red Hat would like to thank Matt McCutchen for reporting this issue. Red Hat would like to thank Context Information Security for reporting this issue. Red Hat would like to thank Cyrus IMAP project for reporting this issue. Upstream acknowledges Stefan Cornelius of Secunia Research as the original reporter. Red Hat would like to thank the Openswan project for reporting this issue. Upstream acknowledges Paul Wouters as the original reporter. Red Hat would like to thank Kevan Carstensen for reporting this issue. Red Hat would like to thank Kevan Carstensen for reporting this issue. Red Hat would like to thank Kevan Carstensen for reporting this issue. Red Hat would like to thank Gideon Naim for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue. Red Hat would like to thank David Black for reporting this issue. Red Hat would like to thank David Black for reporting this issue. Red Hat would like to thank Zheng Liu for reporting this issue. Red Hat would like to thank the Puppet team for reporting this issue. Upstream acknowledges Ricky Zhou as the original reporter. Red Hat would like to thank researcher with a nickname vladz for reporting this issue. Red Hat would like to thank researcher with a nickname vladz for reporting this issue. Red Hat would like to thank the Openswan project for reporting this issue. Upstream acknowledges Petar Tsankov, Mohammad Torabi Dashti and David Basin of the information security group at ETH Zurich as the original reporters. Red Hat would like to thank Nick Bowler for reporting this issue. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges Julian Wälde and Alexander Klink as the original reporters. Red Hat would like to thank Jan Iven for reporting this issue. Red Hat would like to thank Shubham Goyal for reporting this issue. This issue was discovered by Huzaifa Sidhpurwala of the Red Hat Security Response Team. Red Hat would like to thank Andy Adamson for reporting this issue. Red Hat would like to thank Clement Lecigne for reporting this issue. Red Hat would like to thank William Hoffmann for reporting this issue. Red Hat would like to thank Sasha Levin for reporting this issue. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges Julian Wälde and Alexander Klink as the original reporters. Red Hat would like to thank Jonathan Foote of the CERT Coordination Center for reporting this issue. Red Hat would like to thank Jonathan Foote of the CERT Coordination Center for reporting this issue. Red Hat would like to thank Tyler Krpata for reporting this issue. Red Hat would like to thank Tetsuo Handa for reporting this issue. Upstream acknowledges Mathieu Desnoyers as the original reporter. Red Hat would like to thank the Pidgin project for reporting these issues. Upstream acknowledges Evgeny Boger as the original reporter. Red Hat would like to thank the Pidgin project for reporting these issues. Upstream acknowledges Thijs Alkemade as the original reporter. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Diego Bauche Madero from IOActive as the original reporter. Red Hat would like to thank Paul Kot for reporting this issue. Red Hat would like to thank Christian Schlüter (VIADA) for reporting this issue. Red Hat would like to thank NTT OSSC for reporting this issue. Red Hat would like to thank Maynard Johnson for reporting this issue. Red Hat would like to thank Masaki Tachibana for reporting this issue. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges Julian Wälde and Alexander Klink as the original reporters. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges Julian Wälde and Alexander Klink as the original reporters. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges Julian Wälde and Alexander Klink as the original reporters. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges Julian Wälde and Alexander Klink as the original reporters. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank Dan Rosenberg for reporting this issue. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges Julian Wälde and Alexander Klink as the original reporters. Red Hat would like to thank Nicolae Mogoreanu for reporting this issue. Red Hat would like to thank the cURL project for reporting this issue. Upstream acknowledges Dan Fandrich as the original reporter. Red Hat would like to thank Timothy D. Morgan of VSR for reporting this issue. Red Hat would like to thank Wang Xi for reporting this issue. Red Hat would like to thank Chen Haogang for reporting this issue. Red Hat would like to thank Stephan Bärwolf for reporting this issue. Red Hat would like to thank Jüri Aedla for reporting this issue. This issue was discovered by Ramon de C Valle of the Red Hat Product Security Team. This issue was discovered by Ramon de C Valle of the Red Hat Product Security Team. Red Hat would like to thank Simon McVittie for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Rafal Wojtczuk as the original reporter. Red Hat would like to thank the Xen for reporting this issue. Red Hat would like to thank the CERT/CC for reporting this issue. The CERT/CC acknowledges Martin Winter at OpenSourceRouting.org as the original reporter. Red Hat would like to thank the CERT/CC for reporting this issue. The CERT/CC acknowledges Martin Winter at OpenSourceRouting.org as the original reporter. Red Hat would like to thank the CERT/CC for reporting this issue. The CERT/CC acknowledges Martin Winter at OpenSourceRouting.org as the original reporter. Red Hat would like to thank CERT-FI for reporting this issue. CERT-FI acknowledges Aleksis Kauppinen, Joonas Kuorilehto, Tuomas Parttimaa and Lasse Ylivainio of Codenomicon's CROSS project as the original reporters. Red Hat would like to thank CERT-FI for reporting this issue. CERT-FI acknowledges Aleksis Kauppinen, Joonas Kuorilehto, Tuomas Parttimaa and Lasse Ylivainio of Codenomicon's CROSS project as the original reporters. Red Hat would like to thank the Mozilla project for reporting these issues. Red Hat would like to thank the Mozilla project for reporting these issues. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Aki Helin from OUSPG as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen from OUSPG as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Anne van Kesteren of Opera Software as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges wushi of team509 via iDefense as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Matias Juntunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jordi Chancel and Eddy Bordi, and Chris McGowen as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Masato Kinugawa as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ms2ger as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jeroen van der Gun as the original reporter. Red Hat would like to thank Andrew Lutomirski for reporting this issue. Red Hat would like to thank Todd C. Miller for reporting this issue. Upstream acknowledges joernchen of Phenoelit as the original reporter. This issue was discovered by Ramon de C Valle of the Red Hat Product Security Team. Red Hat would like to thank Graham Leggett for reporting this issue. Red Hat would like to thank Thomas Swan of FedEx for reporting this issue. Red Hat would like to thank the Samba team for reporting this issue. Upstream acknowledges Andy Davis of NGS Secure as the original reporter. Red Hat would like to thank Sebastian Krahmer of the SUSE Security Team for reporting this issue. This issue was discovered by David Jorm of the Red Hat Security Response Team. Red Hat would like to thank Kees Cook for reporting this issue. Red Hat would like to thank Ludwig Nussel of the SUSE security team for reporting this issue. Red Hat would like to thank H. Peter Anvin for reporting this issue. This issue was discovered by Dominic Cleal of Red Hat Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Red Hat would like to thank Mateusz Jurczyk of the Google Security Team for reporting this issue. Upstream acknowledges Tielei Wang via Secunia SVCRP as the original reporter of this issue. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges Julian Wälde and Alexander Klink as the original reporters. Red Hat would like to thank Timo Warns for reporting this issue. Red Hat would like to thank Timo Warns for reporting this issue. Red Hat would like to thank Matthew Hall of Mu Dynamics for reporting this issue. Red Hat would like to thank Matthew Hall of Mu Dynamics for reporting this issue. Red Hat would like to thank CERT-FI for reporting this issue. CERT-FI acknowledges Aleksis Kauppinen, Joonas Kuorilehto, Tuomas Parttimaa and Lasse Ylivainio of Codenomicon's CROSS project as the original reporters. Red Hat would like to thank the CERT/CC for reporting this issue. The CERT/CC acknowledges Denis Ovsienko as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Igor Bukanov, Olli Pettay, Boris Zbarsky, and Jesse Ruderman as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jesse Ruderman, Igor Bukanov, Bill McCloskey, Christian Holler, Andrew McCreight, and Brian Bondy as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges security researcher Abhishek Arya of Google as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges security researcher Abhishek Arya of Google as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges security researcher Adam Barth as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges security researcher Paul Stone as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges security researcher Arthur Gerkis as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges security researcher Abhishek Arya of Google as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Brian Smith, Gary Kwong, Christian Holler, Jesse Ruderman, Christoph Diehl, Chris Jones, Brad Lassey, and Kyle Huey as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges security researcher Mario Gomes and research firm Code Audit Labs as the original reporters of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Google security researcher Abhishek Arya as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Google security researcher Abhishek Arya as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Google security researcher Abhishek Arya as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Google security researcher Abhishek Arya as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Mariusz Mlynski as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Mariusz Mlynski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Mario Heiderich as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Arthur Gerkis as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mozilla developer Bobby Holley as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Google developer Tony Payne as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mozilla developer Frédéric Buclin as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Bill Keese as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Karthikeyan Bhargavan of Prosecco at INRIA as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security Researcher Matt McCutchen for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researchers Mario Gomes and Soroush Dalili as the original reporters of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges moz_bug_r_a4 as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges moz_bug_r_a4 as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gary Kwong, Christian Holler, Jesse Ruderman, Steve Fink, Bob Clary, Andrew Sutherland, and Jason Smith as the original reporters. These flaws affected Firefox 14. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Abhishek Arya (Inferno) of Google Chrome Security Team as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Abhishek Arya (Inferno) of Google Chrome Security Team as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Abhishek Arya (Inferno) of Google Chrome Security Team as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Abhishek Arya (Inferno) of Google Chrome Security Team as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Abhishek Arya (Inferno) of Google Chrome Security Team as the original reporter of this flaw. Red Hat would like to thank Puppet Labs for reporting this issue. Red Hat would like to thank Puppet Labs for reporting this issue. Red Hat would like to thank Puppet Labs for reporting this issue. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Ivano Cristofolini as the original reporter of this issue. This issue was found by Karel Volný of Red Hat Quality Engineering. Red Hat would like to thank Vadim Ponomarev for reporting this issue. Red Hat would like to thank Shachar Raindel for reporting this issue. Red Hat would like to thank Ronald van Zantvoort for reporting this issue. Red Hat would like to thank Phillips Wolf for reporting this issue. Upstream acknowledges Rubin Xu and Joseph Bonneau as the original reporters of this issue. This issue was discovered by the Red Hat Security Response Team. Red Hat would like to thank Stephan Mueller for reporting this issue. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Codenomicon as the original reporter. Upstream acknowledges Sven Jacobi as the original reporter of this issue. This issue was discovered by Li Honggang of Red Hat. This issue was discovered by Jian Li of Red Hat. This issue was discovered by Red Hat. Red Hat would like to thank the Apache CXF project for reporting this issue. Red Hat would like to thank the Apache CXF project for reporting this issue. Red Hat would like to thank Xinli Niu for reporting this issue. Upstream acknowledges Timo Warns as the original reporter of this issue. This issue was discovered by Marek Schmidt and Stan Silvert of Red Hat. This issue was discovered by Paul Wouters of Red Hat. These issues were discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Stanislav Graf of Red Hat. These issues were discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. Red Hat would like to thank Ray Rocker for reporting this issue. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges Julian Wälde and Alexander Klink as the original reporters. Red Hat would like to thank Antonios Atlasis working with Beyond Security's SecuriTeam Secure Disclosure program for reporting this issue. Red Hat would like to thank Joseph Sheridan of Reaction Information Security for reporting this issue. Red Hat would like to thank Chris Evans of the Google Security Team for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter Red Hat would like to thank Dan Fandrich for reporting this issue. Upstream acknowledges Mateusz Jurczyk of the Google Security Team as the original reporter. Red Hat would like to thank Dan Fandrich for reporting this issue. Upstream acknowledges Mateusz Jurczyk of the Google Security Team as the original reporter. Red Hat would like to thank Dan Fandrich for reporting this issue. Upstream acknowledges Mateusz Jurczyk of the Google Security Team as the original reporter. Red Hat would like to thank Dan Fandrich for reporting this issue. Upstream acknowledges Yunho Kim as the original reporter. Red Hat would like to thank Dan Fandrich for reporting this issue. Upstream acknowledges Yunho Kim as the original reporter. Red Hat would like to thank Dan Fandrich for reporting this issue. Red Hat would like to thank Dan Fandrich for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Joseph Sheridan for reporting this issue. Red Hat would like to thank George Hedfors of Cybercom Sweden East AB for reporting this issue. This issue was discovered by Carlo de Wolf of Red Hat. This issue was discovered by Carlo de Wolf of Red Hat. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Ulf Härnhammar as the original reporter. Red Hat would like to thank Jim Meyering for reporting this issue. Upstream acknowledges Stefano Lattarini as the original reporter. This issue was discovered by Huzaifa Sidhpurwala of the Red Hat Security Response Team. Red Hat would like to thank Ben Hutchings of Solarflare (tm) for reporting this issue. Red Hat would like to thank Ken Hahn and Dan Bradley for reporting this issue. This issue was discovered by the Red Hat Security Response Team. Red Hat would like to thank Chamal De Silva for reporting this issue. This issue was discovered by Aleksandar Kostadinov of the Red Hat QE Team. This issue was discovered by Arun Neelicattu of the Red Hat Security Response Team. Red Hat would like to thank Sigbjorn Lie of the Atea Norway for reporting this issue. This issue was discovered by the Red Hat InfiniBand team. This issue was discovered by Steven Hawkins of Red Hat. Red Hat would like to thank the Xen for reporting this issue. Red Hat would like to thank the Xen for reporting this issue. Red Hat would like to thank the Apache CXF project for reporting this issue. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. Red Hat would like to thank Matthias Weckbecker of the SUSE Security Team for reporting this issue. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Peter Eisentraut as the original reporter. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Noah Misch as the original reporter. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Matthew Daley as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Matthew Daley as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Matthew Daley as the original reporter. Red Hat would like to thank Alexander Peslyak for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Pablo Neira Ayuso for reporting this issue. Red Hat would like to thank Sebastian Krahmer of the SUSE Security Team for reporting this issue. These issues were discovered by Trevor Jay of Red Hat Quality Engineering penetration testing. This issue was discovered by Huzaifa Sidhpurwala of the Red Hat Security Response Team. This issue was discovered by James Laska of Red Hat. Red Hat would like to thank Thomas Biege of SUSE for reporting this issue. Red Hat would like to thank Dolph Mathews for reporting this issue. Red Hat would like to thank Timo Warns of PRESENSE Technologies GmbH for reporting this issue. Red Hat would like to thank Hafid Lin for reporting this issue. Upstream acknowledges Markus Hietava of Codenomicon CROSS project as the original reporter of this issue. Upstream acknowledges Markus Hietava of Codenomicon CROSS project as the original reporter of this issue. Red Hat would like to thank Puppet Labs for reporting this issue. Red Hat would like to thank Puppet Labs for reporting this issue. Red Hat would like to thank Puppet Labs for reporting this issue. Upstream acknowledges Glen Eustace of Massey University, New Zealand, as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Abhishek Arya (Inferno) of Google Chrome Security Team as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Abhishek Arya (Inferno) of Google Chrome Security Team as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Abhishek Arya (Inferno) of Google Chrome Security Team as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Abhishek Arya (Inferno) of Google Chrome Security Team as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Abhishek Arya (Inferno) of Google Chrome Security Team as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Abhishek Arya (Inferno) of Google Chrome Security Team as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Abhishek Arya (Inferno) of Google Chrome Security Team as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Abhishek Arya (Inferno) of Google Chrome Security Team as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Abhishek Arya (Inferno) of Google Chrome Security Team as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Mariusz Mlynski as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Frédéric Hoguin as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges miaubiz as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges miaubiz as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Arthur Gerkis as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Arthur Gerkis as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges security researcher Christoph Diehl as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Nicolas Grégoire as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mozilla security researcher Mark Goodwin as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mozilla security researcher Masato Kinugawa as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mozilla security researcher vsemozhetbyt as the original reporter of this flaw. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges security Security researcher Mark Poticha as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges security Mozilla security researcher moz_bug_r_a4 as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges security Security researcher Colby Russell as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler and Jesse Ruderman as the original reporters. These flaws affect Firefox 10.0.7 ESR and Firefox 15. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges David Bloom of Cue as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Johnny Stenback as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Soroush Dalili as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges miaubiz as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Alice White as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski as the original reporter Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges moz_bug_r_a4 as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gareth Heyes as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges moz_bug_r_a4 as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski, moz_bug_r_a4 and Antoine Delignat-Lavaud as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski, moz_bug_r_a4 and Antoine Delignat-Lavaud as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski, moz_bug_r_a4 and Antoine Delignat-Lavaud as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges moz_bug_r_a4 as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen from OUSPG as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges kakzz.ng@gmail.com as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Scott Bell as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gabor Krizsanits as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Masato Kinugawa as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Peter Van der Beken as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank Tetsuo Handa for reporting this issue. Red Hat would like to thank Marc Schönefeld for reporting this issue. Red Hat would like to thank Sebastian Krahmer of the SUSE Security Team for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Dolph Mathews for reporting this issue. These issues were discovered by Kurt Seifried of Red Hat, and Jim Meyering. This issue was discovered by Wenlong Huang of the Red Hat Virtualization QE Team. Red Hat would like to thank Sebastian Krahmer of the SUSE Security Team for reporting this issue. This issue was discovered by Murray McAllister of Red Hat Security Response Team. Red Hat would like to thank Antonios Atlasis working with Beyond Security's SecuriTeam Secure Disclosure program and Loganaden Velvindron of AFRINIC for reporting this issue. Red Hat would like to thank Timo Warns of PRESENSE Technologies GmbH for reporting this issue. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Noriko Hosoi of Red Hat. This issue was discovered by Karel Volný of the Red Hat Quality Engineering team. This issue was discovered by Peter Jones of the Red Hat Installer Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. Red Hat would like to thank Jon Howell for reporting this issue. This issue was discovered by Daniel Horak of the Red Hat Enterprise MRG Quality Engineering Team. This issue was discovered by Vit Ondruch of Red Hat. This issue was discovered by Florian Weimer of Red Hat. This issue was discovered by Miroslav Lichvar of Red Hat. This issue was discovered by Tomas Mraz of Red Hat. This issue was discovered by the Red Hat Security Response Team. Red Hat would like to thank Theodore Ts'o for reporting this issue. Upstream acknowledges Dmitry Monakhov as the original reporter. Red Hat would like to thank Vincent Untz for reporting this issue. This issue was discovered by Florian Weimer of Red Hat Product Security Team. This issue was discovered by Florian Weimer of Red Hat Product Security Team and Kurt Seifried of the Red Hat Security Response Team. Red Hat would like to thank the upstream Django project for reporting this vulnerability. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Arthur Gerkis for reporting this issue. This issue was discovered by Paolo Bonzini of Red Hat. Red Hat would like to thank the Xen project for reporting this issue. This issue was discovered by Marko Myllynen of Red Hat. This issue was discovered by Arun Neelicattu of the Red Hat Security Response Team. This issue was discovered by Josef Cacek of the Red Hat JBoss EAP Quality Engineering team. Red Hat would like to thank Patrick Raspante and Ryan Millay of GDC4S for reporting this issue. Red Hat would like to thank Patrick Raspante and Ryan Millay of GDC4S for reporting this issue. This issue was discovered by Huzaifa S. Sidhpurwala of Red Hat Security Response Team. This issue was discovered by Rodrigo Freire of Red Hat. This issue was discovered by Josef Cacek of the Red Hat JBoss EAP Quality Engineering team. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Gabe Westmaas as the original reporter of CVE-2012-4573. This issue was discovered by Kurt Seifried of the Red Hat Security Response Team. Red Hat would like to thank the Perl project for reporting this issue. Upstream acknowledges Tim Brown as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges David Bloom of Cue as the original reporter. This issue was discovered by Kurt Seifried of Red Hat Security Response Team. This issue was discovered by Kurt Seifried of Red Hat Security Response Team. This issue was discovered by Derek Horton of Red Hat. This issue was discovered by Kurt Seifried of the Red Hat Security Response Team. Red Hat would like to thank Petr Menšík for reporting this issue. This issue was discovered by Aaron Weitekamp of the Red Hat Cloud Quality Engineering team. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. This issue was discovered by Allon Mureinik of Red Hat. This issue was discovered by Dan Kenigsberg of Red Hat. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank SUSE Security Team for reporting this issue. SUSE Security Team acknowledges Thomas Biege of SUSE as the original issue reporter. Red Hat would like to thank Hideharu Ohkuma of Ricoh Company for reporting these issues. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. Red Hat would like to thank Stefan Bühler for reporting this issue. Upstream acknowledges Jesse Sipprell from McClatchy Interactive, Inc. as the original reporter. This issue was discovered by Aaron Weitekamp of the Red Hat Cloud Quality Engineering team. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Anndy as the original reporter. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Vijaya Erukala as the original reporter. Red Hat would like to thank Tibor Jager, Kenneth G. Paterson and Juraj Somorovsky of Ruhr-University Bochum for reporting this issue. This issue was discovered by Huzaifa S. Sidhpurwala of Red Hat Security Response Team. This issue was discovered by Lukas Zapletal of Red Hat. This issue was discovered by Og Maciel of Red Hat. This issue was discovered by James Labocki of Red Hat. This issue was discovered by Red Hat. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Eric Windisch as the original reporter of CVE-2012-5625. This issue was discovered by Zbyněk Roubalík of Red Hat. Red Hat would like to thank the Xen project for reporting this issue. These issues were discovered by Kurt Seifried of the Red Hat Security Response Team and Michael Scherer of the Red Hat Regional IT team. This issue was discovered by Red Hat. This issue was discovered by Michael Scherer of the Red Hat Regional IT team. This issue was discovered by Michael Scherer of the Red Hat Regional IT team. This issue was discovered by Miloslav Trmač of Red Hat. Red Hat would like to thank Martin Carpenter of Citco for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges miaubiz as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges miaubiz as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges miaubiz as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jonathan Stephens as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Masato Kinugawa as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges miaubiz as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bobby Holley as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jesse Ruderman, Andrew McCreight, Bob Clary, and Kyle Huey as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gary Kwong, Jesse Ruderman, Christian Holler, Bob Clary, Kyle Huey, Ed Morley, Chris Lord, Boris Zbarsky, Julian Seward, and Bill McCloskey as the original reporter. This issue was discovered by Andrew Cathrow of Red Hat. This issue was discovered by Dominic Cleal and James Laska of Red Hat. This issue was discovered by James Laska of Red Hat. This issue was discovered by Tomas Sedovic of Red Hat. Red Hat would like to thank Ben Ford of Puppet Labs for reporting this issue. Red Hat would like to thank Sam Richardson for reporting this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Thijs Alkemade and Robert Vehse as the original reporters of this issue. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. This issue was discovered by Michael Scherer of the Red Hat Regional IT team. This issue was discovered by Michael Scherer of the Red Hat Regional IT team. This issue was discovered by Michael Scherer of the Red Hat Regional IT team. This issue was discovered by Dan Kenigsberg of the Red Hat Enterprise Virtualization team. This issue was discovered by Ondrej Machacek of Red Hat. This issue was discovered by Tingting Zheng of Red Hat. This issue was discovered by David Jorm of the Red Hat Security Response Team. This issue was discovered by David Jorm of the Red Hat Security Response Team. Red Hat would like to thank the Andrew Cooper of Citrix for reporting this issue. This issue was discovered by Jeremy Choi of the Red Hat Hosted and Shared Services team. Red Hat would like to thank Martin Kosek of Red Hat for reporting this issue. This issue was discovered by Tim Waugh of Red Hat. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Phil Day as the original reporter. This issue was discovered by Dan Prince of Red Hat. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Jann Horn as the original reporter. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Jann Horn as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. This issue was discovered by Arun Neelicattu of the Red Hat Security Response Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. These issues were discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Andrew Jones of Red Hat. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Simon McVittie for reporting this issue. This issue was discovered by Dan Prince of Red Hat. Red Hat would like to that Daniel Stenberg of cURL project for reporting of this issue. Upstream acknowledges researcher known as Volema as the original issue reporter. Red Hat would like to thank the Qt project for reporting this issue. Upstream acknowledges Tim Brown and Mark Lowe of Portcullis Computer Security Ltd. as the original reporters. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Sumit Soni via Secunia SVCRP as the original issue reporter. Red Hat would like to thank Eric Hodel of RDoc upstream for reporting this issue. Upstream acknowledges Evgeny Ermakov as the original issue reporter. This issue was discovered by Kurt Seifried of the Red Hat Security Response Team. This issue was discovered by Trevor McKay of Red Hat. This issue was discovered by Derek Higgins of the Red Hat OpenStack team. Red Hat would like to thank Ruby on Rails upstream for reporting this issue. Upstream acknowledges Thomas Hollstegge of Zweitag and Ben Murphy as the original reporters. This issue was discovered by Dan Prince of Red Hat. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Chris Wysopal of Veracode as the original issue reporter. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Daniel Atallah as the original reporter. Red Hat would like to thank the Pidgin project for reporting this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Red Hat would like to thank the Ruby on Rails project for reporting this issue. The Ruby on Rails project acknowledges Tobias Kraze as the original reporter. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Nathanael Burton (National Security Agency) as the original reporter. This issue was discovered by Kaushik Banerjee of Red Hat. Red Hat would like to thank Garth Mollett for reporting this issue. This issue was discovered by Mike Burns of Red Hat. This issue was discovered by Thierry Bordaz of Red Hat. This issue was discovered by Nick Scavelli of Red Hat. This issue was discovered by Arun Neelicattu and David Jorm of the Red Hat Security Response Team. Red Hat would like to thank Ruby on Rails upstream for reporting this issue. Upstream acknowledges Lawrence Pit of Mirror42 as the original reporter. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Loganathan Parthipan (HP) and Rohit Karajgi (NTT Data) as the original, independent reporters. This issue was discovered by Sumit Bose of Red Hat. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Olli Pettay as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Boris Zbarsky as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jesse Ruderman as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jesse Ruderman as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bill Gianopoulos, Benoit Jacob, Christoph Diehl, Christian Holler, Gary Kwong, Robert O'Callahan, Scoobidiver, Jesse Ruderman and Julian Seward as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges pa_kt as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Sviatoslav Chagaev as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges regenrecht as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges regenrecht as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges regenrecht as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges regenrecht as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Masato Kinugawa as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jerry Baker as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Boris Zbarsky as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges miaubiz as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christoph Diehl, Christian Holler, Mats Palmgren, and Chiaki Ishikawa as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bill Gianopoulos, Benoit Jacob, Christoph Diehl, Christian Holler, Gary Kwong, Robert O'Callahan, Scoobidiver, Jesse Ruderman and Julian Seward as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bobby Holley as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Frederik Braun as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Michal Zalewski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Olli Pettay, Christoph Diehl, Gary Kwong, Jesse Ruderman, Andrew McCreight, Joe Drew, and Wayne Mery as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Alon Zakai, Christian Holler, Gary Kwong, Jesse Ruderman, Luke Wagner, Terrence Cole, Timothy Nikkel, Olli Pettay, Bill McCloskey, and Nicolas Pierron as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges VUPEN Security via the TippingPoint Zero Day Initiative project as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Olli Pettay, Jesse Ruderman, Boris Zbarsky, Christian Holler, Milan Sreckovic, and Joe Drew as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Andrew McCreight, Randell Jesup, Gary Kwong, Jesse Ruderman, Christian Holler, and Mats Palmgren as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ambroz Bizjak as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tobias Schula as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Cody Crews as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges miaubiz as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christoph Diehl, Christian Holler, Jesse Ruderman, Timothy Nikkel, and Jeff Walden as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Andrew Cooper and the Citrix XenServer team as the original reporters. Red Hat would like to thank the Perl 5 Security Team for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Raphael Geissert for reporting these issues during a review for EDF. Red Hat would like to thank Tim Brown for reporting this issue. Red Hat would like to thank US-CERT for reporting this issue. US-CERT acknowledges Oracle as the original reporter. Red Hat would like to thank Puppet Labs for reporting this issue. Red Hat would like to thank Puppet Labs for reporting this issue. Red Hat would like to thank Puppet Labs for reporting this issue. Red Hat would like to thank Perl project for reporting this issue. Upstream acknowledges Yves Orton as the original issue reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bob Clary, Ben Turner, Benoit Jacob, Bobby Holley, Christoph Diehl, Christian Holler, Andrew McCreight, Gary Kwong, Jason Orendorff, Jesse Ruderman, Matt Wobensmith, and Mats Palmgren as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Cody Crews as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges moz_bug_r_a4 as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ms2ger as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gary Kwong, Jesse Ruderman, and Andrew McCreight as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Bobby Holley, Gary Kwong, Jesse Ruderman, Ben Turner, Ehsan Akhgari, Mats Palmgren, and John Schoenick as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Johnathan Kuskos as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Paul Stone as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Boris Zbarsky as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bob Owen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Frédéric Buclin as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges moz_bug_r_a4 as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Matt Wobensmith as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges 3ric Johanson, Richard Newman and Holt Sorenson as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jeff Gilbert and Henrik Skupin as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ben Turner, Christian Holler, Andrew McCreight, Gary Kwong, Jan Varga, and Jesse Ruderman as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Aki Helin as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges moz_bug_r_a4 as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges moz_bug_r_a4 as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bobby Holley and moz_bug_r_a4 as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Cody Crews as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Federico Lanusse as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Georgi Guninski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges André Bargull, Scoobidiver, Bobby Holley, and Reuben Morais as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Makoto Kato, Jesse Ruderman, Jason Smith, Jan de Mooij, Gary Kwong, Scoobidiver, Olli Pettay, Bobby Holley, and Bob Clary as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Alex Chapman as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Masayuki Nakano as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Scott Bell as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ms2ger as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Dan Gohman as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Victor Porof as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Sachin Shinde as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Aki Helin as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Boris Zbarsky as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tavis Ormandy as the original reporter of this issue. This issue was discovered by Mateusz Guzik of Red Hat EMEA GSS SEG Team. Red Hat would like to thank Andrew Honig of Google for reporting this issue. Red Hat would like to thank Andrew Honig of Google for reporting this issue. Red Hat would like to thank Andrew Honig of Google for reporting this issue. Red Hat would like to thank Simon McVittie for reporting this issue. This issue was discovered by Derek Higgins of the Red Hat OpenStack team. Red Hat would like to thank Finke Lamein for reporting this issue. This issue was discovered by Sureshkumar Thirugnanasambandan of the Red Hat Quality Engineering Team. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Vish Ishaya (Nebula) as the original reporter. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Stuart McLaren (HP) as the original reporter. Red Hat would like to thank the Apache Subversion project for reporting this issue. Upstream acknowledges Alexander Klink as the original reporter of this flaw. Red Hat would like to thank the Apache Subversion project for reporting this issue. Upstream acknowledges Ben Reser as the original reporter of this flaw. Red Hat would like to thank the Apache Subversion project for reporting this issue. Upstream acknowledges Philip Martin and Ben Reser as the original reporter of this flaw. Red Hat would like to thank Ruby on Rails upstream for reporting this issue. Upstream acknowledges Ben Murphy as the original reporter. Red Hat would like to thank Ruby on Rails upstream for reporting this issue. Upstream acknowledges Charlie Somerville as the original reporter. Red Hat would like to thank Ruby on Rails upstream for reporting this issue. Upstream acknowledges Alan Jenkins as the original reporter. Red Hat would like to thank Alyssa Milburn for reporting this issue. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Guang Yee (HP) as the original reporter. Red Hat would like to thank Ryan Giobbi of UPMC for reporting this issue. Red Hat would like to thank Ryan Giobbi of UPMC for reporting this issue. Red Hat would like to thank the Apache Subversion for reporting this issue. Upstream acknowledges Greg McMullin, Stefan Fuhrmann, Philip Martin and Ben Reser as the original reporters of this flaw. This issue was discovered by Martin Kosek of Red Hat. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Mitsumasa Kondo and Kyotaro Horiguchi as the original issue reporters. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Marko Kreen as the original issue reporter. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Noah Misch as the original issue reporter. This issue was discovered by Petr Matousek of the Red Hat MRG Messaging team. Red Hat would like to thank Willy Tarreau of HAProxy upstream for reporting this issue. Upstream acknowledges Yves Lafon from the W3C as the original reporter. This issue was discovered by Murray McAllister of the Red Hat Security Response Team. Red Hat would like to thank the Xen for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. This issue was found by Daniel Berrange of Red Hat. This issue was discovered by Jiri Vanek of the Red Hat OpenJDK Team. This issue was discovered by the Red Hat Security Response Team. Red Hat would like to thank IBM for reporting this issue. This issue was found by David Airlie and Peter Hutterer of Red Hat. This issue was discovered by Michael S. Tsirkin of Red Hat. Red Hat would like to thank the cURL project for reporting this issue. Upstream acknowledges YAMADA Yasuharu as the original reporter. Red Hat would like to thank Michael Armstrong for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. This issue was discovered by Murray McAllister of Red Hat Security Response Team. Red Hat would like to thank Emmanuel Bouillon (NCI Agency) for reporting this issue. Red Hat would like to thank Emmanuel Bouillon (NCI Agency) for reporting this issue. Red Hat would like to thank Edoardo Comar of IBM for reporting this issue. Red Hat would like to thank the Xen for reporting this issue. Red Hat would like to thank Simon Fayer of Imperial College London for reporting this issue. This issue was discovered by Murray McAllister of the Red Hat Security Response Team. Red Hat would like to thank Andy Lutomirski for reporting this issue. This issue was discovered by Laszlo Ersek of Red Hat. This issue was found by Jason Wang of Red Hat. Red Hat would like to thank Atzm WATANABE of Stratosphere Inc. for reporting this issue. This issue was discovered by Grant Murphy of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Ramon de C Valle of the Red Hat Product Security Team. This issue was discovered by Ramon de C Valle of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Jan Pazdziora of the Red Hat Satellite Engineering team. This issue was discovered by Vit Ondruch of Red Hat. This issue was discovered by Ramon de C Valle of the Red Hat Product Security Team. Red Hat would like to thank Amazon Web Services for reporting this issue. Amazon Web Services acknowledges Sylvain Beucler as the original reporter. This issue was discovered by Paolo Bonzini and Laszlo Ersek of Red Hat. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. This issue was discovered by Florian Weimer (Red Hat Product Security). This issue was discovered by Red Hat. This issue was discovered by Eoghan Glynn of Red Hat. This issue was discovered by Ramon de C Valle of the Red Hat Product Security Team. This issue was discovered by Michael Scherer of the Red Hat Regional IT team. This issue was discovered by Ramon de C Valle of the Red Hat Product Security Team. This issue was discovered by Richard Opalka and Arun Neelicattu of Red Hat. This issue was discovered by Ramon de C Valle of the Red Hat Product Security Team. This issue was discovered by Daniel Erez of the Red Hat Enterprise Virtualization Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. Red Hat would like to thank Scott Cantor of Apache Santuario-C++ upstream for reporting of this issue. Upstream acknowledges James Forshaw of Context Information Security as the original issue reporter. Red Hat would like to thank Scott Cantor of Apache Santuario-C++ upstream for reporting of this issue. Upstream acknowledges James Forshaw of Context Information Security as the original issue reporter. Red Hat would like to thank Scott Cantor of Apache Santuario-C++ upstream for reporting of this issue. Upstream acknowledges James Forshaw of Context Information Security as the original issue reporter. Red Hat would like to thank Scott Cantor of Apache Santuario-C++ upstream for reporting of this issue. Upstream acknowledges James Forshaw of Context Information Security as the original issue reporter. Red Hat would like to thank Thierry Carrez of OpenStack upstream for reporting this issue. Upstream acknowledges Jose Castro Leon of CERN as the original issue reporter. Red Hat would like to thank Andreas Falkenberg of SEC Consult Deutschland GmbH, and Christian Mainka, Juraj Somorovsky and Joerg Schwenk of Ruhr-University Bochum for reporting this issue. Red Hat would like to thank Alex Gaynor from Rackspace for reporting this issue. Red Hat would like to thank Takeshi Terada (Mitsui Bussan Secure Directions, Inc.) for reporting this issue. Red Hat would like to thank the OpenStack project for reporting these issues. Upstream acknowledges Paul McMillan of Nebula as the original reporter. Red Hat would like to thank the OpenStack project for reporting these issues. Upstream acknowledges Paul McMillan of Nebula as the original reporter. Red Hat would like to thank the cURL project for reporting this issue. Upstream acknowledges Timo Sirainen as the original reporter. Red Hat would like to thank HAProxy upstream for reporting this issue. Upstream acknowledges David Torgerson as the original reporter. This issue was discovered by Jiri Belka of Red Hat. This issue was discovered by Mateusz Guzik of Red Hat. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Martin Carpenter of Citco for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen for reporting this issue. Upstream acknowledges Zhenzhong Duan as the original reporter. This issue was discovered by Daniel P. Berrange of Red Hat. This issue was discovered by Ludwig Krispenz of Red Hat. This issue was discovered by Zhenfeng Wang of Red Hat. This issue was discovered by Lev Veyde of Red Hat. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges hzrandd from NetEase as the original reporter. Upstream also acknowledges Ken'ichi Ohmichi from NEC for providing a corrected fix for this issue. Red Hat would like to thank Puppet Labs for reporting this issue. Red Hat would like to thank Puppet Labs for reporting this issue. Red Hat would like to thank Moshe Kaplan for reporting this issue. Red Hat would like to thank Moshe Kaplan for reporting this issue. Red Hat would like to thank Kees Cook for reporting this issue. Red Hat would like to thank Kees Cook for reporting this issue. Red Hat would like to thank Kees Cook for reporting this issue. Red Hat would like to thank the Xen and KVM upstreams for reporting this issue. Xen upstream acknowledged Gábor PÉK of CrySyS Lab as the original reporter Red Hat would like to thank Puppet Labs for reporting this issue. Upstream acknowledges Ben Murphy as the original reporter. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Thomas Leaman of HP as the original reporter. This issue was discovered by Marek Hulán of the Red Hat Foreman team. Red Hat would like to thank Hannes Frederic Sowa for reporting this issue. This issue was discovered by Wolf-Dieter Fink of the Red Hat GSS Team. This issue was discovered by David Gibson of Red Hat. Red Hat would like to thank Ben Reser of Apache Subversion project for reporting this issue. Upstream acknowledges Daniel Shahaf of Apache Infrastructure as the original issue reporter. The issues were discovered as part of the state loading code audit performed by Michael S. Tsirkin of Red Hat, Anthony Liguori and Michael Roth. The issues were discovered as part of the state loading code audit performed by Michael S. Tsirkin of Red Hat, Anthony Liguori and Michael Roth. The issues were discovered as part of the state loading code audit performed by Michael S. Tsirkin of Red Hat, Anthony Liguori and Michael Roth. The issues were discovered as part of the state loading code audit performed by Michael S. Tsirkin of Red Hat, Anthony Liguori and Michael Roth. This issue was discovered by Petr Krempa of Red Hat. This issue was discovered by Alex Jia of Red Hat. This issue was discovered by Peter Portante of Red Hat. These issues were discovered by Gowrishankar Rajaiyan of Red Hat and Kurt Seifried of the Red Hat Security Response Team. Red Hat would like to thank Hannes Frederic Sowa for reporting this issue. Red Hat would like to thank Hannes Frederic Sowa for reporting this issue. Red Hat would like to thank the researcher with the nickname vladz for reporting this issue. This issue was discovered by James Laska of Red Hat. This issue was discovered by Grant Murphy of the Red Hat Product Security Team. This issue was discovered by Marek Hulán of the Red Hat Foreman team. Red Hat would like to thank Kayhan KAYIHAN of Endersys A.Ş. for reporting this issue. Red Hat would like to thank Daniel Lobato of CERN IT-PES-PS for reporting this issue. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Vishvananda Ishaya from Nebula as the original reporter. This issue was discovered by Grant Murphy of the Red Hat Product Security Team. This issue was discovered by Jan Pokorný of Red Hat. This issue was discovered by James Livingston of Red Hat Support Engineering Group. This issue was discovered by Wolf-Dieter Fink of the Red Hat GSS Team. This issue was discovered by Grant Murphy of the Red Hat Product Security Team. This issue was discovered by Grant Murphy of the Red Hat Product Security Team. This issue was found by Florian Weimer of Red Hat Product Security Team. This issue was found by Florian Weimer of Red Hat Product Security Team. This issue was found by Florian Weimer of Red Hat Product Security Team. This issue was found by Florian Weimer of Red Hat Product Security Team. This issue was discovered by Florian Weimer (Red Hat Product Security Team). This issue was found by David Gibson of Red Hat. This issue was discovered by Murray McAllister of the Red Hat Security Response Team. This issue was discovered by Huzaifa Sidhpurwala of the Red Hat Security Response Team. Red Hat would like to thank Ben Reser of the Apache Subversion project for reporting this issue. Upstream acknowledges Ivan Zhakov from VisualSVN as the original issue reporter. This issue was found by Florian Weimer of the Red Hat Product Security Team. This issue was found by Matthew Farrellee of Red Hat. Red Hat would like to thank Michael Scherer for reporting this issue. Red Hat would like to thank Michael Scherer for reporting this issue. This issue was discovered by Jaroslav Henner of Red Hat. Red Hat would like to thank Ben Reser of the Apache Subversion project for reporting this issue. Upstream acknowledges Daniel Shahaf of Apache Infrastructure as the original issue reporter. This issue was discovered by Miroslav Vadkerti of Red Hat. This issue was discovered by David Jorm of the Red Hat Security Response Team. Red Hat would like to thank Ben Reser of the Apache Subversion project for reporting this issue. Upstream acknowledges Daniel Shahaf of elego Software Solutions GmbH as the original issue reporter. This issue was discovered by Tomas Jamrisko of Red Hat. Red Hat would like to thank Rubygems upstream for reporting this vulnerability. Upstream acknowledges Damir Sharipov as the original reporter. Red Hat would like to thank Sebastian Krahmer of the SUSE Security Team for reporting this issue. Red Hat would like to thank Seth Arnold for reporting this issue. Red Hat would like to thank Seth Arnold for reporting this issue. This issue was discovered by Larry O'Leary of the Red Hat Middleware Support Engineering Group. Red Hat would like to thank Thierry Carrez of OpenStack upstream for reporting this issue. Upstream acknowledges Kieran Spear of University of Melbourne as the original reporter. This issue was discovered by Daniel P. Berrange of Red Hat. Red Hat would like to thank Fujitsu for reporting this issue. Red Hat would like to thank James Bennett of Django for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Thomas Swan of FedEx for reporting this issue. This issue was discovered by Asias He of Red Hat. Red Hat would like to thank Stephan Mueller for reporting this issue. This issue was found by Jason Wang of Red Hat. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. This issue was discovered by Yedidyah Bar David of Red Hat. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. This issue was discovered by Sibiao Luo of Red Hat. This issue was discovered by Dominic Cleal of Red Hat. Red Hat would like to thank the Ruby on Rails project for reporting this issue. Upstream acknowledges Aaron Neyer as the original reporter. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. Red Hat would like to thank the X.Org security team for reporting this issue. Upstream acknowledges Pedro Ribeiro as the original reporter. Red Hat would like to thank Timo Warns for reporting this issue. This issue was discovered by Zhenfang Wang of Red Hat. Red Hat would like to thank Sebastian Krahmer of the SUSE Security Team for reporting this issue. Red Hat would like to thank Werner Koch for reporting this issue. Upstream acknowledges Taylor R Campbell as the original reporter. This issue was discovered by Tomáš Nováčik of the Red Hat MRG Quality Engineering team. This issue was discovered by Tomáš Nováčik of the Red Hat MRG Quality Engineering team. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Stefan Metzmacher and Michael Adam of SerNet as the original reporters of this issue. Red Hat would like to thank the Review Board project for reporting this issue. Upstream acknowledges Frederik Braun from Mozilla as the original reporter. This issue was discovered by Tomáš Nováčik of the Red Hat MRG Quality Engineering team. Red Hat would like to thank Adam Willard and Jose Carlos de Arriba of Foreground Security for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Thomas Sanders of Citrix as the original reporter. This issue was discovered by Michael Scherer of the Red Hat Regional IT team. Red Hat would like to thank Cloud Technology Development Department, Ricoh Company, Ltd. for reporting this issue. Red Hat would like to thank the OpenStack Project for reporting this issue. The OpenStack Project acknowledges Stuart McLaren from HP as the original reporter. Red Hat would like to thank Michael Vishchers from Seven Principles AG for reporting this issue. This issue was discovered by Larry O'Leary of the Red Hat Middleware Support Engineering Group. This issue was discovered by Tomáš Nováčik of the Red Hat MRG Quality Engineering team. Red Hat would like to thank Thierry Carrez of the OpenStack project for reporting this issue. Upstream acknowledges Bernhard M. Wiedemann of SuSE as the original reporter. Red Hat would like to thank Hannes Frederic Sowa for reporting this issue. This issue was discovered by Andrew Spurrier of Red Hat. This issue was discovered by Jan Pokorný of Red Hat. This issue was discovered by Jan Pokorný of Red Hat. Red Hat would like to thank Vladimir Davydov (Parallels) for reporting this issue. This issue was discovered by David Jorm of the Red Hat Security Response Team. The reporter acknowledges Adrian Hayes of Security-Assessment.com as the original reporter of this category of flaw. Red Hat would like to thank Ruby on Rails upstream for reporting this issue. Upstream acknowledges Peter McLarnan as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank David Beer of Adaptive Computer for reporting this issue. Upstream acknowledges Matt Ezell of Oak Ridge National Labs as the original reporter. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Andrew Bartlett as the original reporter. Red Hat would like to thank the Apache Subversion project for reporting this issue. Upstream acknowledges Ben Reser as the original reporter. This issue was discovered by Arun Neelicattu and David Jorm of the Red Hat Security Response Team. The issues were discovered as part of the state loading code audit performed by Michael S. Tsirkin of Red Hat, Anthony Liguori and Michael Roth. The issues were discovered as part of the state loading code audit performed by Michael S. Tsirkin of Red Hat, Anthony Liguori and Michael Roth. The issues were discovered as part of the state loading code audit performed by Michael S. Tsirkin of Red Hat, Anthony Liguori and Michael Roth. The issues were discovered as part of the state loading code audit performed by Michael S. Tsirkin of Red Hat, Anthony Liguori and Michael Roth. The issues were discovered as part of the state loading code audit performed by Michael S. Tsirkin of Red Hat, Anthony Liguori and Michael Roth. The issues were discovered as part of the state loading code audit performed by Michael S. Tsirkin of Red Hat, Anthony Liguori and Michael Roth. This issue was discovered by Michael S. Tsirkin of Red Hat. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich as the original reporter. Red Hat would like to thank the Apache Subversion project for reporting this issue. Upstream acknowledges Philip Martin as the original reporter. Red Hat would like to thank Saran Neti of TELUS Security Labs for reporting this issue. Red Hat would like to thank Albert Smith of OUSD(AT&L) for reporting this issue. Red Hat would like to thank Werner Koch of GnuPG upstream for reporting this issue. Upstream acknowledges Genkin, Shamir, and Tromer as the original reporters. This issue was discovered by Arun Babu Neelicattu of the Red Hat Security Response Team. Red Hat would like to thank Andrew Honig of Google for reporting this issue. Red Hat would like to thank Puppet Labs for reporting this issue. Red Hat would like to thank Puppet Labs for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jesse Ruderman and Christoph Diehl as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Vladimir Vukicevic, Jesse Ruderman, Gary Kwong, and Kannan Vijayan as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jordi Chancel as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Dan Gohman as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ezra Pool as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Byoungyoung Lee as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Cody Crews as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Camilo Viecco as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Pascal Cuoq, Kamil Dudka, and Wan-Teh Chang as the original reporters of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ben Turner, Bobby Holley, Jesse Ruderman, and Christian Holler as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler and Christoph Diehl as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Myk Melez as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Masato Kinugawa as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tyson Smith, Jesse Schwartzentruber and Atte Kettunen as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Daniel Veditz as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Eric Faust as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jesse Schwartzentruber as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Dan Gohman as the original reporter. Red Hat would like to thank Raphael Geissert for reporting these issues during a review for EDF. Red Hat would like to thank Raphael Geissert for reporting these issues during a review for EDF. Red Hat would like to thank Raphael Geissert for reporting these issues during a review for EDF. Red Hat would like to thank Raphael Geissert for reporting these issues during a review for EDF. Red Hat would like to thank Andrew Honig of Google for reporting this issue Red Hat would like to thank Andrew Honig of Google for reporting this issue This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Lars Bull of Google for reporting this issue. Red Hat would like to thank Jeremy Stanley of the OpenStack Project for reporting this issue. Upstream acknowledges Steven Hardy of Red Hat as the original reporter. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. The issues were discovered as part of the state loading code audit performed by Michael S. Tsirkin of Red Hat, Anthony Liguori and Michael Roth. Red Hat would like to thank the Xen project for reporting this issue. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by the Red Hat Security Response Team. Red Hat would like to thank Ruby on Rails upstream for reporting this issue. Upstream acknowledges Toby Hsieh as the original reporter. Red Hat would like to thank Ruby on Rails upstream for reporting this issue. Upstream acknowledges Ankit Gupta as the original reporter. Red Hat would like to thank the Ruby on Rails project for reporting this issue. The Ruby on Rails project acknowledges Sudhir Rao as the original reporter. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. Red Hat would like to thank the OpenStack Project for reporting this issue. Upstream acknowledges Aaron Rosen of VMware as the original reporter. Red Hat would like to thank the PHP project for reporting this issue. Upstream acknowledges Stefan Esser as the original reporter of this issue. Red Hat would like to thank the cURL project for reporting this issue. Upstream acknowledges Marc Deslauriers as the original reporter. Red Hat would like to thank Jeremy Stanley of the OpenStack Project for reporting this issue. Upstream acknowledges Steven Hardy of Red Hat as the original reporter. Red Hat would like to thank Jeremy Stanley of the OpenStack Project for reporting this issue. Upstream acknowledges Steven Hardy of Red Hat as the original reporter. This issue was discovered by Jon Passki of Coverity SRL and Arun Neelicattu of the Red Hat Security Response Team. Red Hat would like to thank Mr Hannes Frederic Sowa for reporting this issue. This issue was discovered by Kashyap Chamarthy of Red Hat. Red Hat would like to thank Michael Samuel of Amcom for reporting this issue. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Martin Kletzander of Red Hat. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Phil Day from HP as the original reporter. This issue was discovered by Adrian Likins of RedHat. This issue was discovered by David Illsley, Ron Gutierrez of Gotham Digital Science, and David Jorm of the Red Hat Security Response Team. Red Hat would like to thank the Debian Project for reporting this issue. The Debian Project acknowledges Florian Sagar as the original reporter. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Noel Power as the original reporter. This issue was discovered by Martin Povolný of Red Hat. This issue was discovered by Florian Weimer and Stephen Gallagher of Red Hat. This issue was discovered by Tomáš Nováčik of the Red Hat MRG Quality Engineering team. Red Hat would like to thank Jon Passki of Coverity SRL for reporting this issue. Red Hat would like to thank Jon Passki of Coverity SRL for reporting this issue. Red Hat would like to thank the X.Org security team for reporting this issue. Red Hat would like to thank Grégory DRAPERI for reporting this issue. The CVE-2013-6468 issue was discovered by Marc Schoenefeld of the Red Hat Security Response Team. Red Hat would like to thank Grégory Draperi for independently reporting this issue. These issues were discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Jaime Breva Ribes as the original reporter of this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Jacob Appelbaum of the Tor Project as the original reporter of this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Daniel Atallah as the original reporter of this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Fabian Yamaguchi and Christian Wressnegger of the University of Goettingen as the original reporters of this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Fabian Yamaguchi and Christian Wressnegger of the University of Goettingen as the original reporters of this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Matt Jones of Volvent as the original reporter of this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Yves Younan and Ryan Pentney of Sourcefire VRT as the original reporters of this issue. Red Hat would like to thank Teguh P. Alko for reporting this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Yves Younan and Pawel Janic of Sourcefire VRT as the original reporters of this issue. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Yves Younan of Sourcefire VRT as the original reporter of this issue. This issue was discovered by Michael Scherer of the Red Hat Regional IT team. This issue was discovered by David Jorm of Red Hat Product Security. This issue was discovered by Jan Pokorny of Red Hat. This issue was discovered by Michael Scherer of Red Hat. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tyson Smith as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Vincent Lefevre as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Sijie Xia as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Fabián Cuchietti and Ateeq ur Rehman Khan as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich as the original reporter. Red Hat would like to thank Raphael Geissert for reporting these issues during a review for EDF. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. Red Hat would like to thank the OpenStack project for reporting this issue. The OpenStack project acknowledges Loganathan Parthipan as the original reporter. Red Hat would like to thank M.Schwarz of resellerdesktop.de for reporting this issue. Red Hat would like to thank Hannes Frederic Sowa for reporting this issue. Red Hat would like to thank Hannes Frederic Sowa for reporting this issue. Red Hat would like to thank Hannes Frederic Sowa for reporting this issue. Red Hat would like to thank Hannes Frederic Sowa for reporting this issue. Red Hat would like to thank Hannes Frederic Sowa for reporting this issue. Red Hat would like to thank Hannes Frederic Sowa for reporting this issue. This issue was discovered by Marian Krcmarik of Red Hat. Red Hat would like to thank George Hedfors of Cybercom Sweden East AB for reporting this issue. Red Hat would like to thank Ben Reser of the Apache Subversion project for reporting this issue. Upstream acknowledges Daniel Shahaf of Apache Infrastructure as the original issue reporter. Red Hat would like to thank Nicholas Bebout for reporting this issue. Red Hat would like to thank CERT/CC for reporting this issue. This issue was discovered by Garth Mollett of the Red Hat Security Response Team. This issue was discovered by David Jorm of the Red Hat Security Response Team. This issue was discovered by David Jorm of the Red Hat Security Response Team. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Josef Cacek of the Red Hat JBoss EAP Quality Engineering team. Red Hat would like to thank the Openstack Project for reporting this issue. Upstream acknowledges Samuel Merritt of SwiftStack as the original reporter. This issue was discovered by Lukas Zapletal of Red Hat. This issue was discovered by Arun Babu Neelicattu of the Red Hat Security Response Team. Red Hat would like to thank the cURL project for reporting this issue. Upstream acknowledges Paras Sethia as the original reporter and Yehezkel Horowitz for discovering the security impact. Red Hat would like to thank Aris Adamantiadis for reporting this issue. This issue was discovered by Stuart Douglas of Red Hat. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Daniel Atallah as the original reporter of this issue. This issue was discovered by Miroslav Lichvar of Red Hat. This issue was discovered by Hui Wang and Lingyan Zhuang of Red Hat. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Eric Blake of the Red Hat libvirt team. This issue was discovered by Hui Wang and Yu Zheng of Red Hat. Red Hat would like to thank Michael Samuel of Amcom for reporting this issue. Red Hat would like to thank Robert Scheck of ETES GmbH for reporting this issue. This issue was discovered by Grant Murphy of the Red Hat Product Security Team. This issue was discovered by Grant Murphy of the Red Hat Product Security Team. This issue was discovered by Grant Murphy of the Red Hat Product Security Team. Red Hat would like to thank Lars Bull of Google for reporting this issue. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Aaron Rosen from VMware as the original reporter. This issue was discovered by Jan Rusnacko of the Red Hat Product Security Team. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Noah Misch as the original reporter. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Andres Freund as the original reporter. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Robert Haas and Andres Freund as the original reporters. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Noah Misch as the original reporter. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Heikki Linnakangas and Noah Misch as the original reporters. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Peter Eisentraut and Jozef Mlich as the original reporters. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Honza Horak and Bruce Momjian as the original reporters. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Noah Misch as the original reporter. Red Hat would like to thank Al Viro for reporting this issue. This issue was discovered by David Jorm of Red Hat Product Security. This issue was discovered by Michael S. Tsirkin of Red Hat. This issue was discovered by Jan Rusnacko of the Red Hat Product Security Team. Red Hat would like to thank Robert Scheck of ETES GmbH for reporting this issue. Red Hat would like to thank the Ruby on Rails Project for reporting this issue. Upstream acknowledges Godfrey Chan as the original reporter. Red Hat would like to thank the Ruby on Rails Project for reporting this issue. Upstream acknowledges Kevin Reintjes as the original reporter. Red Hat would like to thank the Ruby on Rails Project for reporting this issue. Upstream acknowledges Toby Hsieh of SlideShare as the original reporter. Red Hat would like to thank Pierre Carrier of airbnb for reporting this issue. This issue was discovered by Andy Grimm of Red Hat. This issue was discovered by Graeme Colman of Red Hat. This issue was discovered by Jan Rusnacko of the Red Hat Product Security Team. This issue was discovered by Jeremy Choi and Keqin Hong of the Red Hat HSS Pen-Test Team. This issue was discovered by Jeremy Choi and Keqin Hong of the Red Hat HSS Pen-Test Team. This issue was discovered by Nikos Mavrogiannopoulos of the Red Hat Security Technologies Team. This issue was discovered by Josef Cacek of the Red Hat JBoss EAP Quality Engineering team. This issue was discovered by Nikolay Aleksandrov of Red Hat. Red Hat would like to thank Nokia Siemens Networks for reporting this issue. Red Hat would like to thank Michael Samuel for reporting this issue. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Kieran Spear from the University of Melbourne as the original reporter. Red Hat would like to thank Todd C. Miller for reporting this issue. Upstream acknowledges Sebastien Macke as the original reporter. This issue was discovered by David Jorm of the Red Hat Security Response Team. This issue was discovered by David Jorm of the Red Hat Security Response Team. Red Hat would like to thank the Squid project for reporting this issue. Upstream acknowledges Mathias Fischer and Fabian Hugelshofer from Open Systems AG as the original reporters. This issue was discovered by Michael S. Tsirkin of Red Hat. Red Hat would like to thank the OpenStack Project for reporting this issue. Upstream acknowledges Stanislaw Pitucha from Hewlett Packard as the original reporter. This issue was discovered by Jan Rusnacko of Red Hat Product Security. This issue was discovered by Jan Rusnacko of the Red Hat Product Security Team. Red Hat would like to thank the cURL project for reporting this issue. Upstream acknowledges Steve Holme as the original reporter. Red Hat would like to thank the cURL project for reporting this issue. Upstream acknowledges Richard Moore from Westpoint Ltd. as the original reporter. This issue was discovered by Jan Rusnacko of Red Hat Product Security. These issues were discovered by Kevin Wolf of Red Hat Inc. These issues were discovered by Kevin Wolf and Stefan Hajnoczi of Red Hat Inc. These issues were discovered by Fam Zheng, Jeff Cody, Kevin Wolf and Stefan Hajnoczi of Red Hat Inc. These issues were discovered by Stefan Hajnoczi of Red Hat Inc. This issue was discovered by Kevin Wolf of Red Hat Inc. These issues were discovered by Kevin Wolf of Red Hat Inc. This issue was discovered by Jeff Cody of Red Hat Inc. This issue was discovered by Michael S. Tsirkin of Red Hat. This issue was discovered by Red Hat. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Cristian Fiorentino from Intel as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Neel Mehta of Google Security as the original reporter. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Paul McMillan (Nebula) as the original reporter. This issue was discovered by Jeremy Choi of the Red Hat Quality Engineering Group. Red Hat would like to thank the Openstack Project for reporting this issue. Upstream acknowledges Marc Heckmann of Ubisoft as the original reporter. This issue was discovered by Ondrej Lukas of the Red Hat JBoss EAP Quality Engineering team. This issue was discovered by David Jorm of Red Hat Product Security. This issue was discovered by David Jorm of Red Hat Product Security. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. This issue was discovered by Stanislav Graf of Red Hat. This issue was discovered by Martin Povolny of Red Hat. Red Hat would like to thank the Samba project for reporting this issue. The Samba project acknowledges Christof Schmitt as the original reporter. Red Hat would like to thank the upstream Libvirt project for reporting this issue. Upstream acknowledges Daniel P. Berrange and Richard Jones as the original reporters. This issue was discovered by Jan Rusnacko of the Red Hat Product Security Team. Red Hat would like to thank Andy Lutomirski for reporting this issue. The issues were discovered as part of the state loading code audit performed by Michael S. Tsirkin of Red Hat, Anthony Liguori and Michael Roth. This issue was discovered by Jan Hutar of Red Hat. Red Hat would like to thank Christian Hoffmann for reporting this issue. Red Hat would like to thank Sal Castiglione for reporting this issue. This issue was discovered by Daniel P. Berrange of Red Hat. Red Hat would like to thank James Roper of Typesafe for reporting this issue. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Jüri Aedla as the original reporter of this issue. This issue was discovered by Red Hat. This issue was discovered by Red Hat. This issue was discovered by Red Hat. This issue was discovered by Red Hat. Red Hat would like to thank Vladimir Davydov of Parallels for reporting this issue. Red Hat would like to thank the Openstack project for reporting this issue. Upstream acknowledges Michael Stancampiano of IBM as the original reporter. The security impact of this issue was discovered by Mateusz Guzik of Red Hat. This issue was discovered by Mateusz Guzik of Red Hat. This issue was discovered by Francisco Alonso of Red Hat Product Security. This issue was discovered by Jan Hutař of Red Hat. Red Hat would like to thank the X.org project for reporting this issue. Upstream acknowledges Ilja van Sprundel as the original reporter of this issue. Red Hat would like to thank the X.org project for reporting this issue. Upstream acknowledges Ilja van Sprundel as the original reporter of this issue. Red Hat would like to thank the X.org project for reporting this issue. Upstream acknowledges Ilja van Sprundel as the original reporter of this issue. This issue was discovered by Frantisek Reznicek of Red Hat. This issue was discovered by David Jorm of Red Hat Product Security. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Imre Rad of Search-Lab as the original reporter of this issue. Red Hat would like to thank NSA for reporting this issue. Red Hat would like to thank NSA for reporting this issue. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges KIKUCHI Masashi of Lepidum as the original reporter of this issue. This issue was discovered by Jeremy Choi of the Red Hat HSS Pen-test Team. This issue was discovered by Kurt Seifried of the Red Hat Security Response Team. This issue was discovered by Francisco Alonso of the Red Hat Security Response Team. This issue was discovered by Francisco Alonso of Red Hat Product Security. This issue was discovered by Francisco Alonso of Red Hat Product Security. Red Hat would like to thank Graham Dumpleton for reporting of this issue. Upstream acknowledges Róbert Kisteleki as the original reporter. Red Hat would like to thank Graham Dumpleton for reporting of this issue. Upstream acknowledges Buck Golemon as the original issue reporter. Red Hat would like to thank LSE Leading Security Experts GmbH for reporting this issue. Red Hat would like to thank Daniel Berteaud of FIREWALL-SERVICES SARL for reporting this issue. Red Hat would like to thank Dolev Farhi of F5 Networks for reporting this issue. This issue was discovered by Marek Schmidt of Red Hat. This issue was discovered by Arpit Tolani of Red Hat, with the security implications raised by Stephen Gallagher of Red Hat. Red Hat would like to thank the upstream Django project for reporting this issue. Upstream acknowledges Benjamin Bach as the original reporter. Red Hat would like to thank the upstream Django project for reporting this issue. Upstream acknowledges Paul McMillan as the original reporter. Red Hat would like to thank the upstream Django project for reporting this issue. Upstream acknowledges the Ruby on Rails team, and specifically Michael Koziarski, as the original reporters. Red Hat would like to thank Stephane Chazelas for reporting this issue. Red Hat would like to thank Thomas Stangner for reporting this issue. Red Hat would like to thank the upstream Django project for reporting this issue. Upstream acknowledges Florian Apolloner as the original reporter. Red Hat would like to thank the upstream Django project for reporting this issue. Upstream acknowledges David Wilson as the original reporter. Red Hat would like to thank the upstream Django project for reporting this issue. Upstream acknowledges David Greisen as the original reporter. Red Hat would like to thank the upstream Django project for reporting this issue. Upstream acknowledges Collin Anderson as the original reporter. Red Hat would like to thank Nikolaus Rath for reporting this issue. Red Hat would like to thank Tester Red (ACME) for reporting this issue. Upstream acknowledges Tester Bluö as the original reporter. Red Hat would like to thank the upstream Django project for reporting this issue. Upstream acknowledges Michael Nelson, Natalia Bidart, and James Westby as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Terrence Cole, Jesse Ruderman, Gary Kwong, Eric Rescorla, Jonathan Kew, Dan Gohman, Ryan VanderMeulen, and Sotaro Ikeda as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gary Kwong, Christian Holler, Jesse Ruderman, Carsten Book, Andrew Sutherland, Byron Campen, Nicholas Nethercote, Paul Adenot, David Baron, Julian Seward, and Dan Gohman as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Cody Crews as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jordi Chancel as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Boris Zbarsky as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Fredrik "Flonka" Lönnqvist as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jordan Milne as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Frederik Braun as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Arthur Gerkis as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Masato Kinugawa as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Soeren Balko as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Yazan Tommalieh as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Brian Smith as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Antoine Delignat-Lavaud and Karthikeyan Bhargavan as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Benoit Jacob, Olli Pettay, Jan Varga, Jan de Mooij, Jesse Ruderman, Dan Gohman, and Christoph Diehl as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gregor Wagner, Olli Pettay, Gary Kwong, Jesse Ruderman, Luke Wagner, Rob Fletcher, and Makoto Kato as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Ash as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges David Keeler as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ehsan Akhgari as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tim Philipp Schäfers and Sebastian Neef as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jeff Gilbert as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nicolas Golubovic as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Robert O'Callahan as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tyson Smith and Jesse Schwartzentruber as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges John Thomson as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security research firm VUPEN as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jüri Aedla as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges George Hotz as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bobby Holley, Carsten Book, Christoph Diehl, Gary Kwong, Jan de Mooij, Jesse Ruderman, Nathan Froyd, and Christian Holler as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher Ash as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Boris Zbarsky as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jukka Jylänki as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges moz_bug_r_a4 as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tyson Smith and Jesse Schwartzentruber of the BlackBerry Security Automated Analysis Team as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gary Kwong, Christoph Diehl, Christian Holler, Hannes Verschore, Jan de Mooij, Ryan VanderMeulen, Jeff Walden, and Kyle Huey as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gary Kwong, Jesse Ruderman, Christian Holler, Gregor Wagner, Benoit Jacob, Karl Tomlinson, and Jeff Walden as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tyson Smith and Jesse Schwartzentruber as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Looben Yang as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tyson Smith and Jesse Schwartzentruber as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, David Keeler and Byron Campen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Gary Kwong, Jesse Ruderman, Andrew McCreight, Alon Zakai, Bobby Holley, Jonathan Watt, Shu-yu Guo, Steve Fink, and Terrence Cole as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Boris Zbarsky as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Jan de Mooij, Karl Tomlinson, Randell Jesup, Gary Kwong, Jesse Ruderman, JW Wang, Gary Kwong, Christian Holler, and David Weir as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Jan de Mooij, Karl Tomlinson, Randell Jesup, Gary Kwong, Jesse Ruderman, JW Wang, Gary Kwong, Christian Holler, and David Weir as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jethro Beekman as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Patrick Cozzi as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mozilla community member John as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges David Chan and Gijs Kruitbosch as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jan de Mooij as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Michal Zalewski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges regenrecht as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Antoine Delignat-Lavaud and Intel Product Security Incident Response Team as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bobby Holley, Christian Holler, David Bolter, Byron Campen, and Jon Coppeard as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Carsten Book, Christian Holler, Martijn Wargers, Shih-Chiang Chien, Terrence Cole, Eric Rahm , and Jeff Walden as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Michal Zalewski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges regenrecht as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Patrick McManus and David Keeler as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Boris Zbarsky as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Patrick McManus and David Keeler as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Eric Shepherd and Jan-Ivar Bruaroey as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Eric Shepherd and Jan-Ivar Bruaroey as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gary Kwong, Randell Jesup, Nils Ohlmeier, Jesse Ruderman, and Max Jonas Werner as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Gary Kwong, Jon Coppeard, Eric Rahm, Byron Campen, Eric Rescorla, and Xidorn Quan as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Cody Crews as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Joe Vennix as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Muneaki Nishimura as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Berend-Jan Wever as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Boris Zbarsky as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. This issue was discovered by Daniel Borkmann of Red Hat Inc. Red Hat would like to thank Matthew Daley for reporting these issues. Red Hat would like to thank Matthew Daley for reporting these issues. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Fabián Cuchietti and Ateeq ur Rehman Khan as the original reporter. Red Hat would like to thank the strongSwan project for reporting this issue. This issue was discovered by the Red Hat Security Response Team. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges Ivan Fratric of the Google Security Team as the original reporter. This issue was discovered by Jaroslav Henner of Red Hat. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Török Edwin for discovering this bug. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Heikki Linnakangas and Noah Misch as the original reporters. Red Hat would like to thank the CERT Coordination Center (CERT/CC) for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Kees Cook of Google for reporting this issue. Google acknowledges Pinkie Pie as the original reporter. Red Hat would like to thank Andy Lutomirski for reporting this issue. Red Hat would like to thank Puppet Labs for reporting this issue. Upstream acknowledges Dennis Rowe (shr3kst3r) as the original reporter. Red Hat would like to thank Puppet Labs for reporting this issue. This issue was discovered as part of the state loading QEMU audit performed by Michael S. Tsirkin of Red Hat, Anthony Liguori, and Michael Roth. This issue was discovered by Tomas Kyjovsky of the Red Hat Quality Engineering Team. Red Hat would like to thank GnuTLS upstream for reporting this issue. Red Hat would like to thank GnuTLS upstream for reporting this issue. Upstream acknowledges Joonas Kuorilehto of Codenomicon as the original reporter. Red Hat would like to thank GnuTLS upstream for reporting this issue. Red Hat would like to thank GnuTLS upstream for reporting this issue. Red Hat would like to thank GnuTLS upstream for reporting this issue. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Felix Gröbert and Ivan Fratrić of Google as the original reporters of this issue. Red Hat would like to thank CA Technologies for reporting this issue. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Jason Hullinger from Hewlett Packard as the original reporter. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Craig Lorentzen from Cisco as the original reporter. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Michael Xin from Rackspace as the original reporter. This issue was discovered by Steven Hardy of Red Hat. Red Hat would like to thank D-Bus upstream for reporting this issue. Upstream acknowledges Alban Crequy of Collabora Ltd. as the original reporter. This issue was discovered by Francisco Alonso of Red Hat Product Security. This issue was discovered by Francisco Alonso of Red Hat Product Security. This issue was discovered by Francisco Alonso of Red Hat Product Security. This issue was discovered by the Red Hat JBoss Enterprise Application Platform QE team. Red Hat would like to thank the Ruby on Rails project for reporting this issue. Upstream acknowledges Sean Griffin of thoughtbot as the original reporter. Red Hat would like to thank the Ruby on Rails project for reporting this issue. Upstream acknowledges Sean Griffin of thoughtbot as the original reporter. This issue was discovered by David Jorm of Red Hat Product Security. This issue was discovered by Kurt Seifried of Red Hat Product Security. This issue was discovered by Francisco Alonso of Red Hat Product Security. Red Hat would like to thank Laurentiu Luca for reporting this issue. This issue was discovered by David Jorm of Red Hat Product Security. This issue was discovered by Dominic Cleal of Red Hat. Red Hat would like to thank the Samba project for reporting this issue. The Samba project acknowledges Simon Arlott as the original reporter. This issue was discovered by Eric Christensen of Red Hat Product Security. This issue was discovered by Jeremy Choi of the Red Hat HSS Pen-test Team. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges the Globo.com Security Team as the original reporter. This issue was discovered by Michael Scherer (Red Hat). Red Hat would like to thank Jon Stanley for reporting this issue. Red Hat would like to thank the Subversion project for reporting this issue. Upstream acknowledges Ben Reser of WANdisco as the original reporter. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Alex Gaynor from Rackspace as the original reporter. Red Hat would like to thank Harun ESUR of Sceptive for reporting this issue. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Jamie Lennox from Red Hat as the original reporter. This issue was discovered by Radek Steiger of Red Hat. Red Hat would like to thank the Subversion project for reporting this issue. Upstream acknowledges Ben Reser of WANdisco as the original reporter. Red Hat would like to thank Alexander Papadakis for reporting this issue. Red Hat would like to thank D-Bus upstream for reporting this issue. Upstream acknowledges Alban Crequy of Collabora Ltd. as the original reporter. Red Hat would like to thank D-Bus upstream for reporting this issue. Red Hat would like to thank Martin Schwidefsky of IBM for reporting this issue. This issue was discovered by Carsten Clasohm of Red Hat. This issue was discovered by Francisco Alonso of the Red Hat Security Response Team. This issue was discovered by Jan Kaluža (Red Hat Web Stack Team). Red Hat would like to thank Andrew Ayer for reporting this issue. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Liping Mao from Cisco as the original reporter. This issue was discovered by Idan Shaby and Allon Mureinik of Red Hat. This issue was discovered by David Jorm of Red Hat Product Security. This issue was discovered by Ludwig Krispenz of Red Hat. Red Hat would like to thank Tomáš Trnka for reporting this issue. This issue was discovered by Arun Babu Neelicattu of Red Hat Product Security. Red Hat would like to thank Georgi Geshev of MWR Labs for reporting this issue. Red Hat would like to thank the Subversion project for reporting this issue. Upstream acknowledges Evgeny Kotkov of VisualSVN as the original reporter. This issue was discovered by Juraj Marko of the Red Hat QE Team. Red Hat would like to thank Andrew Drake of Dropbox for reporting this issue. This issue was discovered by Jan Hutař of Red Hat. This issue was discovered by Jan Pokorný of Red Hat. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Dennis Felsch and Mario Heiderich from the Horst Görtz Institute for IT-Security, Ruhr-University Bochum as the original reporters. Red Hat would like to thank Ron Bowes of Google for reporting this issue. This issue was discovered by David Jorm and Arun Neelicattu of Red Hat Product Security. This issue was discovered by David Kutálek of Red Hat BaseOS QE. Red Hat would like to thank Andrew Drake of Dropbox for reporting this issue. Red Hat would like to thank Georgi Geshev of MWR Labs for reporting this issue. Red Hat would like to thank Georgi Geshev of MWR Labs for reporting this issue. Red Hat would like to thank Jack Morgenstein of Mellanox for reporting this issue; the security impact of this issue was discovered by Michael Tsirkin of Red Hat. This issue was discovered by Arun Babu Neelicattu of Red Hat Product Security. This issue was discovered by Francisco Alonso of Red Hat Product Security. This issue was discovered by Garth Mollett of Red Hat Product Security. Red Hat would like to thank the Squid project for reporting this issue. Upstream acknowledges Matthew Daley as the original reporter. Red Hat would like to thank Lars Bull of Google and Nadav Amit for reporting this issue. Red Hat would like to thank Lars Bull of Google for reporting this issue. Red Hat would like to thank Georgi Geshev of MWR Labs for reporting this issue. Red Hat would like to thank the cURL project for reporting this issue. Upstream acknowledges Tim Ruehsen as the original reporter. This issue was discovered by Laszlo Ersek of Red Hat. Red Hat would like to thank qinghao tang of Qihoo 360 Technology for reporting this issue. Red Hat would like to thank the cURL project for reporting these issues. Upstream acknowledges Tim Ruehsen as the original reporter. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Brant Knudson from IBM as the original reporter. Red Hat would like to thank Frey Alfredsson for reporting this issue. This issue was discovered by Luyao Huang of Red Hat. Red Hat would like to thank Rainer Gerhards of rsyslog upstream for reporting this issue. Red Hat would like to thank D-Bus upstream for reporting this issue. Upstream acknowledges Simon McVittie as the original reporter. Red Hat would like to thank D-Bus upstream for reporting this issue. Upstream acknowledges Alban Crequy as the original reporter. Red Hat would like to thank D-Bus upstream for reporting this issue. Upstream acknowledges Alban Crequy as the original reporter. Red Hat would like to thank D-Bus upstream for reporting this issue. Upstream acknowledges Alban Crequy as the original reporter. Red Hat would like to thank D-Bus upstream for reporting this issue. Upstream acknowledges Alban Crequy as the original reporter. Red Hat would like to thank Xavier Mehrenberger and Stephane Duverger of Airbus for reporting this issue. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Duncan Thomas from Hewlett Packard as the original reporter. This issue was discovered by Jan Rusnacko of Red Hat Product Security. Red Hat would like to thank the Advanced Threat Research team at Intel Security for reporting this issue. Red Hat would like to thank the Advanced Threat Research team at Intel Security for reporting this issue. Red Hat would like to thank Nadav Amit for reporting this issue. This issue was discovered by Jan Rusnacko and Trevor Jay of Red Hat Product Security. This issue was discovered by Florian Weimer of Red Hat Product Security. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank Ron Bowes of Google for reporting this issue. This issue was discovered by Florian Weimer of Red Hat Product Security. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Daniel Beck as the original reporter. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Daniel Beck as the original reporter. Red Hat would like to thank the Jenkins project for reporting these issues. Upstream acknowledges Daniel Beck as the original reporter. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Jesse Glick as the original reporter. Red Hat would like to thank the Jenkins project for reporting this issue. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Stephen Connolly as the original reporter. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Jesse Glick as the original reporter. This issue was discovered by Liu Wei of Red Hat. Red Hat would like to thank the SUSE Security Team for reporting this issue. Red Hat would like to thank the SUSE Security Team for reporting this issue. Red Hat would like to thank the SUSE Security Team for reporting this issue. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Wilder Rodrigues as the original reporter. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Wilder Rodrigues as the original reporter. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Matthias Schmalz as the original reporter. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Seth Graham as the original reporter. This issue was discovered by David Jorm of Red Hat Product Security. Red Hat would like to thank the rsyslog upstream for reporting this issue. Upstream acknowledges mancha as the original reporter. Red Hat would like to thank Jouni Malinen for reporting this issue. Red Hat would like to thank the Advanced Threat Research team at Intel Security for reporting this issue. Red Hat would like to thank Andy Lutomirski for reporting this issue. This issue was discovered by the Red Hat CloudForms Team. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Jacob Appelbaum and Moxie Marlinspike as the original reporters. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Yves Younan (Cisco Talos) and Richard Johnson (Cisco Talos) as the original reporters. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Yves Younan (Cisco Talos) and Richard Johnson (Cisco Talos) as the original reporters. Red Hat would like to thank the Pidgin project for reporting this issue. Upstream acknowledges Thijs Alkemade and Paul Aurich as the original reporters. This issue was discovered by Kurt Seifried of Red Hat Product Security. This issue was discovered by Andrew Griffiths of Red Hat Product Security. This issue was discovered by Kurt Seifried of Red Hat Product Security. This issue was discovered by Andrew Griffiths of Red Hat Product Security. This issue was discovered by Yair Fried of Red Hat. Red Hat would like to thank the cURL project for reporting this issue. Upstream acknowledges Symeon Paraschoudis as the original reporter. Red Hat would like to thank the OpenStack Project for reporting this issue. Upstream acknowledges Mohammed Naser from Vexxhost as the original reporter. This issue was discovered by Florian Weimer of Red Hat Product Security. This issue was discovered by Francisco Alonso (Red Hat Product Security). This issue was discovered by Jan Rusnacko of Red Hat Product Security. Red Hat would like to thank the upstream Django project for reporting this issue. Upstream acknowledges Peter Kuma and Gavin Wahl as the original reporters. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich as the original reporter. Red Hat would like to thank David Reid, Alex Gaynor, and Glyph Lefkowitz from Rackspace for reporting this issue. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank the Ricardo Signes for reporting this issue. Upstream acknowledges Markus Vervier of LSE Leading Security Experts as the original reporter. Red Hat would like to thank Don A. Bailey from Lab Mouse Security for reporting this issue. Red Hat would like to thank Don A. Bailey from Lab Mouse Security for reporting this issue. Red Hat would like to thank Gopal Reddy Kodudula of Nokia Siemens Networks for reporting this issue. Red Hat would like to thank Andy Lutomirski for reporting this issue. Red Hat would like to thank the GNU Wget project for reporting this issue. Upstream acknowledges HD Moore of Rapid7, Inc as the original reporter. Red Hat would like to thank Sasha Levin for reporting this issue. Red Hat would like to thank Vasily Averin of Parallels for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the upstream Libvirt project for reporting this issue. Upstream acknowledges Daniel P. Berrange and Richard Jones as the original reporters. Red Hat would like to thank Mischa Salle and Wilco Baan Hofman of Nikhef for reporting this issue. Red Hat would like to thank Mischa Salle and Wilco Baan Hofman of Nikhef for reporting this issue. Red Hat would like to thank the MIT Kerberos project for reporting this issue. The MIT Kerberos project acknowledges Nico Williams for assisting with the analysis of CVE-2014-5352. Red Hat would like to thank Michael S. Tsirkin for reporting this issue. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges Nicolas RUFF as the original reporter. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges Nicolas RUFF as the original reporter. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges Nicolas RUFF as the original reporter. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges Nicolas RUFF as the original reporter. Red Hat would like to thank oCERT for reporting these issues. oCERT acknowledges Nicolas RUFF as the original reporter. Red Hat would like to thank the Xen for reporting this issue. Xen acknowledges Vitaly Kuznetsov from Red Hat as the original reporter of this issue and David Vrabel of Citrix as the one who diagnosed this issue as having security repercussions. Red Hat would like to thank Stephane Chazelas for reporting this issue. Red Hat would like to thank Nick Mathewson of Libevent upstream for reporting this issue. Upstream acknowledges Andrew Bartlett of Catalyst as the original reporter. Red Hat would like to thank the Docker project for reporting these issues. Upstream acknowledges Florian Weimer of Red Hat Product Security and independent researcher Tõnis Tiigi as the original reporters. Red Hat would like to thank the Docker project for reporting this issue. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank the Xen for reporting this issue. Red Hat would like to thank the Xen for reporting this issue. Red Hat would like to thank the Xen for reporting this issue. This issue was discovered by Florian Weimer of Red Hat Product Security. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank the Xen for reporting this issue. Red Hat would like to thank Mickaël Gallier for reporting this issue. Red Hat would like to thank Mickaël Gallier for reporting this issue. This issue was discovered by Aaron Patterson of the Red CloudForms Team. This issue was discovered by the Red Hat CloudForms Team. Red Hat would like to thank James Spadaro of Cisco for reporting this issue. Red Hat would like to thank Roberto Soares of Conviso Application Security for reporting this issue. This issue was discovered by Tim Waugh of the Red Hat Developer Experience Team. Red Hat would like to thank the Ruby on Rails project for reporting this issue. Upstream acknowledges Eaden McKee, Dennis Hackethal & Christian Hansen of Crowdcurity, Juan C. Müller & Mike McClurg of Greenhouse.io, and Alex Ianus of Coinbase as the independent, original reporters. Red Hat would like to thank the Ruby on Rails project for reporting this issue. Upstream acknowledges Eaden McKee, Dennis Hackethal & Christian Hansen of Crowdcurity, Juan C. Müller & Mike McClurg of Greenhouse.io , and Alex Ianus of Coinbase as the independent, original reporters. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Henry Yamauchi, Charles Neill and Michael Xin (Rackspace) as the original reporters. Red Hat would like to thank Akira Fujita of NEC for reporting this issue. This issue was discovered by Eric Blake of Red Hat. Red Hat would like to thank Robert Święcki for reporting these issues. Red Hat would like to thank Robert Święcki for reporting these issues. This issue was discovered by Ondra Lukas of the Red Hat Quality Engineering Team. Red Hat would like to thank FreeIPA upstream for reporting this issue. Red Hat would like to thank the Ruby on Rails project for reporting this issue. Upstream acknowledges Behrouz Sadeghipour, Patrick Toomey of GitHub, and Remon Oldenbeuving of hackerone as the original, independent reporters. This issue was discovered by Michael S. Tsirkin of Red Hat. This issue was discovered by Liu Wei of Red Hat. Red Hat would like to thank Nadav Amit for reporting this issue. This issue was discovered by Miloš Prchlík of Red Hat. This issue was discovered by Darran Lofthouse of the Red Hat JBoss Enterprise Application Platform Team. This issue was discovered by Darran Lofthouse of the Red Hat JBoss Enterprise Application Platform Team. This issue was discovered by Red Hat Product Security. Red Hat would like to thank the OpenVPN project for reporting this issue. Upstream acknowledges Dragana Damjanovic as the original reporter. This issue was discovered by Petr Špaček of the Red Hat Identity Management Engineering Team. This issue was discovered by Paolo Bonzini of Red Hat. Red Hat would like to thank the Subversion project for reporting this issue. Upstream acknowledges Evgeny Kotkov of VisualSVN as the original reporter. This issue was discovered by Ludwig Krispenz of the Red Hat Identity Management Engineering Team. Red Hat would like to thank David Jorm for reporting this issue. Red Hat would like to thank David Jorm for reporting this issue. Red Hat would like to thank Thomas Jarosch (Intra2net AG) for reporting this issue. Red Hat would like to thank Thomas Jarosch (Intra2net AG) for reporting this issue. This issue was discovered by Florian Weimer of Red Hat Product Security. This issue was discovered by Hao Liu of Red Hat. This issue was discovered by Elliott Baron of Red Hat. This issue was discovered by Robin Hack of Red Hat. Red Hat would like to thank Rune Steinseth of JProfessionals for reporting this issue. Red Hat would like to thank Fabian Keil for reporting this issue. Red Hat would like to thank the OpenStack Project for reporting this issue. Upstream acknowledges Eric Peterson from Time Warner Cable as the original reporter. This issue was discovered by Jeremy Lindop of Red Hat. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank Andy Lutomirski for reporting this issue. Red Hat would like to thank Andy Lutomirski for reporting this issue. Red Hat would like to thank oCERT for reporting these issues. oCERT acknowledges Jose Duart of the Google Security Team as the original reporter. Red Hat would like to thank oCERT for reporting these issues. oCERT acknowledges Jose Duart of the Google Security Team as the original reporter. Red Hat would like to thank oCERT for reporting these issues. oCERT acknowledges Michele Spagnuolo of the Google Security Team as the original reporter. Red Hat would like to thank oCERT for reporting these issues. oCERT acknowledges Michele Spagnuolo of the Google Security Team as the original reporter. Red Hat would like to thank oCERT for reporting these issues. oCERT acknowledges Michele Spagnuolo of the Google Security Team as the original reporter. Red Hat would like to thank the Samba Team for reporting this issue. Upstream acknowledges Andrew Bartlett of Catalyst IT as the original reporter. Red Hat would like to thank oCERT for reporting these issues. oCERT acknowledges Michele Spagnuolo of the Google Security Team as the original reporter. Red Hat would like to thank the cURL project for reporting this issue. Upstream acknowledges Andrey Labunets of Facebook as the original reporter. Red Hat would like to thank the curl project for reporting this issue. Upstream acknowledges Marc Hesse of RethinkDB as the original reporter. This issue was discovered by Marcel Kolaja of Red Hat. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges pyddeh as the original reporter. Red Hat would like to thank oCERT for reporting this issue. oCERT acknowledges pyddeh as the original reporter. Red Hat would like to thank Mellanox for reporting this issue. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Stephen Frost as the original reporter. Red Hat would like to thank Travis Emmert for reporting this issue. Red Hat would like to thank Travis Emmert for reporting this issue. This issue was discovered by Dhiru Kholia of Red Hat Product Security. Red Hat would like to thank the Georgia Institute of Technology for reporting this issue. This issue was reported by Jay Kumar SenSharma of Red Hat. Red Hat would like to thank the OpenSSL project for reporting this issue. This issue was discovered by Fam Zheng (Red Hat). This issue was discovered by Matt Rogers of Red Hat. This issue was discovered by Eric Helms (Red Hat). This issue was discovered by Raphael Sanchez Prudencio (Red Hat). Red Hat would like to thank Intel for reporting these issues. Upstream acknowledges Rafal Wojtczuk, Bromium and Corey Kallenberg, MITRE, as the original reporters. Red Hat would like to thank Nadav Amit and Andy Lutomirski for reporting this issue. Red Hat would like to thank Nadav Amit and Andy Lutomirski for reporting this issue. Red Hat would like to thank GnuTLS upstream for reporting this issue. Upstream acknowledges Sean Burford as the original reporter. Red Hat would like to thank the mod_auth_mellon team for reporting this issue. Upstream acknowledges Matthew Slowe as the original reporter. Red Hat would like to thank the mod_auth_mellon team for reporting this issue. Red Hat would like to thank the Xen for reporting this issue. Red Hat would like to thank the Xen for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bobby Holley as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bobby Holley as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler and Patrick McManus as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christoph Diehl, Christian Holler, Gary Kwong, Jesse Ruderman, Byron Campen, Terrence Cole, and Nils Ohlmeier as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bobby Holley as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Michal Zalewski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Muneaki Nishimura as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Xiaofeng Zheng as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mitchell Harper as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Brian Smith as the original reporter. Red Hat would like to thank the Xen for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank oCERT for reporting these issues. oCERT acknowledges Jose Duart of the Google Security Team as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the strongSwan developers for reporting this issue. Upstream acknowledges Mike Daskalakis as the original reporter. Red Hat would like to thank Mahmoud Al-Qudsi of NeoSmart Technologies for reporting this issue. Red Hat would like to thank Andy Lutomirski for reporting this issue. Red Hat would like to thank Docker Inc. for reporting this issue. Red Hat would like to thank Docker Inc. for reporting this issue. Red Hat would like to thank Docker Inc. for reporting this issue. Red Hat would like to thank Carl Henrik Lunde for reporting this issue. Red Hat would like to thank the MIT Kerberos project for reporting this issue. Red Hat would like to thank the MIT Kerberos project for reporting this issue. Red Hat would like to thank the MIT Kerberos project for reporting this issue. Red Hat would like to thank Robert Scheck of the Fedora Project for reporting this issue. Red Hat would like to thank Carl Henrik Lunde for reporting this issue. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Tushar Patil of NTT as the original reporter. Red Hat would like to thank Yann Rouillard for reporting this issue. Red Hat would like to thank Yann Rouillard for reporting this issue. This issue was discovered by Alexandre Oliva of Red Hat Inc. Red Hat would like to thank Nathan Hoad for reporting this issue. Red Hat would like to thank Carl H Lunde for reporting this issue Red Hat would like to thank Carl H Lunde for reporting this issue Red Hat would like to thank Carl H Lunde for reporting this issue Red Hat would like to thank Carl H Lunde for reporting this issue. Red Hat would like to thank the Apache Software Foundation for reporting this issue. Upstream acknowledges Evgeny Kotkov of VisualSVN as the original reporter. Red Hat would like to thank the Apache Software Foundation for reporting this issue. Upstream acknowledges G. Geshev from MWR Labs as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Per Allansson as the original reporters. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Stephen Henson of the OpenSSL development team as the original reporter. Red Hat would like to thank the upstream Django project for reporting this issue. Red Hat would like to thank the upstream Django project for reporting this issue. Red Hat would like to thank the upstream Django project for reporting this issue. Red Hat would like to thank the upstream Django project for reporting this issue. This issue was discovered by Kurt Seifried of Red Hat Product Security. This issue was discovered by Kurt Seifried of Red Hat Product Security. Red Hat would like to thank Qualys for reporting this issue. This issue was found by Luyao Huang of Red Hat. This issue was discovered by Red Hat Enterprise Visualization Engineering. Red Hat would like to thank Marcos for reporting this issue. Red Hat would like to thank Nadav Amit for reporting this issue. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Richard van Eeden of Microsoft Vulnerability Research as the original reporter of this issue. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Andres Freund, Peter Geoghegan, Bernd Helmle, and Noah Misch as the original reporters. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Bruce Momjian as the original reporter. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Marko Tiikkaja as the original reporter. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Emil Lenngren as the original reporter. Red Hat would like to thank oCERT for reporting these issues. oCERT acknowledges Jose Duart of the Google Security Team as the original reporter. Red Hat would like to thank the Apache Software Foundation for reporting this issue. Upstream acknowledges Evgeny Kotkov of VisualSVN as the original reporter. Red Hat would like to thank the Apache Software Foundation for reporting this issue. Upstream acknowledges Evgeny Kotkov of VisualSVN as the original reporter. This issue was discovered by Olivier Fourdan of Red Hat. This issue was discovered by Yedidyah Bar David of the Red Hat Enterprise Virtualization team. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Brian Manifold of Cisco and Paul McMillan of Nebula as the original reporters. This issue was discovered by Harald Hoyer of Red Hat. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Sara Perez Merino of SensePost for reporting this issue. Red Hat would like to thank Eric Windisch of the Docker project for reporting this issue. This issue was discovered by Xiong Zhou of Red Hat. This issue was discovered by Ondrej Kotek of Red Hat. Red Hat would like to thank Takeshi Terada of Mitsui Bussan Secure Directions, Inc. for reporting this issue. This issue was discovered by Nikos Mavrogiannopoulos of the Red Hat Security Technologies Team. This issue was discovered by Sumit Bose of Red Hat. This issue was discovered by Jan Hutař (Red Hat). Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Matt Caswell of the OpenSSL development team as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Stephen Henson of the OpenSSL development team as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Emilia Käsper as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Brian Carpenter as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Michal Zalewski of Google as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Daniel Danner and Rainer Mueller as the original reporters. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges David Ramos of Stanford University as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Robert Dugal and David Ramos as the original reporters. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Sean Burford (Google) and Emilia Käsper (the OpenSSL development team) as the original reporters. This issue was discovered by Nikos Mavrogiannopoulos of the Red Hat Security Technologies Team. Red Hat would like to thank Alessandro Cavaliere for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. This issue was discovered by Red Hat. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Aki Helin as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Muneaki Nishimura as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Olli Pettay and Boris Zbarsky as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bobby Holley as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christoph Kerschbaumer and Muneaki Nishimura as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mitchell Harper as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Felix Gröbert as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Armin Razmdjou as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Aki Helin as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Andrew McCreight, Gary Kwong, Karl Tomlinson, Randell Jesup, Shu-yu Guo, Steve Fink, and Tooru Fujisawa as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Byron Campen, and Steve Fink as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges ilxu1a as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mariusz Mlynski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Matthew Noorenberghe as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Armin Razmdjou as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Armin Razmdjou as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Pantrombka as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Daniele Di Proietto as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Paul Bandha as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Muneaki Nishimura as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Alexander Kolesnik as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Gary Kwong, Jesse Ruderman, Byron Campen, Randell Jesup, Robin Whittleton, Jon Coppeard, and Nikhil Marathe as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Carsten Book, Christoph Diehl, Gary Kwong, Jan de Mooij, Liz Henry, Byron Campen, Tom Schuster, and Ryan VanderMeulen as the original reporter. Red Hat would like to thank the CERT/CC for reporting this issue. Red Hat would like to thank the CERT/CC for reporting this issue. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Jin Liu of EMC as the original reporter. Red Hat would like to thank William Robinet for reporting this issue. Red Hat would like to thank Canonical for reporting this issue. Red Hat would like to thank ISC for reporting this issue. This issue was discovered by Sun Baoliang of Red Hat. This issue was found by Marcelo Ricardo Leitner of Red Hat. Red Hat would like to thank the Xen for reporting this issue. Upstream acknowledges Julien Grall as the original reporter. This issue was discovered by Daniel P. Berrange of Red Hat. This issue was discovered by Arjun Shankar of Red Hat. This issue was discovered by Rob Crittenden of Red Hat. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Matt Caswell of the OpenSSL development team as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Red Hat would like to thank the OpenSSL project for reporting this issue. Red Hat would like to thank the OpenSSL project for reporting this issue. Red Hat would like to thank the OpenSSL project for reporting this issue. Red Hat would like to thank the OpenSSL project for reporting this issue. Red Hat would like to thank OpenSSL upstream for reporting this issue. Upstream acknowledges Adam Langley of Google and David Benjamin of BoringSSL as the original reporters. This issue was discovered by Florian Weimer of Red Hat Product Security. This issue was discovered by Miroslav Lichvár of Red Hat. This issue was discovered by Miroslav Lichvár of Red Hat. The security impact of this issue was discovered by Red Hat. Red Hat would like to thank Sebastian Krahmer of the SUSE Security Team for reporting this issue. Red Hat would like to thank David Jorm of IIX Product Security for reporting this issue. This issue was discovered by Florian Weimer (Red Hat Product Security). This issue was discovered by Miroslav Lichvár of Red Hat. This issue was discovered by Miroslav Lichvár of Red Hat. This issue was discovered by Sumit Bose of Red Hat. Red Hat would like to thank Michael Scherer of Red Hat for reporting this issue. Red Hat would like to thank Michael Scherer of Red Hat for reporting this issue. Red Hat would like to thank the Ruby on Rails project for reporting this issue. This issue was discovered by Einav Cohen or Red Hat. This issue was discovered by Alessandro Vozza of Red Hat. Red Hat would like to thank Eric Windisch of Docker Inc. for reporting this issue. This issue was discovered by Tomas Jelinek of Red Hat. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Brant Knudson from IBM as the original reporter. This issue was discovered by Miroslav Lichvár of Red Hat. This issue was discovered by Simo Sorce of Red Hat. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Clay Gerrard of SwiftStack as the original reporter. Red Hat would like to thank Richard Moore of KDE for reporting this issue. Red Hat would like to thank Richard Moore of KDE for reporting this issue. Red Hat would like to thank Richard Moore of KDE for reporting this issue. Red Hat would like to thank Jouni Malinen of the wpa_supplicant upstream for reporting this issue. Upstream acknowledges Alibaba security team as the original reporter. This issue was discovered by Florian Weimer of Red Hat Product Security. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the upstream Django project for reporting this issue. Red Hat would like to thank the upstream Django project for reporting this issue. Red Hat would like to thank the upstream Django project for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jesse Ruderman, Mats Palmgren, Byron Campen, and Steve Fink as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gary Kwong, Andrew McCreight, Christian Holler, Jesse Ruderman, Mats Palmgren, Jon Coppeard, and Milan Sreckovic as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Alex Verstak as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Dougall Johnson as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Scott Bell as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tyson Smith as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ucha Gobejishvili as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges laf.intel as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mark Hammond as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Karthikeyan Bhargavan as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Looben Yan as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bob Clary, Christian Holler, Bobby Holley, Andrew McCreight, Terrence Cole, Steve Fink, Mats Palmgren, Wes Kocher, and Andreas Pehrson as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bob Clary, Christian Holler, Bobby Holley, Andrew McCreight, Terrence Cole, Steve Fink, Mats Palmgren, Wes Kocher, and Andreas Pehrson as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Tooru Fujisawa, Andrew Sutherland, Andrew McCreight, and Gary Kwong as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jann Horn as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Paul Bandha as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Watson Ladd as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Herre as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Looben Yan as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges David Keeler as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jonas Jenwald as the original reporter. Red Hat would like to thank the Xen for reporting this issue. Red Hat would like to thank the Xen for reporting this issue. Red Hat would like to thank the Xen for reporting this issue. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank Daniel Stenberg (curl upstream) for reporting this issue. Upstream acknowledges Paras Sethia as the original reporter. Red Hat would like to thank Daniel Stenberg (curl upstream) for reporting this issue. Upstream acknowledges Hanno Böck as the original reporter. Red Hat would like to thank Daniel Stenberg (curl upstream) for reporting this issue. Upstream acknowledges Hanno Böck as the original reporter. Red Hat would like to thank the libssh team for reporting this issue. The libssh team acknowledges Mariusz Ziulek from the Open Web Application Security Project (OWASP) as the original reporter. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank Daniel Stenberg (curl upstream) for reporting this issue. Upstream acknowledges Isaac Boukris as the original reporter. This issue was discovered by Florian Weimer of Red Hat Product Security. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank Rufus Järnefelt of Coresec for reporting this issue. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Benkocs Norbert Attila as the original reporter. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Noah Misch as the original reporter. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Noah Misch as the original reporter. Red Hat would like to thank Harsha Vardhan Boppana (@hvboppana) for reporting this issue. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank Grant Murphy for reporting this issue. This issue was discovered by Martin Žember of Red Hat. Red Hat would like to thank Apache Software Foundation for reporting this issue. Upstream acknowledges C. Michael Pilato, CollabNet, as the original reporter. Red Hat would like to thank Apache Software Foundation for reporting this issue. Upstream acknowledges C. Michael Pilato, CollabNet, as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Nimrod Aviram and Sebastian Schinzel as the original reporters. Red Hat would like to thank Jaanus Kääp for reporting this issue. This issue was discovered by the Red Hat Thermostat Team. Red Hat would like to thank Javantea for reporting this issue. Red Hat would like to thank David Jorm of IIX Product Security for reporting this issue. Red Hat would like to thank Matt Tait of Google's Project Zero security team for reporting this issue. Red Hat would like to thank Gena Makhomed for reporting this issue. This issue was discovered by Ji Jianwen of Red Hat Engineering. Red Hat would like to thank Matt Tait of Google's Project Zero security team for reporting this issue. Red Hat would like to thank Google Project Zero for reporting this issue. Red Hat would like to thank the OpenStack Project for reporting this issue. Upstream acknowledges Nikita Konovalov from Mirantis as the original reporter. Red Hat would like to thank the OpenStack upstream for reporting this issue. Upstream acknowledges Darragh O'Reilly (HP) as the original reporter. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Thilo Uttendorfer as the original reporter. Red Hat would like to thank Ruby upstream developers for reporting this. Upstream acknowledges Tomek Rabczak from the NCC Group as the original reporter. Red Hat would like to thank Ruby upstream developers for reporting this issue. Upstream acknowledges Francois Chagnon of Shopify as the original reporter. Red Hat would like to thank the Ruby upstream developers for reporting this issue. Upstream acknowledges Tomek Rabczak from the NCC Group, and Matthew Draper as the original reporters. Red Hat would like to thank William Robinet of Conostix S.A. for reporting this issue. Red Hat would like to thank curl upstream for reporting this issue. Upstream acknowledges Tomas Tomecek and Kamil Dudka as the original reporters. Red Hat would like to thank curl upstream for reporting this issue. Upstream acknowledges Daniel Stenberg as the original reporter. Red Hat would like to thank Sebastien Macke of Trustwave SpiderLabs for reporting this issue. This issue was discovered by Paolo Bonzini of Red Hat. This issue was discovered by Paul Wouters of Red Hat. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges George Shuklin of Webzilla LTD as the original reporter. Red Hat would like to thank Liferay, Inc. for reporting this issue. Red Hat would like to thank Qualys for reporting this issue. Red Hat would like to thank Qualys for reporting this issue. This issue was discovered by Frediano Ziglio of Red Hat. This issue was discovered by Marko Myllynen of Red Hat. This issue was discovered by Petr Sklenar of Red Hat. Red Hat would like to thank the Xen project for reporting this issue. This issue was discovered by Martin Poole of the Red Hat Software Maintenance Engineering group. Red Hat would like to thank Martin Poole of Software Maintenance Engineering group for reporting this issue. Red Hat would like to thank Martin Poole of Software Maintenance Engineering group for reporting this issue. Red Hat would like to thank the OpenStack upstream project for reporting this issue. Upstream acknowledges George Shuklin from Webzilla LTD and Tushar Patil from NTT DATA, Inc. as the original reporters. Red Hat would like to thank Kirill A. Shutemov (Intel) for reporting this issue. Red Hat would like to thank Andy Lutomirski for reporting this issue. Red Hat would like to thank Andy Lutomirski for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Jason Geffner of CrowdStrike for reporting this issue. Red Hat would like to thank Eric Windisch of the Docker project for reporting this issue. Red Hat would like to thank Eric Windisch of the Docker project for reporting this issue. Red Hat would like to thank Eric Windisch of the Docker project for reporting this issue. Red Hat would like to thank Eric Windisch of the Docker project for reporting this issue. Red Hat would like to thank the upstream Django project for reporting this issue. This issue was discovered by Tomas Jelinek of Red Hat. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Carl H Lunde for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gary Kwong, Christian Holler, and Byron Campen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tyson Smith, Bobby Holley, Chris Coulson, Byron Campen, and Eric Rahm as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Aki Helin as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jordi Chancel as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges SkyLined as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges André Bargull as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Massimiliano Tomassoli, laf.intel, Massimiliano Tomassoli and Tyson Smith as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Massimiliano Tomassoli, laf.intel, Massimiliano Tomassoli and Tyson Smith as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Masato Kinugawa as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jukka Jylänki as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christoph Kerschbaumer as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gustavo Grieco as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Looben Yang as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Massimiliano Tomassoli, laf.intel, Massimiliano Tomassoli and Tyson Smith as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Cody Crews as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Joshua Drake as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jean-Max Reymond and Ucha Gobejishvili as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bas Venis as the original reporter. Red Hat would like to thank the Mozilla project for reporting these issues. Upstream acknowledges Andrew Osmond, Olli Pettay, Andrew Sutherland, Christian Holler, David Major, Andrew McCreight, and Cameron McCormack as the original reporters of these issues. Red Hat would like to thank the Mozilla project for reporting these issues. Upstream acknowledges Bob Clary and Randell Jesup as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges André Bargull as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges David Chan as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Felix Gröbert of Google as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Khalil Zhani as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Spandan Veggalam as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Juho Nurminen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Looben Yang as the original reporter of this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Francisco Alonso of the NowSecure Research Team as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, David Major, Jesse Ruderman, Tyson Smith, Boris Zbarsky, Randell Jesup, Olli Pettay, Karl Tomlinson, Jeff Walden, and Gary Kwong as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Andrew McCreight, Georg Fritzsche, Tyson Smith, and Carsten Book as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tim Brown as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jeff Walden as the original reporter. Red Hat would like to thank the Mozilla project for reporting these issues. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mario Heiderich as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mario Gomes as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ehsan Akhgari as the original reporter. Red Hat would like to thank the Mozilla project for reporting these issues. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting these issues. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank ISC for reporting this issue. Red Hat would like to thank Daniel Borkmann for reporting this issue. Red Hat would like to thank Andrea Palazzo of Truel IT for reporting this issue. Red Hat would like to thank the upstream Django project for reporting this issue. Red Hat would like to thank the upstream Django project for reporting this issue. Red Hat would like to thank the upstream Django project for reporting this issue. This issue was discovered by Kevin Wolf of Red Hat. Red Hat would like to thank Qinghao Tang of QIHU 360 for reporting this issue. This issue was discovered by Jason Wang of Red Hat. This issue was discovered by Donghai Zhu of Alibaba. This issue was discovered by Florian Weimer of Red Hat Product Security. This issue was discovered by Richard W.M. Jones (Red Hat). Red Hat would like to thank the OpenStack team for reporting this issue. Upstream acknowledges Eric Harney (Red Hat) as the original reporter. This issue was discovered by Brian Bouterse of Red Hat. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Donghai Zhu of Alibaba as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Donghai Zhu of Alibaba as the original reporter. Red Hat would like to thank Liferay, Inc. for reporting this issue. Red Hat would like to thank Qinghao Tang of QIHU 360 for reporting this issue. This issue was discovered by Florian Weimer (Red Hat Product Security). Red Hat would like to thank Naftali Rosenbaum of Comsec Consulting for reporting this issue. Red Hat would like to thank Naftali Rosenbaum of Comsec Consulting for reporting this issue. Red Hat would like to thank Naftali Rosenbaum of Comsec Consulting for reporting this issue. Red Hat would like to thank Naftali Rosenbaum of Comsec Consulting for reporting this issue. Red Hat would like to thank Qinghao Tang (QIHU 360) for reporting this issue. This issue was discovered by Steve Grubb of Red Hat. This issue was discovered by Jason Greene of the Red Hat Middleware Engineering Team. This issue was discovered by Tomáš Jelínek of Red Hat. This issue was discovered by Tomáš Jelínek of Red Hat. This issue was discovered by Florian Weimer of Red Hat Product Security. This issue was discovered by Miroslav Lichvár of Red Hat. This issue was discovered by Florian Weimer of Red Hat Product Security. This issue was discovered by Florian Weimer of Red Hat Product Security. This issue was discovered by Florian Weimer of Red Hat Product Security. This issue was discovered by Michal Skrivanek of Red Hat. This issue was discovered by Brian Bouterse of Red Hat. Red Hat would like to thank Gustavo Grieco for reporting this issue. This issue was discovered by Michael Scherer of Red Hat. This issue was discovered by Patrick Uiterwijk of Red Hat. This issue was discovered by Miroslav Lichvar of Red Hat. This issue was discovered by Aaron Ogburn of Red Hat GSS Middleware Team Red Hat would like to thank Josselin Feist for reporting this issue. This issue was discovered by Cesar Wong of the Red Hat OpenShift Enterprise Team. Red Hat would like to thank the Openstack project for reporting this issue. Upstream acknowledges Richard Hawkins of Rackspace and the Swift core reviewers as the original reporters of this issue. Red Hat would like to thank Mr Qinghao Tang from QIHU 360 Inc. and Mr Zuozhi from Alibaba Inc. for reporting this issue. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank Jeff Layton for reporting this issue. This issue was discovered by Florian Weimer of Red Hat Product Security. This is issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank Andrea Palazzo (Truel IT) for reporting this issue. Red Hat would like to thank Andrea Palazzo (Truel IT) for reporting this issue. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank Lian Yihan of Qihoo 360 for reporting this issue. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Kevin Benton from Mirantis as the original reporter. Red Hat would like to thank Adam Willard (Foreground Security) for reporting this issue. This issue was discovered Hubert Kario of Red Hat. Red Hat would like to thank Maciej Grela of Trustwave for reporting this issue. Red Hat would like to thank Jordan Liggitt of the Red Hat OpenShift Team for reporting this issue. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Hemanth Makkapati of Rackspace as the original reporter. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Jan "Yenya" Kasprzak and the Computer Systems Unit team at Faculty of Informatics, Masaryk University as the original reporters. Red Hat would like to thank the Apache Software Foundation for reporting this issue. Upstream acknowledges Ivan Zhakov of VisualSVN as the original reporter. This issue was discovered by Frediano Ziglio of Red Hat. This issue was discovered by Frediano Ziglio of Red Hat. This issue was discovered by Christian Schwede and Emilien Macchi of Red Hat. Red Hat would like to thank Philip Pettersson of Samsung for reporting this issue. This issue was discovered by Sumit Bose and Lukáš Slebodník of Red Hat. This issue was discovered by Qinghao Tang of QIHU 360 Inc. Red Hat would like to thank Qinghao Tang of QIHU 360 Inc. for reporting this issue. This issue was discovered by Ji Jianwen from Red Hat engineering. This issue was discovered by Jan Cholasta of Red Hat. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Mike Fedosin and Alexei Galkin of Mirantis as the original reporters. Red Hat would like to thank Philip Pettersson of Samsung for reporting this issue. This issue was discovered by Steven Hardy of Red Hat. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Stefan Metzmacher of the Samba Team and Sernet.de as the original reporters. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges partha@exablox.com as the original reporter. Red Hat would like to thank Aanchal Malhotra, Isaac E. Cohen, and Sharon Goldberg of Boston University for reporting this issue. This issue was discovered by Patrick Uiterwijk and Rob Crittenden of Red Hat. This issue was discovered by Bastien Nocera of Red Hat. This issue was discovered by Steven Hardy of Red Hat. This issue was discovered by Ladislav Thon of Red Hat Middleware Quality Engineering. This issue was discovered by Jordan Liggitt of Red Hat. Red Hat would like to thank Ben Serebrin of Google Inc. for reporting this issue. Red Hat would like to thank Mimi Zohar of IBM for reporting this issue. Red Hat would like to thank Kota Akatsuka of NEC for reporting this issue. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Douglas Bagnall as the original reporter. Red Hat would like to thank Moodle project for reporting this issue. Red Hat would like to thank Moodle project for reporting this issue. Red Hat would like to thank Moodle project for reporting this issue. Red Hat would like to thank Moodle project for reporting this issue. Red Hat would like to thank Moodle project for reporting this issue. Red Hat would like to thank Moodle project for reporting this issue. Red Hat would like to thank Moodle project for reporting this issue. Red Hat would like to thank Moodle project for reporting this issue. Red Hat would like to thank Moodle project for reporting this issue. Red Hat would like to thank Moodle project for reporting this issue. Red Hat would like to thank the Apache Software Foundation for reporting this issue. Upstream acknowledges Ivan Zhakov of VisualSVN as the original reporter. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Jouni Knuutinen (Synopsis) as the original reporter. Red Hat would like to thank ISC for reporting this issue. Upstream acknowledges Jonathan Foote as the original reporter. Red Hat would like to thank Qinghao Tang (QIHU 360) for reporting this issue. This issue was discovered by Florian Weimer of Red Hat Product Security. This issue was discovered by Florian Weimer of Red Hat Product Security. Red Hat would like to thank ISC for reporting this issue. Upstream acknowledges Hanno Böck as the original reporter. Red Hat would like to thank the upstream Django project for reporting this issue. Red Hat would like to thank the upstream Django project for reporting this issue. Upstream acknowledges Lin Hua Cheng as the original reporter. Red Hat would like to thank ISC for reporting this issue. Red Hat would like to thank Michael S. Tsirkin of Red Hat Engineering for reporting this issue responsibly. This issue was discovered by Qinghao Tang of QIHU 360 Inc. This issue was discovered by Qinghao Tang of QIHU 360 Inc. Red Hat would like to thank the Mozilla project for reporting these issues. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting these issues. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting these issues. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting these issues. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting these issues. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting these issues. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting these issues. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tyson Smith as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges David Keeler as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ryan Sleevi as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jason Hamilton as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Michał Bentkowski as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Looben Yang as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Shinto K Anto as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gustavo Grieco as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Frans Rosén as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Vytautas Staraitis as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ehsan Akhgari as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Andrei Vaida, Jesse Ruderman, and Bob Clary as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Jesse Ruderman, Eric Rahm, Robert Kaiser, Harald Kirschner, and Michael Henretty as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Cajus Pollmeier as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges cgvwzq as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Security researcher musicDespiteEverything as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Looben Yang as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abdulrahman Alqabandi as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tsubasa Iinuma as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Masato Kinugawa as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gustavo Grieco as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gustavo Grieco as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Stuart Larsen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Stuart Larsen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gerald Squelart as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Kris Maglione as the original reporter. This issue was discovered by Jason Wang of Red Hat Inc. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Michael Young of Durham University as the original reporter. Red Hat would like to thank the Mozilla project for reporting these issues. Upstream acknowledges Yossef Oren, Vasileios P. Kemerlis, Simha Sethumadhavan, and Angelos D. Keromytis of Columbia University's Network Security Lab, and Amit Klein as the original reporters. Red Hat would like to thank the GNOME project for reporting this issue. Upstream acknowledges Kostya Serebryany as the original reporter. Red Hat would like to thank the GNOME project for reporting this issue. Upstream acknowledges Kostya Serebryany as the original reporter. Red Hat would like to thank the GNOME project for reporting this issue. Upstream acknowledges Kostya Serebryany as the original reporter. Red Hat would like to thank the GNOME project for reporting this issue. Upstream acknowledges Kostya Serebryany as the original reporter. This issue was independently discovered by Qinghao Tang of QIHU 360 Marvel Team and Ling Liu of Qihoo 360 Inc. This issue was discovered by Florian Weimer of Red Hat. This issue was independently discovered by Ling Liu of Qihoo 360 Inc. and Jason Wang of Red Hat Inc. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Brad Morgan from Rackspace as the original reporter. Red Hat would like to thank Ralf Spenneberg of OpenSource Security for reporting this issue. This issue was discovered by Jordan Liggitt of Red Hat Atomic OpenShift. This issue was discovered by Mateusz Guzik of Red Hat. Red Hat would like to thank the Samba project for reporting this issue. This issue was discovered by Alexander Wels (Red Hat). This issue was discovered by the Google Security Team and Red Hat. This issue was discovered by Matthew Booth of Red Hat. This issue was reported by Qinghao Tang of QIHU 360 Marvel Team. Red Hat would like to thank Dmitry Vyukov of Google for reporting this issue. Red Hat would like to thank Gustavo Grieco for reporting this issue. Red Hat would like to thank Hans Jerry Illikainen for reporting this issue. Red Hat would like to thank Gustavo Grieco for reporting this issue. Red Hat would like to thank Gustavo Grieco for reporting this issue. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Jeremy Allison (Google) and the Samba team as the original reporters. Red Hat would like to thank Ralf Spenneberg of OpenSource Security for reporting this issue. Red Hat would like to thank Ruby on Rails project for reporting this issue. Upstream acknowledges Daniel Waterworth as the original reporter. Red Hat would like to thank Ruby on Rails project for reporting this issue. Upstream acknowledges Justin Coyne as the original reporter. Red Hat would like to thank Ruby on Rails project for reporting this issue. Upstream acknowledges Arthur Neves from GitHub and Spyros Livathinos from Zendesk as the original reporters. Red Hat would like to thank Ruby on Rails project for reporting this issue. Upstream acknowledges Arnaud Germis, Nate Clark, and John Colvin as the original reporters. Red Hat would like to thank Ruby on Rails project for reporting this issue. Red Hat would like to thank Gustavo Grieco for reporting this issue. This issue was discovered by Miroslav Lichvár of Red Hat. Red Hat would like to thank Aanchal Malhotra, Isaac E. Cohen, and Sharon Goldberg of Boston University for reporting this issue. Red Hat would like to thank Ralf Spenneberg of OpenSource Security for reporting this issue. Red Hat would like to thank Linn Crosetto of HP for reporting this issue. Red Hat would like to thank puzzor for reporting this issue. Red Hat would like to thank ISC for reporting this issue. Red Hat would like to thank the Django project for reporting this issue. Upstream acknowledges Ryan Butterfield as the original reporter. Red Hat would like to thank the GNOME project for reporting this issue. Upstream acknowledges Hugh Davenport as the original reporter. Red Hat would like to thank the GNOME project for reporting this issue. Upstream acknowledges Hugh Davenport as the original reporter. Red Hat would like to thank the GNOME project for reporting this issue. Upstream acknowledges Hanno Boeck as the original reporter. Red Hat would like to thank Dmitriy Monakhov of OpenVZ project for reporting this issue. This issue was discovered by Miloslav Trmač of Red Hat. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Julien Grall of Citrix as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Julien Grall of Citrix and Jan Beulich of SUSE as the original reporters. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Julien Grall of Citrix and Jan Beulich of SUSE as the original reporters. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges George Dunlap of Citrix as the original reporter. This issue was discovered by Qinghao Tang of QIHU 360 Marvel Team. Red Hat would like to thank ISC for reporting this issue. Upstream acknowledges John O'Brien of the University of Pennsylvania as the original reporter. Red Hat would like to thank the Samba project for reporting this issue. Upstream cknowledges Andrew Bartlett of the Samba Team and Catalyst as the original reporters. This issue was discovered by Lian Yihan of Qihoo 360 Inc. Red Hat would like to thank Xiao Qixue for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Felix Wilhelm (ERNW Research, KIT / Operating Systems Group) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Qinghao Tang of QIHU 360 for reporting this issue. This issue was discovered by Qinghao Tang of QIHU 360 Marvel Team. This issue was discovered by Qinghao Tang of QIHU 360 Marvel Team. Red Hat would like to thank ISC for reporting this issue. Upstream acknowledges Sebastian Poehn of Sophos as the original reporter. Red Hat would like to thank upstream developer Ricardo Signes for reporting this issue. Upstream acknowledges David Golden of MongoDB as the original reporter. Red Hat would like to thank Qinghao Tang of Qihoo 360 Inc. for reporting this issue. Red Hat would like to thank Ling Liu of Qihoo 360 Inc. for reporting this issue. This issue was discovered by Simo Sorce of Red Hat. Red Hat would like to thank Nathan Williams for reporting this issue. This issue was discovered by David Alan Gilbert of Red Hat. Red Hat would like to thank Qinghao Tang of Qihoo 360 for reporting this issue. Red Hat would like to thank ISC for reporting this issue. Red Hat would like to thank ISC for reporting this issue. Red Hat would like to thank Ling Liu of Qihoo 360 Inc. for reporting this issue. This issue was discovered by Venkatesh Pottem (Red Hat Engineering). Red Hat would like to thank Donghai Zdh of Alibaba Inc. for reporting this issue. Red Hat would like to thank Donghai Zdh of Alibaba Inc. for reporting this issue. This issue was discovered by Florian Weimer of Red Hat Product Security Team. This issue was discovered by Florian Weimer of Red Hat Product Security Team. This issue was discovered by Miroslav Vadkerti (Red Hat Engineering). This issue was discovered by Miroslav Vadkerti (Red Hat Engineering). This issue was discovered by Adam Miller (Red Hat). Red Hat would like to thank Laurent Guerby for bringing this to our attention. This issue was discovered by CAI Qian (Red Hat Engineering). Red Hat would like to thank Igor Redko (Virtuozzo) and Vasily Averin (Virtuozzo) for reporting this issue. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Antonio Sanso as the original reporter of this issue. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Yuval Yarom (University of Adelaide and NICTA), Daniel Genkin (Technion and Tel Aviv University), and Nadia Heninger (University of Pennsylvania) as the original reporters. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges David Adrian (University of Michigan) and J. Alex Halderman (University of Michigan) as the original reporters. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges David Adrian (University of Michigan) and J. Alex Halderman (University of Michigan) as the original reporters. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Adam Langley (Google/BoringSSL) as the original reporter. Red Hat would like to thank Gustavo Grieco for reporting this issue. This issue was discovered by Martin Prpic (Red Hat Product Security). This issue was discovered by Martin Prpic (Red Hat Product Security). This issue was discovered by Milos Vyletel of Red Hat. Red Hat would like to thank the Perception Point research team for reporting this issue. Red Hat would like to thank Gustavo Grieco for reporting this issue. Red Hat would like to thank Openstack project for reporting this issue. Upstream acknowledges Romain Le Disez from OVH and Örjan Persson from Kiliaro as the original reporters. Red Hat would like to thank Openstack project for reporting this issue. Upstream acknowledges Romain Le Disez from OVH and Örjan Persson from Kiliaro as the original reporters. Red Hat would like to thank Aris Adamantiadis for reporting this issue. Red Hat would like to thank the Pillow project for reporting this issue. Upstream acknowledges FourOne as the original reporter. This issue was discovered by Jing Zhao (Red Hat). Red Hat would like to thank Sebastian Olsson (TrueSec) for reporting this issue. Red Hat would like to thank the Ruby on Rails project for reporting this issue. Upstream acknowledges Aaron Patterson of Red Hat as the original reporter. Red Hat would like to thank Ruby on Rails project for reporting this issue. Upstream acknowledges John Poulin as the original reporter. Red Hat would like to thank Ruby on Rails project for reporting this issue. Upstream acknowledges John Backus from BlockScore as the original reporter. Red Hat would like to thank curl upstream for reporting this issue. Upstream acknowledges Isaac Boukris as the original reporter. Red Hat would like to thank the Openstack project for reporting this issue. Upstream acknowledges Erno Kuvaja (HPE) as the original reporter. Red Hat would like to thank Philip Pettersson of Samsung for reporting this issue. Red Hat would like to thank the samba project for reporting this issue. Upstream acknowledges Garming Sam and Douglas Bagnall as the original reporters of this issue. Red Hat would like to thank PostgreSQL upstream for reporting this issue. Upstream acknowledges Tom Lane and Greg Stark as the original reporters. The security impact of this issue was discovered by Red Hat. Red Hat would like to thank the Pillow project for reporting this issue. Upstream acknowledges Alyssa Besseling as the original reporter. Red Hat would like to thank Qualys for reporting this issue. Red Hat would like to thank Qualys for reporting this issue. Red Hat would like to thank Aris Adamantiadis for reporting this issue. Red Hat would like to thank Tal Solomon of Palantir Security for reporting this issue. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Emilia Käsper as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Nimrod Aviram and Sebastian Schinzel as the original reporters. Red Hat would like to thank Scott Geary (VendHQ) for reporting this issue. Red Hat would like to thank Scott Geary (VendHQ) for reporting this issue. Red Hat would like to thank Scott Geary (VendHQ) for reporting this issue. Red Hat would like to thank Scott Geary (VendHQ) for reporting this issue. Red Hat would like to thank Scott Geary (VendHQ) for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Hongzhenhao Qinghao Tang (360.cn Marvel Team) for reporting this issue. Red Hat would like to thank Hongzhenhao Marvel Team (360.cn Inc.) for reporting this issue. This issue was discovered by Florian Weimer (Red Hat). This issue was discovered by Florian Weimer (Red Hat). Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank the Perl project for reporting this issue. Upstream acknowledges John Lightsey (cPanel Security Team) and Todd Rinaldo (cPanel Security Team) as the original reporters. Red Hat would like to thank ISC for reporting this issue. Red Hat would like to thank ISC for reporting this issue. This issue was discovered by Miroslav Lichvar (Red Hat). Red Hat would like to thank Qinghao Tang of Qihoo 360 Marvel Team for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges 360 Marvel Team as the original reporters. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Donghai Zhu of Alibaba for reporting this issue. Red Hat would like to thank Ling Liu of Qihoo 360 Inc. for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bob Clary, Christian Holler, Nils Ohlmeier, Gary Kwong, Jesse Ruderman, Carsten Book, and Randell Jesup as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bob Clary, Carsten Book, Christian Holler, Nicolas Pierron, Eric Rescorla, Tyson Smith, Gabor Krizsanits, and Randell Jesup as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gustavo Grieco as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Aki Helin as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges window as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges musicDespiteEverything, Nicholas Hurley as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jordi Chancel as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges François Marier as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Francis Gabriel as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bob Clary, Christoph Diehl, Christian Holler, Andrew McCreight, Daniel Holbert, Jesse Ruderman, and Randell Jesup as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Carsten Book, Christoph Diehl, Christian Holler, Andrew McCreight, Daniel Holbert, Gian-Carlo Pascutto, Tyson Smith, Andrea Marchesini, and Jukka Jylänki as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nicolas Golubovic as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Muneaki Nishimura as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ucha Gobejishvili as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jose Martinez and Romina Santillan as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abdulrahman Alqabandi as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Looben Yang as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges ca0nguyen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges lokihardt as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Dominique Hazaël-Massieux as the original reporter. Red Hat would like to thank The Mozilla Project for reporting this issue. Upstream acknowledges Oriol as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nicolas Grégoire as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tsubasa Iinuma as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges the Communications Electronics Security Group (UK) of the GCHQ as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jordi Chancel as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Luke Li as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Eric Rescorla as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tim Taubert as the original reporter. Red Hat would like to thank the upstream Django project for reporting this issue. Red Hat would like to thank Philip Pettersson (Samsung) for reporting this issue. Red Hat would like to thank the Open vSwitch project for reporting this issue. Upstream acknowledges Kashyap Thimmaraju and Bhargava Shastry as the original reporters. Red Hat would like to thank ISC for reporting this issue. This issue was discovered by Aaron Ogburn of Red Hat. Red Hat would like to thank the Ruby on Rails project for reporting this issue. Upstream acknowledges Jyoti Singh and Tobias Kraze (makandra) as the original reporters. Red Hat would like to thank the Ruby on Rails project for reporting this issue. Upstream acknowledges Tobias Kraze (makandra) and joernchen (Phenoelit) as the original reporters. Red Hat would like to thank Gustavo Grieco for reporting this issue. Red Hat would like to thank Adam Willard (Raytheon Foreground Security) for reporting this issue. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Juraj Somorovsky as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Huzaifa Sidhpurwala (Red Hat), Hanno Böck, and David Benjamin (Google) as the original reporters. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Stefan Metzmacher (SerNet) as the original reporter. Red Hat would like to thank the Samba project for reporting this issue. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Stefan Metzmacher (SerNet) as the original reporter. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Stefan Metzmacher (SerNet) as the original reporter. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Stefan Metzmacher (SerNet) as the original reporter. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Stefan Metzmacher (SerNet) as the original reporter. Red Hat would like to thank Justin Yackoski (Cryptonite) for reporting this issue. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Stefan Metzmacher (SerNet) as the original reporter. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Stefan Metzmacher as the original reporter. This issue was discovered by Honza Horak (Red Hat) and Remi Collet (Red Hat). This issue was discovered by Matthew Booth (Red Hat). This issue was discovered by Dennis Reed (Red Hat). This issue was discovered by Jan Hutař (Red Hat). Red Hat would like to thank Olav Morken (Uninett) for reporting this issue. Upstream acknowledges Vincent Rasneur as the original reporter. Red Hat would like to thank Olav Morken (Uninett) for reporting this issue. Upstream acknowledges Vincent Rasneur as the original reporter. Red Hat would like to thank Nico Golde (Qualcomm Product Security Initiative) for reporting this issue. Red Hat would like to thank Nico Golde (Qualcomm Product Security Initiative) for reporting this issue. This issue was discovered by Wesley Hearn (Red Hat). This issue was discovered by Frediano Ziglio (Red Hat). Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank OpenVPN for reporting this issue. Upstream acknowledges Karthikeyan Bhargavan (Inria) and Gaëtan Leurent (Inria) as the original reporters. Red Hat would like to thank Ralf Spenneberg (OpenSource Security) for reporting this issue. Red Hat would like to thank Ralf Spenneberg (OpenSource Security) for reporting this issue. Red Hat would like to thank Ralf Spenneberg (OpenSource Security) for reporting this issue. Red Hat would like to thank Ralf Spenneberg (OpenSource Security) for reporting this issue. Red Hat would like to thank Ralf Spenneberg (OpenSource Security) for reporting this issue. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Ashutosh Bapat as the original reporter. Red Hat would like to thank Zuozhi Fzz of Alibaba Inc. for reporting this issue. Red Hat would like to thank Zuozhi Fzz of Alibaba Inc. for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Stephane Chazelas for reporting this issue. Red Hat would like to thank Zuozhi Fzz of Alibaba Inc. for reporting this issue. Red Hat would like to thank Qinghao Tang (QIHU 360 Marvel Team) for reporting this issue. Red Hat would like to thank the Django project for reporting this issue. Red Hat would like to thank the Django project for reporting this issue. Red Hat would like to thank Qinghao Tang (QIHU 360 Marvel Team) for reporting this issue. Red Hat would like to thank ISC for reporting this issue. Red Hat would like to thank ISC for reporting this issue. Red Hat would like to thank Ralf Spenneberg (OpenSource Security) for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gary Kwong, Christian Holler, Andrew McCreight, Boris Zbarsky, and Steve Fink as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gary Kwong, Christian Holler, Jesse Ruderman, Mats Palmgren, Carsten Book, Boris Zbarsky, David Bolter, and Randell Jesup as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Tyson Smith, and Phil Ringalda as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges CESG (the Information Security Arm of GCHQ) as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ken Okuyama as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Looben Yang as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Looben Yang as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Maryam Mehrnezhad as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Sascha Just as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christoph Diehl, Julian Hector, Jan de Mooij, Mats Palmgren, and and Tooru Fujisawa as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Muneaki Nishimura as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Muneaki Nishimura as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Gary Kwong, Jesse Ruderman, Tyson Smith, Timothy Nikkel, Sylvestre Ledru, Julian Seward, Olli Pettay, and Karl Tomlinson as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges firehack as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mark Goodwin as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges firehack as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jordi Chancel as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Armin Razmdjou as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges jomo as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tim McCormack as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Toni Huttunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges sushi Anton Larsson as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges John Schoenick as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Matt Wobensmith as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tyson Smith and Jed Davis as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Tyson Smith, Boris Zbarsky, Byron Campen, and and Julian Seward as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Carsten Book, Christian Holler, Gary Kwong, Jesse Ruderman, Andrew McCreight, Phil Ringnalda, and Philipp as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bert Massop as the original reporter. Red Hat would like to thank Hongke Yang of Huawei Technologies Co. Ltd. for reporting this issue. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank Tetsuo Handa for reporting this issue. Red Hat would like to thank Ling Liu (Qihoo 360 Inc.) for reporting this issue. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Andreas Seltenreich as the original reporter. This issue was discovered by Daniel P. Berrange (Red Hat). Red Hat would like to thank Blake Burkhart for reporting this issue. Red Hat would like to thank Blake Burkhart for reporting this issue. This issue was discovered by Jan Stancek (Red Hat). Red Hat would like to thank Hans Jerry Illikainen for reporting this issue. This issue was discovered by Florian Weimer (Red Hat). Red Hat would like to thank the Pillow project for reporting this issue. Upstream acknowledges Alyssa Besseling as the original reporter. Red Hat would like to thank Hans Jerry Illikainen for reporting this issue. This issue was discovered by Jan Hutař (Red Hat). This issue was discovered by Jan Hutař (Red Hat). This issue was discovered by Alex Szczuczko (Red Hat). This issue was discovered by Randy Barlow (Red Hat). This issue was discovered by Evgeni Golov (Red Hat). This issue was discovered by Jan Hutař (Red Hat). This issue was discovered by Rob Crittenden (Red Hat). Red Hat would like to thank Stephan Mueller (Atsec) for reporting this issue. Red Hat would like to thank Simon Budail Essard and Philippe Jacquot for reporting this issue. This issue was discovered by Florian Weimer (Red Hat) and Sander Bos. This issue was discovered by Randy Barlow (Red Hat) and Jeremy Cline (Red Hat). This issue was discovered by Jeremy Cline (Red Hat) and Sander Bos. Red Hat would like to thank Michal Karm Babacek for reporting this issue. This issue was discovered by Jeremy Cline (Red Hat). This issue was discovered by Jeremy Cline (Red Hat). Red Hat would like to thank Dennis Felsch (Ruhr-University Bochum) and Emanuel Durmaz (Ruhr-University Bochum) for reporting this issue. Red Hat would like to thank Ralf Spenneberg (OpenSource Security) for reporting this issue. Red Hat would like to thank Ralf Spenneberg (OpenSource Security) for reporting this issue. Red Hat would like to thank Ralf Spenneberg (OpenSource Security) for reporting this issue. Red Hat would like to thank Ralf Spenneberg (OpenSource Security) for reporting this issue. Red Hat would like to thank Ralf Spenneberg (OpenSource Security) for reporting this issue. Red Hat would like to thank the Virtuozzo kernel team and Solar Designer (Openwall) for reporting this issue. Red Hat would like to thank Andy Lutomirski for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Josselin Feist for reporting this issue. Red Hat would like to thank Aladdin Mubaied for reporting this issue. Red Hat would like to thank Aladdin Mubaied for reporting this issue. Red Hat would like to thank Aladdin Mubaied for reporting this issue. Red Hat would like to thank Mei Wang (Qihoo 360) for reporting this issue. Red Hat would like to thank Mei Wang (Qihoo 360) for reporting this issue. Red Hat would like to thank Mei Wang (Qihoo 360) for reporting this issue. Red Hat would like to thank Mei Wang (Qihoo 360) for reporting this issue. Red Hat would like to thank Mei Wang (Qihoo 360) for reporting this issue. Red Hat would like to thank Mei Wang (Qihoo 360) for reporting this issue. Red Hat would like to thank Mei Wang (Qihoo 360) for reporting this issue. Red Hat would like to thank Kaixiang Zhang (Qihoo 360) for reporting this issue. Red Hat would like to thank Dennis Reed and Red Hat for reporting this issue. This issue was discovered by Dominic Cleal (Red Hat). Red Hat would like to thank Linn Crosetto (HP) for reporting this issue. Red Hat would like to thank Sander Bos for reporting this issue. This issue was discovered by Mrunal Patel (Red Hat). Red Hat would like to thank Julien Bernard (Viagénie) for reporting this issue. Red Hat would like to thank Linn Crosetto (HP) for reporting this issue. This issue was discovered by Travis Scheponik (Red Hat). This issue was discovered by Jordan Liggitt (Red Hat). Red Hat would like to thank Randy Barlow (RedHat) for reporting this issue. This issue was discovered by Michael Petlan (Red Hat). This issue was discovered by Ben Parees (Red Hat). Red Hat would like to thank Wei Xiao (360.cn Marvel Team) and Qinghao Tang (360.cn Marvel Team) for reporting this issue. Red Hat would like to thank Zuozhi Fzz (Alibaba Inc.) for reporting this issue. Red Hat would like to thank David Matlack (Google) for reporting this issue. Red Hat would like to thank Adith Sudhakar for reporting this issue. Red Hat would like to thank the Foreman project for reporting this issue. Upstream acknowledges Lukas Zapletal (Red Hat) as the original reporter. Red Hat would like to thank the Moodle project for reporting this issue. Red Hat would like to thank the Moodle project for reporting this issue. Red Hat would like to thank the Moodle project for reporting this issue. Red Hat would like to thank the Moodle project for reporting this issue. Red Hat would like to thank the Moodle project for reporting this issue. This issue was discovered by Jason Shepherd (Red Hat). This issue was discovered by David Eads (Red Hat). Red Hat would like to thank Daniel Stenberg (curl upstream) for reporting this issue. Upstream acknowledges Moti Avrahami as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Oleksandr Bazhaniuk of Advanced Threat Research team at Intel Inc. for reporting this issue. Red Hat would like to thank Oleksandr Bazhaniuk of Advanced Threat Research team at Intel Inc. for reporting this issue. Red Hat would like to thank Donghai Zdh (Alibaba Inc.) for reporting this issue. Red Hat would like to thank Du Shaobo (Qihoo 360) for reporting this issue. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Beth Lancaster (Virginia Tech) and Brandon Sawyers (Virginia Tech) as the original reporters. This issue was discovered by Aldy Hernandez (Red Hat). Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. This issue was discovered by Simone Tiraboschi (Red Hat). This issue was discovered by Milos Malik (Red Hat). This issue was discovered by Red Hat Product Security. This issue was discovered by Milos Malik (Red Hat). This issue was discovered by Marek Hulán (Red Hat). Red Hat would like to thank Li Qiang (Qihoo 360 Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360) and Qinghao Tang (Qihoo 360) for reporting this issue. Red Hat would like to thank Robert Scheck for reporting this issue. This issue was discovered by Nikos Mavrogiannopoulos (Red Hat). This issue was discovered by Simon Lukasik (Red Hat). This issue was discovered by Robert Bost (Red Hat). This issue was discovered by David Howells (Red Hat). This issue was discovered by Simon Lukasik (Red Hat). Red Hat would like to thank the Expat project for reporting this issue. Upstream acknowledges Pascal Cuoq (TrustInSoft) as the original reporter. Red Hat would like to thank Hans Jerry Illikainen for reporting this issue. Red Hat would like to thank David Patterson (Dell) for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Jann Horn for reporting this issue. This issue was discovered by Eric W. Biederman (Red Hat). Red Hat would like to thank Yuguang Cai (Qihoo 360) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Inc.) for reporting this issue. This issue was discovered by Miroslav Lichvar (Red Hat). This issue was discovered by Jakub Prokes of Red Hat Quality Engineering. This issue was discovered by Miroslav Lichvar (Red Hat). This issue was discovered by Miroslav Lichvar (Red Hat). Red Hat would like to thank CERT/CC for reporting this issue. Upstream acknowledges Nicolas Edet (Cisco) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Inc.) for reporting this issue. Red Hat would like to thank GNU wget project for reporting this issue. Upstream acknowledges Dawid Golunski as the original reporter. Red Hat would like to thank Kirill Zaitsev (Mirantis) for reporting this issue. This issue was discovered by Yaakov Selkowitz (Red Hat). Red Hat would like to thank Apache Software Foundation for reporting this issue. Upstream acknowledges Erki Aring (Liewenthal Electronics Ltd) as the original reporter. This issue was discovered by Kurt Seifried (Red Hat). This issue was discovered by Kurt Seifried (Red Hat). This issue was discovered by Kurt Seifried (Red Hat). This issue was discovered by Kurt Seifried (Red Hat). Red Hat would like to thank the OpenStack Ironic project for reporting this issue. Upstream acknowledges Devananda van der Veen (IBM) as the original reporter. This issue was discovered by Red Hat Product Security. This issue was discovered by Petr Spacek (Red Hat) and Martin Basti (Red Hat). Red Hat would like to thank Calum Hutton (NCC Group) and Mikhail Egorov (Odin) for reporting this issue. This issue was discovered by Dominic Cleal (Red Hat). This issue was discovered by Thom Carlin (Red Hat). This issue was discovered by David Gutierrez (Red Hat). Red Hat would like to thank the Ceph project for reporting this issue. Upstream acknowledges Xiaoxi Chen as the original reporter. Red Hat would like to thank Shi Pu (China Electronic Technology Cyber Security) for reporting this issue. Red Hat would like to thank Michael Gruhn for reporting this issue. Upstream acknowledges Christian Moch as the original reporter. Red Hat would like to thank Li Qiang (Qihoo 360 Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Inc.) for reporting this issue. Red Hat would like to thank Phil Oester for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Aaron Cornelius (DornerWorks) as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Catalin Dumitru as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Firas Salem as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Georg Koppen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jukka Jylänki as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christoph Diehl, Christian Holler, Gary Kwong, Nathan Froyd, Honza Bambas, Seth Fowler, and Michael Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mozilla developers, Christoph Diehl, Andrew McCreight, Dan Minor, Byron Campen, Jon Coppeard, Steve Fink, Tyson Smith, Philipp, and Carsten Book as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Looben Yang as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Looben Yang as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mike Kaply as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Samuel Groß as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nikita Arykov as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abdulrahman Alqabandi as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Rafael Gieschke as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges musicDespiteEverything as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Rafael Gieschke as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mei Wang as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Brian Carpenter as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Richard Newman as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gavin Sharp as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ryan Duff as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mozilla developers as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Olli Pettay, Christian Holler, Ehsan Akhgari, Jon Coppeard, Gary Kwong, Tooru Fujisawa, Philipp, and and Randell Jesup as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Yuyang Zhou as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Daniel Browning as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges André Bargull as the original reporter. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Security Team (Huawei Inc.) and Li Qiang (360.cn Inc.) for reporting this issue. This issue was discovered by Eric Hayes (Red Hat). Red Hat would like to thank Tobias Stoeckmann for reporting this issue. Red Hat would like to thank Scott Geary (VendHQ) for reporting this issue. Red Hat would like to thank Scott Geary (VendHQ) for reporting this issue. Red Hat would like to thank Scott Geary (VendHQ) for reporting this issue. Red Hat would like to thank Scott Geary (VendHQ) for reporting this issue. Red Hat would like to thank the Foreman project for reporting this issue. Upstream acknowledges Daniel Lobato Garcia, Nacho Barrientos, and Steve Traylen as the original reporters. This issue was discovered by Paul Wouters (Red Hat). This issue was discovered by Yanping Zhang (Red Hat). This issue was discovered by Jeremy Choi (Red Hat Product Security Team). Red Hat would like to thank Hans Jerry Illikainen for reporting this issue. Red Hat would like to thank James Patrick-Evans for bringing this to our attention. This issue was discovered by Jeremy Choi (Red Hat Product Security Team). This issue was discovered by Simon Lukasik (Red Hat). Red Hat would like to thank hongzhenhao (Marvel Team) for reporting this issue. This issue was discovered by Fraser Tweedale (Red Hat). This issue was discovered by William Brown (Red Hat). This issue was discovered by Tomaz Cerar (Red Hat). Red Hat would like to thank Amos Jeffries (Squid) for reporting this issue. This issue was discovered by Thom Carlin (Red Hat). This issue was discovered by Simo Sorce (Red Hat). This issue was discovered by Viktor Ashirov (Red Hat). Red Hat would like to thank Insomnia Security for reporting this issue. This issue was discovered by Jeremy Choi (Red Hat Product Security Team). Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Heikki Linnakangas as the original reporter. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Nathan Bossart as the original reporter. Red Hat would like to thank Dawid Golunski (http://legalhackers.com) for reporting this issue. This issue was discovered by Yedidyah Bar David (Red Hat). Red Hat would like to thank Yue Cao (Cyber Security Group of the CS department of University of California in Riverside) for reporting this issue. This issue was discovered by Borja Tarraso (Red Hat). Red Hat would like to thank the upstream Django project for reporting this issue. This issue was discovered by CAI Qian (Red Hat). This issue was discovered by CAI Qian (Red Hat). This issue was discovered by Qian Cai (Red Hat). Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Dennis Detering for reporting this issue. This issue was discovered by Florian Weimer (Red Hat). This issue was discovered by Miroslav Lichvar (Red Hat). Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Shi Lei (Gear Team of Qihoo 360 Inc.) as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Alex Gaynor as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Shi Lei (Gear Team of Qihoo 360 Inc.) as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Shi Lei (Gear Team of Qihoo 360 Inc.) as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Shi Lei (Gear Team of Qihoo 360 Inc.) as the original reporter. This issue was discovered by Jiri Belka (Red Hat). Red Hat would like to thank Luca Bueti for reporting this issue. Upstream acknowledges WildFly as the original reporter. Red Hat would like to thank Felix Dörre and Vladimir Klebanov for reporting this issue. Red Hat would like to thank the Ruby on Rails project for reporting this issue. Upstream acknowledges Andrew Carpenter (Critical Juncture) as the original reporter. Red Hat would like to thank the Ruby on Rails project for reporting this issue. Upstream acknowledges joernchen (Phenoelit) as the original reporter. Red Hat would like to thank CSG Labs for reporting this issue. This issue was discovered by Marek Hulán (Red Hat). This issue was discovered by Sanket Jagtap (Red Hat). Red Hat would like to thank Harry Sintonen for reporting this issue. This issue was discovered by Thom Carlin (Red Hat). This issue was discovered by Red Hat Product Security. Liu Bingchang (IIE) Red Hat would like to thank OpenVPN for reporting this issue. Upstream acknowledges Karthikeyan Bhargavan (Inria) and Gaëtan Leurent (Inria) as the original reporters. This issue was discovered by Greg Sheremeta (Red Hat). This issue was discovered by Red Hat QCI QE team. Red Hat would like to thank Fabrice Bacchella for reporting this issue. This issue was discovered by Jeremy Choi (Red Hat Product Security Team). This issue was discovered by Jeremy Choi (Red Hat Product Security Team). Red Hat would like to thank Mikhail Egorov (Odin) for reporting this issue. Red Hat would like to thank Mikhail Egorov (Odin) for reporting this issue. Red Hat would like to thank Mikhail Egorov (Odin) for reporting this issue. Red Hat would like to thank Mikhail Egorov (Odin) for reporting this issue. This issue was discovered by CAI Qian (Red Hat). Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Franco Constantini for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank SUSE for reporting this issue. Upstream acknowledges Niklaus Schiess as the original reporter. Red Hat would like to thank Li Qiang (Qihoo 360 Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Inc.) for reporting this issue. This issue was discovered by Petr Spacek (Red Hat). This issue was discovered by Florian Weimer (Red Hat). This issue was discovered by Jeremy Choi (Red Hat Product Security Team). This issue was discovered by Jeremy Choi (Red Hat Product Security Team). This issue was discovered by Jan "poki" Pokorny (Red Hat) and Alain Moulle (ATOS/BULL). This issue was discovered by Tim Wade (Red Hat). Red Hat would like to thank Jonas Bauters (NVISO) for reporting this issue. This issue was discovered by Ondrej Kozina (Red Hat). This issue was discovered by Simon Lukasik (Red Hat). Red Hat would like to thank the PostgreSQL project for reporting this issue. Red Hat would like to thank Mikhail Egorov (Odin) for reporting this issue. Red Hat would like to thank Adith Sudhakar for reporting this issue. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Tyler Nighswander (ForAllSecure) as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Robert Święcki (Google Security Team) as the original reporter. Red Hat would like to thank the OpenSSL project for reporting this issue. This issue was discovered by QCI QE Team (Red Hat). Red Hat would like to thank Federico Dotta (Mediaservice.net) and Maurizio Agazzini (Mediaservice.net) for reporting this issue. This issue was discovered by Florian Weimer (Red Hat). Red Hat would like to thank the Foreman project for reporting this issue. Upstream acknowledges Jitendra Yejare as the original reporter. Red Hat would like to thank the Foreman project for reporting this issue. Upstream acknowledges Daniel Lobato Garcia as the original reporter. Red Hat would like to thank Grisha Levit for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jérémie Boutoille (Quarkslab) and Shangcong Luan (Alibaba Cloud) as the original reporters. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Brian Marcotte as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Andrew Cooper (Citrix) as the original reporter. This issue was discovered by Andreas Gruenbacher (Red Hat) and Jan Kara (SUSE). Red Hat would like to thank Felix Wilhelm (ERNW) for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Mikhail Gorobets (Advanced Threat Research; Intel Security) as the original reporter. Red Hat would like to thank Li Qiang (360.cn Inc.) and Victor V (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Victor V (360.cn Marvel Team) for reporting this issue. Red Hat would like to thank Qinghao Tang and Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank the upstream Django project for reporting this issue. Red Hat would like to thank Li Qiang and Victor V (360.cn Inc.) for reporting this issue. Red Hat would like to thank Qinghao Tang (360.cn Marvel Team) and Zhenhao Hong (360.cn Marvel Team) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank Alain Moulle (ATOS/BULL) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Inc.) for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. This issue was discovered by Kirill Gaevskii (Red Hat). Red Hat would like to thank Hiroyuki Wada (Nomura Research Institute) for reporting this issue. Red Hat would like to thank Shi Lei (Gear Team of Qihoo 360 Inc.) for reporting this issue. This issue was discovered by Luke Hinds (Red Hat). This issue was discovered by Sanket Jagtap (Red Hat). This issue was discovered by Darran Lofthouse (Red Hat) and Brian Stansberry (Red Hat). This issue was discovered by Michael Scherer (Red Hat). This issue was discovered by Jordan Liggitt (Red Hat). Red Hat would like to thank Qian Zhang from Qihoo 360 Marvel Team for reporting this issue. Red Hat would like to thank Eyal Itkin for reporting this issue. This issue was discovered by Sanket Jagtap (Red Hat). This issue was discovered by Hubert Kario (Red Hat). Red Hat would like to thank Andreas Stieger (SUSE Security Team) for reporting this issue. This issue was discovered by Patrick Uiterwijk (Red Hat) and Howard Johnson. This issue was discovered by Sanket Jagtap (Red Hat). Red Hat would like to thank Vincent Malguy for reporting this issue. Red Hat would like to thank Marco Grassi for reporting this issue. Red Hat would like to thank Igor Redko (Virtuozzo kernel team) for reporting this issue. This issue was discovered by Jason Shepherd (Red Hat). This issue was discovered by Jason Shepherd (Red Hat). Red Hat would like to thank Liu Bingchang (IIE) for reporting this issue. Red Hat would like to thank Philip Pettersson for reporting this issue. Red Hat would like to thank PSIRT (Huawei Inc.) for reporting this issue. Red Hat would like to thank PSIRT (Huawei Inc.) for reporting this issue. Red Hat would like to thank PSIRT (Huawei Inc.) for reporting this issue. This issue was discovered by Florian Weimer (Red Hat). Red Hat would like to thank Shi Lei (Qihoo 360) for reporting this issue. Red Hat would like to thank ISC for reporting this issue. Upstream acknowledges Tony Finch (University of Cambridge) and Marco Davids (SIDN Labs) as the original reporters. Red Hat would like to thank PSIRT (Huawei Inc.) for reporting this issue. Red Hat would like to thank Andrew Henderson (Intelligent Automation Inc.) for reporting this issue. Red Hat would like to thank the Django project for reporting this issue. Red Hat would like to thank the Django project for reporting this issue. Red Hat would like to thank the NTP project for reporting this issue. Upstream acknowledges Matthew Van Gundy (Cisco) as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Gustavo Grieco as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Samuel Groß as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abdulrahman Alqabandi as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Xiaoyin Liu as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Will Bamberg as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Franziskus Kiefer as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Kris Maglione as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mats Palmgren as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Markus Stange as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Red Hat would like to thank Gustavo Grieco for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank ISC for reporting this issue. Red Hat would like to thank ISC for reporting this issue. This issue was discovered by Doran Moppert (Red Hat Product Security Team). This issue was discovered by Doran Moppert (Red Hat Product Security Team). Red Hat would like to thank the Pillow project for reporting this issue. Red Hat would like to thank the Pillow project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Andrew Cooper (Citrix) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Andrew Cooper (Citrix) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Daniel Richman (the Cambridge University Student-Run Computing Facility) and Gábor Szarka (the Cambridge University Student-Run Computing Facility) as the original reporters. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Daniel Richman (the Cambridge University Student-Run Computing Facility) and Gábor Szarka (the Cambridge University Student-Run Computing Facility) as the original reporters. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges yanghongke (Huawei Security Test Team) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich (SUSE) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges George Dunlap (Citrix) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Roger Pau Monné (Citrix) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Andrew Cooper (Citrix) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Andrew Cooper (Citrix) as the original reporter. Red Hat would like to thank ISC for reporting this issue. Red Hat would like to thank Liu Bingchang (IIE) for reporting this issue. Red Hat would like to thank Liu Bingchang (IIE) for reporting this issue. This issue was discovered by Liam Campbell (Red Hat). This issue was discovered by Frediano Ziglio (Red Hat). This issue was discovered by Frediano Ziglio (Red Hat). Red Hat would like to thank chunibalon (chunibalon of VARAS@IIE) for reporting this issue. Red Hat would like to thank chunibalon (VARAS@IIE) for reporting this issue. Red Hat would like to thank Liu Bingchang (IIE) for reporting this issue. This issue was discovered by Jason Shepherd (Red Hat). Red Hat would like to thank Daniel Stenberg for reporting this issue. Red Hat would like to thank Gabriel Lavoie (Halogen Software) for reporting this issue. Red Hat would like to thank Hans Feldt (Ericsson) for reporting this issue. Red Hat would like to thank Liu Bingchang (IIE) for reporting this issue. This issue was discovered by Pavel Moravec (Red Hat). Red Hat would like to thank Daniel Stenberg for reporting this issue. Upstream acknowledges Kamil Dudka (Red Hat) as the original reporter. This issue was discovered by Evgeni Golov (Red Hat). This issue was discovered by Ben Nemec (Red Hat). Red Hat would like to thank Liu Bingchang (IIE) for reporting this issue. Red Hat would like to thank Bingchang Liu (IIE) for reporting this issue. Red Hat would like to thank Jann Horn (Google Project Zero) for reporting this issue. This issue was discovered by David Howells (Red Hat). Red Hat would like to thank Moritz Bechler (AgNO3 GmbH & Co. KG) for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. This issue was discovered by Doran Moppert (Red Hat Product Security). This issue was discovered by Qian Cai (Red Hat). Red Hat would like to thank Wjjzhang (tencent.com) for reporting this issue. Red Hat would like to thank ISC for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges ARM engineering personnel as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges ARM engineering personnel as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges ARM engineering personnel as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges ARM engineering personnel as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jan de Mooij, Iris Hsiao, Christian Holler, Carsten Book, Timothy Nikkel, Christoph Diehl, Olli Pettay, Raymond Forbes, and Boris Zbarsky as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Andrew Krasichkov as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Aral as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges insertscript as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Wladimir Palant as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Wladimir Palant as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jann Horn as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Philipp as the original reporter. Red Hat would like to thank Qinghao Tang (Qihoo 360), Li Qiang (Qihoo 360), and Jiangxin (Huawei Inc.) for reporting this issue. Red Hat would like to thank Qinghao Tang (Qihoo 360), Li Qiang (Qihoo 360), and Jiangxin (Huawei Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Docker project for reporting this issue. Upstream acknowledges Aleksa Sarai (SUSE) and Tõnis Tiigi (Docker) as the original reporters. Red Hat would like to thank Felix Wilhelm (Google Security Team) for reporting this issue. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Jesse Glick (CloudBees) as the original reporter. Red Hat would like to thank the Jenkins project for reporting this issue. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Jesse Glick (CloudBees) as the original reporter. Red Hat would like to thank the Jenkins project for reporting this issue. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Simon St John and Green as the original reporters. Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Even Rouault as the original reporter. Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Even Rouault as the original reporter. Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Brian Carpenter as the original reporter. Red Hat would like to thank Willem de Bruijn for reporting this issue. Red Hat would like to thank Andrey Konovalov for reporting this issue. Red Hat would like to thank the Mercurial Security Team for reporting this issue. Red Hat would like to thank the Subversion Team for reporting this issue. Red Hat would like to thank Thomas Jarosch (Intra2net AG) for reporting this issue. Red Hat would like to thank Armis Labs for reporting this issue. Red Hat would like to thank Armis Labs for reporting this issue. Red Hat would like to thank Jan H. Schönherr (Amazon) for reporting this issue. Red Hat would like to thank Qualys Research Labs for reporting this issue. Red Hat would like to thank Daniel Stenberg for reporting this issue. Upstream acknowledges Max Dymond as the original reporter. Red Hat would like to thank Michael Ellerman, Gustavo Romero, Breno Leitao, Paul Mackerras, and Cyril Bur for reporting this issue. This issue was discovered by Daniel P. Berrange (Red Hat). Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Brian Carpenter and the OSS-Fuzz project as the original reporters. Red Hat would like to thank the Jenkins project for reporting this issue. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Jesse Glick (CloudBees) as the original reporter. Red Hat would like to thank the Jenkins project for reporting this issue. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Steve Marlowe (Cisco ASIG) as the original reporter. Red Hat would like to thank OpenDaylight project for reporting this issue. Red Hat would like to thank OpenDaylight project for reporting this issue. Upstream acknowledges Andi Bidaj as the original reporter. Red Hat would like to thank OpenDaylight project for reporting this issue. Upstream acknowledges Andi Bidaj as the original reporter. Red Hat would like to thank OpenDaylight project for reporting this issue. Upstream acknowledges Andi Bidaj as the original reporter. Red Hat would like to thank OpenDaylight project for reporting this issue. Upstream acknowledges Andi Bidaj as the original reporter. Red Hat would like to thank Roee Hay (HCL Technologies) for reporting this issue. Red Hat would like to thank Qualys Research Labs for reporting this issue. Red Hat would like to thank Qualys Inc. for reporting this issue. Red Hat would like to thank Qualys Research Labs for reporting this issue. Red Hat would like to thank Qualys Security for reporting this issue. Red Hat would like to thank Qualys Inc for reporting this issue. Red Hat would like to thank Qualys Inc for reporting this issue. Red Hat would like to thank Qualys Inc for reporting this issue. Red Hat would like to thank Qualys Inc for reporting this issue. Red Hat would like to thank Alexander Potapenko (Google) for reporting this issue. Red Hat would like to thank Daniel Stenberg for reporting this issue. Upstream acknowledges LCatro as the original reporter. Red Hat would like to thank Eylon Ben Yaakov and Daniel Shapiro for reporting this issue. Red Hat would like to thank Vaibhav Hemant Dixit (Arizona State University) for reporting this issue. Red Hat would like to thank Qualys Research Labs for reporting this issue. Red Hat would like to thank Qualys Research Labs for reporting this issue. Red Hat would like to thank Armis Labs for reporting this issue. Red Hat would like to thank Vaibhav Hemant Dixit for reporting this issue. This issue was discovered by Joel Smith (Red Hat). Red Hat would like to thank Li Qiang (Qihoo 360 Gear Team) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Gear Team) for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Anthony Perard (Citrix) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jann Horn (Google) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jann Horn (Google) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jann Horn (Google) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Andrew Cooper (Citrix) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Andrew Cooper (Citrix) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Ankur Arora (Oracle) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Julien Grall (ARM) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Julien Grall (ARM) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich (SUSE) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich (SUSE) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich (SUSE) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Julien Grall (ARM) as the original reporter. Red Hat would like to thank the FreeRADIUS project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the FreeRADIUS project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the FreeRADIUS project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the FreeRADIUS project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the FreeRADIUS project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the FreeRADIUS project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the FreeRADIUS project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the FreeRADIUS project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the FreeRADIUS project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the FreeRADIUS project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the FreeRADIUS project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank Alex for reporting this issue. Red Hat would like to thank Reno Robert for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan H. Schönherr (Amazon) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich (SUSE) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Ian Jackson (Citrix) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Andrew Cooper (Citrix) as the original reporter. This issue was discovered by Ryan Petrello (Red Hat). Red Hat would like to thank Joao F M Figueiredo for reporting this issue. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Stefan Metzmacher (SerNet) as the original reporter. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Stefan Metzmacher (SerNet) as the original reporter. Red Hat would like to thank bo Zhang for reporting this issue. Red Hat would like to thank Jim Mattson (Google.com) for reporting this issue. Red Hat would like to thank Katuya Kawakami (NEC) for reporting this issue. Red Hat would like to thank Mykhailo Stadnyk (Playtech) for reporting this issue. Red Hat would like to thank Prapti Mittal for reporting this issue. Red Hat would like to thank Bart Toersche (Simacan) for reporting this issue. Red Hat would like to thank Yihan Lian and Zhibin Hu (Qihoo 360 Gear Team), Stefan Metzmacher (SerNet), and Jeremy Allison (Google) for reporting this issue. Red Hat would like to thank Tobias Guggenmos for reporting this issue. This issue was discovered by Stuart Douglas (Red Hat). Red Hat would like to thank the OpenVPN project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. This issue was discovered by Brian Stansberry (Red Hat) and Jeremy Choi (Red Hat). This issue was discovered by Rob Crittenden (Red Hat). Red Hat would like to thank KAWAHARA Masashi for reporting this issue. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Antoine Scemama (Brainloop) as the original reporter. This issue was discovered by Sumit Bose (Red Hat). This issue was discovered by Masafumi Miura (Red Hat). Red Hat would like to thank the Xorg project for reporting this issue. Red Hat would like to thank the Xorg project for reporting this issue. Red Hat would like to thank the Xorg project for reporting this issue. Red Hat would like to thank the Xorg project for reporting this issue. Red Hat would like to thank the Xorg project for reporting this issue. Red Hat would like to thank the Xorg project for reporting this issue. Red Hat would like to thank the Xorg project for reporting this issue. Red Hat would like to thank the Xorg project for reporting this issue. Red Hat would like to thank the Xorg project for reporting this issue. Red Hat would like to thank the Xorg project for reporting this issue. Red Hat would like to thank the Xorg project for reporting this issue. Red Hat would like to thank the Xorg project for reporting this issue. Red Hat would like to thank Vitaly Mayatskih for reporting this issue. This issue was discovered by Gellert Kis (Red Hat). Red Hat would like to thank Fan Wu (University of Hong Kong), Haoran Qiu (University of Hong Kong), Shixiong Zhao (University of Hong Kong), and Heming Cui (University of Hong Kong) for reporting this issue. This issue was discovered by Rich Megginson (Red Hat). This issue was discovered by Jan Stourac (Red Hat). This issue was discovered by Christian Heimes (Red Hat). Red Hat would like to thank the Varnish Cache project for reporting this issue. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Zane Bitter (Red Hat) as the original reporter. Red Hat would like to thank Ryan Salsamendi (Palo Alto Networks PSIRT) for reporting this issue. Red Hat would like to thank Sawyer X (Perl) for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich (SUSE) as the original reporter. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank CERT for reporting this issue. Upstream acknowledges Mathy Vanhoef (University of Leuven) as the original reporter. Red Hat would like to thank CERT for reporting this issue. Upstream acknowledges Mathy Vanhoef (University of Leuven) as the original reporter. Red Hat would like to thank CERT for reporting this issue. Upstream acknowledges Mathy Vanhoef (University of Leuven) as the original reporter. Red Hat would like to thank CERT for reporting this issue. Upstream acknowledges Mathy Vanhoef (University of Leuven) as the original reporter. Red Hat would like to thank CERT for reporting this issue. Upstream acknowledges Mathy Vanhoef (University of Leuven) as the original reporter. Red Hat would like to thank CERT for reporting this issue. Upstream acknowledges Mathy Vanhoef (University of Leuven) as the original reporter. Red Hat would like to thank CERT for reporting this issue. Upstream acknowledges Mathy Vanhoef (University of Leuven) as the original reporter. Red Hat would like to thank CERT for reporting this issue. Upstream acknowledges Mathy Vanhoef (University of Leuven) as the original reporter. Red Hat would like to thank CERT for reporting this issue. Upstream acknowledges Mathy Vanhoef (University of Leuven) as the original reporter. Red Hat would like to thank CERT for reporting this issue. Upstream acknowledges Mathy Vanhoef (University of Leuven) as the original reporter. Red Hat would like to thank the GNU Wget project for reporting this issue. Red Hat would like to thank the GNU Wget project for reporting this issue. Red Hat would like to thank David Buchanan for reporting this issue. Red Hat would like to thank David Buchanan for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank Wjjzhang (Tencent.com) for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank Thomas Garnier (Google.com) for reporting this issue. Red Hat would like to thank Matthew Daley for reporting this issue. Red Hat would like to thank Eric Chanudet (AIS) for reporting this issue. Red Hat would like to thank Matthew Daley for reporting this issue. Red Hat would like to thank Andrew Cooper (Citrix) for reporting this issue. This issue was discovered by Dave Chinner (Red Hat). Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Dovecot project for reporting this issue. Upstream acknowledges Aleksandar Nikolic (Cisco Talos) and flxflndy as the original reporters. This issue was discovered by ChunYu Wang (Red Hat). Red Hat would like to thank Felix Wilhelm (Google Security Team), Fermin J. Serna (Google Security Team), Gabriel Campana (Google Security Team), Kevin Hamacher (Google Security Team), and Ron Bowes (Google Security Team) for reporting this issue. Red Hat would like to thank Felix Wilhelm (Google Security Team), Fermin J. Serna (Google Security Team), Gabriel Campana (Google Security Team), Kevin Hamacher (Google Security Team), and Ron Bowes (Google Security Team) for reporting this issue. Red Hat would like to thank Felix Wilhelm (Google Security Team), Fermin J. Serna (Google Security Team), Gabriel Campana (Google Security Team), Kevin Hamacher (Google Security Team), and Ron Bowes (Google Security Team) for reporting this issue. Red Hat would like to thank Felix Wilhelm (Google Security Team), Fermin J. Serna (Google Security Team), Gabriel Campana (Google Security Team), Kevin Hamacher (Google Security Team), and Ron Bowes (Google Security Team) for reporting this issue. Red Hat would like to thank Felix Wilhelm (Google Security Team), Fermin J. Serna (Google Security Team), Gabriel Campana (Google Security Team), Kevin Hamacher (Google Security Team), and Ron Bowes (Google Security Team) for reporting this issue. Red Hat would like to thank Felix Wilhelm (Google Security Team), Fermin J. Serna (Google Security Team), Gabriel Campana (Google Security Team), Kevin Hamacher (Google Security Team), and Ron Bowes (Google Security Team) for reporting this issue. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Yihan Lian (Qihoo 360 Gear Team) and Zhibin Hu (Qihoo 360 Gear Team) as the original reporters. Red Hat would like to thank Tuomas Tynkkynen for reporting this issue. Red Hat would like to thank Man Yue Mo (Semmle/lgtm.com) for reporting this issue. Red Hat would like to thank Liao Xinxi (NSFOCUS) for reporting this issue. This issue was discovered by Pedro Barbosa (Red Hat) and the PostgreSQL project. Upstream acknowledges Antoine Scemama (Brainloop) as the original reporter. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges David Rowley as the original reporter. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Dean Rasheed as the original reporter. Red Hat would like to thank Samuel Thibault for reporting this issue. Red Hat would like to thank James Patrick Evans for reporting this issue. Red Hat would like to thank Markus Krell (NTT Security) for reporting this issue. This issue was discovered by Siddharth Sharma (Red Hat). Red Hat would like to thank Ralph Dolmans (NLnet Labs) and Karst Koymans (University of Amsterdam) for reporting this issue. Red Hat would like to thank Ralph Dolmans (NLnet Labs) and Karst Koymans (University of Amsterdam) for reporting this issue. Red Hat would like to thank Seth Arnold (Canonical) for reporting this issue. This issue was discovered by Jiri Belka (Red Hat). This issue was discovered by Daniel P. Berrange (Red Hat). This issue was discovered by ChunYu Wang (Red Hat). This issue was discovered by ChunYu Wang (Red Hat). This issue was discovered by Eric Blake (Red Hat). This issue was discovered by Eric Blake (Red Hat). This issue was discovered by Miklos Szeredi (Red Hat). This issue was discovered by Daniel Berrange (Red Hat). This issue was discovered by Yadnyawalk Tale (Red Hat). Red Hat would like to thank Kirill Tkhai for reporting this issue. Red Hat would like to thank The Dovecot Project for reporting this issue. Red Hat would like to thank The Dovecot Project for reporting this issue. Red Hat would like to thank the miekg-dns project for reporting this issue. This issue was discovered by Martin Poole (Red Hat). This issue was discovered by Jan Hutař (Red Hat). This issue was discovered by Ben Parees (Red Hat). This issue was discovered by Jessica Forrester (Red Hat). Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Volker Lendecke (SerNet and the Samba Team) as the original reporter. Red Hat would like to thank Guoxiang Niu (Huawei.com) for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jann Horn (Google) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Roger Pau Monné (Citrix) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Simon Gaiser (Qubes OS) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Vitaly Kuznetsov (Red Hat) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Andrew Cooper (Citrix) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich (SUSE) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Andrew Cooper (Citrix) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jann Horn (Google) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Pawel Wieczorkiewicz (Amazon) as the original reporter. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges George Shuklin (Servers.com) as the original reporter. Red Hat would like to thank the HTCondor project for reporting this issue. Red Hat would like to thank Cyrille Chatras (Orange.com) for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Julien Grall (Linaro) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges George Dunlap (Citrix) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Matt Riedemann (Huawei) as the original reporter. Red Hat would like to thank Huawei IT Network Security Alpha Lab and Dengzhan Heyuandong Bijunhua and Liweichao (Huawei Inc.) for reporting this issue. Red Hat would like to thank 0c0c0f from 360观星实验室 for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich (SUSE) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich (SUSE) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich (SUSE) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich (SUSE) as the original reporter. This issue was discovered by Eric Blake (Red Hat Inc.). Red Hat would like to thank chunibalon (VARAS@IIE) for reporting this issue. Red Hat would like to thank chunibalon (VARAS@IIE) for reporting this issue. Red Hat would like to thank chunibalon (VARAS@IIE) for reporting this issue. This issue was discovered by Hynek Mlnarik (Red Hat). Red Hat would like to thank Xiaohan Zhang (Huawei Inc.) for reporting this issue. Red Hat would like to thank Richard Kettelerij (Mindloops) for reporting this issue. Red Hat would like to thank chunibalon (VARAS@IIE) for reporting this issue. Red Hat would like to thank chunibalon (VARAS@IIE) for reporting this issue. This issue was discovered by Adam Willard (Blue Canopy) and Dennis Reed (Red Hat). This issue was discovered by Fraser Tweedale (Red Hat). Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Divya K Konoor (IBM) as the original reporter. This issue was discovered by Hooman Broujerdi (Red Hat). Red Hat would like to thank Dmitry Vyukov (Google Inc.) for reporting this issue. This issue was discovered by Dominic Geevarghes (Red Hat). Red Hat would like to thank Wjjzhang (Tencent.com Inc.) and Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Tobias Stöckmann for reporting this issue. This issue was discovered by Hooman Broujerdi (Red Hat). This issue was discovered by Paul Moore (Red Hat Engineering). Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Jann Horn (Google) as the original reporter. Red Hat would like to thank Hans Feldt (Ericsson) for reporting this issue. Red Hat would like to thank Hans Feldt (Ericsson) for reporting this issue. This issue was discovered by Colin Walters (Red Hat). Red Hat would like to thank Eric Sesterhenn (X41 D-Sec GmbH) for reporting this issue. Red Hat would like to thank Eric Sesterhenn (X41 D-Sec GmbH) for reporting this issue. Red Hat would like to thank Eric Sesterhenn (X41 D-Sec GmbH) for reporting this issue. This issue was discovered by Garth Mollett (Red Hat). This issue was discovered by Paulo Andrade (Red Hat). Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Marcus Hoffmann as the original reporter. This issue was discovered by Matouš Mojžíš (Red Hat). This issue was discovered by Wade Mealing (Red Hat Product Security). This issue was discovered by Yanqiu Zhang (Red Hat). Red Hat would like to thank Alexander Popov for reporting this issue. This issue was discovered by David Gurtner (Red Hat). This issue was discovered by Jonathan Mason (Red Hat). Red Hat would like to thank the Pidgin project for reporting this issue. Red Hat would like to thank Igor Redko (Virtuozzo) and Andrey Ryabinin (Virtuozzo) for reporting this issue. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Tim Otten (CiviCRM LLC) as the original reporter. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Caleb Tennis (CloudBees) as the original reporter. Red Hat would like to thank the Jenkins project for reporting this issue. Upstream acknowledges Caleb Tennis (CloudBees) as the original reporter. This issue was discovered by Martin Weiler (Red Hat). Red Hat would like to thank Microsoft for reporting this issue. This issue was discovered by Brad Buckingham (Red Hat). This issue was discovered by Cedric Buissart (Red Hat). This issue was discovered by Libor Pichler (Red Hat) and Martin Povolny (Red Hat). Red Hat would like to thank Siddharth Sharma for reporting this issue. This issue was discovered by Radim Hatlapatka (Red Hat). This issue was discovered by Tomas Strachota (Red Hat). Red Hat would like to thank Joachim Jabs (F24) for reporting this issue. Red Hat would like to thank the Dovecot project for reporting this issue. Red Hat would like to thank Gregory Ramsperger and Ryan Moak for reporting this issue. Red Hat would like to thank the Openstack project for reporting this issue. Upstream acknowledges Boris Bobrov (Mail.Ru) as the original reporter. Red Hat would like to thank Chris Hebert, Vikas Pandey, Harold Schliesske, and Ryan Stanley (Noblis) for reporting this issue. Red Hat would like to thank Aleksandar Nikolic (Cisco Talos) for reporting this issue. Red Hat would like to thank ISC for reporting this issue. Upstream acknowledges Ramesh Damodaran (Infoblox) and Aliaksandr Shubnik (Infoblox) as the original reporter. Red Hat would like to thank ISC for reporting this issue. Upstream acknowledges Oleg Gorokhov (Yandex) as the original reporter. Red Hat would like to thank ISC for reporting this issue. Red Hat would like to thank ISC for reporting this issue. Upstream acknowledges Mike Lalumiere (Dyn) as the original reporter. Red Hat would like to thank Internet Systems Consortium for reporting this issue. Upstream acknowledges Oli Schacher (Switch) as the original reporter. Red Hat would like to thank Internet Systems Consortium for reporting this issue. Upstream acknowledges Clement Berthaux (Synacktiv) as the original reporter. Red Hat would like to thank Internet Systems Consortium for reporting this issue. Upstream acknowledges Clement Berthaux (Synacktiv) as the original reporter. Red Hat would like to thank ISC for reporting this issue. Upstream acknowledges Jayachandran Palanisamy (Cygate AB) as the original reporter. Red Hat would like to thank CERT for reporting this issue. Upstream acknowledges Adi Sosnovich, Orna Grumberg, and Gabi Nakibly as the original reporters. This issue was discovered by Red Hat Product Security. This issue was discovered by Red Hat Product Security. Red Hat would like to thank Pali Rohár for reporting this issue. This issue was discovered by Red Hat Product Security. Red Hat would like to thank the OpenSSL project for reporting this issue. Upstream acknowledges Joe Orton (Red Hat) as the original reporter. Red Hat would like to thank Chris Salls for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Gary Kwong, André Bargull, Jan de Mooij, Tom Schuster, and Oriol as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Rh0 as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nicolas Grégoire as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jann Horn as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Armin Razmjou as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Muneaki Nishimura as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jerri Rice as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Filipe Gomes as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Boris Zbarsky, Christian Holler, Honza Bambas, Jon Coppeard, Randell Jesup, André Bargull, Kan-Ru Chen, and Nathan Froyd as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Rh0 as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Anton Eliasson as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ivan Fratric of Google Project Zero as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Anonymous as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges David Kohlbrenner as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Eric Lawrence of Chrome Security as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jerri Rice as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Chaitin Security Research Lab via Trend Micro's Zero Day Initiative as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mozilla developers and community as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Huzaifa Sidhpurwala as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nicolas Grégoire as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nicolas Grégoire as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nicolas Grégoire as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Chamal De Silva as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Chamal De Silva as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Chamal De Silva as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Chun Han Hsiao as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ivan Fratric (Google Project Zero) as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Anonymous working with Trend Micro's Zero Day Initiative as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jordi Chancel as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jose María Acuña as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Haik Aftandilian as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Paul Theriault as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Julian Hector as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Daniel Veditz as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Atte Kettunen as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ronald Crane as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Vladimir Klebanov and Franziskus Kiefer as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ivan Fratric (Google Project Zero) as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Takeshi Terada as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Heather Miller (Google Skia team) as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Anonymous as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Petr Cerny as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tyson Smith, Mats Palmgren, Philipp, Masayuki Nakano, Christian Holler, Andrew McCreight, Gary Kwong, André Bargull, Carsten Book, Jesse Schwartzentruber, Julian Hector, Marcia Knous, Ronald Crane, and Nils as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank the Tcpdump project for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) Jiangxin (PSIRT Huawei Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Jiang Xin (Huawei PSIRT) for reporting this issue. Red Hat would like to thank Google Project Zero for reporting this issue. Red Hat would like to thank Google Project Zero for reporting this issue. Red Hat would like to thank Google Project Zero for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Jiang Xin (Huawei) and Wjjzhang (Tencent) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Andrey Konovalov (Google) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank the SANE project for reporting this issue. Upstream acknowledges Kritphong Mongkhonvanit as the original reporter. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank the NTP project for reporting this issue. Upstream acknowledges Cure53 as the original reporter. Red Hat would like to thank the NTP project for reporting this issue. Upstream acknowledges Cure53 as the original reporter. Red Hat would like to thank the NTP project for reporting this issue. Upstream acknowledges Cure53 as the original reporter. Red Hat would like to thank the NTP project for reporting this issue. Upstream acknowledges Cure53 as the original reporter. Red Hat would like to thank the NTP project for reporting this issue. Upstream acknowledges Cure53 as the original reporter. Red Hat would like to thank the NTP project for reporting this issue. Upstream acknowledges Cure53 as the original reporter. Red Hat would like to thank the NTP project for reporting this issue. Upstream acknowledges Cure53 as the original reporter. Red Hat would like to thank the NTP project for reporting this issue. Upstream acknowledges Cure53 as the original reporter. Red Hat would like to thank the NTP project for reporting this issue. Upstream acknowledges Cure53 as the original reporter. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Chaitin Security Research Lab for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Django project for reporting this issue. Red Hat would like to thank the Django project for reporting this issue. Red Hat would like to thank Li Qiang (360.cn Inc.) for reporting this issue. Red Hat would like to thank Chris Hebert, Vikas Pandey, Harold Schliesske, and Ryan Stanley (Noblis) for reporting this issue. This issue was discovered by Jason Shepherd (Red Hat). This issue was discovered by Jason Shepherd (Red Hat). This issue was discovered by Evgeni Golov (Red Hat). Red Hat would like to thank Alexander Peslyak (Openwall) for reporting this issue. Red Hat would like to thank Bert Stel (SUSE) for reporting this issue. This issue was discovered by David Moreau Simard (Red Hat). Red Hat would like to thank Nick Shearer (Quest) for reporting this issue. Red Hat would like to thank Pádraig Brady for reporting this issue. Red Hat would like to thank the OpenVPN project for reporting this issue. Upstream acknowledges QuarksLab as the original reporter. Red Hat would like to thank the OpenVPN project for reporting this issue. Upstream acknowledges QuarksLab as the original reporter. This issue was discovered by Michael Scherer (Red Hat). This issue was discovered by Evgeni Golov (Red Hat). Red Hat would like to thank Shi Lei (Qihoo 360 Gear Team) for reporting this issue. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Robert Haas as the original reporter. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Daniel Gustafsson as the original reporter. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Andrew Wheelwright as the original reporter. Red Hat would like to thank Li Qiang (Qihoo 360) for reporting this issue. This issue was discovered by Tomas Mraz (Red Hat) and Thorsten Scherf (Red Hat). This issue was discovered by Katerina Novotna (Red Hat). Red Hat would like to thank Leo Gaspard for reporting this issue. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges steelo as the original reporter. Red Hat would like to thank Takeshi Nishimura (NEC) for reporting this issue. This issue was discovered by Michael Scherer (Red Hat). This issue was discovered by Gellert Kis (Red Hat). Red Hat would like to thank Ludwig Nussel (SUSE) for reporting this issue. This issue was discovered by Cedric Buissart (Red Hat). This issue was discovered by Jason Shepherd (Red Hat Product Security) and Katerina Novotna (Red Hat Quality Engineering). Red Hat would like to thank Joao Filho Matos Figueiredo for reporting this issue. This issue was discovered by David Caplan (Red Hat). This issue was discovered by Frediano Ziglio (Red Hat). This issue was discovered by Hubert Kario (Red Hat QE BaseOS Security team). Red Hat would like to thank the OpenVPN project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank Ryan Nauman (TruCode) for reporting this issue. Lukáš Hellebrandt (Red Hat) This issue was discovered by Jan Hutar (Red Hat). This issue was discovered by Cedric Buissart (Red Hat). This issue was discovered by Matt Wringe (Red Hat). Red Hat would like to thank Stan K for reporting this issue. Red Hat would like to thank the OpenVPN project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the OpenVPN project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank the OpenVPN project for reporting this issue. Upstream acknowledges Guido Vranken as the original reporter. Red Hat would like to thank William Roberts (Intel) for reporting this issue. Upstream acknowledges Imran Desai (Intel) as the original reporter. Red Hat would like to thank Liao Xinxi (NSFOCUS) for reporting this issue. Red Hat would like to thank the Libgcrypt project for reporting this issue. This issue was discovered by Alberto Gonzalez (Red Hat). Red Hat would like to thank the Nginx project for reporting this issue. This issue was discovered by Tim Wade (Red Hat). Red Hat would like to thank Leilei Lin (Alibaba Group), Fan Wu (The University of Hong Kong), Shixiong Zhao (The University of Hong Kong), Shankara Pailoor (Columbia University), and Andrew Aday (Columbia University) for reporting this issue. Red Hat would like to thank Jeandre Le Roux (LSD Information Technology) for reporting this issue. This issue was discovered by Sanket Jagtap (Red Hat). This issue was discovered by Gunnar Morling (Red Hat). This issue was discovered by Christina Fu (Red Hat). This issue was discovered by Ales Dujicek (Red Hat). This issue was discovered by Tomer Brisker (Red Hat). This issue was discovered by Paul Needle (Red Hat). Red Hat would like to thank Lili Xu (Chinese Acadamy of Sciences) and Bingchang Liu (Chinese Acadamy of Sciences) for reporting this issue. Red Hat would like to thank Man Yue Mo (Semmle) for reporting this issue. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Ben de Graaff, Jelte Fennema, and Jeroen van der Ham as the original reporters. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Jeff Janes as the original reporter. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Chapman Flack as the original reporter. This issue was discovered by Matthew Booth (Red Hat). Red Hat would like to thank Stefano Mazzucco (Kirontech) for reporting this issue. Red Hat would like to thank Tomas Rzepka for reporting this issue. Red Hat would like to thank Tomas Rzepka for reporting this issue. Red Hat would like to thank Tomas Rzepka for reporting this issue. This issue was discovered by Han Han (Red Hat). Red Hat would like to thank the PowerDNS project for reporting this issue. Upstream acknowledges Nixu as the original reporter. This issue was discovered by Stefano Brivio (Red Hat). This issue was discovered by Stuart Douglas (Red Hat). This issue was discovered by Jason Shepherd (Red Hat Product Security). Red Hat would like to thank Jiangxin (PSIRT Huawei Inc.) for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges SkyLined as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges F. Alonso (revskills) as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nicolas Trippar (Zimperium zLabs) as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Samuel Erb as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek and Tyson Smith as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mozilla developers and community as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mozilla developers and community as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Antonio Sanso as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Amit Sangra as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Oliver Wagner as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Muneaki Nishimura as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Muneaki Nishimura as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jose María Acuña as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Fraser Tweedale as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abhishek Arya as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jann Horn as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Anne van Kesteren as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Frederik Braun as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Frederik Braun as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Looben Yang as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Rhys Enniks as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Martin Thomson as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mathias Karlsson as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jun Kokatsu as the original reporter. Red Hat would like to thank The Mozilla Project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christoph Diehl, Jan de Mooij, Jason Kratzer, Randell Jesup, Tom Ritter, Tyson Smith, and Sebastian Hengst as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges François Marier as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jun Kokatsu as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Omair and Andre Weissflog as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Khalil Zhani as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, David Keeler, Jon Coppeard, Julien Cristau, Jan de Mooij, Jason Kratzer, Philipp, Nicholas Nethercote, Oriol Brufau, André Bargull, Bob Clary, Jet Villegas, Randell Jesup, Tyson Smith, Gary Kwong, and Ryan VanderMeulen as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Sabri Haddouche as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jun Kokatsu as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Konark as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges cure53 as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges cure53 as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges cure53 as the original reporter. Red Hat would like to thank Dai Ge (Chinese Academy of Sciences) for reporting this issue. Red Hat would like to thank Ari Kauppi for reporting this issue. Red Hat would like to thank Jiaqi Peng (Chinese Academy of Sciences) for reporting this issue. Red Hat would like to thank Dai Ge (Chinese Academy of Sciences) for reporting this issue. Red Hat would like to thank Jiangxin (PSIRT Huawei Inc.) and Li Qiang (Qihoo 360 Gear Team) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Gear Team) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Gear Team) YY Z(Researcher) for reporting this issue. Red Hat would like to thank Jiang Xin (Huawei PSIRT) for reporting this issue. Red Hat would like to thank Jiang Xin (Huawei PSIRT) for reporting this issue. Red Hat would like to thank YY Z(Researcher) Wjjzhang (Tencent.com Inc.) for reporting this issue. Red Hat would like to thank Sebastian Krahmer (SUSE) for reporting this issue. Red Hat would like to thank the Varnish project for reporting this issue. Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Alex Nichols as the original reporter. Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges the OSS-Fuzz project as the original reporter. Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges John Schoenick as the original reporter. Red Hat would like to thank Mohamed Ghannam for reporting this issue. Red Hat would like to thank Sebastian Krahmer (SUSE) for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jann Horn (Google) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jann Horn (Google) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jann Horn (Google) as the original reporter. Red Hat would like to thank Mamoru Tasaka for reporting this issue. Red Hat would like to thank Mamoru Tasaka for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Gear Team) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Gear Team) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Gear Team) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Gear Team) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Gear Team) for reporting this issue. Red Hat would like to thank Li Qiang (Qihoo 360 Gear Team) for reporting this issue. Red Hat would like to thank Chris Coulson (Canonical) for reporting this issue. Red Hat would like to thank Zhangyanyu for reporting this issue. This issue was discovered by Colin Walters (Red Hat). Red Hat would like to thank Hanno Böck for reporting this issue. Red Hat would like to thank the Subversion Team for reporting this issue. Red Hat would like to thank OWL337 Team for reporting this issue. Red Hat would like to thank the Curl project for reporting this issue. Red Hat would like to thank Ben Adams (Illyriad Games) for reporting this issue. Red Hat would like to thank halfdog for reporting this issue. Red Hat would like to thank Ralph Dolmans (NLnet Labs) and Karst Koymans (University of Amsterdam) for reporting this issue. Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Zhouyihai Ding as the original reporter. Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Craig de Stigter as the original reporter. Red Hat would like to thank R. Freingruber (SEC Consult Vulnerability Lab) for reporting this issue. Red Hat would like to thank R. Freingruber (SEC Consult Vulnerability Lab) for reporting this issue. Red Hat would like to thank R. Freingruber (SEC Consult Vulnerability Lab) for reporting this issue. Red Hat would like to thank R. Freingruber (SEC Consult Vulnerability Lab) for reporting this issue. Red Hat would like to thank R. Freingruber (SEC Consult Vulnerability Lab) for reporting this issue. Red Hat would like to thank Debashis Pradhan (Huawei Technologies) for reporting this issue. This issue was discovered by Han Han (Red Hat). Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Duy Phan Thanh as the original reporter. Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Dario Weisser as the original reporter. Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Max Dymond as the original reporter. Red Hat would like to thank Rainer Gerhards (rsyslog) for reporting this issue. Upstream acknowledges Bas van Schaik (lgtm.com / Semmle) and Kevin Backhouse (lgtm.com / Semmle) as the original reporters. Red Hat would like to thank the Nghttp2 project for reporting this issue. Red Hat would like to thank Andy Lutomirski for reporting this issue. Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Dario Weisser as the original reporter. Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges the OSS-fuzz project as the original reporter. This issue was discovered by OpenShift team (Red Hat). This issue was discovered by Lubomir Rintel (Red Hat). Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Danny Grander (Snyk) for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Andrew Cooper (Citrix) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Anthony Perard (Citrix) as the original reporter. Red Hat would like to thank the Samba project for reporting this issue. Red Hat would like to thank Rui Chong (Baidu) for reporting this issue. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Álvaro Herrera and David Rowley as the original reporters. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Tom Lane as the original reporter. Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Björn Baumbach (Sernet) as the original reporter. This issue was discovered by Maxime Coquelin (Red Hat). Red Hat would like to thank the Python security response team for reporting this issue. Red Hat would like to thank the Python security response team for reporting this issue. This issue was discovered by Idan Shaby (Red Hat). This issue was discovered by Renaud Métrich (Red Hat). This issue was discovered by Daniel P. Berrange (Red Hat). Red Hat would like to thank Ammarit Thongthua (Deloitte Thailand Pentest team) and Nattakit Intarasorn (Deloitte Thailand Pentest team) for reporting this issue. Red Hat would like to thank Jean-marie Bourbon (Excellium-Services) and Anthony Maia (Excellium-Services) for reporting this issue. Red Hat would like to thank Jean-marie Bourbon (Excellium-Services) and Anthony Maia (Excellium-Services) for reporting this issue. Red Hat would like to thank Andreas Skoglund (Basefarm AS) for reporting this issue. This issue was discovered by Mark Chappell (Red Hat). This issue was discovered by Richard Maciel Costa (Red Hat). This issue was discovered by Yedidyah Bar David (Red Hat). Red Hat would like to thank chenyuan (NESA Lab) for reporting this issue. This issue was discovered by Yedidyah Bar David (Red Hat). Red Hat would like to thank chenyuan (NESA Lab) for reporting this issue. Red Hat would like to thank Vaibhav Hemant Dixit (Arizona State University) for reporting this issue. This issue was discovered by Ondrej Mular (Red Hat). This issue was discovered by Fraser Tweedale (Red Hat). This issue was discovered by Richard Maciel Costa (Red Hat). Red Hat would like to thank Daniel Shapira (Twistlock) and Arash Tohidi for reporting this issue. Red Hat would like to thank Citrix Security Response Team for reporting this issue. This issue was discovered by Jeremy Choi (Red Hat). Red Hat would like to thank David Hocky (Comcast) for reporting this issue. This issue was discovered by Thierry Bordaz (Red Hat). This issue was discovered by Jakub Hrozek (Red Hat). Red Hat would like to thank Andy Lutomirski and Mika Penttilä for reporting this issue. Red Hat would like to thank Tobias Henkel (BMW Car IT GmbH) for reporting this issue. This issue was discovered by Cedric Buissart (Red Hat). This issue was discovered by Doran Moppert (Red Hat). This issue was discovered by Riccardo Schirone (Red Hat Product Security). This issue was discovered by Riccardo Schirone (Red Hat Product Security). This issue was discovered by Riccardo Schirone (Red Hat Product Security). This issue was discovered by Riccardo Schirone (Red Hat Product Security). This issue was discovered by Riccardo Schirone (Red Hat Product Security). This issue was discovered by Riccardo Schirone (Red Hat Product Security). This issue was discovered by Riccardo Schirone (Red Hat Product Security). Red Hat would like to thank Andy Lutomirski for reporting this issue. This issue was discovered by Riccardo Schirone (Red Hat Product Security). This issue was discovered by Frediano Ziglio (Red Hat). Red Hat would like to thank Michael Scherer (OSAS) for reporting this issue. This issue was discovered by Brian Coca (Red Hat). This issue was discovered by John Strunk (Red Hat). This issue was discovered by Chris Meyers (Red Hat). Red Hat would like to thank Taichi Kageyama (NEC) for reporting this issue. Red Hat would like to thank Riccardo Schirone (Product Security Red Hat) for reporting this issue. Red Hat would like to thank Riccardo Schirone (Product Security Red Hat) for reporting this issue. Red Hat would like to thank Greg Kubok for reporting this issue. This issue was discovered by Antonio Murdaca (Red Hat). This issue was discovered by Frediano Ziglio (Red Hat). This issue was discovered by Benjamin Berg (Red Hat). Red Hat would like to thank Jay Grizzard (Clover Network) and Aaron Levy (Clover Network) for reporting this issue. Red Hat would like to thank Vegard Nossum (Oracle Corporation) for reporting this issue. Red Hat would like to thank Trend Micro Zero Day Initiative for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Stephen Gappinger (American Express) for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. This issue was discovered by Nir Soffer (Red Hat). Red Hat would like to thank Chris Marchesi for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Andrew Krasichkov as the original reporter. Red Hat would like to thank Simon Baatz (Telekom Deutschland GmbH) for reporting this issue. Red Hat would like to thank Volker Mauel (the Samba project) for reporting this issue. Red Hat would like to thank Phillip Kuhrt (the Samba project) for reporting this issue. Red Hat would like to thank Wen Xu for reporting this issue. Red Hat would like to thank Petr Spacek and the CZ.NIC team for reporting this issue. Upstream acknowledges Marek Vavruza as the original reporter. This issue was discovered by Scott Gayou (Red Hat). This issue was discovered by Scott Gayou (Red Hat). Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank the PostgreSQL project for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Wen Xu for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. This issue was discovered by Cedric Buissart (Red Hat). This issue was discovered by Aaron Conole (Red Hat). Red Hat would like to thank the libssh team for reporting this issue. Upstream acknowledges Peter Winter-Smith (NCC Group) as the original reporter. Red Hat would like to thank Jakub Palaczynski for reporting this issue. Red Hat would like to thank the PostgreSQL project for reporting this issue. This issue was discovered by Sam Padgett (Red Hat). Red Hat would like to thank Wen Xu for reporting this issue. Red Hat would like to thank Wen Xu for reporting this issue. This issue was discovered by Martin Povolny (Red Hat). Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich (SUSE) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Roger Pau Monné (Citrix) as the original reporter. This issue was discovered by Richard Maciel Costa (Red Hat). This issue was discovered by Graham Mainwaring (Red Hat). Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Michael Hanselmann (Independent) for reporting this issue. Red Hat would like to thank Simon Vikström for reporting this issue. Red Hat would like to thank Matthias Gerstner (SUSE) for reporting this issue. Red Hat would like to thank Felix Wilhelm (Google Security Team) for reporting this issue. Red Hat would like to thank the PostgreSQL project for reporting this issue. Upstream acknowledges Stephen Frost as the original reporter. Red Hat would like to thank Qualys Research Labs for reporting this issue. Red Hat would like to thank Qualys Research Labs for reporting this issue. Red Hat would like to thank Qualys Research Labs for reporting this issue. Red Hat would like to thank Qualys Research Labs for reporting this issue. Red Hat would like to thank Qualys Research Labs for reporting this issue. Red Hat would like to thank Qualys Research Labs for reporting this issue. Red Hat would like to thank Qualys Research Labs for reporting this issue. This issue was discovered by Filip Balák (Red Hat). Red Hat would like to thank Evgenii Shatokhin (Virtuozzo Team) for reporting this issue. Red Hat would like to thank Feng Xiao (Wuhan University) and Jianwei Huang (Wuhan University) for reporting this issue. This issue was discovered by Vivek Das (Red Hat). Red Hat would like to thank Laurent Debomy and Andrej Gessel and Kai Blin (The samba project) for reporting this issue. Red Hat would like to thank Jskz - Zero Day Initiative (trendmicro.com) for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ben Kelly as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges R as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges F. Alonso (revskills) as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges David Black as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Alex Gaynor as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges OSS-Fuzz as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Andrea Marchesini as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abdulrahman Alqabandi as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jonathan Kingston as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jun Kokatsu as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges anonymous as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Jesse Ruderman, Sebastian Hengst, Nicolas Grunbaum, and Gary Kwong as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Alex Gaynor, Boris Zbarsky, Christoph Diehl, Christian Holler, Jason Kratzer, Jed Davis, Tyson Smith, Bogdan Tara, Karl Tomlinson, Mats Palmgren, Nika Layzell, and Ted Campbell as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Zhanjia Song as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Holger Fuhrmannek as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jana Squires as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jordi Chancel as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jurgen Gaeremyn as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Philipp as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Niklas Baumstark, Samuel Groß, and Bruno Keith via Beyond Security's SecuriTeam Secure Disclosure program as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Niklas Baumstark and Bruno Keith via Beyond Security's SecuriTeam Secure Disclosure program as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Daniel Veditz and Philipp as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Bob Owen, Boris Zbarsky, Calixte Denizet, Jason Kratzer, Jed Davis, Taegeon Lee, Philipp, Ronald Crane, Raul Gurzau, Gary Kwong, Tyson Smith, Raymond Forbes, and Bogdan Tara as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jun Kokatsu as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges r as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Rob Wu and Andrew Swan as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Rob Wu as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Rob Wu as the original reporter. Red Hat would like to thank Fakhri Zulkifli for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich (SUSE) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Andrew Cooper (Citrix) as the original reporter. Red Hat would like to thank Hosein Askari for reporting this issue. Red Hat would like to thank Chris Coulson (Ubuntu Security) for reporting this issue. Red Hat would like to thank the Curl project and Daniel Stenberg for reporting this issue. Upstream acknowledges Zhaoyang Wu as the original reporter. This issue was discovered by Florian Weimer (Red Hat) and Ondrej Mosnacek (Red Hat). Red Hat would like to thank Lars Haugan for reporting this issue. Red Hat would like to thank Vincent Pelletier for reporting this issue. Red Hat would like to thank Qualys Research Labs for reporting this issue. This issue was discovered by Viktor Ashirov (Red Hat). This issue was discovered by Ivan Necas (Red Hat). Red Hat would like to thank Tim Düsterhus and Willy Tarreau for reporting this issue. Red Hat would like to thank the Python Security Response Team for reporting this issue. This issue was discovered by Riccardo Schirone (Red Hat Product Security). Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. Red Hat would like to thank Michael Hanselmann (hansmi.ch) for reporting this issue. This issue was discovered by Sanket Jagtap (Red Hat Pune India). Red Hat would like to thank Narendra Shinde for reporting this issue. Red Hat would like to thank M. Vefa Bicakci and the Xen project for reporting this issue. Upstream acknowledges Andy Lutorminski as the original reporter. Red Hat would like to thank Jeffery M for reporting this issue. Upstream acknowledges GNOME Project as the original reporter. Red Hat would like to thank Giorgi Maisuradze (Saarland University), Christian Rossow (Saarland University), Nael Abu-Ghazaleh (University of California), Esmaiel Mohammadian Koruyeh (University of California), Khaled Khasawneh (University of California), and Chengyu Song (University of California) for reporting this issue. Red Hat would like to thank Ubuntu and Jann Horn (Google Project Zero) for reporting this issue. Red Hat would like to thank Ubuntu and Jann Horn (Google Project Zero) for reporting this issue. Red Hat would like to thank Ubuntu Security Team for reporting this issue. Upstream acknowledges Felix Wilhelm (Google) as the original reporter. Red Hat would like to thank Jann Horn (Google.com) for reporting this issue. Red Hat would like to thank Tavis Ormandy (Google Project Zero) for reporting this issue. Red Hat would like to thank Tavis Ormandy (Google Project Zero) for reporting this issue. Red Hat would like to thank Tavis Ormandy (Google Project Zero) for reporting this issue. Red Hat would like to thank Tavis Ormandy (Google Project Zero) for reporting this issue. Red Hat would like to thank Tavis Ormandy (Google Project Zero) for reporting this issue. Red Hat would like to thank Tavis Ormandy (Google Project Zero) for reporting this issue. Red Hat would like to thank Markus Teufelberger (mgIT Consulting) for reporting this issue. Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Harry Sintonen as the original reporter. Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Brian Carpenter (Geeknik Labs) as the original reporter. Red Hat would like to thank the Curl project for reporting this issue. Upstream acknowledges Brian Carpenter (Geeknik Labs) as the original reporter. Red Hat would like to thank Li Qiang for reporting this issue. Red Hat would like to thank Daniel Shapira (Twistlock) and Arash Tohidi for reporting this issue. Red Hat would like to thank Daniel Shapira (Twistlock) and Arash Tohidi for reporting this issue. Red Hat would like to thank Daniel Shapira (Twistlock) for reporting this issue. Red Hat would like to thank Arash Tohidi for reporting this issue. Red Hat would like to thank Deja vu Security (dejavusecurity.com) for reporting this issue. This issue was discovered by Red Hat Product Security. This issue was discovered by Red Hat Product Security. Red Hat would like to thank Intel OSSIRT (Intel.com) for reporting this issue. Red Hat would like to thank Ken Johnson (Microsoft Security Response Center) and Jann Horn (Google Project Zero) for reporting this issue. Red Hat would like to thank Intel OSSIRT (Intel.com) for reporting this issue. Red Hat would like to thank Julian Stecklina (Amazon.de), Thomas Prescher (cyberus-technology.de), and Zdenek Sojka (sysgo.com) for reporting this issue. Red Hat would like to thank Vladimir Kiriansky (MIT) and Carl Waldspurger (Carl Waldspurger Consulting) for reporting this issue. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Jason Kratzer, Marcia Knous, Nathan Froyd, Oriol Brufau, Ronald Crane, Randell Jesup, Tyson Smith, Cobos Álvarez, Ryan VanderMeulen, Sebastian Hengst, Karl Tomlinson, Xidorn Quan, Ludovic Hirlimann, and Jason Orendorff as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Looben Yang as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Anonymous as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Xisigr as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Bob Clary, Olli Pettay, Christian Holler, Nils Ohlmeier, Randell Jesup, Tyson Smith, Ralph Giles, and Philipp as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges James Grant as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tony Paloma as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ben Kelly as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Root Object as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jet Villegas and Randell Jesup as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Richard Zhu via Trend Micro's Zero Day Initiative as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christoph Diehl, Randell Jesup, Tyson Smith, Alex Gaynor, Ronald Crane, Julian Hector, Kannan Vijayan, and Jason Kratzer as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christoph Diehl, Christian Holler, Jon Coppeard, Jason Kratzer, Nathan Froyd, Paul Theriault, Ryan VanderMeulen, Tyson Smith, Sebastian Hengst, Byron Campen, Emilio Cobos Álvarez, Ronald Crane, and Phillipp as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Andy McKay as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Dennis Fuchs as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Wladimir Palant as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Wladimir Palant as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Ivan Fratric as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Andreas Perhson as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nicolas B and Pierron as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Khalil Zhani as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges David Parks as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Francois Lajeunesse Robert as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Wladimir Palant as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Wladimir Palant as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abdulrahman Alqabandi as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abdulrahman Alqabandi as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abdulrahman Alqabandi as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jimmy as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Masato Kinugawa as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Tadj Youssouf as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Guyio as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Root Object as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Nils as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Abdulrahman Alqabandi as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Jordi Chancel as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Mozilla Developers as the original reporter. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Jason Kratzer, Jon Coppeard, Randell Jesup, Ronald Crane, and Boris Zbarsky as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Christian Holler, Sebastian Hengst, Nils Ohlmeier, Jon Coppeard, Randell Jesup, Ted Campbell, Gary Kwong, and Jean-Yves Avenard as the original reporters. Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges Alex Gaynor, Christoph Diehl, Christian Holler, Jason Kratzer, David Major, Jon Coppeard, Nicolas B. Pierron, Marcia Knous, and Ronald Crane as the original reporters. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Andrew Cooper (Citrix) as the original reporter. Red Hat would like to thank the Quagga project for reporting this issue. Red Hat would like to thank the Quagga project for reporting this issue. Red Hat would like to thank the Quagga project for reporting this issue. Red Hat would like to thank the Quagga project for reporting this issue. Red Hat would like to thank CERT for reporting this issue. Red Hat would like to thank Juha-Matti Tilli (Aalto University - Department of Communications and Networking and Nokia Bell Labs) for reporting this issue. Red Hat would like to thank Juha-Matti Tilli (Aalto University - Department of Communications and Networking and Nokia Bell Labs) for reporting this issue. Red Hat would like to thank Jiang Xin and Lin ZheCheng for reporting this issue. Red Hat would like to thank ISC for reporting this issue. Upstream acknowledges Felix Wilhelm (Google) as the original reporter. Red Hat would like to thank ISC for reporting this issue. Upstream acknowledges Felix Wilhelm (Google) as the original reporter. Red Hat would like to thank ISC for reporting this issue. Red Hat would like to thank ISC for reporting this issue. Red Hat would like to thank ISC for reporting this issue. Upstream acknowledges Tony Finch (University of Cambridge) as the original reporter. This issue was discovered by Daniel P. Berrange (Red Hat) and Peter Krempa (Red Hat). Red Hat would like to thank Perl 5 Porters for reporting this issue. Upstream acknowledges Brian Carpenter as the original reporter. Red Hat would like to thank Perl 5 Porters for reporting this issue. Upstream acknowledges Nguyen Duc Manh as the original reporter. Red Hat would like to thank Perl 5 Porters for reporting this issue. Upstream acknowledges GwanYeong Kim as the original reporter. Red Hat would like to thank the Django project for reporting this issue. Red Hat would like to thank the Django project for reporting this issue. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jann Horn (Google) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Jan Beulich (SUSE) as the original reporter. Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Ian Jackson (Citrix) as the original reporter. Red Hat would like to thank Cyrille Chatras (Orange.com) and CERT-CC (Orange.com) for reporting this issue. Red Hat would like to thank Ross Lagerwall (Citrix.com) for reporting this issue. This issue was discovered by Coty Sutherland (Red Hat). This issue was discovered by Coty Sutherland (Red Hat). Red Hat would like to thank Eedo Shapira (GE Digital) for reporting this issue. Red Hat would like to thank Chris McCown for reporting this issue. Red Hat would like to thank Microsoft for reporting this issue. Red Hat would like to thank Nick Peterson (Everdox Tech LLC) and Andy Lutomirski for reporting this issue. Red Hat would like to thank Billy Bob Brumley, Cesar Pereida Garcia, Sohaib ul Hassan, Nicola Tuveri (Tampere University of Technology; Finland), and Alejandro Cabrera Aldaya (Universidad Tecnologica de la Habana CUJAE; Cuba) for reporting this issue. This issue has been addressed in nfs-server packages as shipped in Red Hat Linux since version nfs-server-2.2beta37. Not vulnerable. This flaw is specific to statd on Solaris, IRIX, Unixware and AIX platforms. Not vulnerable. This flaw is specific to statd on Solaris platform. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG. The Linux kernel has implemented secure random number generated initial TCP sequences to prevent TCP hijacking attacks since 1996. Not vulnerable. This flaw is specific to automountd on Solaris platform. Not vulnerable. This flaw is specific to statd on Solaris platform. Red Hat Enterprise Linux by default does respond to ICMP echo requests, although it's likely that in a production environment those would be filtered by some firewall on entry to your network. However you can happily block ICMP ping responses using iptables if you so wish, but note that there is no known vulnerability in allowing them. For more details, please see: http://kbase.redhat.com/faq/FAQ_43_4304.shtm Red Hat Enterprise Linux is configured by default to respond to all ICMP requests. Users may configure the firewall to prevent a system from responding to certain ICMP requests. Red Hat does not consider CVE-1999-0997 to be a security vulnerability. The wu-ftpd process chroots itself into the target ftp directory and will only run external commands as the user logged into the ftp server. Because the process chroots itself, an attacker needs a valid login with write access to the ftp server, and even then they could only potentially execute commands as themselves. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This issue has been addressed in nfs-utils packages as shipped in Red Hat Linux 6.2 via https://rhn.redhat.com/errata/RHSA-2000-043.html. This issue is a duplicate of CVE-2000-0666, which has been corrected via RHSA-2000:043. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 2.1 ships with wu-ftp version 2.6.2 which is not vulnerable to this issue. This issue did NOT affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the version of atmel-firmware as shipped with Red Hat Enterprise Linux 6 as it did not implement the SNMP protocol support. CVE-2001-0935 refers to vulnerabilities found when SUSE did a code audit of the wu-ftpd glob.c file in wu-ftpd 2.6.0. They shared these details with the wu-ftpd upstream authors who clarified that some of the issues did not apply, and all were addressed by the version of glob.c in upstream wu-ftpd 2.6.1. Therefore we believe that the issues labelled as CVE-2001-0935 do not affect wu-ftpd 2.6.1 or later versions and therefore do not affect Red Hat Enterprise Linux 2.1. Red Hat does not consider this flaw to be a security issue. If UserDir is enabled, you can configure httpd to respond with a custom error page and a single error code whether the user exists or not. The UserDir functionality is disabled by default in httpd on Red Hat Enterprise Linux 5, 6, and 7, and is thus not exposed on default installations. This issue affects the version of the openssh as shipped with Red Hat Enterprise Linux 4. The Red Hat Security Response Team has rated this issue as having low security impact. This issue is not currently planned to be addressed in future openssh updates for Red Hat Enterprise Linux 4. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of openssh as shipped with Red Hat Enterprise Linux 5 and 6, since it is SSH-1 protocol specific and those versions did not enable SSH-1 protocol support in the default configuration. Not vulnerable. This issue did not affect the versions of OpenSSH as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. This is not a security issue. The mod_usertrack cookies are not designed to be used for authentication. This is a duplicate CVE name and is a combination of CVE-2003-0020 and CVE-2003-0083. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. This flaw is specific to Apache HTTP server on Windows platforms. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat do not consider this to be a security issue and there are many ways that you can identify or fingerprint a Linux machine. Users that wish to block fingerprinting can use various techniques to disguise their operating system, for example see http://www.infosecwriters.com/text_resources/pdf/nmap.pdf Not vulnerable. This issue did not affect the versions of OpenSSH as shipped with Red Hat Enterprise Linux 3 or later. This issue did not affect the OpenSSL packages as shipped with Red Hat Enterprise Linux 2.1 as they were not compiled with S/Key or BSD_AUTH support. The upstream patch for this issue and CVE-2002-0640 was included in an errata so that users recompiling OpenSSL with support for those authentication methods would also be protected: https://rhn.redhat.com/errata/RHSA-2002-131.html Not vulnerable. This issue did not affect the versions of PostgreSQL as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. This issue did not affect the versions of SquirrelMail as shipped with Red Hat Enterprise Linux 3 or 4. Not vulnerable. This issue did not affect the versions of SquirrelMail as shipped with Red Hat Enterprise Linux 3 or 4. Not vulnerable. This issue did not affect the versions of SquirrelMail as shipped with Red Hat Enterprise Linux 3 or 4. Not vulnerable. This issue did not affect the versions of Apache HTTP server as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=162899 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Not vulnerable. This issue did not affect the versions of Mozilla as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. This issue only affects a third-party patch to Cyrus SASL, not distributed with Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. This issue did not affect the versions of Mozilla as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. This issue did not affect the versions of Apache HTTP server as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. This issue did not affect the versions of Samba as distributed with Red Hat Enterprise Linux 2.1, 3, or 4. We do not believe this is a security vulnerability. This is the documented and expected behaviour of rpm. Not vulnerable. This issue did not affect the RPM packages of OpenOffice as distributed with Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. This issue did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG. Red Hat Enterprise Linux 4 and 5 are not vulnerable to this issue as they both contain a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This issue affected Red Hat Enterprise Linux 2.1 and an update was released to correct it: http://rhn.redhat.com/errata/RHSA-2003-244.html Red Hat Enterprise Linux 3 contained a backported patch to correct this issue since release. This issue does not affect the versions of Apache in Enterprise Linux 4 or later. This issue has been addressed in nfs-utils packages as shipped in Red Hat Enterprise Linux 2 via https://rhn.redhat.com/errata/RHSA-2003-207.html. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. For Red Hat Enterprise Linux 2.1 OpenSSL packages (openssl, openssl096, openssl095a) issue was addressed via RHSA-2003:293. The OpenSSL packages in Red Hat Enterprise Linux 3 and 4 (openssl, openssl096b) contain a backported patch since their initial release. The OpenSSL packages in Red Hat Enterprise Linux 5 are based on fixed upstream release (openssl), or contain backported patch since their initial release (openssl097a). For Red Hat Enterprise Linux 2.1 OpenSSL packages (openssl, openssl096, openssl095a) issue was addressed via RHSA-2003:293. The OpenSSL packages in Red Hat Enterprise Linux 3 and 4 (openssl, openssl096b) contain a backported patch since their initial release. The OpenSSL packages in Red Hat Enterprise Linux 5 are based on fixed upstream release (openssl), or contain backported patch since their initial release (openssl097a). Not vulnerable. The OpenSSL packages in Red Hat Enterprise Linux 2.1 were not affected by this issue. The OpenSSL packages in Red Hat Enterprise Linux 3 and 4 contain a backported patch since their initial release (openssl), or were not affected by this issue (openssl096b). The OpenSSL packages in Red Hat Enterprise Linux 5 are based on fixed upstream release (openssl), or contain backported patch since their initial release (openssl097a). Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114923 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue does not affect Red Hat Enterprise Linux 4. Not vulnerable. This flaw is fixed in Red Hat Enterprise Linux 2.1 via the errata RHSA-2003:280. This flaw is fixed in Red Hat Enterprise Linux 3 as a backported patch. The source RPM contains the patch openssh-3.6.1p2-owl-realloc.diff which resolved this flaw before Red Hat Enterprise Linux 3 GA. This flaw does not affect any subsequent versions of Red Hat Enterprise Linux. Not vulnerable. This flaw is fixed in Red Hat Enterprise Linux 2.1 via the errata RHSA-2003:280. This flaw is fixed in Red Hat Enterprise Linux 3 as a backported patch. The source RPM contains the patch openssh-3.6.1p2-owl-realloc.diff which resolved this flaw before Red Hat Enterprise Linux 3 GA. This flaw does not affect any subsequent versions of Red Hat Enterprise Linux. Not vulnerable. This flaw is fixed in Red Hat Enterprise Linux 2.1 via the errata RHSA-2003:280. This flaw is fixed in Red Hat Enterprise Linux 3 as a backported patch. The source RPM contains the patch openssh-3.6.1p2-owl-realloc.diff which resolved this flaw before Red Hat Enterprise Linux 3 GA. This flaw does not affect any subsequent versions of Red Hat Enterprise Linux. Not vulnerable. This issue did not affect the version of openssh as shipped with Red Hat Enterprise Linux 3 as it did not include the upstream PAM password authentication module reimplementation, introduced in OpenSSH 3.7. This issue did not affect the versions of openssh as shipped with Red Hat Enterprise Linux 4, 5, and 6. Not affected. Red Hat did not ship iptables-devel or anything else that used these vulnerable functions with Red Hat Enterprise Linux 2.1 or 3. Red Hat Enterprise Linux 4 and 5 contained a backported patch to correct this issue. We do not consider these to be security issues: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 We do not consider these to be security issues: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 Not vulnerable. This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1. The PHP packages in Red Hat Enterprise Linux 3 contain a backported patch to address this issue since release. The issue was fixed upstream in PHP 4.3.3. The PHP packages in Red Hat Enterprise Linux 4 and 5 are based on fixed upstream versions. This issue did not affect the versions of Xscreensaver as distributed with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue. This is not a vulnerability. When PHP scripts are interpreted using the dynamically loaded mod_php DSO, the PHP interpreter executes with the privileges of the httpd child process. The PHP intepreter does not "sandbox" PHP scripts from the environment in which they run. On any modern Unix system a process can easily obtain access to all the parent file descriptors anyway, even if they have been closed. Not vulnerable. Red Hat Enterprise Linux 2.1 shipped with fvwm, however this issue does not affect the included version of fvwm. Red Hat does not consider this issue to be a security vulnerability since no trust boundary is crossed. The user must voluntarily interact with the attack mechanism to exploit this flaw, with the result being the ability to run code as themselves. Red Hat does not consider this to be a security issue. The information returned poses no threat to the target machine running httpd. Not vulnerable. This issue did not affect the versions of SpamAssassin as shipped with Red Hat Enterprise Linux 3, 4, or 5. The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 2.1 and 3 which is in maintenance mode. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. This issue did not affect Linux. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. The DHS advisory is a good source of background information about the issue: http://www.us-cert.gov/cas/techalerts/TA04-111A.html It is important to note that the issue described is a known function of TCP. In order to perform a connection reset an attacker would need to know the source and destination ip address and ports as well as being able to guess the sequence number within the window. These requirements seriously reduce the ability to trigger a connection reset on normal TCP connections. The DHS advisory explains that BGP routing is a specific case where being able to trigger a reset is easier than expected as the end points can be easily determined and large window sizes are used. BGP routing is also signficantly affected by having its connections terminated. The major BGP peers have recently switched to requiring md5 signatures which mitigates against this attack. The following article from Linux Weekly News also puts the flaw into context and shows why it does not pose a significant threat: http://lwn.net/Articles/81560/ Red Hat does not have any plans for action regarding this issue. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. This issue did not affect the versions of MySQL as shipped with Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. This issue did not affect the versions of MySQL as shipped with Red Hat Enterprise Linux 4, 5, or 6. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. cdrecord is not shipped setuid and does not need to be made setuid with Red Hat Enterprise Linux 2.1, 3, or 4 packages. Not Vulnerable. This issue only affected Apache 2.0.51, which was not shipped in any version of Red Hat Enterprise Linux. We do not class this as a security issue; this can only cause a denial of service for the attacker. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140074 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 2.1 which is in maintenance mode. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140058 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. cscope packages shipped with Red Hat Enterprise Linux 3, 4, and 5 contain a backported patch since their first release. This issue is only will only cause a denial of service on the connection the attacker is using. It therefore is not a security issue. Red Hat does not consider this issue to be a security vulnerability since no trust boundary is crossed. There are no known uses of this function which could allow a remote attacker to execute arbitrary code. We do not consider this to be a security issue: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139478#c1 We do not consider safe_mode / open_basedir restriction bypass issues being security sensitive. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php We do not consider safe_mode / open_basedir restriction bypass issues being security sensitive. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This issue did not affect the versions of mailman shipped with Red Hat Enterprise Linux 2.1, 3, or 4. In addition, we believe this issue does not apply to the 2.0.x versions of mailman due to setting of STEALTH_MODE Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This issue was resolved in all affected libtiff versions as shipped with Red Hat Enterprise Linux 2.1, 3, and 4 via a patch for CVE-2004-0886. For updates containing patches for CVE-2004-0886, see: https://rhn.redhat.com/errata/CVE-2004-0886.html Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. We do not consider these to be security issues: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 Permitting TCP forwarding is the expected and known default configuration. If it is not desired, it can disabled using the AllowTcpForwarding option in the /etc/ssh/sshd_config configuration file. However, only disabling TCP forwarding does not improve security unless users are also denied shell access. For more information, see man sshd_config. This CVE is a duplicate (rediscovery) of CVE-2002-0838 The Red Hat Security Response Team rated this issue as having low security impact. This issue affected Red Hat Enterprise Linux 2.1 but due to the low severity will not be fixed. metamail was not shipped in Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. These issues did not affect the versions of OpenLDAP as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. We did not ship snmpd setuid root in Red Hat Enterprise Linux 2.1, 3, or 4. The Apache Software Foundation do not treat this as a security issue. A configuration change can be made to disable the ability to respond to HTTP TRACE requests if required. For more information please see: http://www.apacheweek.com/issues/03-01-24#news Red Hat does not consider this to be a security issue. Not vulnerable. This issue did not affect the versions of Samba as distributed with Red Hat Enterprise Linux 3, or 4. Red Hat Enterprise Linux 2.1 shipped with a version of Samba prior to 3.0.6, but we verified by code audit that it is not affected by this issue. Not vulnerable. This issue only affected 2.5 STABLE4 and 2.5 STABLE5 versions of Squid and does not affect the versions of Squid distributed with Red Hat Enterprise Linux. The Red Hat Security Response Team has rated this issue as having low security impact. We no longer plan to fix this flaw in Red Hat Enterprise Linux 4. Not vulnerable. The Linux kernel as shipped with with Red Hat Enterprise Linux 2.1, 3, 4 and 5 did not include the Sbus PROM module and therefore are not affected by this issue. The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 2.1 which is in maintenance mode. Please see http://kbase.redhat.com/faq/docs/DOC-15379 Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. These issues did not affect the versions of htdig as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=144263 Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. Red Hat Enterprise Linux 2.1 shipped with wu-ftpd, however we were unable to reproduce this issue. Additionally, a code analysis showed that attempts to exploit this issue would be caught in the versions we shipped. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149720 Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of Cyrus SASL as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. We do not consider this a security vulnerability; this is the expected behaviour. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. We do not consider this a security issue, the bug can only manifest if the software is invoked on a sudoers file that is contained in a world writable directory. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This is defined and documented behaviour: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=156313 Not vulnerable. Adobe told us this issue did not affect the Linux version of Adobe Reader. Red Hat does not consider this to be a vulnerability. htdigest is not supplied setuid or setgid and should not be run from a CGI program. Not vulnerable. This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Based on our research we believe that the "OpenSSL ASN.1 brute forcer." is actually exploiting flaws CVE-2003-0543, CVE-2003-0544, CVE-2003-0545. Those issues are all addressed in Red Hat Enterprise Linux and therefore CVE-2005-1730 is a duplicate assignment. We do not believe this is a security issue; this is a deliberate circumvention of the Javamail API. The Javamail API provides a comprehensive and secure method to retrieve mail. In this example, the author retreives the message directly from the mail directory on the filesystem. Even if the user insists on using this incorrect way of accessing mail, then the permissions set by the dovecot and tomcat packages are enough to protect against direct access to most of the files listed in the bug report. The OpenSSL Team do not consider this issue to be a practical threat. Conducting an attack such as this has shown to be impractical outside of a controlled lab environment. If the OpenSSL Team decide to produce an update to correct this issue, we will consider including it in a future security update. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This issue was addressed in unzip packages as shipped with Red Hat Enterprise Linux 3 and 4 via RHBA-2007:0418 and RHSA-2007:0203 respectively. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This is the documented and expected behaviour of tar. Not vulnerable. These issues did not affect the version of BlueZ as shipped with Red Hat Enterprise Linux 4. Not vulnerable. This issue did not affect the Linux versions of Mutt. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=162681 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. This issue did not affect the versions of OpenSSH as shipped with Red Hat Enterprise Linux 2.1, 3 or 4. This issue does not affect Red Hat Enterprise Linux 2.1 and 3. This flaw was fixed in Red Hat Enterprise Linux 4 via errata RHSA-2005:527: http://rhn.redhat.com/errata/RHSA-2005-527.html Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169803 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ We do not consider this to be a security issue: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139478#c1 Not vulnerable. These issues did not affect the versions of Mozilla and Firefox as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. This issue did not affect the ncompress packages as distributed with Red Hat Enterprise Linux 2.1, 3, or 4. Updated packages to correct this issue are available along with our advisory: http://rhn.redhat.com/errata/CVE-2005-3011.html Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. We do not consider these to be security issues: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=170518 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 2.1 and 3 which are in maintenance mode. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. These issues do not affect the versions of Squid as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. We do not class this as a security issue as it only allows local users who have the privileges to create .htaccess files the ability to cause a denial of service. Untrusted users should never be given the ability to create .htaccess files. We do not consider these to be security issues: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 We do not consider these to be security issues: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 Not vulnerable. This issue is caused by the way ImageMagick was packaged by Gentoo and does not affect Red Hat Enterprise Linux packages. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. We do not consider this to be a security issue. https://bugzilla.redhat.com/show_bug.cgi?id=139478#c1 This issue was addressed in Red Hat Enterprise Linux 4 via https://rhn.redhat.com/errata/RHSA-2007-0245.html and in Red Hat Enterprise Linux 3 via https://rhn.redhat.com/errata/RHSA-2010-0145.html. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. The Red Hat Security Response Team has rated this issue as having low security impact. An update is available for Red Hat Enterprise Linux 4 to correct this issue: http://rhn.redhat.com/errata/RHSA-2007-0018.html This issue did not affect Red Hat Enterprise Linux 2.1 and 3. This issue did not affect the versions of OpenLDAP as distributed with Red Hat Enterprise Linux 2.1, 3, or 4. This issue did not affect the versions of OpenOffice.org as distributed with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=178960 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 2.1 which is in maintenance mode. Not vulnerable. This issue did not affect the FreeRADIUS packages as distributed with Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. This issue did not affect the FreeRADIUS packages as distributed with Red Hat Enterprise Linux 2.1, 3, or 4. This issue did not affect the Linux glibc. gas (and gcc) make no promise that they are fault tolerant to bad input. We do not plan on producing security updates for Red Hat Enterprise Linux to correct these bugs. gas (and gcc) make no promise that they are fault tolerant to bad input. We do not plan on producing security updates for Red Hat Enterprise Linux to correct these bugs. Not vulnerable. The MadWiFi wireless driver is not shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2005-4881 This issue has been rated as having moderate security impact. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, and Red Hat Enterprise MRG. It affects Red Hat Enterprise Linux 3, and 4. It was addressed in Red Hat Enterprise Linux 4 via: https://rhn.redhat.com/errata/RHSA-2009-1522.html This issue is not planned to be fixed in Red Hat Enterprise Linux 3, due to this product being in Production 3 of its maintenance life-cycle, where only qualified security errata of important and critical impact are addressed. For further information about Errata Support Policy, visit: http://www.redhat.com/security/updates/errata/ This issue affects the version of coreutils package, as shipped with Red Hat Enterprise Linux 4. Red Hat Enterprise Linux 4 is however in the Extended Life Cycle Support (ELS) phase. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. We do not consider this to be a security issue. https://bugzilla.redhat.com/show_bug.cgi?id=139478#c1 This issue was addressed in Red Hat Enterprise Linux 2.1, 3 and 4: https://rhn.redhat.com/errata/CVE-2006-0225.html https://www.redhat.com/security/data/cve/CVE-2006-0225.html Issue was fixed upstream in version 4.3. The openssh packages in Red Hat Enterprise Linux 5 are based on the fixed upstream version and were not affected by this flaw. Not vulnerable. We verified that this issue does not affect Linux versions of Thunderbird. This issue did not affect the versions of Fetchmail as distributed with Red Hat Enterprise Linux 2.1, 3, or 4. This issue did not affect the versions of libtiff as distributed with Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. This vulnerability was introduced into the Linux kernel in version 2.6.12 and therefore does not affect users of Red Hat Enterprise Linux 2.1, 3, or 4. This issue only affects parsers which are generated by grammars which either use REJECT or rules with a variable trailing context (in these rules the parser has to keep all backtracking paths). The Red Hat Security Response Team analysed all packages that include flex generated parsers in Red Hat Enterprise Linux (2.1, 3, and 4) and found none were vulnerable. This issue did not affect the versions of PostgreSQL as distributed with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat is aware of this issue and is tracking it via the following bug for Red Hat Enterprise Linux 3 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207347 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue was fixed for Red Hat Enterprise Linux 4 in the following errata: http://rhn.redhat.com/errata/RHEA-2006-0355.html This issue does not affect Red Hat Enterprise Linux 2 Red Hat no longer plans to fix this issue in Red Hat Enterprise Linux 4. This issue is corrected in bluez-hcidump 1.32 as provided by Red Hat Enterprise Linux 5. This issue only affected Dovecot versions 1.0beta1 and 1.0beta2. Red Hat Enterprise Linux 4 shipped with an earlier version of Dovecot and is therefore not vulnerable to this issue. Not vulnerable. Red Hat Enterprise Linux 2.1, 3, and 4 do not include log4net. This issue did not affect the versions of OpenSSH as distributed with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat is aware of this issue and is tracking it via the following bug for Red Hat Enterprise Linux 2.1 and 3: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=194613 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue has been fixed for Red Hat Enterprise Linux 4 in RHSA-2006:0544. Not vulnerable. This issue did not affect the versions of bind as shipped with Red Hat Enterprise Linux 5 and 6 and version of bind97 as shipped with Red Hat Enterprise Linux 5 as in the default configuration the named service accept DNS queries only from localhost. We do not consider these to be security issues: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 We do not consider these to be security issues: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 We do not consider safe_mode / open_basedir restriction bypass issues being security sensitive. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188302 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue does not affect Red Hat Enterprise Linux 2.1 and 3. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187385 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue does not affect Red Hat Enterprise Linux 2.1 or 3. This issue did not affect the versions of mod_python as distributed with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat is aware of this issue and is tracking it via the following bugs: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=193053 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229194 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 2.1 which is in maintenance mode. Not vulnerable. greylistclean.cron is not supplied in the exim packages as distributed with Red Hat Enterprise Linux. This issue did not affect the versions of OpenSSH as distributed with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187900 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. We do not consider these to be security issues: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 Red Hat does not consider this to be a security issue. Enabling the -r option is not suggested without the -x option which is clearly documented in the /etc/sysconfig/syslog configuration file. Red Hat does not consider this to be a security issue. The FastCGI server is local trusted code and not under the control of an attacker, no trust boundary is crossed. For more information please see: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-2050 This issue did not affect the version of bind as shipped with Red Hat Enterprise Linux 5. We do not believe this issue has a security consequence for earlier versions of Red Hat Enterprise Linux. For details please see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=192192 Not vulnerable. This issue does not affect the versions of rsync distributed with Red Hat Enterprise Linux 2.1, 3, or 4. This issue does not affect Red Hat Enterprise Linux 2.1 and 3 This issue was addressed in Red Hat Enterprise Linux 4 via: https://rhn.redhat.com/errata/RHSA-2008-0848.html Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. The winbind plugin is not shipped with Red Hat Enterprise Linux 2.1, 3, or 4. This issue only affected version 4.1.1 and not the versions distributed with Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. This issue does not affect the versions of Dovecot distributed with Red Hat Enterprise Linux. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=192278 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue does not affect Red Hat Enterprise Linux 2.1 or 3. Not vulnerable. This issue does not affect the versions of LibVNCServer as distributed with Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. This issue does not affect the versions of cyrus-imapd distributed with Red Hat Enterprise Linux. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This issue was addressed in libtiff packages as shipped in Red Hat Enterprise Linux 2.1, 3, and 4 via: https://rhn.redhat.com/errata/RHSA-2006-0603.html Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This is not an issue that affects users of Red Hat Enterprise Linux. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=196255 This issue is not exploitable as the status file is only written to and read by the slurpd process. Therefore this is not a vulnerability that affects Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. This issue does not affect the versions of Evolution as distributed with Red Hat Enterprise Linux. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. We do not ship aRts as setuid root on Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat does not consider this a security issue. It is expected behavior that a large input file will cause the processing program to use a large amount of memory. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Unknown: CVE-2006-3018 has been assigned to an issue in PHP where the cause and fix are unknown, and the impact cannot be verified. The source of the CVE assignment was a single line statement in the PHP 5.1.3 release announcement, http://www.php.net/release_5_1_3.php, reading: "Fixed a heap corruption inside the session extension." Of the changes made to the session extension between releases 5.1.2 and 5.1.3, none would fix a bug matching this description by our analysis. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. Adobe told us that this issue does not affect the Linux versions of Adobe Acrobat Reader. This issue did not affect the versions of NetPBM distributed with Red Hat Enterprise Linux 2.1, 3, or 4. This issue has not been able to be reproduced by upstream or after a Red Hat code review. We therefore do not believe this is a security vulnerability. On Red Hat Enterprise Linux 2.1, 3, 4, and 5 this is a two-byte overflow into the middle of the stack and is not exploitable. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This issue affects the version of the passwd command from the shadow-utils package. Red Hat Enterprise Linux 2.1, 3, and 4 are not vulnerable to this issue. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This issue was addressed in mysql packages as shipped in Red Hat Enterprise Linux 4 via: https://rhn.redhat.com/errata/RHSA-2008-0768.html This issue did not affect mysql packages as shipped with Red Hat Enterprise Linux 2.1, 3, or 5, and Red Hat Application Stack v1 and v2. We do not consider this issue to have security implications, and therefore have no plans to issue MySQL updates for Red Hat Enterprise Linux 2.1, 3, or 4 to correct this issue. Adobe gave a statement that these issues do not affect the Linux versions of Macromedia Flash Player. Adobe gave a statement that these issues do not affect the Linux versions of Macromedia Flash Player. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=198912 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This vulnerability does not affect Red Hat Enterprise Linux 2.1 or 3 as they are based on 2.4 kernels. The exploit relies on the kernel supporting the a.out binary format. Red Hat Enterprise Linux 4, Fedora Core 4, and Fedora Core 5 do not support the a.out binary format, causing the exploit to fail. We are not currently aware of any way to exploit this vulnerability if a.out binary format is not enabled. In addition, a default installation of these OS enables SELinux in enforcing mode. SELinux also completely blocks attempts to exploit this issue. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=198973#c10 We do not consider a crash of a client application such as Konqueror to be a security issue. We do not consider a user-assisted crash of a client application such as Firefox to be a security issue. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. The ability to exploit this issue is dependent on the stack layout for a particular compiled version of mod_rewrite. If the compiler has added padding to the stack immediately after the buffer being overwritten, this issue can not be exploited, and Apache httpd will continue operating normally. The Red Hat Security Response Team analyzed Red Hat Enterprise Linux 3 and Red Hat Enterprise Linux 4 binaries for all architectures as shipped by Red Hat and determined that these versions cannot be exploited. This issue does not affect the version of Apache httpd as supplied with Red Hat Enterprise Linux 2.1 This issue is not a security issue in Tomcat itself, but is caused when directory listings are enabled. Details on how to disable directory listings are available at: http://tomcat.apache.org/faq/misc.html#listing This issue does not affect versions of Mikmod 3.2.0-beta2 or prior. Versions of Mikmod distributed with Red Hat Enterprise Linux 2.1, 3, and 4 are based on version 3.1.11 and are therefore not vulnerable to this issue. This issue was corrected in all affected mysql packages versions as shipped in Red Hat Enterprise Linux or Red Hat Application Stack via: https://rhn.redhat.com/errata/CVE-2006-4031.html This issue did not affect mysql packages as shipped with Red Hat Enterprise Linux 2.1 or 3 Not Vulnerable. The version of BIND that ships with Red Hat Enterprise Linux is not vulnerable to this issue as it does not handle signed RR records. Not Vulnerable. This issue was found and fixed as part of Red Hat Enterprise Linux 4 update 4: http://rhn.redhat.com/errata/RHBA-2006-0288.html and Red Hat Enterprise Linux 3 update 8: http://rhn.redhat.com/errata/RHBA-2006-0287.html This issue does not affect Red Hat Enterprise Linux 2.1 LessTif is shipped with Red Hat Enterprise Linux 2.1 but not 3 or 4. On Enterprise Linux 2.1 we build LessTif with debugging disabled, so the DEBUG_FILE environment variable is ignored and this issue cannot be exploited. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Updates to address this issue are available for Red Hat Enterprise Linux 3 and 4: https://rhn.redhat.com/cve/CVE-2006-4146.html Red Hat Enterprise Linux 5 was not vulnerable to this issue as it contained a backported patch. Not Vulnerable. Red Hat does not ship GNU Radius in Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=203426 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue does not affect Red Hat Enterprise Linux 2.1 or 3 This issue did not affect the versions of MySQL as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Issue was addressed in MySQL packages as shipped in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2008-0364.html Red Hat Enterprise Linux 5 was not vulnerable to this issue as it contained a backported patch since its first release. In Red Hat Enterprise Linux 3 and 4, this issue was addressed via: https://rhn.redhat.com/errata/RHSA-2009-1101.html Red Hat does not consider this flaw a security issue. This flaw is the result of a NULL pointer dereference, which is not exploitable and can only cause a client crash. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat no longer plans to fix this issue in lha for Red Hat Enterprise Linux 4. Red Hat no longer plans to fix this issue in lha for Red Hat Enterprise Linux 4. Red Hat no longer plans to fix this issue in lha for Red Hat Enterprise Linux 4. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=220595 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Vulnerable. This issue affects OpenSSL and OpenSSL compatibility packages in Red Hat Enterprise Linux 2.1, 3, and 4. Updates, along with our advisory are available at the URL below. http://rhn.redhat.com/errata/RHSA-2006-0661.html Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. We do not consider this to be a PHP flaw. The problem is caused by the insufficient input validation performed by Zend platform. This flaw causes a crash but does not result in a denial of service against Sendmail and is therefore not a security issue. Not Vulnerable. This issue does not exist in Red Hat Enterprise Linux 2.1 or 3. This issue not exploitable in Red Hat Enterprise Linux 4. A detailed analysis of this issue can be found in the Red Hat Bug Tracking System: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=195555 We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Not vulnerable. This issue did not affect versions of wvWare library included in koffice packages as shipped with Red Hat Enterprise Linux 2.1 Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat no longer plans to fix this issue in Red Hat Enterprise Linux 4. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=205826 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 2.1 which is in maintenance mode. Red Hat is aware of this issue and is tracking it via the following bug for Red Hat Enterprise Linux 4: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=204912 This issue does not affect Red Hat Enterprise Linux 2.1 or 3. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=205651 The Red Hat Security Response Team has rated this issue as having low security impact and expects to release a future update to address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 2.1 and 3 which are in maintenance mode. This bug will be addressed in a future update of Red Hat Enterprise Linux 4. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. Red Hat Enterprise Linux 2.1, 3, and 4 do not include imlib2. Not vulnerable. Red Hat Enterprise Linux 2.1, 3, and 4 do not include imlib2. Not vulnerable. Red Hat Enterprise Linux 2.1, 3, and 4 do not include imlib2. Not vulnerable. Red Hat Enterprise Linux 2.1, 3, and 4 do not include imlib2. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 3, and 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This issue also affects other OS that use NSPR. However, Red Hat does not ship any application linked setuid or setgid against NSPR and therefore is not vulnerable to this issue. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat does not consider this flaw a security issue. This flaw can cause an OpenSSH client to crash when connecting to a malicious server, which does not result in a denial of service condition. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This issue did not affect Red Hat Enterprise Linux 2.1 and 3. This issue was addressed in Red Hat Enterprise Linux 4 and 5 via https://rhn.redhat.com/errata/RHSA-2007-0703.html and https://rhn.redhat.com/errata/RHSA-2007-0540.html respectively. Red Hat is aware of this issue and is tracking it via the following bug for Red Hat Enterprise Linux 4: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=210128 This issue does not affect Red Hat Enterprise Linux 2.1 or 3. Red Hat does not consider this issue to be a security vulnerability. We have been in contact with the upstream project regarding this problem and agree that this issue currently poses no security threat. In the event more information becomes available, we will revisit this issue in the future. Red Hat does not consider this issue to be a security vulnerability. We have been in contact with the upstream project regarding this problem and agree that this issue currently poses no security threat. In the event more information becomes available, we will revisit this issue in the future. Not Vulnerable. This flaw only affects kernel versions 2.6.14 to 2.6.18. Red Hat Enterprise Linux 2.1, 3, and 4 does not ship with a vulnerable kernel version. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat has been unable to reproduce this flaw and believes that the reporter was experiencing behavior specific to his environment. We will not be releasing update to address this issue. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211085 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 2.1 which is in maintenance mode. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211085 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 2.1 which is in maintenance mode. Not vulnerable. These issues did not affect the versions of libX11 as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat non longer plans to fix this flaw in Red Hat Enterprise Linux 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat is aware of this issue and are tracking it via bug 213214 for Red Hat Enterprise Linux 4: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=213214 This issue does not affect Red Hat Enterprise Linux 2.1 or 3 Red Hat does not consider a user-assisted crash of a client application such as Firefox to be a security issue. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, or 5. Red Hat Enterprise Linux 2.1 did not ship for PowerPC architecture. Not Vulnerable. The squashfs module is not distributed as part of Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This flaw does not affect the Linux kernel shipped with Red Hat Enterprise Linux 2.1 or 3. This flaw affects the Linux kernel shipped with Red Hat Enterprise Linux 4. We are tracking this flaw via bug 216452: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=216452 Red Hat Enterprise Linux 2.1 is not vulnerable to this issue as it only affects x86_64 architectures. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch at release. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not Vulnerable. The OpenLDAP versions shipped with Red Hat Enterprise Linux 4 and earlier do not contain the vulnerable code in question. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This issue did not affect Red Hat Enterprise Linux 2.1. This issue was addressed in Red Hat Enterprise Linux 3 and 4 via https://rhn.redhat.com/errata/RHSA-2006-0738.html . Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. The CVE-2006-5823 is about a corrupted cramfs (MOKB-07-11-2006) that can cause a memory corruption and so crash the machine. For Red Hat Enterpise Linux 3 this issue is tracked via Bugzilla #216960 and for Red Hat Enterprise Linux 4 it is tracked via Bugzilla #216958. Red Hat Enterprise Linux 2.1 is not vulnerable to this issue. This issue has been rated as having low impact, because root privileges or physical access to the machine are needed to mount a corrupted filesystem and crash the machine. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat is aware of this issue and is tracking it via the following bug for Red Hat Enterprise Linux 2.1. This issue did not affect Red Hat Enterprise Linux 3 or 4. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=215593 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 2.1 which is in maintenance mode. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. The vulnerable code is not used by any application likned with libsoup shipped with Red Hat Enterprise Linux 2.1, 3, and 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. Red Hat Enterprise Linux 2.1 shipped with fvwm, however this issue does not affect the included version of fvwm. Not vulnerable. This issue does not affect the versions of fetchmail distributed with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat does not consider unexploitable client application crashes to be security flaws. This bug causes a stack recursion crash which is not exploitable. Not vulnerable. This issue did not affect Linux versions of Adobe Reader. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not Vulnerable. The kernel as shipped with Red Hat Enterprise Linux 2.1, 3, and 4 do not contain gfs2 filesystem support. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. This flaw was first introduced in gdm version 2.14. Therefore these issues did not affect the earlier versions of gdm as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat is aware of this issue and is tracking it for Red Hat Enterprise Linux 4 via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=218602 This issue does not affect the version of the Linux kernel shipped with Red Hat Enterprise Linux 2.1 or 3. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. Red Hat Enterprise Linux 2.1, 3, and 4 ship with versions of Kerberos 5 prior to version 1.4 and are therefore not affected by these vulnerabilities. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. Red Hat Enterprise Linux 2.1, 3, and 4 ship with versions of Kerberos 5 prior to version 1.4 and are therefore not affected by these vulnerabilities. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Red Hat does not consider this bug to be a security flaw. In order for this flaw to be exploited, a user would be required to enter shellcode into an interactive GnuPG session. Red Hat considers this to be an unlikely scenario. Red Hat Enterprise Linux 5 contains a backported patch to address this issue. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. This issue does not affect the Linux version of Adobe Reader. We do not consider a crash of a client application such as Konqueror or other KFile users to be a security issue. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. For other versions of Red Hat Enterprise Linux see http://rhn.redhat.com/cve/CVE-2006-6303.html This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG. Shipped kernels do not include upstream commit d025c9db that introduced the problem. This upstream commit was backported in Red Hat Enterprise Linux 5 via RHSA-2009:0225. It was later reported and addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0046.html Not vulnerable. This issue does not affect the versions of net-smtp as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. The MadWiFi wireless driver is not shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Not Vulnerable. eEye Research advisory AD20061207 (Intel Network Adapter Driver Local Privilege Escalation) describes a flaw in the Linux Kernel drivers for the e100, e1000, and ixgb Intel network cards. The flaw affects the NDIS miniport drivers and its OID support. The Linux Kernel drivers do not support the NDIS API and the OID concept from Microsoft Windows. Not vulnerable. OpenLDAP as shipped with Red Hat Enterprise Linux 2.1, 3, and 4 does not support the LDAP_AUTH_KRBV41 authentication method. Red Hat does not consider this flaw a security issue. This flaw will only crash OpenOffice.org and presents no possibility for arbitrary code execution. Not vulnerable. This issue did not affect the versions of KDE as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. The Red Hat Security Response Team has rated this issue as having low security impact. The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 3, 4, or 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221459 We do not consider a crash of a client application such as wget to be a security issue. This flaw was fixed in wget shipped in Red Hat Enterprise Linux 5 before the initial release of the product. Version of wget shipped in Red Hat Enterprise Linux 3 and 4 are affected by this bug. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. We do not consider a crash of a client application such as KsIRC to be a security issue. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1 or 3. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=223072 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue can only be exploited if pending signals (ulimit -i) is set to "unlimited". In case of Red Hat Enterprise Linux version 2.1, 3 and 4 this is not the case and therefore they are not vulnerable to this issue. Not vulnerable. This issue was specific to a Debian patch to Apache HTTP Server. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This flaw has been rated as having a low severity by the Red Hat Security Response Team. More information about this rating can be found here: http://www.redhat.com/security/updates/classification/ This flaw is currently being tracked via the following bugs: https://bugzilla.redhat.com/show_bug.cgi?id=231449 https://bugzilla.redhat.com/show_bug.cgi?id=231448 The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 2.1 and 3 which are in maintenance mode. Not vulnerable. Our testing found that this issue did not affect the versions of Kmail as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. ** DISPUTED ** Sendmail classes the CipherList directive as "for future release"; currently unsupported and undocumented. Therefore the lack of support for the CipherList directive in various Red Hat products is not a vulnerability. Not vulnerable. The MadWiFi wireless driver is not shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. The MadWiFi wireless driver is not shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. The MadWiFi wireless driver is not shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. The MadWiFi wireless driver is not shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php The memory_limit configuration option is used to constrain the amount of memory which a script can consume during execution. If this setting is disabled (or set unreasonably high), it is expected behaviour that scripts will be able to consume large amounts of memory during script execution. The memory_limit setting is enabled by default in all versions of PHP distributed in Red Hat Enterprise Linux and Application Stack. Red Hat does not consider a user assisted client crash such as this to be a security flaw. This issue did not affect the MySQL packages as shipped in Red Hat Enterprise Linux 2.1, 3, and 4 as they did not support INFORMATION_SCHEMA, introduced in MySQL version 5. MySQL packages as shipped in Red Hat Enterprise Linux 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2008-0364.html The MySQL packages as shipped in Red Hat Application Stack v1 and v2 are based on upstream version which has the fix included. Not vulnerable. This issue did not affect the versions of the xterm package, as shipped with Red Hat Enterprise Linux 3, 4, and 5, and the version of the XFree86 (providing xterm) and hanterm-xf packages, as shipped with Red Hat Enterprise Linux 2.1. This issue was addressed in Red Hat Enterprise Linux 5 via RHBA-2012:0319: https://rhn.redhat.com/errata/RHBA-2012-0319.html It did not affect versions of gnutls as shipped with Red Hat Enterprise Linux 4 and 6. These flaws do not affect any version of libpng shipped with Red Hat Enterprise Linux. This issue was corrected in Red Hat Enterprise Linux 5 via RHSA-2009:1335. It did not affect openssl packages shipped with Red Hat Enterprise Linux 6. This issue was corrected in Red Hat Enterprise Linux 5 via RHSA-2009:1335. It did not affect openssl packages shipped with Red Hat Enterprise Linux 6. Not vulnerable. These issues did not affect the versions of pam as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. Not vulnerable. This issue did not affect the versions of dhcp as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. The Red Hat Security Response Team has rated this issue as having low security impact. The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 2.1, 3, 4, or 5: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2007-0062 This issue is the same as CVE-2007-5365. The affected dhcp versions were fixed via: https://rhn.redhat.com/errata/RHSA-2007-0970.html Not vulnerable. The affected code is in an optional module that is not shipped in Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat does not consider this issue to be a security vulnerability. The pottential attacker has to send acknowledgement packets periodically to make server generate traffic. Exactly the same effect could be achieved by simply downloading the file. The statement that setting the TCP window size to arbitrarily high value would permit the attacker to disconnect and stop sending ACKs is false, because Red Hat Enterprise Linux limits the size of the TCP send buffer to 4MB by default. Some implementations of the PDF specification erroneously allow page tree objects that refer back to themselves. As a result, an infinite loop could be created. We believe this could only result in a denial of service against the application. We do not consider a user-assisted DoS of a client application to be a security issue. Not Vulnerable. This flaw is the result of an infinite recursion flaw in xpdf, which cannot result in arbitrary code execution. Not vulnerable. This issue does not affect the older versions of neon as shipped with Red Hat Enterprise Linux 2.1, 3, and 4. This issue also does not affect the older versions of neon included in the cadaver package. Not vulnerable. This issue did not affect the versions of slocate as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. This issue did not affect the versions of libgtop as shipped with Red Hat Enterprise Linux 2.1 or 3. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This flaw affects Red Hat Enterprise Linux 4 and is being tracked via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249884 Not vulnerable. This issue did not affect Zope included within the conga package shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This issue did not affect the versions of squid as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat Enterprise Linux 5 is not vulnerable to this issue as it contains a backported patch. This issue did not affect the versions of Squid as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Not vulnerable. These issues did not affect Linux versions of Samba. Not vulnerable. These issues affect the AFS ACL module which is not distributed with Samba in Red Hat Enterprise Linux 2.1, 3, 4, or 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234312 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of ISC BIND as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=225414 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Red Hat does not consider this issue to be a security vulnerability. The user would have to voluntarily interact with the attack mechanism to exploit the flaw, and the result would be the ability to run code as themselves. The Red Hat Security Response Team has rated this issue as having low security impact. There are no longer plans to fix this flaw in Red Hat Enterprise Linux 4. The Red Hat Security Response Team has rated this issue as having low security impact. There are no longer plans to fix this flaw in Red Hat Enterprise Linux 4. Not vulnerable. Red Hat did not ship the incomplete patch for CVE-2006-5456 and is therefore not affected by this issue. Red Hat does not consider this issue to be a security vulnerability. On Red Hat Enterprise Linux processes that change their effective UID do not dump core by default when they receive a fatal signal. Therefore the NULL pointer dereference does not lead to an information leak. Red Hat does not consider this issue to be a security vulnerability. It is correct and expected behavior for xterm not to zero-fill its scrollback buffer upon reception of terminal clear excape sequence. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Not vulnerable. This flaw is a regression of the fix for CVE-2007-0906 affecting PHP version 5.2.1 only which results in any use of str_replace() causing a crash regardless of user input. These issues did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. This issue was fixed in php package updates for Red Hat Enterprise Linux and Red Hat Application Stack: http://rhn.redhat.com/cve/CVE-2007-1001.html This issue did not affect the versions of gd as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect versions of libevent as shipped with Red Hat Enterprise Linux 5. The JBoss AS console manager should always be secured prior to deployment, as directed in the JBoss Application Server Guide and release notes. By default, the JBoss AS installer gives users the ability to password protect the console manager. If the user did not use the installer, the raw JBoss services will be in a completely unconfigured state and these steps should be performed manually: http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureJBoss Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-1199 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232347 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ The phpinfo function should not be used in publically-accessible PHP scripts. Not vulnerable. This issue did not affect Xen as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect Xen as shipped with Red Hat Enterprise Linux 5. We do not consider this flaw to be a security issue as it is only exploitable by the script author. No trust boundary is crossed. This flaw exists in versions of PHP as shipped in Red Hat Enterprise Linux 5 and Red Hat Application Stack 1. These issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, Stronghold 4.0, or Red Hat Application Stack 2. The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. Not vulnerable. These issues did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, Stronghold 4.0, or Red Hat Application Stack 1. Not vulnerable. These issues did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, Stronghold 4.0, or Red Hat Application Stack 1. Our previous fixes for CVE-2007-0906 included a patch that also addressed the issue now given CVE name CVE-2007-1380. For a full list of versions that contained a fix for this issue please see: https://rhn.redhat.com/cve/CVE-2007-1380.html Not vulnerable. These issues did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, Stronghold 4.0, or Red Hat Application Stack 1. The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. Red Hat does not consider this to be a security vulnerability. Using import_request_variables() is generally a discouraged practice and it is improper use that can lead to security problems, not flaw of PHP itself. Not vulnerable. The zip extension was not shipped in versions of PHP provided for Red Hat Enterprise Linux 2.1, 3, 4, 5, Stronghold 4.0, or Red Hat Application Stack 1. Not vulnerable. PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5 does not include Cracklib support. Not vulnerable. PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5 does not include mssql support. Not vulnerable. PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5 does not include ClibPDF support. Not vulnerable. The php-snmp package as shipped with Red Hat Enterprise Linux 4 and 5 use net-snmp which is not vulnerable to this issue. This issue did not affect mysql packages as shipped in Red Hat Enterprise Linux 2.1, 3, and 4. Issue was addressed in mysql packages as shipped in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2008-0364.html Not vulnerable. The filter extension was not shipped in versions of PHP provided for Red Hat Enterprise Linux 2.1, 3, 4, 5, Stronghold 4.0, or Red Hat Application Stack 1. Not vulnerable. The filter extension was not shipped in versions of PHP provided for Red Hat Enterprise Linux 2.1, 3, 4, 5, Stronghold 4.0, or Red Hat Application Stack 1. Not vulnerable. The filter extension was not shipped in versions of PHP provided for Red Hat Enterprise Linux 2.1, 3, 4, 5, Stronghold 4.0, or Red Hat Application Stack 1. Not vulnerable. The zip extension was not shipped in versions of PHP provided for Red Hat Enterprise Linux 2.1, 3, 4, 5, Stronghold 4.0, or Red Hat Application Stack 1. The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. Not vulnerable. PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5 does not include ibase support. The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=233592 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ We do not consider a crash of a client application such as Konqueror to be a security issue. The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. This CVE name is a duplicate as the vulnerability is addressed by CVE-2007-0907. Not vulnerable. These issues did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, Stronghold 4.0, or Red Hat Application Stack 1. The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. This CVE name is a duplicate as the vulnerability is addressed by CVE-2007-0910. Not vulnerable. PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, Red Hat Application Stack, and Stronghold 4.0 do not include PHPDoc support. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=233581 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue has no security impact. Not vulnerable. This issue did not affect the version of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. These attacks are reliant on an insecure configuration of the server - that the user the server runs as has write access to the document root. The suexec security model is not intented to protect against privilege escalation in such a configuration These attacks are reliant on an insecure configuration of the server - that the user the server runs as has write access to the document root. The suexec security model is not intented to protect against privilege escalation in such a configuration These attacks are reliant on an insecure configuration of the server - that the user the server runs as has write access to the document root. The suexec security model is not intented to protect against privilege escalation in such a configuration Not vulnerable. The zip extension was not distributed with PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, Stronghold 4.0, or Red Hat Application Stack 1. The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. This CVE name is a duplicate as the vulnerability is addressed by CVE-2007-0906. The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. Not vulnerable. This issue was specific to httpd version 2.2.4 and did not affect the versions of httpd as shipped with Red Hat Enterprise Linux 2.1, 3, 4 or 5. The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. This CVE name is a duplicate as the vulnerability is addressed by CVE-2007-0906. We do not consider this flaw to be a security issue as it is only exploitable by the script author. No trust boundary is crossed. For more information please see: https://bugzilla.redhat.com/show_bug.cgi?id=mopb#c37 Not vulnerable. These issues did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, Stronghold 4.0, or Red Hat Application Stack 1. Not vulnerable. These issues did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, Stronghold 4.0, or Red Hat Application Stack 1. Not vulnerable. These issues did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, Stronghold 4.0, or Red Hat Application Stack 1. The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. Not vulnerable. The filter extension was not shipped in the versions of PHP supplied for Red Hat Enterprise Linux 2.1, 3, 4, 5, Stronghold 4.0, or Red Hat Application Stack 1. Not vulnerable. These issues did not affect the versions of file as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. This issue affected Red Hat Enterprise Linux 4 and 5. Update packages were released to correct it via: http://rhn.redhat.com/errata/RHSA-2009-1471.html Red Hat no longer plans to fix this issue in Red Hat Enterprise Linux 4. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=235093 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Not vulnerable. This issue is a flaw in the way Java and Quicktime interact. This issue did not affect Red Hat Enterprise Linux prior to version 5. An update to Red Hat Enterprise Linux 5 was released to correct this issue: https://rhn.redhat.com/errata/RHSA-2008-0297.html Not vulnerable. These issues did not affect the versions of BIND as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. The OpenSSH packages as shipped with Red Hat Enterprise Linux do not contain S/KEY support. This issue was fixed in RealPlayer for Red Hat Enterprise Linux 3 Extras, 4 Extras, 5 Supplementary by RHSA-2007:0841 on 17th August 2007: https://rhn.redhat.com/errata/RHSA-2007-0841.html (Our original advisory did not mention this issue was fixed as the details of the issue were not made public by RealNetworks until 25th October 2007) This issue was fixed in RealPlayer for Red Hat Enterprise Linux 3 Extras, 4 Extras, 5 Supplementary by RHSA-2007:0841 on 17th August 2007: https://rhn.redhat.com/errata/RHSA-2007-0841.html (Our original advisory did not mention this issue was fixed as the details of the issue were not made public by RealNetworks until 25th October 2007) This issue does not affect lftp as supplied with Red Hat Enterprise Linux 3. This issue was addressed for Red Hat Enterprise Linux 5 by https://rhn.redhat.com/errata/RHSA-2009-1278.html The Red Hat Security Response Team has rated this issue as having low security impact, this issue will not fixed in Red Hat Enterprise Linux 4. Red Hat ship Axis in a number of products; however the installation path of Axis is fixed and deterministic, so this flaw does not disclose otherwise unknown information. We do not plan on issuing updates to fix this issue. Not vulnerable. This flaw is specific to Mac OS X and does not affect any version of Red Hat Enterprise Linux. Red Hat does not consider a user assisted client crash such as this to be a security flaw. Not vulnerable. These issues did not affect the versions of Samba as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-2448 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. Red Hat did not ship GNU locate in Red Hat Enterprise Linux 2.1, 3, 4, or 5. This issue does not affect the mlocate or slocate packages that are supplied with Red Hat Enterprise Linux. This issue did not affect the versions of the the Linux kernel supplied with Red Hat Enterprise Linux 2.1, 3, or 4. For systems based on Red Hat Enterprise Linux 5, this is only an issue for systems without a real time clock, harddrive activity, or user input during boot time. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=241718 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or Red Hat Application Stack v2. Updates to correct this issue for Red Hat Enterprise Linux 5, and Red Hat Application Stack v1 are available at http://rhn.redhat.com/cve/CVE-2007-2510.html The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. This bug described in CVE-2007-2511 can only be triggered by a script author since no trust boundary is crossed, this issue is not treated as security-sensitive. Installation of a PEAR package from an untrusted source could allow malicious code to be installed and potentially executed by the root user. This is true regardless of the existence of this particular bug in the PEAR installer, so the bug would not be treated as security-sensitive. As when handling system RPM packages, the root user must always ensure that any packages installed are from a trusted source and have been packaged correctly. This issue did not affect mysql packages as shipped in Red Hat Enterprise Linux 2.1, 3, and 4. Issue was addressed in mysql packages as shipped in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2008-0364.html Red Hat does not consider this flaw to have security consequences. For more details please see the following: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=240055 Updates for Red Hat Enterprise Linux are available from http://rhn.redhat.com/errata/RHSA-2007-0386.html Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-2691 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue did not affect mysql packages as shipped in Red Hat Enterprise Linux 2.1, 3 and 4. Affected mysql packages as shipped in Red Hat Enterprise Linux 5 and Red Hat Application Stack were fixed via: https://rhn.redhat.com/errata/CVE-2007-2692.html Not vulnerable. These issues did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect versions of ghostscript as shipped with Red Hat Enterprise Linux 2.1, 3, 4 or 5 as they do not include a bundled JasPer library. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5, or Red Hat Application Stack 1, or 2, as the packages shipped are not compiled with the mcrypt extension affected by this issue. Not vulnerable. This issue did not affect the versions of lcms as shipped with Red Hat Enterprise Linux 5. We do not consider this flaw to be a security issue as it is only exploitable by the script author. No trust boundary is crossed. This flaw exists in versions of PHP as shipped in Red Hat Enterprise Linux 5 and Red Hat Application Stack 1. These issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or Red Hat Application Stack 2. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates for libwmf in Red Hat Enterprise Linux 5 and 6. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. OPIE for PAM is not shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, 6, or 7. Red Hat does not consider a user-assisted crash of a user application such as Emacs to be a security issue. Not vulnerable. PHP is not built or supported in a multi-threaded environment in the packages distributed in Red Hat Enterprise Linux or Application Stack. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-2872 The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1 or 3. Not vulnerable. This issue did not affect Xen as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issu did not affect the versions of bind as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Updates are available for Red Hat Enterprise Linux 2.1, 3, 4, and 5 to correct this issue: http://rhn.redhat.com/errata/RHSA-2007-0740.html Not vulnerable. This issue did not affect the versions of bind as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248542 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Not vulnerable. This issue did not affect version of Sylpheed as shipped with Red Hat Enterprise Linux 2.1. Sylpheed and claws-mail are not shipped with Red Hat Enterprise Linux 3, 4, or 5. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php The Apache Software Foundation do not treat this as a security issue. A configuration change can be made to disable the ability to respond to HTTP TRACE requests if required. For more information please see: http://www.apacheweek.com/issues/03-01-24#news This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1 or 3. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1 or 3. Red Hat does not consider a user-assisted crash of a user application such as GIMP to be a security issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. Mozilla is no longer shipped as part of any version of Red Hat Enterprise Linux. Mozilla was replaced by SeaMonkey in Red Hat Enterprise Linux by SeaMonkey which is not affected by this issue. Not vulnerable. Versions of sudo package shipped with Red Hat Enterprise Linux versions 2.1, 3, 4 and 5 are linked with PAM support and never use libkrb5 authentication. This is not a security vulnerability: it is the expected behaviour of parse_str when used without a second parameter. Red Hat does not consider this do be a security issue. dblink is disabled in default configuration of PostgreSQL packages as shipped with Red Hat Enterprise Linux versions 2.1, 3, 4 and 5, and it is a configuration decision whether to grant local users arbitrary access. Fixes to correct this bug were included in PostgreSQL updates: https://rhn.redhat.com/cve/CVE-2007-3278.html Red Hat does not consider this do be a security issue. Creating functions is intended feature of the PL/pgSQL language and is definitely not a security problem. Weak passwords are generally more likely to be guessed with brute force attacks and choosing a strong password according to good practices is considered to be a sufficent protection against this kind of attack. Red Hat does not consider this do be a security issue. The ability of the superuser to execute code on behalf of the database server is an intended feature and imposes no security threat as the superuser account is restricted to the database administrator. Not vulnerable. PHP is not complied with the tidy library as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5, or Red Hat Application Stack v1 or v2. Not a vulnerability. In the security model used by Apache httpd, the less-privileged child processes (running as the "apache" user) completely handle the servicing of new connections. Any local user who is able to run arbitrary code in those children is therefore able to prevent new requests from being serviced, by design. Such users will also be able to "simulate" server load and force the parent to create children up to the configured limits, by design. Not vulnerable. This issue did not affect the versions of avahi as shipped with Red Hat Enterprise Linux 5. Not vulnerable, Red Hat do not ship the Lhaca file archiver. Note that an identical flaw was found affecting the lha file archiver in 2004, CVE-2004-0234. This issue was corrected by security update RHSA-2004:178 for Red Hat Enterprise Linux 2.1 and 3. Red Hat Enterprise Linux 4 was not vulnerable as it contained a backported patch to correct this issue from release. http://rhn.redhat.com/errata/RHSA-2004-178.html We do not consider this to be security issues. For more details see: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1 or 3. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates to libwmf on Red Hat Enterprise Linux 5 and 6. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates to libwmf on Red Hat Enterprise Linux 5 and 6. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of gd as shipped with Red Hat Enterprise Linux 2.1 or 3 as they did not offer GIF image support. We do not plan to backport a fix for this issue to the gd packages as shipped in Red Hat Enterprise Linux 4 and 5 due to the low likelihood of an application affected by this problem being exposed in a way that would allow a trust boundary to be crossed. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-3475 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-3476 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Due to the minimal impact of this flaw (temporary DoS by high CPU usage) and low likelihood of this problem being exposed in a way that would allow trust boundary crossing, we currently do not plan to backport a fix for this issue to the versions of gd as shipped in Red Hat Enterprise Linux 2.1, 3, 4 or 5. We currently do not plan to backport a fix for this issue to gd packages in current versions of Red Hat Enterprise Linux 2.1, 3, 4, and 5 due to the low likelihood of and application affected by this problem being exposed in a way that would allow trust boundary to be crossed. Not vulnerable. These issues did not affect the versions of freetype as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. After careful analysis by Red Hat and several Glibc developers, it has been determined that this bug is not exploitable. For more information please see Red Hat Bugzilla bug #247208 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=247208 This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. The curl packages as shipped with Red Hat Enterprise Linux versions 2.1, 3, 4 and 5 are not linked against the gnutls library. Red Hat does not consider bugs which result in a user-assisted crash of end user application to be a security issue. Not vulnerable. This plugin is not shipped with Squirrelmail in Red Hat Enterprise Linux. Not vulnerable. This plugin is not shipped with Squirrelmail in Red Hat Enterprise Linux. Not vulnerable. This plugin is not shipped with Squirrelmail in Red Hat Enterprise Linux. Not vulnerable. These issues did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. The Red Hat Security Response Team has rated this issue as having moderate security impact. The risks associated with fixing this bug are greater than the moderate severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG. Not vulnerable. libsilc was not shipped with Enterprise Linux 2.1 or 3. This issue did not affect the versions of libsilc as shipped with Red Hat Enterprise Linux 4 or 5. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1 or 3. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248553 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248553 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This flaw is specific to PHP on Windows. This issue does not affect the version of tcpdump shipped in Red Hat Enterprise Linux 2.1 or 3. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=250275 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-3799 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This issue only affected PHP on Windows platforms. This issue did not affect Red Hat Enterprise Linux 2.1 or 3. For Red Hat Enterprise Linux 4 and 5, Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248537 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1 or 3. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=250648 The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. Not vulnerable. This issue does not affect the versions of Firefox or Thunderbird as shipped with Red Hat Enterprise Linux. This issue did not affect the versions of sysstat as shipped with Red Hat Enterprise Linux 4. This issue has been addressed in Red Hat Enterprise Linux 5 via RHSA-2011:1005 advisory. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-3919 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue affected Red Hat Enterprise Linux 5 with a low security impact. An update to the compiz package was released to correct this issue: https://rhn.redhat.com/errata/RHSA-2008-0485.html Red Hat does not consider a user assisted client crash such as this to be a security flaw. Not vulnerable. fsplib is part of gftp in Red Hat Enterprise Linux 5, but this issue does not affect Linux. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1. Not vulnerable. Versions of PHP packages as shipped with current Red Hat products are not linked with t1lib. Not vulnerable. This issue does not affect the versions of Firefox or Thunderbird as shipped with Red Hat Enterprise Linux. Not vulnerable. This issue does not affect the versions of Firefox or Thunderbird as shipped with Red Hat Enterprise Linux. The CVE description for this bug is incorrect. The backported patch for CVE-2007-2447 missed the character c in the shell escaping whitelist of allowed characters, therefore not allowing commands with a c in them to be executed. This is therefore a regression bug and not a security vulnerability. The Red Hat Security Response Team has rated this issue as having low security impact. Updates to correct this are available: https://rhn.redhat.com/cve/CVE-2007-4045.html Not vulnerable. This is a rediscovery and therefore a duplicate of CVE-2000-1205 which was corrected in upstream Apache httpd 1.3.11. Not vulnerable. This flaw did not affect Red Hat Enterprise Linux 2.1, 3, or 4 due to the version of rsync. This flaw does exist in Red Hat Enterprise Linux 5, but due to the nature of the flaw it is not exploitable with any security consequence due to stack-protector. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. These issues did not affect the versions of Samba as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. These issues did not affect the dovecot versions as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. An update to Red Hat Enterprise Linux 5 was released to correct this issue: https://rhn.redhat.com/errata/RHSA-2008-0297.html Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=251708 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. Not vulnerable. These issues did not affect the versions of konqueror as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Red Hat does not consider a crash of a client application such as Konqueror to be a security flaw. Red Hat does not consider this flaw a security issue. This flaw will only crash OpenOffice.org if a victim opens a malicious document. Not vulnerable. PHP packages as shipped with Red Hat Enterprise Linux versions 2.1, 3, 4, and 5 are not compiled with msql library and are not vulnerable to this issue. Vulnerable. This issue affected the CUPS packages in Red Hat Enterprise Linux 5. This issue also affected the versions of CUPS packages in Red Hat Enterprise Linux 3 and 4, but exploitation would only lead to a possible denial of service. Updates are available from https://rhn.redhat.com/cve/CVE-2007-4351.html This is actually a flaw in browsers that do not derive the response character set as required by RFC 2616. This does not affect the default configuration of Apache httpd in Red Hat products and will only affect customers who have removed the "AddDefaultCharset" directive and are using directory indexes. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-4465 This issue was addressed in Red Hat Enterprise Linux 4 and 5 via https://rhn.redhat.com/errata/RHSA-2010-0141.html for tar. It did not affect the version of tar as shipped with Red Hat Enterprise Linux 3. This issue was also addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0144.html for cpio. It did not affect the version of cpio as shipped with Red Hat Enterprise Linux 3 and 4. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5, or Red Hat Application Stack 1. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=263261 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue was addressed in fetchmail packages as shipped in Red Hat Enterprise Linux 3, 4, and 5 via: https://rhn.redhat.com/errata/RHSA-2009-1427.html This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG. Shipped kernels do not include upstream commit a11d206d that introduced the problem. This upstream commit was backported in Red Hat Enterprise Linux 5 via RHBA-2008:0314. It was reported and addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0019.html Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1 or 3. This issue affected users who were running 64-bit versions of Red Hat Enterprise Linux 3, 4, or 5 on x86_64 architecture. It did not affect users of Red Hat Enterprise Linux 2.1. Updates are available for Red Hat Enterprise Linux 3, 4, and 5 to correct this issue. New kernel packages along with our advisory are available at the URL below as well as via the Red Hat Network. http://rhn.redhat.com/errata/CVE-2007-4573.html Not vulnerable. This issue did not affect the version of IrcII as shipped with Red Hat Enterprise Linux 2.1. IrcII was not shipped in Enterprise Linux 3, 4, or 5. Not vulnerable. This issue does not affect the versions of PHP shipped with Red Hat Enterprise Linux. It only affects the PHP version for Windows. Not vulnerable. This issue did not affect the versions of RealPlayer as shipped with Red Hat Enterprise Linux 3 Extras, 4 Extras, or 5 Supplementary. Not vulnerable. This issue was specific to a patch from Debian project and did not affect versions of tcp_wrappers packages as shipped with Red Hat Enterprise Linux. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php The only effect of this bug is to cause the process to read from a random segment of memory, if a large "length" parameter is passed to the strspn/strcspn function, which is under the control of the script author. This bug has no security impact. This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1. Not vulnerable. These issues did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Application Stack v1. Not vulnerable. Red Hat did not include an incomplete fix for CVE-2007-2872 for PHP in Red Hat Enterprise Linux or Red Hat Application Stack. For more details, see: https://bugzilla.redhat.com/show_bug.cgi?id=278161#c5 Not vulnerable. Red Hat did not include an incomplete fix for CVE-2007-2872 for PHP in Red Hat Enterprise Linux or Red Hat Application Stack. This bug can only be triggered by supplying a non-default openssl.conf configuration file, which is entirely under the control of the script author or server administrator, and hence is not a security issue. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Duplicate of CVE-2007-6113. This flaw was fixed for Red Hat Enterprise Linux 4 in RHSA-2007-0898: https://rhn.redhat.com/errata/RHSA-2007-0898.html Red Hat Enterprise Linux 5 is not affected by this flaw. More information can be found here: https://bugzilla.redhat.com/show_bug.cgi?id=285991 Red Hat Enterprise Linux 2.1 and 3 do not support the composite extension and are not vulnerable to this flaw. This issue did not affect the OpenSSH packages as distributed with Red Hat Enterprise Linux 2.1 or 3, as they do not support Trusted X11 forwarding. For Red Hat Enterprise Linux 4 and 5, this issue was addressed via: https://rhn.redhat.com/errata/RHSA-2008-0855.html We do not consider this to be a security issue. For more information please see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php We do not consider this to be a security issue. For more information please see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php We do not consider this to be a security issue. For more information please see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php We do not consider this to be a security issue. For more information please see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=285691 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-4829 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ We do not consider this to be a security issue. For more information please see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Not vulnerable. This flaw does not affect the Linux version of Firefox. Not vulnerable. There is no support for jffs2 in the Linux kernel as distributed with Red Hat Enterprise Linux 2.1 or 3. There is no ACL support for jffs2 in the Linux kernel as distributed with Red Hat Enterprise Linux 4 or 5. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php The argument passed to the dl() function must always be under the control of the script author. We therefore do not consider this to be a security issue. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php We do not consider a crash of a client application such as RealPlayer or Helix Player to be a security issue. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=295971 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Note: As the address of the overwritten byte is not under attackers control, the worst impact his bug could have is an application crash. It can not be exploited to execute arbitrary code. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of OpenSSL as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. An update to correct this issue for Enterprise Linux 5 is available. http://rhn.redhat.com/cve/CVE-2007-4995.html Please note that the CVE description is incorrect, this issue did not affect upstream versions of OpenSSL prior to 0.9.8. Not vulnerable. These issues did not affect the versions of Pidgin or Gaim as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. This issue affects the busybox package in Red Hat Enterprise Linux 2.1, 3, 4, and 5, This issue affects the fileutils package in Red Hat Enterprise Linux 2.1. This issue affects the coreutils package in Red Hat Enterprise Linux 3. The coreutils package in Red Hat Enterprise Linux 4 and 5 are not vulnerable to this issue. Given this issue has minimal risk we do not intend to issues updates to correct this issue in affected versions of Red Hat Enterprise Linux. For more information please see: https://bugzilla.redhat.com/show_bug.cgi?id=356471 Not vulnerable. This issue did not affect the versions of Pidgin or Gaim as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect version of balsa as shipped with Red Hat Enterprise Linux 2.1. According to Abobe this issue affects only the Windows platform and therefore does not affect Adobe Acrobat Reader as distributed with Red Hat Enterprise Linux Extras. http://www.adobe.com/support/security/advisories/apsa07-04.html Not vulnerable. These issues did not affect the versions of Firefox as shipped with Red Hat Enterprise Linux. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=181302 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Not vulnerable. This issue did not affect the versions of RealPlayer as shipped with Red Hat Enterprise Linux 3 Extras, 4 Extras, or 5 Supplementary. This issue was fixed in RealPlayer for Red Hat Enterprise Linux 3 Extras, 4 Extras, 5 Supplementary by RHSA-2007:0841 on 17th August 2007: https://rhn.redhat.com/errata/RHSA-2007-0841.html (Our original advisory did not mention this issue was fixed as the details of the issue were not made public by RealNetworks until 25th October 2007) Not vulnerable. These issues did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-5137 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Updates are available to address this issue: https://rhn.redhat.com/errata/RHSA-2007-0969.html Not vulnerable. These issues do not affect Linux versions of Sun JDK or JRE. Not vulnerable. These issues did not affect the versions of Sun JDK as shipped with Red Hat Enterprise Linux Extras 4 or 5. Not vulnerable. This issue did not affect the versions of libpng and libpng10 as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of libpng and libpng10 as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of libpng and libpng10 as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-5333 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This issue did not affect versions of tog-pegasus as shipped with Red Hat Enterprise Linux 4, or 5. For more details see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2007-5360 Not vulnerable. Red Hat Enterprise Linux 2.1, 3, and 4 did not include the Tramp extension with Emacs. The version of Tramp included with Emacs in Red Hat Enterprise Linux 5 was not vulnerable to this issue. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-5378 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Red Hat does not consider this to be a security issue. The function behaves as documented. Furthermore, the function shouldnt be considered a security feature, for reasons described at https://bugzilla.redhat.com/show_bug.cgi?id=332451#c3 and http://www.php.net/security-note.php Not vulnerable. The versions of bind as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5 do not support GSS-TSIG and are not linked with libgssapi library. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This vulnerability only affected the OpenSSL FIPS Object Module which is not enabled or used by OpenSSL in Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect versions of RealPlayer as shipped with Red Hat Enterprise Linux 3 and 4 Extras or with Red Hat Enterprise Linux 5 Supplementary. Not vulnerable. These issues did not affect PHP on Linux. Not vulnerable. This issue did not affect the versions of OpenLDAP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect Xen as shipped with Red Hat Enterprise Linux 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-5729 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This issue did not affect versions of plone included in conga/luci packages as shipped with Red Hat Enterprise Linux 5 or Red Hat Cluster Suite for Red Hat Enterprise Linux 4. Red Hat does not consider a user assisted client crash such as this to be a security flaw. Not vulnerable. This issue did not affect versions of Emacs as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect versions of geronimo-specs packages as shipped Red Hat Enterprise Linux 5, Red Hat Application Stack, Red Hat Application Server, Red Hat Directory Server and Red Hat Certificate System, as the geronimo-specs package only contains the specification of the Apache Geronimo Servers services and interfaces and not the vulnerable J2EE server classes. Not vulnerable. After a detailed analysis of this flaw, it has been determined that it is not exploitable on Red Hat Enterprise Linux 3, 4, or 5. For more information please see: https://bugzilla.redhat.com/show_bug.cgi?id=415141 Not vulnerable. This flaw does not affect the version of CUPS shipped in Red Hat Enterprise Linux 3 or 4. After a detailed analysis of this flaw, it has been determined it does not pose a security threat on Red Hat Enterprise Linux 5. For more details regarding this analysis, please see: https://bugzilla.redhat.com/show_bug.cgi?id=415131 This issue is not a vulnerability, for more information see http://marc.info/?m=119743235325151 Red Hat does not consider this flaw a security issue. This flaw is not exploitable and can only cause a client to stop responding or crash. This issue was fixed in all affected PHP versions shipped in Red Hat products. For list of security advisories, visit: https://rhn.redhat.com/errata/CVE-2007-5898.html The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run; any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-5901 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue is not a practical vulnerability, for more information see http://marc.info/?m=119743235325151 Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-5935 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of tetex packages as shipped with Red Hat Enterprise Linux 3, 4, or 5, as they do not provide the dviljk binary. Not vulnerable. This issue did not affect the versions of tetex packages as shipped with Red Hat Enterprise Linux 3, 4, or 5, as they do not provide dviljk binary. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-5963 The Red Hat Security Response Team has rated this issue as having low security impact, at this time Red Hat does not intend to address this flaw in a future update. Not vulnerable. This issue did not affect versions of qt or qt4 packages as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, and 4. It was addressed in Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2009-1193.html, and https://rhn.redhat.com/errata/RHSA-2008-0585.html respectively. Not vulnerable. This issue did not affect the mysql packages as shipped in Red Hat Enterprise Linux 2.1, 3, 4, 5, Red Hat Application Stack v1, and v2, as the versions shipped do not support table partitioning. The partitioning feature was introduced in development MySQL version 5.1. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-5971 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. See http://marc.info/?m=119743235325151 This issue is not a vulnerability, for more information see http://marc.info/?m=119743235325151 Not vulnerable. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 4 and 5. Red Hat doesnt consider this a security issue. The arguments to the functions in question should always be under the control of the script author, rather than untrusted script input, so these issues would not be treated as security-sensitive. Red Hat does not consider this issue to be a security vulnerability since no trust boundary is crossed. The user must voluntarily interact with the attack mechanism to exploit this flaw, with the result being the ability to run code as themselves. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-6113 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Red Hat does not consider this to be a security issue. Versions of rsync as shipped with Red Hat Enterprise Linux 2.1, 3, 4 and 5 behave as expected and that behavior was well documented. The Red Hat Security Response Team has rated this issue as having moderate security impact. This flaw has been addressed in Red Hat Enterprise Linux 5 via RHSA-2011:0999 advisory. This flaw did not affect the version of rsync as shipped with Red Hat Enterprise Linux 6. Red Hat does not intend to fix this flaw in Red Hat Enterprise Linux 4. Red Hat does not consider this issue to be a vulnerability. In order to exploit this for cross-site scripting, the attacker would have to get the victim to supply an arbitrary malformed HTTP method to a target site. However, this has been fixed in Red Hat Enterprise Linux 5 via RHBA-2009:0185 as a bug fix. Not vulnerable. These issues did not affect the versions of the zsh package as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Xen and KVM, as shipped with Red Hat Enterprise Linux 5 by default use only peripheral device emulation of QEMU and are therefore not vulnerable to this issue. Red Hat does not consider this a security issue. The downloading of arbitrary files will be harmless unless there is a vulnerability in the application handling these other filetypes. This flaw is not exploitable to run arbitrary code and can only cause an application crash. Red Hat does not consider a crash of the flac application or applications that use flac libraries such as media players to be a security issue. An update to Red Hat Enterprise Linux 5 was released to correct this issue: https://rhn.redhat.com/errata/RHSA-2008-0300.html Not Vulnerable. Red Hat does not ship a version of Apache Tomcat that enables the native APR connector. This issue did not affect the mysql packages as shipped in Red Hat Enterprise Linux 2.1, 3, 4, or 5. This issue affected the mysql packages as shipped in Red Hat Application Stack v1 and v2 and was addressed by RHSA-2007:1157: http://rhn.redhat.com/errata/RHSA-2007-1157.html Not vulnerable. The MySQL versions as shipped in Red Hat Enterprise Linux 2.1, 3, and 4 do not support federated storage engine. The MySQL package as shipped in Red Hat Enterprise Linux 5, Red Hat Application Stack v1, and Red Hat Application Stack v2 are not compiled with support for federated storage engine. Not vulnerable. This issue did not affect the versions of MySQL as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Red Hat does not consider this flaw to be a security issue. For more information please see: https://bugzilla.redhat.com/show_bug.cgi?id=426437 The versions of SquirrelMail packages shipped in Red Hat Enterprise Linux 3, 4, and 5 were not affected by this issue. In addition, the Red Hat Security Response Team have verified that the malicious code is not part of released Red Hat Enterprise Linux squirrelmail packages. Not vulnerable. Red Hat Enterprise Linux versions 2.1, 3, 4 and 5 do not ship with the alternate pdftops.pl CUPS printing filter that is affected by this flaw. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2008-0885.html mod_proxy_balancer is shipped in Red Hat Enterprise Linux 5 and Red Hat Application Stack v2. We do not plan on correcting this issue as it poses a very low security risk: The balancer manager is not enabled by default, the user targeted by the CSRF would need to be authenticated, and the consequences of an exploit would be limited to a web server denial of service. mod_proxy_balancer is included in the version of Apache HTTP Server as shipped in Red Hat Enterprise Linux 5 and Red Hat Application Stack v2. Red Hat was unable to reproduce this issue. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Enterprise MRG. Old versions of the Linux 2.4 kernel allowed the lookup of names containing backslashes over smbfs -- so there were multiple names which would reference any particular file, allowing the bypass of Apache controls such as AddType. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue was corrected with a backported patch for Red Hat Enterprise Linux 2.1 by RHSA-2007:0672. https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2007-6514 Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect versions of Dovecot as shipped with Red Hat Enterprise Linux before version 5. An update to Red Hat Enterprise Linux 5 was released to correct this issue: https://rhn.redhat.com/errata/RHSA-2008-0297.html Red Hat does not consider this flaw a security issue. This flaw is not exploitable beyond causing the web browser to crash. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-6720 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue affects the version of httpd package as shipped with Red Hat Enterprise Linux 4. This issue is mitigated by the use of mod_reqtimeout module shipped with the httpd package in Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect cryptography library packages as shipped with Red Hat products, as they do not implement Dual EC DRBG algorithm. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG. Red Hat Enterprise Linux 5 is now in Extended Life-cycle Support phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. NVD clarification: To exploit this flaw an attacker needs to print a malicious file through the vulnerable filter (either themselves or by convincing a victim to do so), it should therefore be AC:M In CUPS, print filters run as an unprivileged user no superuser (root), therefore this should be scored C:P, I:P, A:P This issue did not affect the versions of GNU libc as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. This issue affects the versions of libbind as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5, however the vulnerable function is not used by any shipped applications. The Red Hat Security Response Team has therefore rated this issue as having low security impact, a future update may address this flaw. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2008-0122 An update to Red Hat Enterprise Linux 5 was released to correct this issue: https://rhn.redhat.com/errata/RHSA-2008-0300.html Red Hat does not consider this to be a security issue. Regression introduced break glob() functionality, but does not bypass security restrictions. Furthermore, "open_basedir" bypass issues are not treated as security sensitive as described at https://bugzilla.redhat.com/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This flaw was caused by a third-party vendor patch to the OpenSSL library. This patch has never been used by Red Hat, and this issue therefore does not affect any Fedora, Red Hat, or upstream supplied OpenSSL packages. This issue did not affect the version of boost as shipped with Red Hat Enterprise Linux 4 and 6. This issue was addressed in boost packages in Red Hat Enterprise Linux 5 via RHSA-2012:0305. This issue did not affect the version of boost as shipped with Red Hat Enterprise Linux 4 and 6. This issue was addressed in boost packages in Red Hat Enterprise Linux 5 via RHSA-2012:0305. Not vulnerable. This issue did not affect versions of MySQL as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, Red Hat Application Stack v1, and v2, as they are not built with yaSSL support. Not vulnerable. This issue did not affect versions of MySQL as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, Red Hat Application Stack v1, and v2, as they are not built with yaSSL support. Not vulnerable. These issues did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2008-0414 The Red Hat Security Response Team has rated this issue as having moderate security impact, a future updates will address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ We believe this issue is a duplicate of CVE-2007-5360. Not vulnerable. This issue did not affect versions of tog-pegasus as shipped with Red Hat Enterprise Linux 4, or 5. For more details see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2007-5360 Not vulnerable. This does not affect the versions of Firefox or SeaMonkey shipped in Red Hat Enterprise Linux. Not vulnerable. This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5, and Red Hat Application Stack v1. For Red Hat Application Stack v2, issue was addressed via: https://rhn.redhat.com/errata/RHSA-2008-0505.html This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4. Updated kernel packages are available to correct this issue for Red Hat Enterprise Linux 5: https://rhn.redhat.com/errata/RHSA-2008-0129.html Not vulnerable. This issue did not affect the versions of PCRE as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2008-0883 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of OpenSSL as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect versions of pax as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect versions of pcre as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of cups as shipped with Red Hat Enterprise Linux 3, 4, or 5. The affected version of Wireshark as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2008-0890.html The affected version of Wireshark as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2008-0890.html The affected version of Wireshark as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2008-0890.html The risks associated with fixing this bug are greater than the low severity security risk.We therefore currently have no plans to fix this flaw in Red HatEnterprise Linux. For more information please see the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=435420 Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2008-1142 This issue does not affect Red Hat Enterprise Linux 3, 4, or 5. The Red Hat Security Response Team has rated this issue as having low security impact. Due to the minimal security consequences of this issue, we do not intend to fix this in Red Hat Enterprise Linux 2.1. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue was addressed in affected versions of Ruby as shipped in Red Hat Enterprise Linux 4 and 5 via: https://rhn.redhat.com/errata/RHSA-2008-0897.html Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2008-1198 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2008-1199 This issue does not affect the default configuration of Dovecot as shipped in Red Hat Enterprise Linux. The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. An update to Red Hat Enterprise Linux 5 was released to correct this issue: https://rhn.redhat.com/errata/RHSA-2008-0297.html Not vulnerable. This issue did not affect versions of Dovecot as shipped with Red Hat Enterprise Linux 4 or 5. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2008-0612.html Not vulnerable. This issue did not affect versions of RealPlayer as shipped with Red Hat Enterprise Linux 3 Extras, 4 Extras, or 5 Supplementary. Not vulnerable. This issue did not affect the versions of dhcp as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Red Hat has re-evaluated the potential impact of this flaw and has released an update which corrects this behavior: http://rhn.redhat.com/errata/RHSA-2008-0893.html This issue does not affect the version of libpng as shipped with Red Hat Enterprise Linux 3. Updates for affected versions of Red Hat Enterprise Linux can be found here: http://rhn.redhat.com/errata/RHSA-2009-0333.html Red Hat do not consider this to be a security vulnerability: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-1384 Red Hat does not consider this to be a security issue. Properly written application should not use arbitrary untrusted data as part of the format string passed to functions as strfmon or printf family functions. http://rhn.redhat.com/errata/RHSA-2008-0533.html All openssh versions shipped in Red Hat Enterprise Linux 5 include the patch for this issue. This issue was fixed in Red Hat Enterprise Linux 4 via: https://rhn.redhat.com/errata/RHSA-2005-527.html Red Hat Enterprise Linux 3 is affected by this issue. The Red Hat Security Response Team has rated this issue as having low security impact. https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-1483 This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 5, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise Linux 4 via: https://rhn.redhat.com/errata/RHSA-2008-0972.html Not vulnerable. This issue does not affect the versions of gnupg packages as shipped with Red Hat Enterprise Linux versions 2.1, 3, 4 or 5. Red Hat does not consider this issue to be a security flaw as SILC is not used in a vulnerable manner in Red Hat Enterprise Linux 4 and 5. More information can be found here: https://bugzilla.redhat.com/show_bug.cgi?id=440049 The affected version of Wireshark as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2008-0890.html The affected version of Wireshark as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2008-0890.html The affected version of Wireshark as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2008-0890.html Red Hat does not consider this libTIFF bug to be a security issue. This issue did not affect the audit packages as shipped with Red Hat Enterprise Linux 4. Red Hat is not treating this issue as a security vulnerability for Red Hat Enterprise Linux 5 as no application used the affected interface, and the only result is a controlled application termination as the overflow is detected by the FORTIFY_SOURCE protection mechanism. We plan to address this as non-security bug fix in updated audit packages for Red Hat Enterprise Linux 5.2. For further details, please see: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-1628 Not vulnerable. These issues did not affect the versions of OpenSSH as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This flaw does not affect teh version of wu-ftpd as shipped in Red Hat Enterprise Linux 2.1. Not vulnerable. This issue did not affect versions of KDE as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect versions of KDE as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of OpenSSL as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2, 3, 4, 5 or Red Hat Enterprise MRG. The but existed on Red Hat Enterprise Linux 3, 4, and 5. However, this is only a security issue if the SLOB or SLUB memory allocators were used (introduced in Linux kernel versions 2.6.16 and 2.6.22, respectively). All Red Hat Enterprise Linux and Red Hat Enterprise MRG kernels use the SLAB memory allocator, which in this case, cannot be exploited to allow arbitrary code execution. As a preventive measure, the underlying bug was addressed in Red Hat Enterprise Linux 3, 4, and 5, via the advisories RHSA-2008:0973, RHSA-2008:0508, and RHSA-2008:0519, respectively. Not vulnerable. This issue did not affect versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of mod_ssl or httpd as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5 prior to 5.3. In Red Hat Enterprise Linux 5.3, OpenSSL packages were rebased to upstream version 0.9.8e via RHBA-2009:0181 (https://rhn.redhat.com/errata/RHBA-2009-0181.html), introducing this problem in Red Hat Enterprise Linux 5. Updated httpd packages were released via: https://rhn.redhat.com/errata/RHSA-2009-1075.html Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2008-1679 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ The Red Hat Security Response Team is aware of this new gcc behavior and is currently working to determine what impact these changes will have on the source code processed by the compiler. These changes do not affect Red Hat Enterprise Linux 2, 3, 4, or 5. Red Hat does not consider this to be a security issue. After careful analysis of this issue the Red Hat Security Response Team has determined that this bug has no security impact outside of expected m4 behavior. Red Hat does not consider this to be a security issue. After careful analysis of this issue the Red Hat Security Response Team has determined that this bug has no security impact outside of expected m4 behavior. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue did not affect versions of rsync as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=442005 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Not vulnerable. This issue did not affect the versions of rdesktop as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2008-1891 The risks associated with fixing this flaw outweigh the benefits of the fix. Red Hat does not plan to fix this flaw in Red Hat Enterprise Linux. Red Hat is aware of this issue affecting Red Hat Enterprise Linux 5 and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2008-1926 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue has been addressed in Red Hat Enterprise Linux 4 with the following update: https://rhn.redhat.com/errata/RHSA-2009-0981.html This is not a security flaw in Struts. Struts has never guaranteed to perform filtering of the untrusted user inputs used as html tag attributes names or values. If user inputs need to be used as part of the tag attributes, the JSP page needs to perform filtering explicitly. For further details, see: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-2025 This issue does not affect the version of PHP shipped in Red Hat Enterprise Linux 2.1, 3, or 4. We do not consider this issue to be a security flaw for Red Hat Enterprise Linux 5 since no trust boundary is crossed. More information can be found here: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-2050 This issue did not affect MySQL as supplied with Red Hat Enterprise Linux 3. This issue was addressed for Red Hat Enterprise Linux 4, 5, and Red Hat Application Stack v1, v2: https://rhn.redhat.com/cve/CVE-2008-2079.html Not vulnerable. Red Hat Enterprise Linux 2.1, 3, 4, and 5 do not ship for the SPARC architecture. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This is actually a flaw in browsers that do not derive the response character set as required by RFC 2616. This does not affect the default configuration of Apache httpd in Red Hat products and will only affect customers who have removed the "AddDefaultCharset" directive. https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-2168 Not vulnerable. This issue does not affect the version of c++filt as shipped with binutils in Red Hat Enterprise Linux 3 or 4. Although this bug is present in the version of c++filt as shipped with binutils in Red Hat Enterprise Linux 5, the format string protection from FORTIFY_SOURCE makes this unexploitable. Not vulnerable. This issue did not affect the versions of python as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Affected module was only introduced upstream in python 2.5. This issue does not affect the versions of mtr as shipped with Red Hat Enterprise Linux 4 or 5. For Red Hat Enterprise Linux 2.1 and 3, this issue can only be exploited if an attacker can convince victim to use mtr to trace path to or via the IP, for which an attacker controls PTR DNS records. Additionally, the victim must run mtr in "split mode" by providing -p or --split command line options. The Red Hat Security Response Team has therefore rated this issue as having low security impact, a future update may address this flaw. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2008-0519.html Not vulnerable. This issue did not affect the versions of pan as shipped with Red Hat Enterprise Linux 2.1. No other versions of Red Hat Enterprise Linux have shipped Pan. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2008-2364 The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Not vulnerable. This issue did not affect the versions of PCRE as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of gnutls as shipped with Red Hat Enterprise Linux 4, or 5. Not vulnerable. This issue did not affect the version of the Xen package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. OCSP protocol support was only implemented in upstream stunnel version 4.16. Therefore OCSP protocol is not available in the versions of stunnel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Enterprise MRG. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php This issue was addressed in fetchmail packages as shipped in Red Hat Enterprise Linux 3, 4, and 5 via: https://rhn.redhat.com/errata/RHSA-2009-1427.html Not vulnerable. These issues did not affect the versions of NASM as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of perl as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5, Red Hat Application Stack 1, or Solaris versions of Red Hat Directory Server 7.1 and 8, Certificate System 7.x. Not vulnerable. This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. For more details see: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-2829 Not vulnerable. This issue did not affect the versions of XChat as shipped with Red Hat Enterprise Linux. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2008-0885.html Not vulnerable. This issue did not affect the versions of firefox as shipped with Red Hat Enterprise Linux 4, or 5. These issue was addressed in all affected httpd versions as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2008-0967.html This issue is tracked via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2008-2939 The Red Hat Security Response Team has rated this issue as having low security impact, future updates may address this flaw in other affected products (such as Red Hat Application Stack). Not vulnerable. This issue did not affect the versions of poppler as shipped with Red Hat Enterprise Linux 5, or other PDF parsing applications derived from the xpdf code as shipped in Red Hat Enterprise Linux 2.1, 3, 4, or 5. According to RealNetworks this flaw does not affect the Linux version of RealPlayer. According to RealNetworks this issue does not affect the Linux version of RealPlayer. Not vulnerable. This issue did not affect the versions of sudo as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of the Vim packages, as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5. Note: This CVE is mentioned in the text of RHSA-2008:0580 (https://rhn.redhat.com/errata/RHSA-2008-0580.html), as it was originally used to track multiple issues. Issues that affected Vim packages in Red Hat Enterprise Linux 5 were later assigned separate CVE identifier - CVE-2008-6235. Neither of issues currently covered by CVE-2008-3076 (insufficient shell escaping in mz and mc commands) affected Vim packages shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. We do not consider a crash of a client application such as ImageMagick to be a security issue. The affected version of Wireshark as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2008-0890.html The affected version of Wireshark as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2008-0890.html Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5 The affected version of Wireshark as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2008-0890.html The affected version of Wireshark as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2008-0890.html Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the version of dnsmasq as shipped with Red Hat Enterprise Linux 5. Upon investigating this issue, the Red Hat Security Response Team has determined that this is not a vulnerability. The ability to specify a desired role when connecting to OpenSSH is a feature of how OpenSSH interacts with SELinux. Users can only assign themselves SELinux roles which they have permission to access. They cannot assign themselves arbitrary roles. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Enterprise MRG. Not vulnerable. This issue did not affect the versions of openssh as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. This issue can only be exploited during the package build and it does not affect users of pre-built packages distributed with Red Hat Enterprise Linux. Therefore, we do not plan to backport a fix for this issue to already released version of Red Hat Enterprise Linux 2.1, 3, 4, and 5. Not vulnerable. This issue did not affect the versions of links as shipped with Red Hat Enterprise Linux 2.1, and versions of elinks as shipped with Red Hat Enterprise Linux 3, 4, or 5. Versions of links / elinks shipped do not support "only proxies" feature. Not vulnerable. These issues did not affect the version of dnsmasq as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of OpenOffice.org as shipped with Red Hat Enterprise Linux 3, 4, or 5. The updated Red Hat Enterprise Linux packages are not distributed via the openoffice.org update service, but rather via Red Hat Network, using the package manager capabilities to verify authenticity of updates. Not vulnerable. This issue did not affect the versions of Sun Java packages as shipped with Red Hat Enterprise Linux 4 Extras, or 5 Supplementary. The updated Red Hat Enterprise Linux packages are not distributed via the java.sun.com update service (which is only used for Windows version of Sun Java), but rather via Red Hat Network, using the package manager capabilities to verify authenticity of updates. Red Hat does not consider this flaw a security issue. This flaw is not exploitable beyond causing the web browser to crash. This flaw does not affect the Linux version of RealVNC as shipped in Red Hat Enterprise Linux. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Enterprise MRG. The uvcvideo driver was first added in kernel packages update RHSA-2009:0225 in Red Hat Enterprise Linux 5.3, and it already contained a fix for this flaw. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5. It was addressed in Red Hat Enterprise MRG for RHEL-5 via: https://rhn.redhat.com/errata/RHSA-2008-0857.html This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2008-0957.html This issue does not affect the versions of the yelp package, as shipped with Red Hat Enterprise Linux 3, 4 and 5. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5. It was addressed in Red Hat Enterprise MRG for RHEL-5 via: https://rhn.redhat.com/errata/RHSA-2008-0857.html This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5. It was addressed in Red Hat Enterprise MRG for RHEL-5 via: https://rhn.redhat.com/errata/RHSA-2008-0857.html This issue has been addressed in the affected versions of PHP packages shipped in Red Hat Enterprise Linux via advisories listed on the following page: https://rhn.redhat.com/errata/CVE-2008-3658.html The PHP interpreter does not offer a reliable "sandboxed" security layer (as found in, say, a JVM) in which untrusted scripts can be run any script run by the PHP interpreter must be trusted with the privileges of the interpreter itself. We therefore do not classify this issue as security-sensitive since no trust boundary is crossed. This issue has been fixed in the affected Red Hat Enterprise Linux versions via: https://rhn.redhat.com/errata/RHSA-2009-0010.html Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Enterprise MRG. Not vulnerable. This issue did not affect the version of Xen hypervisor as shipped with Red Hat Enterprise Linux 5, as it does not support XSM. Not vulnerable. This issue did not affect the versions of neon as shipped with Red Hat Enterprise Linux 4, or 5. Not vulnerable. This issue did not affect the versions of samba as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5. It was addressed in Red Hat Enterprise MRG for RHEL-5 via: https://rhn.redhat.com/errata/RHSA-2008-0857.html This issue did not affect the version of pam_krb5 shipped in Red Hat Enterprise Linux 2.1, 3, or 4. Not vulnerable. This issue did not affect the version of utrace as shipped with the Red Hat Enterprise Linux 5 kernel. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2008-0957.html Not vulnerable. This issue did not affect the versions Postfix as shipped with Red Hat Enterprise Linux 3, 4, or 5. Red Hat does not consider this to be a security issue. Since these operations can only be executed by root, no trust boundary is crossed as a result of this behaviour. Red Hat does not consider this to be a security issue. Since these operations can only be executed by root, no trust boundary is crossed as a result of this behaviour. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Enterprise MRG. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5. It was addressed in Red Hat Enterprise MRG for RHEL-5 via: https://rhn.redhat.com/errata/RHSA-2008-0857.html Not vulnerable. This issue did not affect the versions of the emacs package, as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. This issue did not affect MySQL as supplied with Red Hat Enterprise Linux 3 or 4. This issue was addressed for Red Hat Enterprise Linux 5 and Red Hat Application Stack v2 https://rhn.redhat.com/cve/CVE-2008-3963.html Not vulnerable. These issues did not affect the versions of libpng as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of MySQL as shipped with any Red Hat product as the improper fix for CVE-2008-2097 that led to the issuance of this CVE was never used. This issue was addressed in Red Hat Enterprise Linux 4 via https://rhn.redhat.com/errata/RHSA-2010-0110.html and in Red Hat Application Stack v2 via https://rhn.redhat.com/errata/RHSA-2009-1067.html . In Red Hat Enterprise Linux 5, issue CVE-2008-2079 was fixed without introducing CVE-2008-4098 in https://rhn.redhat.com/errata/RHSA-2009-1289.html . The risks associated with fixing this bug are greater than the security risk. We therefore currently have no plans to fix this flaw in Red HatEnterprise Linux 2.1, 3, 4, or 5. For more information please see our bug for this issue: https://bugzilla.redhat.com/show_bug.cgi?id=462772 Not vulnerable. This issue did not affect the versions of python as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. The patch used to fix CVE-2006-5051 in Red Hat Enterprise Linux 2.1, 3, 4, and 5 was complete and does not suffer from this problem. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5. It was addressed in Red Hat Enterprise MRG for RHEL-5 via: https://rhn.redhat.com/errata/RHSA-2008-0857.html Not vulnerable. This flaw does not affect the version of BIND as shipped in Red Hat Enterprise Linux 2.1, 3, 4, or 5. This issue has been addressed via: https://rhn.redhat.com/errata/RHSA-2009-0402.html Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of rsh-server packages as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. The glibcs ruserok function is used to check users authorization against rhosts files. That implementation of ruserok never opens /etc/hosts.equiv for superuser. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2008-0957.html Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue did not affect the versions of Samba as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. We do not consider a crash of a client application such as Konqueror to be a security issue. Not vulnerable. ndiswrapper is not shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Enterprise MRG. Not vulnerable. This issue did not affect the versions of libxml2 as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Enterprise MRG. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5. It was addressed in Red Hat Enterprise MRG for RHEL-5 via: https://rhn.redhat.com/errata/RHSA-2008-0857.html Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-4456 This issue was addressed for Red Hat Enterprise Linux 5 by https://rhn.redhat.com/errata/RHSA-2009-1289.html and Red Hat Enterprise Linux 4 by https://rhn.redhat.com/errata/RHSA-2010-0110.html . The Red Hat Security Response Team has rated this issue as having low security impact, future MySQL package updates may address this flaw for Red Hat Enterprise Linux 3, and Red Hat Application Stack 2. Not vulnerable. This issue did not affect the versions of freeradius as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not Vulnerable. Red Hat Enterprise MRG does not use Xerces-C++ in a manner that is vulnerable to this flaw. We do not consider a crash of a client application such as Konqueror to be a security issue. This issue affected Red Hat Enterprise Linux 5 and was addressed by https://rhn.redhat.com/errata/RHSA-2009-1321.html The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 5. Manual fencing agent is documented to only be provided for testing purposes and should not be used in production environments. Therefore, there is no plan to fix this flaw in Red Hat Cluster Suite for Red Hat Enterprise Linux 4, and in Red Hat Enterprise Linux 5. The attacks reported by Outpost24 AB target the design limitations of the TCP protocol. Due to upstreams decision not to release updates, Red Hat do not plan to release updates to resolve these issues however, the effects of these attacks can be reduced via the mitigation methods as written in http://kbase.redhat.com/faq/docs/DOC-18730. The versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5 were not affected by this issue. This issue only affected the version of Linux kernel as shipped with Red Hat Enterprise MRG and was addressed via: https://rhn.redhat.com/errata/RHSA-2009-0009.html Not vulnerable. This issue did not affect the versions of vim as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. This issue has been addressed in Wireshark packages as shipped in Red Hat Enterprise Linux 3, 4 and 5 via: https://rhn.redhat.com/errata/RHSA-2009-0313.html This issue has been addressed in Wireshark packages as shipped in Red Hat Enterprise Linux 3, 4 and 5 via: https://rhn.redhat.com/errata/RHSA-2009-0313.html This issue has been addressed in Wireshark packages as shipped in Red Hat Enterprise Linux 3, 4 and 5 via: https://rhn.redhat.com/errata/RHSA-2009-0313.html This issue has been addressed in Wireshark packages as shipped in Red Hat Enterprise Linux 3, 4 and 5 via: https://rhn.redhat.com/errata/RHSA-2009-0313.html This issue has been addressed in Wireshark packages as shipped in Red Hat Enterprise Linux 3, 4 and 5 via: https://rhn.redhat.com/errata/RHSA-2009-0313.html This issue has been addressed in Wireshark packages as shipped in Red Hat Enterprise Linux 3, 4 and 5 via: https://rhn.redhat.com/errata/RHSA-2009-0313.html Red Hat does not consider this to be a security flaw. Firefox is handling the ftp:// URL as expected. This issue can only cause pamperspective to crash when used on specially crafted messages. We do not consider this to be a security issue. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2008-4865 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Not vulnerable. This issue did not affect the versions of the dovecot package, as shipped with Red Hat Enterprise Linux 4 or 5. Not vulnerable. This issue did not affect the versions of mgetty as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5, as they include patch that resolves this issue. Not vulnerable. This issue did not affect the versions of OpenOffice.org as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of postfix as shipped with Red Hat Enterprise Linux 3, 4, or 5. Mentioned script is not part of the official postfix distribution and is not included in Red Hat Enterprise Linux postfix packages. The affected code is not used by any application shipped in Red Hat Enterprise Linux 2.1, 3, 4, and 5. The impact of this flaw is limited to a crash of the applications connecting to a misbehaving SMTP server. Due to those reasons, theres currently no plan to include the fix in the imap packages as shipped in Red Hat Enterprise Linux 2.1 and 3, and the libc-client packages as shipped in Red Hat Enterprise Linux 4 and 5. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Enterprise MRG. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. The issue was addressed in the Linux kernel packages as shipped with Red Hat Enterprise MRG via: https://rhn.redhat.com/errata/RHSA-2009-0053.html This issue was addressed for Red Hat Enterprise Linux 5 by https://rhn.redhat.com/errata/RHSA-2009-1287.html After reviewing the upstream fix for this issue, Red Hat does not intend to address this flaw in Red Hat Enterprise Linux 4. Not vulnerable. This issue did not affect the versions of CUPS as shipped with Red Hat Enterprise Linux 3, 4, or 5. Versions shipped do not support RSS subscriptions. Not vulnerable. This issue does not affect the versions of imlib as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. This issue has been addressed in Wireshark packages as shipped in Red Hat Enterprise Linux 3, 4 and 5 via: https://rhn.redhat.com/errata/RHSA-2009-0313.html Not vulnerable. This issue did not affect the versions of dovecot as shipped with Red Hat Enterprise Linux 4, or 5. Those packages do not include ManageSieve server. This issue has been addressed in perl packages as shipped in Red Hat Enterprise Linux 3 and 4 via https://rhn.redhat.com/errata/RHSA-2010-0457.html and Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0458.html. This issue has been addressed in perl packages as shipped in Red Hat Enterprise Linux 3 and 4 via https://rhn.redhat.com/errata/RHSA-2010-0457.html and Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0458.html. The Red Hat Security Response Team has rated this issue as having low security impact. This issue is not currently planned to be addressed in Red Hat Enterprise Linux 6. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2008-5374 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Not vulnerable. This issue did not affect the versions of CUPS as shipped with Red Hat Enterprise Linux 3, 4, or 5. Affected script is not part of the upstream CUPS distribution, but rather an addition used by Debian-based distributions (and possibly others). CUPS packages as shipped in Red Hat Enterprise Linux 5 also provide pstopdf filter. However, that filter is different from the one used in Debian-based distributions, and is unaffected by this flaw. Additionally, all filters used by CUPS on all versions of Red Hat Enterprise Linux are run under an unprivileged "lp" user, making the root privilege escalation mentioned in the published exploit impossible. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Enterprise MRG. It only affected the Ubuntu Privacy Remix (UPR) kernel. Not vulnerable. This issue did not affect the versions of the util-linux packages (providing /bin/login), as shipped with Red Hat Enterprise Linux 2.1, 3, 4 or 5. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Enterprise MRG. Red Hat does not provide support for the Linux kernel on the PA-RISC architecture. Not vulnerable. This issue did not affect the versions of imap as shipped with Red Hat Enterprise Linux 2.1 and 3, and the versions of libc-client as shipped with Red Hat Enterprise Linux 4 and 5. Not vulnerable. This issue did not affect the version of the rsyslog package, as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the version of the rsyslog package, as shipped with Red Hat Enterprise Linux 5. We do not consider these to be security issues. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php We do not consider this to be a security issue. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php This issue did not affect PHP versions as shipped in Red Hat Enterprise Linux 2.1, 3, 4, and 5, and Red Hat Application Stack v1. PHP version in Red Hat Application Stack v2 was fixed via: https://rhn.redhat.com/errata/RHSA-2009-0350.html The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 5. Red Hat does not consider a crash of a client application such as Konqueror to be a security issue. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Enterprise MRG. Red Hat does not provide support for the Linux kernel on the MIPS architecture. Red Hat does not consider a crash of a client application such as Konqueror to be a security issue. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2009-0264.html Not vulnerable. This issue did not affect the versions of Xen as shipped with Red Hat Enterprise Linux 5. Red Hat does not consider a crash of a client application such as Firefox to be a security issue. Not vulnerable. This issue did not affect the versions of Xen as shipped with Red Hat Enterprise Linux 5. Security update released to address CVE-2008-4405 - https://rhn.redhat.com/errata/RHSA-2009-0003.html - contained correct patch which did not introduce this problem and resolved the original issue. Red Hat does not consider a crash of a client application such as Firefox to be a security issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of the php package, as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, and with Red Hat Application Stack v1 and v2. Only PHP version 5.2.7 was affected by this flaw. Red Hat does not consider this bug to be a security issue. For a more detailed explanation, please see the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-5907 This issue does not affect the versions of the eog package, as shipped with Red Hat Enterprise Linux 3, 4, and 5. The costs associated with fixing these bug are greater than the posed security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux at this time. The costs associated with fixing these bug are greater than the posed security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux at this time. The costs associated with fixing these bug are greater than the posed security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux at this time. Not vulnerable. Red Hat Enterprise Linux 2.1, 3, 4, and 5 do not ship for the SPARC architecture. We do not consider a crash of a client application linked to libpng to be a security issue. None of the applications that use libpng are at any risk of causing a denial of service in a meaningful way. The issue does not affect any Red Hat products as no products ship Struts2/XWork binaries. Red Hat does not consider this to be a security issue. The misbehaviour of CMAN is triggered by corrupted / specially crafted cluster.conf configuration file. Ability to edit this file is restricted to system administrator, therefore no privilege boundary is crossed. The costs associated with fixing these bug are greater than the posed security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux at this time. This is not a security issue. For further details, see: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-7002#c7 This is not a security issue. A user with read and write access to a file can reasonably be expected to manipulate the contents of the file, including truncating it. Instead of using dba_replace(), a user could simply fopen() the file in write mode, which provides the same end-result. Not vulnerable. This issue did not affect the versions of libsilc as shipped with Red Hat Enterprise Linux 4, or 5. Not vulnerable. This issue did not affect the versions of libsilc as shipped with Red Hat Enterprise Linux 4, or 5. Not vulnerable. This issue did not affect the versions of nasm as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and 5 as they did not include nfs-export support for tmpfs. A future kernel update in Red Hat Enterprise MRG will address this issue. This issue was addressed in Red Hat Enterprise Linux 5 and 6 by rebasing Firefox to 10.0.0 ESR. Not vulnerable. This issue did not affect the versions of samba as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 and Red Hat Enterprise MRG. This flaw affects most 64-bit architectures, including IBM S/390 and 64-bit PowerPC, but it does not affect x86_64 or Intel Itanium. The risks associated with fixing this flaw are greater than the security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 3, 4, or 5. Red Hat Enterprise MRG is not affected as it is not supported on 64-bit architectures other than x86_64. Not vulnerable. Red Hat does not ship the vulnerable backend that causes this flaw. Red Hat does not consider a crash of a client application such as Firefox to be a security issue. Not vulnerable. This issue did not affect the versions of hplip as shipped with Red Hat Enterprise Linux 5. Red Hat does not consider this to be a security issue. M2Crypto provides python interfaces to multiple OpenSSL functions. Neither of those interfaces is further used by M2Crypto in an insecure way. Additionally, no application shipped in Red Hat Enterprise Linux is known to use affected interfaces provided by M2Crypto. Further details can be found in the following bug report: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-0127#c1 The Red Hat Security Response Team has rated this issue as having low security impact. The risks associated with fixing this bug are greater than the security risk. We therefore have no plans to fix this flaw in Red Hat Enterprise Linux 4 and 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2009-0179 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2009-0241 The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update of Red Hat HPC Solution may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Red Hat does not consider this to be a security issue. For more information, please see the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-0242 This issue can only result in an OpenOffice.org crash, not allowing arbitrary code execution. Red Hat does not consider a crash of a client application such as OpenOffice.org to be a security issue. Not vulnerable. This issue did not affect the versions of BIND as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, and Red Hat Enterprise MRG. This issue does not affect gedit as shipped in Red Hat Enterprise Linux 3 and 4. It does affect gedit in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect vim as shipped in Red Hat Enterprise Linux 3 and 4. This issue is not planned to be fixed in vim packages in Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of the pam_krb5 package, as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of the pam_krb5 package, as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the version of Squid as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of pam as shipped with Red Hat Enterprise Linux 3, 4, 5, or 6. This issue was fixed in openssl packages in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2009-1335.html This issue was fixed in openssl packages in Red Hat Enterprise Linux 3 and 4 via: https://rhn.redhat.com/errata/RHSA-2010-0163.html Not vulnerable. This issue affected OpenSSL CMS functionality which is not present in the openssl packages as shipped with Red Hat Enterprise Linux 2.1, 3, 4 or 5. Red Hat does not consider this to be a security issue. For further details, see: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-0601#c3 Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5, or Red Hat Enterprise MRG. Not vulnerable. This issue was addressed in upstream OpenSSL prior to 0.9.6 and therefore does not affect the versions of OpenSSL as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Disputed: The Red Hat Security Response Team have been unable to confirm the existence of this format string vulnerability in the toolkit, and the sample published exploit is not complete or functional. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 as the affected driver is not enabled in these kernels by default. The affected driver is enabled by default in Red Hat Enterprise Linux 2.1, 3, 5, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2009-0326.html and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2009-0360.html . As Red Hat Enterprise Linux 2.1 and 3 are now in Production 3 of their maintenance life-cycle, http://www.redhat.com/security/updates/errata, and this issue has been rated as having moderate impact, the fix for this issue is not currently planned to be included in the future updates. The upstream fix for this issue is not backwards compatible and introduces an ABI change not allowed in Red Hat Enterprise Linux. Therefore, there is no plan to address this problem directly in cyrus-sasl packages. All applications shipped in Red Hat Enterprise Linux and using affected sasl_encode64() function were investigated and patched if their use of the function could have security consequences. See following bug report for further details: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-0688#c20 This issue affected the dhcp packages as shipped with Red Hat Enterprise Linux 3 and 4. Updated packages to correct this issue are available via Red Hat Network: https://rhn.redhat.com/errata/CVE-2009-0692.html This issue did not affect the dhcp packages as shipped with Red Hat Enterprise Linux 5 due to the use of FORTIFY_SOURCE protection mechanism that changes the exploitability of the issue into a controlled application termination. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and Red Hat Enterprise MRG. This issue was addressed in Red Hat Enterprise Linux 5 by https://rhn.redhat.com/errata/RHSA-2009-1243.html This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and Red Hat Enterprise MRG. This issue was addressed in Red Hat Enterprise Linux 5 by https://rhn.redhat.com/errata/RHSA-2009-1243.html This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and Red Hat Enterprise MRG. This issue was addressed in Red Hat Enterprise Linux 5 by https://rhn.redhat.com/errata/RHSA-2009-1243.html This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and Red Hat Enterprise MRG. This issue was addressed in Red Hat Enterprise Linux 5 by https://rhn.redhat.com/errata/RHSA-2009-1243.html Not vulnerable. This issue did not affect the versions of poppler, xpdf, gpdf and kdegraphics as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue is a duplicate of CVE-2009-0166, which was addressed in affected products via following updates: https://rhn.redhat.com/errata/CVE-2009-0166.html This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2009-0326.html . Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2009-0781 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2009-0473.html . Not vulnerable. This issue only affects a small number of operating systems and does not affect the openssl packages as shipped with Red Hat Enterprise Linux 2.1, 3, 4 or 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2009-0796 The Red Hat Security Response Team has rated this issue as having moderate security impact, a future mod_perl package update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Not vulnerable. This issue did not affect the versions of mysql packages, as shipped with Red Hat Enterprise Linux 3, 4, or 5, and Red Hat Application Stack v2. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5. It was addressed in Red Hat Enterprise MRG via: https://rhn.redhat.com/errata/RHSA-2009-0451.html . Not vulnerable. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, or Red Hat Enterprise MRG. Red Hat does not consider this issue to be a security vulnerability. Affected function is only used to parse PAM configuration files and this bug can only be triggered by specific configuration created by the system administrator. This issue has been addressed in Red Hat Enterprise Linux 4 and 5 via: https://rhn.redhat.com/errata/RHSA-2009-1484.html and in Red Hat Application Stack v2 via: https://rhn.redhat.com/errata/RHSA-2009-1067.html Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, or Red Hat Enterprise MRG. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5. It was addressed in Red Hat Enterprise MRG via: https://rhn.redhat.com/errata/RHSA-2009-0451.html . This issue has been rated as having moderate security impact. It was addressed in Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG, via https://rhn.redhat.com/errata/RHSA-2009-1132.html , https://rhn.redhat.com/errata/RHSA-2009-1106.html , and https://rhn.redhat.com/errata/RHSA-2009-1081.html . This issue is not planned to be fixed in Red Hat Enterprise Linux 2.1 and 3, due to these products being in Production 3 of their maintenance life-cycles, where only qualified security errata of important or critical impact are addressed. This issue has been fixed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2009-0427.html . udev packages as shipped in Red Hat Enterprise Linux 4 were not affected by this flaw, as they do not use netlink sockets for communication. udev is not shipped in Red Hat Enterprise Linux 2.1 and 3. Not vulnerable. This issue did not affect the versions of udev as shipped with Red Hat Enterprise Linux 4, or 5. This flaw affected JBoss Enterprise BRMS Platform 5.1.0 when run on Sun JDK 1.5.x. It was resolved in JBoss Enterprise BRMS Platform 5.2.0, both by updating spring and by dropping support for Sun JDK 1.5.x. Red Hat does not consider this to be a security issue. Affected file is supposed to be used to exchange information between local system users, therefore open permissions are intentional. Red Hat does not consider this to be a security issue. The checks implemented by screen to protect against race condition attacks on /tmp/screen-exchange file provide sufficient protection for this rarely-used buffer exchange feature. For more details, see https://bugzilla.redhat.com/show_bug.cgi?id=492104 https://bugzilla.mozilla.org/show_bug.cgi?id=485941 Red Hat does not consider a user-assisted crash of a client application such as Firefox to be a security issue. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Enterprise MRG. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Enterprise MRG. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 4, 5, or Red Hat Enterprise MRG, as the affected driver is not enabled in these kernels. The affected driver is available in Red Hat Enterprise Linux 3, but only if the kernel-unsupported package is installed. This issue has been rated as having moderate security impact as it does not lead to a denial of service or privilege escalation. As Red Hat Enterprise Linux 3 is now in Production 3 of its maintenance life-cycle, http://www.redhat.com/security/updates/errata, and the affected driver can only be enabled when using the unsupported kernel-unsupported package, a fix for this issue is not currently planned to be included in the future updates. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5. This issue did not affect PHP versions as shipped in Red Hat Enterprise Linux 2.1, 3, 4, and 5, and Red Hat Application Stack v1. PHP version in Red Hat Application Stack v2 was fixed via: https://rhn.redhat.com/errata/RHSA-2009-0350.html Not vulnerable. This issue did not affect PHP versions as shipped in Red Hat Enterprise Linux 2.1, 3, 4, and 5, and Red Hat Application Stack v1 and v2. This problem was introduced in the fix for CVE-2008-5658. Patch for CVE-2008-5658 as used in Red Hat Application Stack v2 also includes the fix for this crash too. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2009-1284 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of ecryptfs-utils as shipped with Red Hat Enterprise Linux 5. eCryptfs encrypted home directories are not set up during the system installation, so theres no possibility for leaking encryption passwords to the installation log file. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG as they did not include upstream commit 7c73a6fa that introduced the problem. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, and 5. It was addressed in Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2009-1081.html . This flaw was caused by a C2Net specific patch added to Apache http_log.c in Stronghold 2.3. C2Net Stronghold 2.3 reached end of life for updates on October 31st 2000. http://www.awe.com/mark/history/stronghold.html Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, or Red Hat Enterprise MRG. This issue did not affect versions of openssl as shipped in Red Hat Enterprise Linux 3 and 4. This issue was addressed for Red Hat Enterprise Linux 5 by http://rhn.redhat.com/errata/RHSA-2009-1335.html Note that both the DTLS specification and OpenSSLs implementation is still in development and unlikely to be used in production environments. There is no component shipped in Red Hat Enterprise Linux 5 using OpenSSLs DTLS implementation, except for OpenSSLs testing command line client - openssl. This issue did not affect versions of openssl as shipped in Red Hat Enterprise Linux 3 and 4. This issue was addressed for Red Hat Enterprise Linux 5 by http://rhn.redhat.com/errata/RHSA-2009-1335.html Note that both the DTLS specification and OpenSSLs implementation is still in development and unlikely to be used in production environments. There is no component shipped in Red Hat Enterprise Linux 5 using OpenSSLs DTLS implementation, except for OpenSSLs testing command line client - openssl. This issue did not affect versions of openssl as shipped in Red Hat Enterprise Linux 3 and 4. This issue was addressed for Red Hat Enterprise Linux 5 by http://rhn.redhat.com/errata/RHSA-2009-1335.html Note that both the DTLS specification and OpenSSLs implementation is still in development and unlikely to be used in production environments. There is no component shipped in Red Hat Enterprise Linux 5 using OpenSSLs DTLS implementation, except for OpenSSLs testing command line client - openssl. Not vulnerable. This issue did not affect the versions of squirrelmail as shipped with Red Hat Enterprise Linux 3, 4, or 5. Updates for squirrelmail released via RHSA-2009:1066 (https://rhn.redhat.com/errata/RHSA-2009-1066.html) fixed original flaw CVE-2009-1579 without introducing CVE-2009-1381. This issue did not affect the versions of the pam_krb5 packages, as shipped with Red Hat Enterprise Linux 3 and 4. The issue was addressed in the pam_krb5 packages as shipped with Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2010-0258.html This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise 5 via: https://rhn.redhat.com/errata/RHSA-2009-1193.html Not vulnerable. This issue did not affect the versions of mutt as shipped with Red Hat Enterprise Linux 3, 4, or 5. Only mutt version 1.5.19 was affected by this flaw. Not vulnerable. This issue did not affect versions of gnutls shipped in Red Hat Enterprise Linux 4 and 5 as it only affected gnutls 2.6.x versions. Not vulnerable. This issue did not affect versions of gnutls shipped in Red Hat Enterprise Linux 4 and 5 as it only affected gnutls 2.6.x versions. The Red Hat Security Response Team has rated this issue as having low security impact. The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 4, or 5. For further details, see: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-1417 The impact of this flaw is limited to application crash, not allowing code execution. Red Hat does not consider a user-assisted crash of a client application such as media players using GStreamer framework to be a security issue. For further details, see: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-1438 Based on our analysis this issue does not have a security consequence and does not lead to a buffer overflow or denial of service. For more details of our technical evaluation see https://bugzilla.redhat.com/show_bug.cgi?id=499252#c18 Not vulnerable. This issue did not affect the versions of libmodplug embedded in gstreamer-plugins as shipped with Red Hat Enterprise Linux 3 and 4, as they do not include support for the PAT file type. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5, or Red Hat Enterprise MRG. This CVE entry is a duplicate of CVE-2009-0689 and has been rejected; please refer to that CVE entry for additional product fixes and information. Not vulnerable. This issue did not affect the versions of zebra as shipped with Red Hat Enterprise Linux 2.1, and the versions of quagga as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, and 3. It was addressed in Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2009-1132.html , https://rhn.redhat.com/errata/RHSA-2009-1106.html , and https://rhn.redhat.com/errata/RHSA-2009-1157.html . Red Hat does not consider this to be a security issue. By default, user home directories are created with mode 0700 permissions, which would not expose the ~/.evolution/ directory regardless of its own permissions. If a user intentionally relaxes permissions on their home directory, they should be auditing all files and directories in order to not expose unwanted files to other local users. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, and 3. It was addressed in Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2009-1211.html , https://rhn.redhat.com/errata/RHSA-2009-1106.html , and https://rhn.redhat.com/errata/RHSA-2009-1157.html . Not vulnerable. This issue did not affect the versions of the kdelibs packages, as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of the kdelibs packages, as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise Linux 4 and 5 via https://rhn.redhat.com/errata/RHSA-2009-1132.html and https://rhn.redhat.com/errata/RHSA-2009-1106.html . This issue did not affect kernel packages as shipped in Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 1. It was addressed in Red Hat Enterprise Linux 4 via https://rhn.redhat.com/errata/RHSA-2009-1438.html . This issue has been rated as having moderate security impact. It is not planned to be fixed in Red Hat Enterprise Linux 3, due to this product being in Production 3 of its maintenance life-cycle, where only qualified security errata of important or critical impact are addressed. For further information about Errata Support Policy, visit: http://www.redhat.com/security/updates/errata/ Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of samba as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue did not affect Red Hat Enterprise Linux 3. It was addressed in Red Hat Enterprise Linux 4 and 5 via RHSA-2009:1529: https://rhn.redhat.com/errata/RHSA-2009-1529.html Not vulnerable. Red Hat Enterprise Linux 3, 4, and 5 provide earlier versions of ISC DHCP which are not vulnerable to this issue. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2009-1897 The flaw only affects the Red Hat Enterprise Linux 5.4 beta kernel, which includes a backport of the upstream bug fix introducing this flaw (git commit 33dccbb0). This issue did not affect the final released Red Hat Enterprise Linux 5.4 kernel. It is also possible to mitigate this flaw by ensuring that the permissions for /dev/net/tun is restricted to root only. This issue does not affect any other released kernel in any Red Hat product. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 2.1, 3, 4, 5 or Red Hat Enterprise MRG. Red Hat does not provide support for the Linux kernel on the SPARC64 architecture. This issue does not affect versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise Linux MRG 2. This issue was fixed in Red Hat Enterprise Linux MRG 1 via https://rhn.redhat.com/errata/RHSA-2009-1157.html. This issue has been addressed in Red Hat Enterprise Linux 3, 4, and 5 via https://rhn.redhat.com/errata/RHSA-2010-0534.html. Not vulnerable. This issue did not affect the versions of openoffice.org and openoffice.org2 packages as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of stardict as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and 5, and Red Hat Enterprise MRG. This flaw does not affect Red Hat JBoss Enterprise Application Platform 5 or 6. Older versions of the community JBoss Application Server 5.x may be affected. The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and Red Hat Enterprise MRG did not include support for eCryptfs, and therefore are not affected by this issue. Red Hat Enterprise Linux 5 was vulnerable to this issue and was addressed via: https://rhn.redhat.com/errata/RHSA-2009-1193.html The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and Red Hat Enterprise MRG did not include support for eCryptfs, and therefore are not affected by this issue. Red Hat Enterprise Linux 5 was vulnerable to this issue and was addressed via: https://rhn.redhat.com/errata/RHSA-2009-1193.html Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-2446 This issue was addressed for Red hat Enterprise Linux 5 by https://rhn.redhat.com/errata/RHSA-2009-1289.html and Red Hat Enterprise Linux 4 by https://rhn.redhat.com/errata/RHSA-2010-0110.html . The Red Hat Security Response Team has rated this issue as having low security impact, future MySQL package updates may address this flaw for Red Hat Enterprise Linux 3 and Red Hat Application Stack 2. Red Hat does not consider a user-assisted crash of a client application such as Konqueror to be a security issue. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 3, 4, or 5. The affected version of Wireshark as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2010-0360.html Vectors (1) Bluetooth L2CAP and (3) MIOP did not affect the versions of the Wireshark package, as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 3, 4, or 5. The affected version of Wireshark as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2010-0360.html The affected version of Wireshark as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2010-0360.html Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 or Red Hat Enterprise MRG. Not vulnerable. This issue did not affect the versions of squid as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of squid as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of gzip as shipped with Red Hat Enterprise Linux 3, 4, or 5. It was corrected in the versions of gzip as shipped with Red Hat Enterprise Linux 6.0 and later. Red Hat does not consider this flaw to be a security issue. The bug can only be triggered by the PHP script author, which does not cross trust boundary. This issue was addressed in php packages shipped in Red Hat Enterprise Linux 3, 4 and 5 via: https://rhn.redhat.com/errata/RHSA-2010-0040.html Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2009-2688 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ The Red Hat Security Response Team has rated this issue as having moderate security impact. We currently have no plans to fix this flaw in Red Hat Enterprise Linux 3, 4, and 5 as it is not possible to trigger the information leak if the suid_dumpable tunable is set to zero (which is the default). It was addressed in Red Hat Enterprise MRG via: https://rhn.redhat.com/errata/RHSA-2009-1540.html Red Hat is aware of this issue. Please see http://kbase.redhat.com/faq/docs/DOC-18065. Updates for Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG to correct this issue are available: https://rhn.redhat.com/cve/CVE-2009-2692.html Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-2693 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue has been addressed in JBoss Enterprise Web Server 1.0.1: https://rhn.redhat.com/errata/RHSA-2010-0119.html This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise MRG. Updates for Red Hat Enterprise Linux 3, 4 and 5 to correct this issue are available: https://rhn.redhat.com/cve/CVE-2009-2698.html This flaw does not affect the version of APR shipped in Red Hat Enterprise Linux. This flaw affected JBoss Enterprise Web Server running on the Solaris platform. Updated httpd packages are available for download from Customer Support Portal. Not vulnerable. This issue did not affect the versions of qt and qt4 as shipped with Red Hat Enterprise Linux 3, 4, or 5. Affected code was introduced upstream in version 4.3. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-2702 This issue did not affect kdelibs packages as shipped in Red Hat Enterprise Linux 3 and 4. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw in Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of ia32el as shipped with Red Hat Enterprise Linux 3, 4 or 5. Not vulnerable. This issue only affected kernels version 2.6.28-rc1 and later. Therefore this issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 or Red Hat Enterprise MRG.. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 or Red Hat Enterprise MRG. Red Hat does not provide support for flat binary support, and additionally this issue only affected kernels version 2.6.29-rc1 and later. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 or Red Hat Enterprise MRG. Please note this issue only affected Linux kernel versions after v2.6.30-rc1 and was fixed in v2.6.31-rc6. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 or Red Hat Enterprise MRG. Red Hat does not provide support for the Linux kernel on the PA-RISC architecture. This issue has been rated as having moderate security impact. It was addressed in Red Hat Enterprise Linux 4, 5 and Red Hat Enterprise MRG: http://rhn.redhat.com/cve/CVE-2009-2847.html This issue is not planned to be fixed in Red Hat Enterprise Linux 3, due to this product being in Production 3 of its maintenance life-cycle, where only qualified security errata of important or critical impact are addressed. For further information about Errata Support Policy, visit: http://www.redhat.com/security/updates/errata/ Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-2849 The flaw was introduced in kernel version 2.6.17-rc1. The Linux kernel as shipped with Red Hat Enterprise Linux 3, and 4 are not affected by this issue. It was addressed in Red Hat Enterprise MRG via: https://rhn.redhat.com/errata/RHSA-2009-1540.html A future kernel update for Red Hat Enterprise Linux 5 will address this flaw. This issue did not affect the versions of the squid packages, as shipped with Red Hat Enterprise Linux 3 and 4. The issue was addressed in the squid packages as shipped with Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2010-0221.html Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-2901 This issue did not affect Tomcat versions running on Linux or Solaris systems. This issue is fixed in the tomcat5 and tomcat6 packages released with JBoss Enterprise Web Server 1.0.1 for Windows. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-2902 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ This issue has been addressed in JBoss Enterprise Web Server 1.0.1: https://rhn.redhat.com/errata/RHSA-2010-0119.html Red Hat is aware of this issue. Please see http://kbase.redhat.com/faq/docs/DOC-19077 This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5, as the affected driver is not enabled in these kernels. The affected driver is available in Red Hat Enterprise MRG. It is also available in Red Hat Enterprise Linux 3, but only if the kernel-unsupported package is installed. Future kernel updates in Red Hat Enterprise Linux 3 and Red Hat Enterprise MRG will address this issue. The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and Red Hat Enterprise MRG do not include support for eCryptfs, and therefore are not affected by this issue. It was addressed in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2009-1548.html This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, or Red Hat Enterprise MRG, as the affected driver is not enabled in these kernels. The affected driver is available in Red Hat Enterprise Linux 3, but only if the kernel-unsupported package is installed. Future kernel update in Red Hat Enterprise Linux 3 may address this flaw. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2009-2910 It has been rated as having moderate security impact. It was addressed in Red Hat Enterprise Linux 4, 5 and Red Hat Enterprise MRG via: https://rhn.redhat.com/errata/RHSA-2009-1671.html , https://rhn.redhat.com/errata/RHSA-2010-0046.html and https://rhn.redhat.com/errata/RHSA-2009-1540.html respectively. This issue is not planned to be fixed in Red Hat Enterprise Linux 3, due to this product being in Production 3 of its maintenance life-cycle, where only qualified security errata of important and critical impact are addressed. For further information about Errata Support Policy, visit: http://www.redhat.com/security/updates/errata/ Red Hat Enterprise Linux 6 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of PyGreSQL as shipped with Red Hat Enterprise Linux 7. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 or Red Hat Enterprise MRG. Red Hat does not provide support for PF_LLC sockets in the Linux kernels. CVE-2009-3002 describes a collection of similar information leaks that affect numerous networking protocols. The Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 did not enable support for the AppleTalk DDP protocol, and therefore were not affected by issue (1). It was addressed in Red Hat Enterprise Linux 3 and Red Hat Enterprise MRG via: https://rhn.redhat.com/errata/RHSA-2009-1550.html and https://rhn.redhat.com/errata/RHSA-2009-1540.html respectively. The Linux kernel as shipped with Red Hat Enterprise Linux 4, 5 and Red Hat Enterprise MRG did not enable support for IrDA sockets, and therefore were not affected by issue (2). It was addressed in Red Hat Enterprise Linux 3 via: https://rhn.redhat.com/errata/RHSA-2009-1550.html The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG did not enable support for the Acorn Econet and AUN protocols, and therefore were not affected by issue (3). The Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG did not enable support for the NET/ROM and ROSE protocols, and therefore were not affected by issues (4) and (5). They were addressed in Red Hat Enterprise Linux 3 via: https://rhn.redhat.com/errata/RHSA-2009-1550.html The raw_getname() leak was introduced in the Linux kernel version 2.6.25-rc1. The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG therefore were not affected by issue (6). Not vulnerable. This issue did not affect the versions of pidgin as shipped with Red Hat Enterprise Linux 3, 4, or 5. Red Hat has released updates to correct this issue: https://rhn.redhat.com/errata/RHSA-2009-1453.html Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 or Red Hat Enterprise MRG, as they do not contain a backport of the tty ldisc rewrite (upstream commits 65b770468e98 and cbe9352fa08f). Not vulnerable. This issue did not affect the versions of libsilc as shipped with Red Hat Enterprise Linux 4, or 5. Not vulnerable. This issue did not affect the versions of Pidgin packages, as shipped with Red Hat Enterprise Linux 3, 4, or 5. List of the errata fixing this flaw in affected products can be found at: https://www.redhat.com/security/data/cve/CVE-2009-3094.html List of the errata fixing this flaw in affected products can be found at: https://www.redhat.com/security/data/cve/CVE-2009-3095.html Not vulnerable. This issue did not affect the versions of libsilc as shipped with Red Hat Enterprise Linux 4, or 5. This issue was addressed in Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG via: https://rhn.redhat.com/errata/RHSA-2009-1522.html , https://rhn.redhat.com/errata/RHSA-2009-1548 and https://rhn.redhat.com/errata/RHSA-2009-1540 respectively. It has been rated as having moderate security impact and is not planned to be fixed in Red Hat Enterprise Linux 3, due to this product being in Production 3 of its maintenance life-cycle, where only qualified security errata of important or critical impact are addressed. For further information about Errata Support Policy, visit: http://www.redhat.com/security/updates/errata/ Not vulnerable. This issue did not affect the versions of PostgreSQL as shipped with Red Hat Enterprise Linux 3, 4, or 5. In PostgreSQL versions prior to 8.2, only database administrator was able to LOAD additional plugins and use it to cause server crash. However, this does not bypass trust boundary, so its not a security flaw for older PostgreSQL versions. Additionally, no plugins are shipped in Red Hat PostgreSQL packages by default. This issue was addressed in Red Hat Application Stack v2 via https://rhn.redhat.com/errata/RHSA-2009-1461.html . Not vulnerable. This issue did not affect the versions of PostgreSQL as shipped with Red Hat Enterprise Linux 3, 4, or 5, as they do not support LDAP authentication, which was introduced upstream in version 8.2. This issue was addressed in Red Hat Application Stack v2 via https://rhn.redhat.com/errata/RHSA-2009-1461.html . Not vulnerable. This issue only affected kernels version v2.6.31-rc1 and later. Therefore this issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 or Red Hat Enterprise MRG. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This vulnerability was introduced into the Linux kernel in version 2.6.30-rc1 via upstream commit 2a519311, and therefore does not affect users of Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2009-1548.html Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 or Red Hat Enterprise MRG. This issue was introduced by upstream commit 10db10d1, and only affected kernels version 2.6.28-rc1 and later. Not vulnerable. This issue does not affect the versions of glib2 as shipped with Red Hat Enterprise Linux 3, 4, or 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2009-3290 This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and Red Hat Enterprise MRG as KVM (Kernel-based Virtual Machine) is only supported in Red Hat Enterprise Linux 5. A future kernel update in Red Hat Enterprise Linux 5 will address this flaw. This problem is not a security flaw in the PHP versions 4.3.5 and later. For further details, see: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-3293 PHP versions shipped in Red Hat Enterprise Linux 4 and 5 do not need this fix. We do not plan to address this flaw in Red Hat Enterprise Linux 3. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 3, 4, or 5, and Red Hat Application Stack v2. Not vulnerable. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of libtheora as shipped with Red Hat Enterprise Linux 4, or 5. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 3, 4, or 5. The affected version of Wireshark as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2010-0360.html Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 3, 4, or 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-3555 Additional information can be found in the Red Hat Knowledgebase article: http://kbase.redhat.com/faq/docs/DOC-20491 This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG. Shipped kernels do not include upstream commit d025c9db that introduced the problem. This upstream commit was backported in Red Hat Enterprise Linux 5 via RHBA-2008:0314 update. Issue was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0046.html We do not consider safe_mode / open_basedir restriction bypass issues being security sensitive. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php We do not consider safe_mode / open_basedir restriction bypass issues being security sensitive. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php The Red Hat Security Response Team does not currently plan to fix this flaw in MRG. Not vulnerable. This issue did not affect the version of poppler as shipped with Red Hat Enterprise Linux 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2009-3612 This issue has been rated as having moderate security impact. It was addressed in Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG via: https://rhn.redhat.com/errata/RHSA-2009-1670.html and https://rhn.redhat.com/errata/RHSA-2009-1540.html respectively. A future kernel update in Red Hat Enterprise Linux 4 will address this flaw. This issue is not planned to be fixed in Red Hat Enterprise Linux 3 due to this product being in Production 3 of its maintenance life-cycle, where only qualified security errata of important or critical impact are addressed. For further information about the Errata Support Policy, visit: http://www.redhat.com/security/updates/errata/ Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2009-3621 This issue has been rated as having moderate security impact. It was addressed in Red Hat Enterprise Linux 4, 5 and Red Hat Enterprise MRG via: https://rhn.redhat.com/errata/RHSA-2009-1671.html , https://rhn.redhat.com/errata/RHSA-2009-1670.html and https://rhn.redhat.com/errata/RHSA-2009-1540.html respectively. This issue is not planned to be fixed in Red Hat Enterprise Linux 3, due to this product being in Production 3 of its maintenance life-cycle, where only qualified security errata of important or critical impact are addressed. For further information about Errata Support Policy, visit: http://www.redhat.com/security/updates/errata/ Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, or Red Hat Enterprise MRG. Those versions do not include the upstream patch that introduced this vulnerability. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, or Red Hat Enterprise MRG. Those versions do not include the upstream patch that introduced this vulnerability. Not vulnerable. This issue did not affect the versions of perl as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue does not affect Red Hat Enterprise Linux 3, 4, or 5. This flaw can only lead to a denial of service if perl-HTML-Parser is used in conjunction with perl 5.10.1. If perl-HTML-Parser is used with earlier versions of perl, this flaw does not lead to a denial of service. Not vulnerable. This issue did not affect the versions of KVM as shipped with Red Hat Enterprise Linux 5. KVM is only supported on AMD64/x86_64 architecture on Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of KVM as shipped with Red Hat Enterprise Linux 5 as it does not contain the patch that introduced this vulnerability (upstream commit f0a3602c). Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-3722 The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update will address this flaw. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 or Red Hat Enterprise MRG, as they do not include the upstream change introducing this flaw. The Linux kernel as shipped with Red Hat Enterprise Linux 3 did not have support for NFSv4, and therefore is not affected by this issue. It was addressed in Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2010-0474.html, https://rhn.redhat.com/errata/RHSA-2009-1670.html and https://rhn.redhat.com/errata/RHSA-2009-1635.html respectively. Not vulnerable. This issue did not affect the versions of mutt as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue was addressed in the openldap packages as shipped with Red Hat Enterprise Linux 5 and 4 via: https://rhn.redhat.com/errata/RHSA-2010-0198.html and https://rhn.redhat.com/errata/RHSA-2010-0543.html respectively. The Red Hat Security Response Team has rated this issue as having moderate security impact, a future openldap update may address this flaw in Red Hat Enterprise Linux 3. The affected version of Wireshark as shipped in Red Hat Enterprise Linux 3, 4, and 5 were fixed via: https://rhn.redhat.com/errata/RHSA-2010-0360.html Not vulnerable. The Linux kernels as shipped with Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG did not have MMU disabled, and therefore are not affected by this issue. This issue did not affect the version of the Linux kernel as shipped with Red Hat Enterprise Linux 3, as it does not implement the sysfs file system ("/sys/"), through which dbg_lvl file is exposed by the megaraid_sas driver. Issue was addressed in Red Hat Enterprise Linux 4, 5 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2010-0076.html , https://rhn.redhat.com/errata/RHSA-2010-0046.html and https://rhn.redhat.com/errata/RHSA-2009-1635.html respectively. Not vulnerable. This issue did not affect the versions of libexif as shipped with Red Hat Enterprise Linux 4, or 5. This issue did not affect the version of dovecot shipped with Red Hat Enterprise Linux 6. Vulnerable. This issue affects gimp packages in Red Hat Enterprise Linux 4 and 5. This issue does not affect gimp package in Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of poppler as shipped with Red Hat Enterprise Linux 5. This issue did not affect the version of the Linux kernel as shipped with Red Hat Enterprise Linux 3, as it does not implement the sysfs file system ("/sys/"), through which poll_mode_io file is exposed by the megaraid_sas driver. Issue was addressed in Red Hat Enterprise Linux 4, 5 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2010-0076.html , https://rhn.redhat.com/errata/RHSA-2010-0046.html and https://rhn.redhat.com/errata/RHSA-2009-1635.html respectively. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and Red Hat Enterprise MRG as KVM (Kernel-based Virtual Machine) is only supported in Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is not vulnerable to this issue because it does not include the change that introduced this buffer overflow vulnerability. The Linux kernel as shipped with Red Hat Enterprise Linux 3, 5, and Red Hat Enterprise MRG did not include support for the HiSax ISDN driver for Colognechip HFC-S USB chip, and therefore were not affected by this issue. Issue was addressed in Red Hat Enterprise Linux 4 via https://rhn.redhat.com/errata/RHSA-2010-0076.html We do not consider safe_mode / open_basedir restriction bypass issues being security sensitive. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php This issue did not affect the version of the Linux kernel as shipped with Red Hat Enterprise MRG as the affected driver is not enabled in this kernel. It was addressed in Red Hat Enterprise Linux 4 and 5 via https://rhn.redhat.com/errata/RHSA-2010-0076.html and https://rhn.redhat.com/errata/RHSA-2010-0046.html respectively. Red Hat Enterprise Linux 3 is now in Production 3 of the maintenance life-cycle, http://www.redhat.com/security/updates/errata, and this issue is rated as having low impact, therefore the fix for this issue is not currently planned to be included in the future updates. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2009-4021 The Linux kernel packages as shipped with Red Hat Enterprise Linux 3 and 4 do not include support for FUSE, and therefore are not affected by this issue. It was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0046.html A future kernel update for Red Hat Enterprise MRG will address this flaw. While this flaw exists in all 9.x versions, we do not plan to release bind updates for Red Hat Enterprise Linux 3 and 4 including this fix. The version of bind shipped in those products is 9.2.4, which has an older DNSSEC implementation, which is incompatible with currently used DNSSEC version and can not be used to secure communication with current public internet DNS servers. This flaw does not introduce additional risks to bind installations that are not using DNSSEC, as a successful attack requires bypass of other cache poisoning protections (such as random query source ports and transaction ids). This flaw only allows for the bypass of protection provided by DNSSEC. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG. Shipped kernels do not include upstream commits d75636ef and d92684e6 that introduced the problem. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2009-4027. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3 and 4 as they do not have support for the mac80211 framework. It did not affect the version of the Linux kernel as shipped with Red Hat Enterprise MRG as they do not include the upstream patch that introduced this vulnerability. A future update will address this flaw in Red Hat Enterprise Linux 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-4029 This issue was addressed in the automake, automake14, automake15, automake16 and automake17 packages as shipped with Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2010-0321.html The Red Hat Security Response Team has rated this issue as having low security impact, theres no plan to address this flaw in automake packages in Red Hat Enterprise Linux 3 and 4. This issue is only security-relevant in PostgreSQL versions 8.4 and later as previous versions did not compare the connection host name with the certificate CommonName at all. Client certificate authentication was introduced in version 8.4. Red Hat Enterprise Linux 5 and earlier provided PostgreSQL versions 8.1.x and earlier, and are thus not affected by this issue. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as the affected code has been removed. It was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2011-1386.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Not vulnerable. This issue did not affect the versions of ruby as shipped with Red Hat Enterprise Linux 5 and 6 as it did not affect the Ruby 1.8 series. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG. Those versions do not include the upstream patch that introduced this vulnerability. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue does not affect users using coreutils binary RPMs, or rebuilding source RPMs. Therefore, we do not plan to release updates addressing this flaw on Red Hat Enterprise Linux 3, 4 and 5. For additional details, refer to the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-4135 This issue was addressed in Red Hat Enterprise Linux 3 via https://rhn.redhat.com/errata/RHSA-2010-0427.html This issue was addressed in Red Hat Enterprise Linux 4 via https://rhn.redhat.com/errata/RHSA-2010-0428.html This issue was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0429.html and https://rhn.redhat.com/errata/RHSA-2010-0430.html Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2009-4138 The Linux kernel packages as shipped with Red Hat Enterprise Linux 3 and 4 have a different (and older) implementation of the driver for OHCI 1394 controllers, which is not affected by this issue. It was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0046.html A future kernel update for Red Hat Enterprise MRG will address this flaw. Vulnerable. This issue has been addressed in Red Hat Network Satellite Server v 5.4.1 via RHSA-2011:0879 https://rhn.redhat.com/errata/RHSA-2011-0879.html. This issue is not planned to be fixed in Red Hat Network Satellite Server version 5.3.0. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG. Shipped kernels do not include upstream commit 233e70f4 that introduced the problem. It was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0046.html We do not consider safe_mode / open_basedir restriction bypass issues being security sensitive. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2009-4227 The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2009-4228 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Red Hat considers this to be a duplicate of the CVE-2009-4033, rather than a separate issue. For further details, see: https://bugzilla.redhat.com/show_bug.cgi?id=542926#c10 Not vulnerable. This issue did not affect the versions of ghostscript as shipped with Red Hat Enterprise Linux 3, 4, or 5. This security issue did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 3, 5 and Red Hat Enterprise MRG. This issue was addressed in Red Hat Enterprise Linux 4 via https://rhn.redhat.com/errata/RHSA-2010-0146.html. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG. Shipped kernels do not include upstream commits c6153b5b and 1080d709 that introduced the problem. It was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0046.html Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2009-4307 The Linux kernel packages as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG do not include support for EXT4, and therefore are not affected by this issue. A future kernel update for Red Hat Enterprise Linux 5 will address this flaw. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2009-4308 The Linux kernel packages as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG do not include support for EXT4, and therefore are not affected by this issue. This issue was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0147.html. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of acl as shipped with Red Hat Enterprise Linux 3, 4, or 5. Red Hat does not consider this to be a security flaw. For further details, see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-4418 Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 3, 4, or 5. The packages use OpenSSL and not yaSSL. Not vulnerable. This issue did not affect the versions of Thunderbird as shipped with Red Hat Enterprise Linux 4 and 5, and Seamonkey as shipped with Red Hat Enterprise Linux 3 and 4. Not vulnerable. This issue did not affect the versions of Firefox, Thunderbird, or Seamonkey as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of gnome-screensaver as shipped with Red Hat Enterprise Linux 5. Red Hat does not consider this bug to be a security issue. Properly written application should not use arbitrary untrusted data as part of the format string passed to functions as strfmon or printf family functions. Red Hat does not consider this bug to be a security issue. Properly written application should not use arbitrary untrusted data as part of the format string passed to functions as strfmon or printf family functions. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and 5. This issue was addressed in Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2010-0161.html. Not vulnerable. This issue did not affect the versions of pcsc-lite as shipped with Red Hat Enterprise Linux 5. This flaw did not affect libtiff as shipped in Red Hat Enterprise Linux 4 or 5. The OJPEG decoder is disabled in those distributions. Not vulnerable. This issue did not affect the versions of groff as shipped with Red Hat Enterprise Linux 4, 5, or 6. These flaws do not affect any version of libpng shipped with Red Hat Enterprise Linux. Not vulnerable. This issue did not affect the versions of groff as shipped with Red Hat Enterprise Linux 4, 5, or 6. The Red Hat Security Response Team has rated this issue as having low security impact because it can only be exploited during package compilation. We do not currently plan to fix this flaw. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of groff as shipped with Red Hat Enterprise Linux 4, 5, or 6. The Red Hat Security Response Team has rated this issue as having low security impact because it can only be exploited during package compilation. We do not currently plan to fix this flaw. This issue did not affect the versions of gnutls as shipped with Red Hat Enterprise Linux 6. This issue did not affect any versions of OpenSSL as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-0003. This issue has been rated as having moderate security impact. A future update in Red Hat Enterprise MRG may address this flaw. This issue was addressed in Red Hat Enterprise Linux 4 and 5 via https://rhn.redhat.com/errata/RHSA-2010-0146.html and https://rhn.redhat.com/errata/RHSA-2010-0147.html respectively. This issue is not planned to be fixed in Red Hat Enterprise Linux 3, due to this product being in Production 3 of its maintenance life-cycle, where only qualified security errata of important or critical impact are addressed. For further information about Errata Support Policy, visit: http://www.redhat.com/security/updates/errata/ Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG as they did not have support for network namespaces, and did not include upstream commit 483a47d2 that introduced the problem. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-0007. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, as it did not include support for ebtables. This issue was addressed in Red Hat Enterprise Linux 4 and 5 via https://rhn.redhat.com/errata/RHSA-2010-0146.html and https://rhn.redhat.com/errata/RHSA-2010-0147.html respectively. A futur e update in Red Hat Enterprise MRG may address this flaw. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3 as it did not include support for SCTP. It did not affect the version of Linux kernel as shipped with Red Hat Enterprise MRG as it has already had the fix to this issue. This was addressed in Red Hat Enterprise Linux 4 and 5 via https://rhn.redhat.com/errata/RHSA-2010-0146.html and https://rhn.redhat.com/errata/RHSA-2010-9419.html respectively. This issue does not affect the Apache HTTP Server versions 2 and greater. This flaw does not affect any supported versions of Red Hat Enterprise Linux. This flaw does affect Red Hat Network Proxy and Red Hat Network Satellite. While those products do not use this feature, we are tracking the issue with the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2010-0010 The Red Hat Security Response Team has rated this issue as having low security impact. We do not currently plan to address this flaw on Red Hat Enterprise Linux 4 and 5. This issue does not affect Red Hat Enterprise Linux 6. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of openoffice.org as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of the bind as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of bind package as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue was addressed for Red Hat Enterprise Linux 4 and 5 via https://rhn.redhat.com/errata/RHSA-2010-0115.html We currently have no plans to fix this flaw in Red Hat Enterprise Linux 3 as the MSN protocol support in the provided version of Pidgin (1.5.1) is out-dated and no longer supported by MSN servers. There are no plans to backport MSN protocol changes for that version of Pidgin. Not vulnerable. This issue did not affect the versions of MIT Kerberos 5 as shipped with Red Hat Enterprise Linux 3, 4 or 5. Those versions do not contain the vulnerable code that was introduced in krb5 1.7. Not vulnerable. This issue did not affect the versions of gnome-screensaver as shipped with Red Hat Enterprise Linux 5 or 6. The risks associated with fixing this bug are greater than the important severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 3 and 4. This issue was addressed in Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2010-0504.html and https://rhn.redhat.com/errata/RHSA-2010-0161.html. Not vulnerable. The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG did not include support for Devtmpfs, and therefore are not affected by this issue. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-0307. This issue has been rated as having moderate security impact. This issue was addressed in Red Hat Enterprise Linux 4 via https://rhn.redhat.com/errata/RHSA-2010-0146.html. Future updates in Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG may address this flaw. This issue is not planned to be fixed in Red Hat Enterprise Linux 3, due to this product being in Production 3 of its maintenance life-cycle, where only qualified security errata of important or critical impact are addressed. For further information about Errata Support Policy, visit: http://www.redhat.com/security/updates/errata/ Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2010-0308 This issue was addressed in the squid packages as shipped with Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2010-0221.html The Red Hat Security Response Team has rated this issue as having low security impact, a future squid update may address this flaw in Red Hat Enterprise Linux 3 and 4. This issue did not affected Red Hat Enterprise Linux 3 and 4 due to the lack of localization in lppasswd as provided in those releases. The affected code is present in Red Hat Enterprise Linux 5, however lppasswd is not shipped setuid so is not vulnerable to this issue. If a user were to enable the setuid bit on lppasswd, the impact would only be a crash of lppasswd due to use of FORTIFY_SOURCE protections. Therefore, there are no plans to correct this issue in Red Hat Enterprise Linux 5. This issue was addressed in the php packages as shipped with Red Hat Enterprise Linux 4 and 5 via: https://rhn.redhat.com/errata/RHSA-2010-0919.html Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-0410. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3 and 4, as they do not include support for kernel connectors. Future updates in Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG may address this flaw. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3 and 4, as they do not include support for sys_move_pages. It was only introduced in kernel version 2.6.18 onwards. This issue was addressed in Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2010-0147.html and https://rhn.redhat.com/errata/RHSA-2010-0161.html. The Red Hat Security Response Team has rated this issue as having low security impact. For Red Hat Enterprise Linux 4 and 5, this issue was addressed via https://rhn.redhat.com/errata/RHSA-2010-0115.html We currently have no plans to fix this flaw in Red Hat Enterprise Linux 3 as the issue only causes Pidgin client to become unresponsive or crash. This issue was addressed in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2010-0122.html It did not affect the versions of the sudo package as shipped with Red Hat Enterprise Linux 3 and 4. This issue was addressed in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2010-0122.html It did not affect the versions of the sudo packages as shipped with Red Hat Enterprise Linux 3 and 4. The CVE-2010-0430 issue was fixed in the kvm packages for Red Hat Enterprise Linux 5 via RHSA-2010:0271, and fixed in the rhev-hypervisor package via RHSA-2010:0476. This CVE was not disclosed at the time the errata were released; therefore, it was not mentioned in them. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2010-0434 This issue was fixed in Red Hat Enterprise Linux 5 via: https://rhn.redhat.com/errata/RHSA-2010-0168.html This issue was fixed in Red Hat Enterprise Linux 4 via: https://rhn.redhat.com/errata/RHSA-2010-0175.html The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw on Red Hat Enterprise Linux 3. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-0437. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3 and 4, as they do not include support for Optimistic Duplicate Address Detection (DAD) in IPv6. This was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-9419.html. A future update in Red Hat Enterprise MRG may address this flaw. Not vulnerable. This issue did not affect the versions of fetchmail as shipped with Red Hat Enterprise Linux 3, 4, or 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-0622. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3 and 4, as they do not include support for priority-inheriting futex. Future updates in Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG may address this flaw. Not vulnerable. This security issue did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG, as they do not include the upstream change that introduced this flaw. Not vulnerable. This flaw does not affect MIT krb5 as provided in Red Hat Enterprise Linux 3, 4, and 5. Not vulnerable. This issue did not affect the versions of squid as shipped with Red Hat Enterprise Linux 3, 4, or 5. Those versions are not compiled with the support for HTCP protocol. Not vulnerable. Apache ActiveMQ is not shipped with any supported Red Hat products. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-0727. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise MRG, as it did not include support for the GFS and GFS2 file systems. For the GFS issue, it was addressed in Red Hat Enterprise Linux 3 in the gfs package, 4 in the GFS-kernel package, and 5 in the gfs-kmod package, via https://rhn.redhat.com/errata/RHSA-2010-9493.html, https://rhn.redhat.com/errata/RHSA-2010-9494.html, https://rhn.redhat.com/errata/RHSA-2010-0291.html respectively. For the GFS2 issue, it was addressed in Red Hat Enterprise Linux 5 in the kernel package via https://rhn.redhat.com/errata/RHSA-2010-0178.html. Not vulnerable. This issue did not affect the versions of the samba package, as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue did not affect the version of the samba3x package, as shipped with Red Hat Enterprise Linux 5. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-0729. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 5 or Red Hat Enterprise MRG, as they do not include the internal change introducing this flaw. A future update in Red Hat Enterprise Linux 4 may address this flaw. This issue was fixed by a patch to JBoss Operations Network 2.3.1, available for download from the Red Hat Customer Portal: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=1983&product=em&version=2.3.1&downloadType=securityPatches Not vulnerable. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. These issues did not affect the versions of OpenSSL as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG as they did not backport an out-of-tree drbd module (drbd8). Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2010-0789 This issue affects Red Hat Enterprise Linux 5 because it ships fusermount suid root, however the impact of this flaw is minimized due to the fact that only members in group fuse may use it the executable is owned root:fuse and mode 4750. Red Hat Enterprise Linux 3 and 4 do not provide the fuse package. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/ Not vulnerable. This issues does not affect the versions of emacs or xemacs as shipped with Red Hat Enterprise Linux. The movemail utility in Red Hat Enterprise Linux does not have the setgid bit set, which is required for this flaw to be exploitable. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue was addressed in Samba packages in Red Hat Enterprise Linux 5. It did not affect Samba packages in Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact. There is no plan to address this flaw in Red Hat Enterprise Linux 4. To prevent this issue, disable "wide links" or "unix extensions" in the Samba configuration file (/etc/samba/smb.conf) and restart smbd (service smb restart). Disabled "wide links" ensure that remote Samba clients will not have wide symbolic links (links pointing outside of the shared directory) resolved on the server side when processing requests from a client that does not support UNIX extensions. Disabled "unix extensions" prevents creation of wide links by malicious clients which support UNIX extensions. For further information, please view http://www.samba.org/samba/news/symlink_attack.html CVE-2010-0928 describes a fault-based attack on OpenSSL where an attacker has precise control over the target system environment in order to be able to introduce faults through power supply manipulation. The attack is not a viable threat to OpenSSL as used in Red Hat products. The Red Hat Security Response Team has rated this issue as having low security impact and we do not intend to issue updates to address it. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-1083 This issue has been rated as having low security impact. A future update in Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG may address this flaw. This issue is not planned to be fixed in Red Hat Enterprise Linux 3, due to this product being in Production 3 of its maintenance life-cycle, where only qualified security errata of important or critical impact are addressed. For further information about Errata Support Policy, visit: http://www.redhat.com/security/updates/errata/ Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-1084 This issue did not affect the version of the Linux kernel as shipped with Red Hat Enterprise 3 and 4, as it did not use sysfs files. A future update in Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG may address this flaw. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-1085 This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3 and Red Hat Enterprise MRG as they did not include the affected function. A future update in Red Hat Enterprise Linux 4 and 5 may address this flaw. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-1086 This issue did not affect the version of the Linux kernel as shipped with Red Hat Enterprise Linux 3 as it did not include support for ULE (Unidirectional Lightweight Encapsulation). We have included a fix for this issue in Red Hat Enterprise Linux 4 and 5 however the affected module is not build by default. This issue was addressed in Red Hat Enterprise MRG via http://rhn.redhat.com/errata/RHSA-2010-0631.html. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-1087 This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3 and 4 as they did not include the upstream commit 150030b7 that had introduced the problem. A future update in Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG may address this flaw. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-1088 This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3 and 4 as this issue only affects kernel version 2.6.18 and onwards. A future update in Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG may address this flaw. This issue is not planned to be fixed in Red Hat Enterprise Linux 3 due to this product being in Production 3 of its maintenance life-cycle, where only qualified security errata of important and critical impact are addressed. For further information about the Errata Support Policy, visit: http://www.redhat.com/security/updates/errata We do not consider safe_mode / open_basedir restriction bypass issues to be security sensitive. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php We do not consider safe_mode / open_basedir restriction bypass issues to be security sensitive. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Not vulnerable. The Linux kernel as shipped with with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG did not include support for reiserfs and therefore are not affected by this issue. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG as they did not include support for POSIX opens on lookup. The risks associated with fixing this flaw are greater than the low severity security risk. We therefore have no plans to fix this flaw. The information leak can be avoided by adjusting the configuration to always specify a realm-name. The Red Hat Security Response Team has rated this issue as having low security impact. The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 3, 4, or 5. This issue was corrected in Red Hat Enterprise Linux 6 prior to its initial release. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates for this or earlier releases. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue was corrected in Red Hat Enterprise Linux 6 prior to its initial release. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates for this or earlier releases. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and 5 as they did not include upstream commit ab521dc0 that introduced the problem. This issue was addressed in Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2010-0631.html. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-1173. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3 as it did not include support for SCTP. Future kernel updates in Red Hat Enterprise Linux 4, 5 and Red Hat Enterprise MRG may address this flaw. For more information, please see http://kbase.redhat.com/faq/docs/DOC-31052. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-1187. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG as they did not include support for Transparent Inter-Process Communication Protocol (TIPC). A future kernel update in Red Hat Enterprise Linux 5 may address this flaw. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-1188 This issue did not affect the version of the Linux kernel as shipped with Red Hat Enterprise MRG, as it was fixed since version v2.6.20-rc6. It was addressed in Red Hat Enterprise Linux 5 in the kernel package via https://rhn.redhat.com/errata/RHSA-2010-0178.html. A future update in Red Hat Enterprise Linux 3 and 4 may address this flaw. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. Apache ActiveMQ is not shipped with any supported Red Hat products. Not vulnerable. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue did not affect Red Hat Enterprise Linux 3, 4, or 5. It was addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2010-0863.html. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 3, 4 and 5. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG as they did not include support for the GFS2 file system. A future kernel update in Red Hat Enterprise Linux 5 will address this issue. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3. Future kernel updates in Red Hat Enterprise Linux 4, 5 and Red Hat Enterprise MRG will address this issue. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG as they did not include support for KGDB, a debugger for the Linux kernel. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG. Red Hat does not provide support for the Linux kernel on the SPARC architecture. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. The Linux kernel as shipped with with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG did not include upstream commit 28b83c51 (v2.6.32-rc1) that introduced the problem. Not vulnerable. Apache ActiveMQ is not shipped with any supported Red Hat products. Not vulnerable. These issues did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue did not affect the versions of the SpringSource Spring Framework, as shipped with JBoss Enterprise Application Platform v4.2.0, v4.3.0, or v.5.0.0. The Red Hat Security Response Team has rated this issue as having low security impact, a future pidgin package update may address this flaw in Red Hat Enterprise Linux 3, 4, and 5. Not vulnerable. This issue did not affect the versions of ghostscript as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. These issues did not affect the versions of OpenSSL as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. These issues did not affect the versions of samba as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG as they did not include support for Btrfs, a new copy on write filesystem. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-1641. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG as they did not include support for the GFS2 file system. A future kernel update in Red Hat Enterprise Linux 5 will address this issue. Red Hat does not consider this to be a security flaw. This issue can cause smbd per-connection child process crash, resulting in the termination of an attacker's connection. Availability of the smb service is not impacted. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and 5 as they did not include nfs-export support for tmpfs. A future kernel update in Red Hat Enterprise MRG will address this issue. Vulnerable. This issue affects quagga packages in Red Hat Enterprise Linux 4 and 5. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw for Red Hat Enterprise Linux 3 and 4 mysql packages. This issue was fixed in mysql packages shipped with Red Hat Enterprise Linux 5 via RHSA-2012:0127. The mysql packages in Red Hat Enterprise Linux 6 include this fix since the initial release of the product. These issues did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 3, or 4. Red Hat does not consider interruption issues allowing safe_mode / open_basedir restriction bypass to be security sensitive. For more details see https://bugzilla.redhat.com/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat does not consider interruption issues allowing safe_mode / open_basedir restriction bypass to be security sensitive. For more details see https://bugzilla.redhat.com/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat does not consider interruption issues allowing safe_mode / open_basedir restriction bypass to be security sensitive. For more details see https://bugzilla.redhat.com/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat does not consider interruption issues allowing safe_mode / open_basedir restriction bypass to be security sensitive. For more details see https://bugzilla.redhat.com/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 3, 4, or 5, and Red Hat Application Stack v2. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 3, 4, or 5, as well as the versions of php53 as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of ghostscript as shipped with Red Hat Enterprise Linux 3, 4, or 5. The issue does not affect any Red Hat products as no products ship Struts2/XWork binaries. Red Hat does not consider interruption issues allowing safe_mode / open_basedir restriction bypass to be security sensitive. For more details see https://bugzilla.redhat.com/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat does not consider interruption issues allowing safe_mode / open_basedir restriction bypass to be security sensitive. For more details see https://bugzilla.redhat.com/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php This issue is not planned to be fixed in Red Hat Enterprise Linux 3 due to this product being in Production 3 of its maintenance life-cycle, where only qualified security errata of important and critical impact are addressed. For further information about the Errata Support Policy, visit: http://www.redhat.com/security/updates/errata This issue has been addressed in Red Hat Enterprise Linux 4 via https://rhn.redhat.com/errata/RHSA-2010-0428.html This issue has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0429.html and https://rhn.redhat.com/errata/RHSA-2010-0430.html There is not plan to address this issue in the PostgreSQL packages as shipped with Red Hat Enterprise Linux 3. The Red Hat Security Response Team does not consider a user assisted denial of service (and potential crash) of end user application, such a Firefox, to be a security issue. The Red Hat Security Response Team has rated this issue as having low security impact. By default, /var/spool/mail/ is not provided with permissions to make an attack scenario possible, and there is no reason for permissions to be relaxed in such a way as to make it possible. We therefore have no plans to fix this flaw in Red Hat Enterprise Linux 4 or 5. The Red Hat Security Response Team has rated this issue as having low security impact. While support for the MBX mailbox format is compiled into Exim, it is not used by default. MBX mailboxes are only useful when used with UW-IMAP or the Pine mail client, neither of which are provided with Red Hat Enterprise Linux. If the MBX format is used, this issue can be worked around by specifying "use_fcntl_lock" rather than "use_mbx_lock". We therefore have no plans to fix this flaw in Red Hat Enterprise Linux 4 or 5. Not vulnerable. This issue did not affect the versions of myfaces as shipped with JBoss Enterprise Web Server. Not vulnerable. These issues did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG as they did not include support for the Ext4 filesystem. A future kernel update in Red Hat Enterprise Linux 5 will address this issue. Not vulnerable. These issues did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG as they did not include support for Btrfs, a new copy on write filesystem. Not Vulnerable. This issue does not affect the versions of Apache CXF as shipped with various Red Hat products. This flaw affects applications using unencrypted client-side view states on Mojarra as shipped with JBoss Communications Platform 1.2.11 and 5.1.1, JBoss Enterprise Application Platform 4.2.0, 4.3.0 and 5.1.1, JBoss Enterprise BRMS Platform 5.1.0, JBoss Enterprise Portal Platform 4.3 and 5.1.1, JBoss Enterprise SOA Platform 4.2.0, 4.3.0 and 5.1.0, JBoss Enterprise Web Platform 5.1.1 and JBoss Web Framework Kit 1.1.0 and 1.2.0. Unencrypted client-side view states are fundamentally insecure and should not be used. Developers are advised to always enable encryption when creating JavaServer Faces (JSF) applications using client-side view state. When using the Mojarra implementation of JSF, this is achieved by adding the following snippet to the application's web.xml: <context-param> <param-name>javax.faces.STATE_SAVING_METHOD</param-name> <param-value>client</param-value> </context-param> <env-entry> <env-entry-name>ClientStateSavingPassword</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>INSERT_YOUR_PASSWORD</env-entry-value> </env-entry> Not Vulnerable. This issue does not affect the version of php as shipped with Red Hat Enterprise Linux 4, 5 and 6. This issue does not affect the version of php53 as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 3, 4, or 5, and Red Hat Application Stack v2. Red Hat does not consider interruption issues allowing safe_mode / open_basedir restriction bypass to be security sensitive. For more details see https://bugzilla.redhat.com/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat does not consider interruption issues allowing safe_mode / open_basedir restriction bypass to be security sensitive. For more details see https://bugzilla.redhat.com/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat does not consider interruption issues allowing safe_mode / open_basedir restriction bypass to be security sensitive. For more details see https://bugzilla.redhat.com/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php The Red Hat Security Response Team does not consider a user assisted denial of service (and potential crash) of end user application, such a Firefox, to be a security issue. Not vulnerable. These issues did not affect the versions of dhcp as shipped with Red Hat Enterprise Linux 3, 4, or 5. Red Hat does not consider interruption issues allowing safe_mode / open_basedir restriction bypass to be security sensitive. For more details see https://bugzilla.redhat.com/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Red Hat does not consider interruption issues allowing safe_mode / open_basedir restriction bypass to be security sensitive. For more details see https://bugzilla.redhat.com/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php We do not consider this to be a security issue as it does not introduce any additional risk in using untrusted RPM .spec files. RPM .spec files can do a lot of things, regardless of how rpmbuild parses the syntax, because certain sections of the .spec file (%prep, %build, etc.) are treated as shell scripts. Because of the ability to easily include malicious commands anywhere, an untrusted .spec file should be carefully examined prior to building, the same as if you were to download and execute an untrusted shell script. Not vulnerable. RPM as provided with Red Hat Enterprise 3, 4, and 5 do not support POSIX capabilities. We do not consider RPM's lack of removing POSIX ACLs to be security sensitive. Users cannot use POSIX ACLs to elevate their privileges; therefore, there is no need to clear them upon package upgrade or removal. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG as they did not include support for the XFS filesystem. A future kernel update in Red Hat Enterprise Linux 5 will address this issue. Not vulnerable. This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 3, 4, or 5. The Red Hat Security Response Team has rated this issue as having Moderate security impact. Satellite 5 is currently in the Production 2 phase of its lifecycle, as such this issue is not currently planned to be addressed in future updates. For additional information, refer to the Satellite Life Cycle: https://access.redhat.com/site/support/policy/updates/satellite page. Not vulnerable. This issue did not affect the version of libvirt as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the version of libvirt as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG: Red Hat Enterprise Linux 3 and 4 did not have the 'current_clocksource' file in /sys/; Red Hat Enterprise Linux 5 restricted 'current_clocksource' to only the root user; and Red Hat Enterprise MRG enabled CONFIG_GENERIC_TIME by default. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3 as it did not have support for CIFS. Future updates in Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG may address this flaw. This issue did not affect the version of lftp as shipped with Red Hat Enterprise Linux 3 and 4 as they did not include support for renaming files to a server-suggested file name. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact due to the series of events required to successfully exploit it, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the perl-libwww-perl package, as shipped with Red Hat Enterprise Linux 4, 5 and 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 3, 4, or 5. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This is not a vulnerability. Red Hat Enterprise Linux does not have /var/log/messages world-readable, nor is GDM run in debug mode; both are requirements for this to be considered a flaw. This issue did not affect the versions of CUPS as shipped with Red Hat Enterprise Linux 3 or 4. It was addressed in Red Hat Enterprise Linux 5 via RHSA-2010:0811. Not vulnerable. This issue did not affect the versions of CUPS as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue was fixed by the 5.0.2 release of the JBoss Enterprise SOA Platform, available for download from the Red Hat Customer Portal: https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?product=soaplatform&downloadType=distributions&version=5.0.2+GA The JBoss Enterprise SOA Platform 5.0.2 Release Notes are available from http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/5.0.2/html/5.0.2_Release_Notes/index.html This issue did not affect python-paste version as shipped with Red Hat Enterprise Linux 6, which included the fixed version since its initial release. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3 and 4, as they do not include support for the Neptune Ethernet driver. It did not affect Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG, as they do not contain the upstream commit 0853ad66 that introduced this flaw. Not vulnerable. This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 3, 4, or 5. Red Hat does not consider interruption issues allowing safe_mode / open_basedir restriction bypass to be security sensitive. For more details see https://bugzilla.redhat.com/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and Red Hat Enterprise MRG did not include support for eCryptfs, and therefore are not affected by this issue. A future update in Red Hat Enterprise Linux 6 may address this flaw. This was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0723.html. These issues were fixed by the 5.0.2 release of the JBoss Enterprise SOA Platform, available for download from the Red Hat Customer Portal: https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?product=soaplatform&downloadType=distributions&version=5.0.2+GA The JBoss Enterprise SOA Platform 5.0.2 Release Notes are available from http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/5.0.2/html/5.0.2_Release_Notes/index.html This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG as they did not backport the upstream commit ffcebb16 that introduced this vulnerability. Not vulnerable. This issue did not affect the versions of freetype as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of freetype as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3 as it did not include support for Network File System (NFS) version 4. Future updates in Red Hat Enterprise 4, 5, and Red Hat Enterprise MRG may address this flaw. The mipv6-daemon packages in Red Hat Enterprise Linux 6 are not vulnerable to this issue, as they contain a backported patch correcting this flaw. The mipv6-daemon packages in Red Hat Enterprise Linux 6 are not vulnerable to this issue, as they contain a backported patch correcting this flaw. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and Red Hat Enterprise MRG as they did not include support for the upcall mechanism for the Common Internet File System (CIFS). This issue was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0723.html. Not vulnerable. This issue did not affect the versions of pidgin as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue is not planned to be fixed in Red Hat Enterprise Linux 3 due to this product being in Production 3 of its maintenance life-cycle, where only qualified security errata of important and critical impact are addressed. For further information about the Errata Support Policy, visit: http://www.redhat.com/security/updates/errata Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG as they did not include support for Btrfs, a new copy on write filesystem. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG as they did not include support for Btrfs, a new copy on write filesystem. This issue does not affect the version of the java-1.6.0-openjdk package, as shipped with Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 3, 4, or 5. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue did not affect the versions of evince as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of evince as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of evince as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of evince as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of KVM as shipped with Red Hat Enterprise Linux 5 as it does not contain the patch that introduced this vulnerability. This issue does not affect the version of the java-1.6.0-openjdk package, as shipped with Red Hat Enterprise Linux 5. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG as they did not include support for the GFS2 file system. A future kernel update in Red Hat Enterprise Linux 5 will address this issue. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG as they did not include support for GPU DRM. Not vulnerable. This issue did not affect the versions of freetype as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of freetype as shipped with Red Hat Enterprise Linux 3, 4, or 5. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue is not planned to be fixed in Red Hat Enterprise Linux 5, as its impact is mitigated by standard glibc protection mechanisms to cause only application abort. Red Hat Security Response Team does not consider a user-assisted crash (abort) of a client application, such as OpenOffice.org Impress tool, to be a security issue. This issue is not planned to be fixed in Red Hat Enterprise Linux 5, as its impact is mitigated by standard glibc protection mechanisms to cause only application abort. Red Hat Security Response Team does not consider a user-assisted crash (abort) of a client application, such as OpenOffice.org Impress tool, to be a security issue. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 3, 4, or 5 as they did not include support for ECDH. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3 as it did not include upstream commit be84c7f6 (history repository) that introduced the problem. A future kernel update in Red Hat Enterprise Linux 4, 5 and Red Hat Enterprise MRG will address this issue. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and Red Hat Enterprise MRG as they did not include support for the XFS file system. A future kernel update in Red Hat Enterprise Linux 5 will address this issue. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5 and Red Hat Enterprise MRG as they did not include support for the Journaled File System (JFS). This issue is not planned to be fixed in Red Hat Enterprise Linux 3 due to this product being in Production 3 of its maintenance life-cycle, where only qualified security errata of important and critical impact are addressed. For further information about the Errata Support Policy, visit: http://www.redhat.com/security/updates/errata A future update in Red Hat Enterprise Linux 4 and Red Hat Enterprise Linux 5 may address this flaw. Not vulnerable. This issue did not affect the versions of quagga package as shipped with Red Hat Enterprise Linux 3, 4, or 5, as these versions do not support 4 byte AS numbers (AS4 support) yet. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG as it did not include support for the IrDA protocol. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and 5 as they did not backport the upstream commit 3d23e349 that had introduced the problem. A future update in Red Hat Enterprise MRG may address this flaw. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG as they did not include support for the broadcast manager (BCM) protocol. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG as it did not include upstream commit ee18d64c that introduced the problem. The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG did not include support for Graphics Execution Manager (GEM) in the i915 driver, and therefore are not affected by this issue. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 3 and 4 as they did not include the upstream commit eb4eeccc that introduced the problem. It did not affect Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG as they did not provide support for the Stradis driver that uses the vulnerable compat code for VIDIOCSMICROCODE. As a preventive measure, we have removed the vulnerable code in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0839.html. We plan to remove the vulnerable code in a future kernel update in Red Hat Enterprise MRG. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG as they did not include support for the Ext4 filesystem. A future kernel update in Red Hat Enterprise Linux 5 will address this issue. Red Hat security response team does not consider a crash of a client application linked against freetype to be a security issue. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 3, 4, or 5, and Red Hat Application Stack v2. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 3, 4, or 5, and Red Hat Application Stack v2. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 3, 4, or 5, and Red Hat Application Stack v2. This issue is not planned to be fixed in Red Hat Enterprise Linux 3 due to this product being in Production 3 of its maintenance life-cycle, where only qualified security errata of important and critical impact are addressed. For further information about the Errata Support Policy, visit: http://www.redhat.com/security/updates/errata This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3 and 4 as they did not include support for eventfd in the Async I/O (AIO) implementation. It did not affect the version of Linux kernel as shipped with Red Hat Enterprise MRG as it has already had the fix to this issue. This issue was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0839.html This issue did not affect the version of Squid as shipped with Red Hat Enterprise Linux 3, 4, or 5. It was corrected in Red Hat Enterprise Linux 6 via RHSA-2011:0545. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and Red Hat Enterprise MRG as they did not include support for the XFS file system. This issue was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0839.html This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and 5, as they do not include support for Ftrace. It did not affect Red Hat Enterprise MRG as it did not contain the upstream commit 8fc0c701 that introduced this flaw. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and 5 as it did not include upstream commit 7034632d that introduced the problem. It did not affect Red Hat Enterprise MRG as the /dev/sequencer device file is restricted to root access only. More information can be found in this kbase: https://access.redhat.com/kb/docs/DOC-40265. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3 and 4, as they do not include support for the Neptune Ethernet driver. It did not affect Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG, as they do not contain the upstream commit 2d96cf8c that introduced this flaw. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3 and 4 as they did not support for the FUTEX_LOCK_PI futex operation. It did not affect the version of Linux kernel as shipped with Red Hat Enterprise MRG as it has already had the fix to this issue. This issue was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0839.html The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. The Red Hat Security Response Team has rated this issue as having low security impact. We do not currently plan to fix this flaw. If more information becomes available at a future date, we may revisit the issue. Not vulnerable. This issue did not affect the versions of conga as shipped with Red Hat Cluster Suite for Red Hat Enterprise Linux 4 and as shipped with Red Hat Enterprise Linux 5 as they use own internal mechanism to verify if user requesting particular page is authenticated. Plone private pages permissions configuration mechanism is not used in conga. The Red Hat Security Response Team has rated this issue as having low security impact, a future update to Red Hat Directory Server may address this flaw. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and 5 as they did not include support for equalizer load-balancer for serial network interfaces. This was addressed in Red Hat Enterprise Linux Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2010-0771.html. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and 5, as they did not support USB Option High Speed Mobile Devices. This was addressed in Red Hat Enterprise Linux Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2010-0771.html. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG, as they do not contain the upstream commit d4d67150 that introduced this flaw. More information can be found in this kbase: https://access.redhat.com/kb/docs/DOC-40330 This issue does not affect the version of dovecot package, as shipped with Red Hat Enterprise Linux 4, 5 and 6. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG as they did not include support for the ROSE protocol. Red Hat Enterprise Linux 3 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Not vulnerable. This issue did not affect the versions of pam as shipped with Red Hat Enterprise Linux 3, 4, 5, or 6. Not vulnerable. This issue did not affect the versions of pam as shipped with Red Hat Enterprise Linux 3, 4, 5, or 6. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3 as it did not include support for SCTP. This was addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2010-0958.html and https://rhn.redhat.com/errata/RHSA-2010-0842.html. Future updates in Red Hat Enterprise Linux 4 and 5 may address this flaw. We do not consider safe_mode / open_basedir restriction bypass issues to be security sensitive. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php The Linux kernel as shipped with Red Hat Enterprise Linux 3 and 4 did not include support for Packet writing layer for ATAPI and SCSI disc media devices, and therefore are not affected by this issue. The Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG only allow root access to the "/dev/pktcdvd/control" file, and therefore are also not affected by this issue. The Red Hat Security Response Team has rated this issue as having low security impact, a future update to wireshark in Red Hat Enterprise Linux 4 and 5 may address this flaw. This issue was addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2010-0924.html. This issue affects the version of the python package as shipped with Red Hat Enterprise Linux 4, 5, and 6. Due to the nature of this flaw, it cannot be fixed in the python language, but must be addressed in each module which calls accept(). This issue did not affect the versions of dhcp as shipped with Red Hat Enterprise Linux 4 and 5 as they did not include support for DHCPv6. The Red Hat Security Response Team has rated this issue as having low security impact. Because the version of bind in Red Hat Enterprise Linux 4 does not implement support for the currently-used DNSSEC protocol version, there is no plan to address this flaw there. It has been addressed in Red Hat Enterprise Linux 5 (via RHSA-2010:0975) and Red Hat Enterprise Linux 6 (via RHSA-2010:0976). Not vulnerable. This issue did not affect the versions of bind as shipped with Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. This issue did not affect the versions of dhcp as shipped with Red Hat Enterprise Linux 3, 4, 5, or 6. Not vulnerable. This issue did not affect the versions of mysql package as shipped with Red Hat Enterprise Linux 3, 4, 5, or 6. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 3 and 4. This issue was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0825.html. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 3 and 4. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 3. This issue was addressed in Red Hat Enterprise Linux 4, 5 and 6 via RHSA-2010:0824, RHSA-2010:0825 and RHSA-2011:0164 respectively. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 3 and 4. This issue was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2010-0825.html. Not vulnerable. This issue did not affect the versions of mysql package as shipped with Red Hat Enterprise Linux 3, 4, or 5. Not vulnerable. This issue did not affect the versions of freeradius as shipped with Red Hat Enterprise Linux 4, 5, or 6. Red Hat does not consider this to a security issue. In order for the crash condition to be observed, the RADIUS server must already be unresponsive for extended periods of time, the net result of which is that you cannot DoS an already-unresponsive server. Other specialized conditions are required as well, that make an attack using this flaw unviable. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-3705. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3 as it did not include support for SCTP. It did not affect Red Hat Enterprise Linux 4 and 5 as it did not include upstream commit 1f485649 that introduced the problem. Future kernel updates in Red Hat Enterprise MRG may address this flaw. Not vulnerable. This issue did not affect the versions of dovecot as shipped with Red Hat Enterprise Linux 4, 5 or 6. This issue did not affect the version of dovecot package, as shipped with Red Hat Enterprise Linux 4 and 5. This issue affects the version of dovecot package as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue did not affect the version of PHP as shipped with Red Hat Enterprise Linux 3, 4 or 5. This issue did not affect the version of php packages as shipped with Red Hat Enterprise Linux 4, 5 or 6. It did affect the PHP 5.3 (php53) package on Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of dovecot as shipped with Red Hat Enterprise Linux 4, 5 or 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 3, 4, 5, or 6. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, 6 or Red Hat Enterprise MRG. Red Hat does not provide support for the Acorn Econet network protocol. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, 6 or Red Hat Enterprise MRG. Red Hat does not provide support for the Acorn Econet network protocol. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, 6 or Red Hat Enterprise MRG. Red Hat does not provide support for the Acorn Econet network protocol. This flaw was resolved in the Red Hat JBoss BRMS 5.1.0 release. It was also resolved in the upstream Drools Guvnor 5.1 release. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 as they did not backport the upstream commit b6a2fea3 that introduced the issue. This was addressed in Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0004.html and https://rhn.redhat.com/errata/RHSA-2010-0958.html. Future kernel updates in Red Hat Enterprise Linux 6 may address this flaw. Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2010-3859. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 6 and Red Hat Enterprise MRG as they did not include support for Transparent Inter-Process Communication Protocol (TIPC). A future kernel update in Red Hat Enterprise Linux 5 may address this flaw. As a preventive measure, we plan to include the fixes in a future kernel update in Red Hat Enterprise Linux 4. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3 and 4, as they do not include support for the Neptune Ethernet driver. It did not affect Red Hat Enterprise Linux 5 as it did not contain the upstream commit 0853ad66 that introduced this flaw. This issue does not affect the versions of OpenSSL as shipped with Red Hat Enterprise Linux versions before Enterprise Linux 6. The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG did not include support for the RDS Protocol, and therefore are not affected by this issue. Future kernel updates in Red Hat Enterprise Linux 5 may address this flaw. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG as they did not include support for CCITT X.25 Packet Layer. The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and 5 did not include CAN bus subsystem support, and therefore are not affected by this issue. Future kernel updates in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG may address this flaw. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG as they did not include support for Amateur Radio AX.25 protocol. This issue is not planned to be fixed in Red Hat Enterprise Linux 3, due to this product being in Extended Life Cycle Phase of its maintenance life-cycle, where only qualified security errata of critical impact are addressed. For further information about the Errata Support Policy, visit: http://www.redhat.com/security/updates/errata This issue is not planned to be fixed in Red Hat Enterprise Linux 3, due to this product being in Extended Life Cycle Phase of its maintenance life-cycle, where only qualified security errata of critical impact are addressed. For further information about the Errata Support Policy, visit: http://www.redhat.com/security/updates/errata This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG as they did not include support for Transparent Inter-Process Communication Protocol (TIPC). A future kernel update in Red Hat Enterprise Linux 5 may address this flaw. The Red Hat Security Response Team has rated this issue as having low security impact. On Red Hat Enterprise Linux 5 and 6, a user must be a member of the 'fuse' group in order to use FUSE. Due to the risks associated with fixing this bug on Red Hat Enterprise Linux 5, and because of the group restrictions in place, we currently have no plans to fix this flaw in Red Hat Enterprise Linux 5. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not include support for monitoring of INET transport protocol sockets. Future updates in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG may address this flaw. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG as they did not include support for Kernel-based Virtual Machine (KVM). A future kernel update in Red Hat Enterprise Linux 5 may address this flaw. The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and Red Hat Enterprise MRG did not include support for the RDS Protocol, and therefore are not affected by this issue. Updates for Red Hat Enterprise Linux 5 and 6 are available to address this flaw. Not vulnerable. This issue did not affect the versions of festival as shipped with Red Hat Enterprise Linux 3, 4, or 5. This issue did not affect the versions of libxml and libxml2 as shipped with Red Hat Enterprise Linux 3, and it did not affect the version of libxml2 as shipped with Red Hat Enterprise Linux 4. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 3, 4 and 5. Not vulnerable. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 4, 5, or 6. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 4 or 5 as the flaw was introduced in a later version of MIT krb5 (1.7). Red Hat does not consider crash of client application, using regcomp() or regexec() routines on untrusted input without preliminary checking the input for the sanity, to be a security issue (the described deficiency implies and is a known limitation of the glibc regular expression engine implementation). The expressions can be modified to avoid quantification nesting, or program modified to limit size of input passed to regular expression engine. We do not currently plan to fix these flaws. If more information becomes available at a future date, we may revisit these issues. Red Hat does not consider crash of client application, using regcomp() or regexec() routines on untrusted input without preliminary checking the input for the sanity, to be a security issue (the described deficiency implies and is a known limitation of the glibc regular expression engine implementation). The expressions can be modified to avoid quantification nesting, or program modified to limit size of input passed to regular expression engine. We do not currently plan to fix these flaws. If more information becomes available at a future date, we may revisit these issues. This issue is not planned to be fixed in Red Hat Enterprise Linux 3, due to this product being in Extended Life Cycle Phase of its maintenance life-cycle, where only qualified security errata of critical impact are addressed. For further information about the Errata Support Policy, visit: http://www.redhat.com/security/updates/errata This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3 as it did not include IPC compat functionality. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and 5 as they did not include support for Moschip USB serial port adapters. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3 as it did not include the affected functionality. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG as they did not include support for Amiga built-in serial port. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and 5 as they did not include support for GlobeTrotter HSPDA PCMCIA card. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, 5, and Red Hat Enterprise MRG as they did not include or support the affected functionality. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and 5 as they did not include support for the Conexant's CX23415/CX23416 codec chip. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3 as it did not include support for RME Hammerfall DSP Audio. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3 and 4 as they did not include support for RME Hammerfall DSP MADI Audio interface. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 3, 4, and 5 as they did not include support for VIA UniChrome (Pro) and Chrome9 graphics boards. This issue is not planned to be fixed in Red Hat Enterprise Linux 3, due to this product being in Extended Life Cycle Phase of its maintenance life-cycle, where only qualified security errata of critical impact are addressed. For further information about the Errata Support Policy, visit: http://www.redhat.com/security/updates/errata We do not consider safe_mode / open_basedir restriction bypass issues to be security sensitive. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php This issue did not affect the version of php packages as shipped with Red Hat Enterprise Linux 4, 5 or 6. It did affect the PHP 5.3 (php53) package on Red Hat Enterprise Linux 5. The Linux kernel as shipped with Red Hat Enterprise Linux 3 did not include the vulnerable code, and therefore is not affected by this issue. Future kernel updates in Red Hat Enterprise Linux 4, 5 and Red Hat Enterprise MRG may address this flaw. The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and 5 did not include L2TP functionality, and therefore are not affected by this issue. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0007.html and https://rhn.redhat.com/errata/RHSA-2011-0330.html. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not backport the upstream commit 93821778 that introduced this. It did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as they have backported the upstream commit fda9ef5d that addressed this. Future kernel update in Red Hat Enterprise Linux 5 may address this flaw. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not backport the upstream commit c5dec1c3 that introduced the issue. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0007.html and https://rhn.redhat.com/errata/RHSA-2011-0330.html. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not backport the upstream commit c5dec1c3 that introduced the issue. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0007.html and https://rhn.redhat.com/errata/RHSA-2011-0330.html. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not include support for CCITT X.25 Packet Layer. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not backport the upstream commit that introduced the issue. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0283.html and https://rhn.redhat.com/errata/RHSA-2011-0330.html. The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and 5 did not backport the upstream commit dab5855 that introduced the issue. Future kernel updates in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG may address this flaw. This issue does not affect the version of the systemtap package as shipped with Red Hat Enterprise Linux 4. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 4 and Red Hat Enterprise MRG as they did not include support for the RDS protocol. It did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6 as they did not backport the upstream commit eff5f53b that introduced this issue. Not vulnerable. This issue did not affect the versions of dracut as shipped with Red Hat Enterprise Linux 6. This issue affects the version of the mercurial package, as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not have support for CPU time clocks for the POSIX clock interface. This has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0004.html, https://rhn.redhat.com/errata/RHSA-2011-0007.html and https://rhn.redhat.com/errata/RHSA-2011-0330.html. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5. It was addressed in Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0330.html. A future kernel update in Red Hat Enterprise Linux 6 may address this flaw. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise MRG as they have already backported the fixes for this issue. Future kernel updates in Red Hat Enterprise Linux 6 may address this flaw. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Not vulnerable. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG as they did not backport the upstream commit 35f3d14d that introduced this issue. The Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG enabled the panic_on_oops sysctl tunable by default, and therefore are not affected by this issue. However, as a preventive measure (for example, for administrators who have turned panic_on_oops off), this issue was fixed in kernel updates in Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG. Because the fix was considered as a preventative measure, this CVE is not listed in the related advisories that provided the fix: RHSA-2011:0162, RHSA-2011:0263, RHSA-2011:0017, RHSA-2011:0498, RHSA-2011:0542, RHSA-2011:0330. The fix is documented in each of these advisories as a regular bug fix, for example as BZ#659568 in RHSA-2011:0162. This issue affects the version of the fontforge package as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 4 and Red Hat Enterprise MRG as they did not include support for PCI I/O Virtualization (IOV). Future updates in Red Hat Enterprise Linux 5 and 6 may address this flaw. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 4 and 5 as they did not include support for the Local Download Sharing Service (LDSS) protocol. This issue was addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2010-0924.html. This issue did not affect the versions of wireshark shipped with Red Hat Enterprise Linux 4, 5, and 6, as they did not include support for the Zigbee Cluster Library (ZCL) protocol. This issue is only a defense-in-depth measure, and we currently have no plans to fix this flaw in Red Hat Enterprise Linux 6. The use of the useHttpOnly setting in Tomcat only prohibits client scripts from accessing cookies when it is correctly implemented in the user's web browser. The use of httpOnly does not guarantee XSS protection; it is only a defense-in-depth measure. Additionally, implementing this as a default setting could have negative impact on existing expected behavior in client scripts. As a result, the Red Hat Security Response Team has determined that this issue is not a security flaw, but a proactive hardening measure and the risk associated with implementing it by default and possibly breaking expected behaviour is greater than any benefits it provides. Users who wish to take advantage of this hardening measure can enable useHttpOnly by adding '<Context useHttpOnly="true">' to the default context.xml or a specific web-application context. This issue did not affect perl-IO-Socket-SSL version as shipped with Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 or Red Hat Enterprise MRG. Red Hat does not provide support for the Acorn Econet network protocol. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not include support for the Brocade Fibre Channel Host Bus Adapter driver. It did not affect the version of Linux kernels as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as they have the included the fix for this issue. A future kernel update in Red Hat Enterprise Linux 5 may address this flaw. The Linux kernel as shipped with Red Hat Enterprise Linux 4 is not vulnerable because it checks for mmap_min_addr even in special cases. The Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG have mmap_min_addr sysctl tunable set to 4096, and therefore are not affected by this issue. However, as a preventive measure (for example, for administrators who have increased mmap_min_addr), we have addressed this in Red Hat Enterprise Linux 5, 6 and MRG via https://rhn.redhat.com/errata/RHSA-2011-0429.html, https://rhn.redhat.com/errata/RHSA-2011-0421.html, and https://rhn.redhat.com/errata/RHSA-2011-0330.html. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and 6 as they did not include upstream commit a1a541d8 and a25ee920 that introduced the problem. This has been addressed in Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0330.html. Notes: This requires debugfs to be mounted on a local system in order to have access to the custom_method file. Debugfs is not mounted by default. You need to run "mount -t debugfs nodev /sys/kernel/debug" as root first. This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 4 and 5. The getSymbol() and setSymbol() functions are unlikely to ever receive untrusted input as an $attr argument, and it is even less likely that they would receive such input when only a small set of pre-defined constants is expected. As a result, this flaw can only be triggered by the script author and cannot be used to cross trust boundaries. The Red Hat Security Response Team does not consider it to be security-relevant. Not vulnerable. This issue did not affect the versions of openssh as shipped with Red Hat Enterprise Linux 4, 5, or 6. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of libxml and libxml2 as shipped with Red Hat Enterprise Linux 3, and it did not affect the version of libxml2 as shipped with Red Hat Enterprise Linux 4 and 5. This issue did not affect the versions of cobbler as shipped with Red Hat Satellite version 5. The Linux kernel as shipped with Red Hat Enterprise Linux 4 did not include upstream commit history:5aabd1fe268e850c2e93048a5ccc5eb6970ac49c, and therefore is not affected by this issue. This has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via http://rhn.redhat.com/errata/RHSA-2011-0163.html, https://rhn.redhat.com/errata/RHSA-2011-0421.html and https://rhn.redhat.com/errata/RHSA-2011-1253.html. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not provide support for Open Sound System (OSS). This issue did not affect the versions of pidgin package as shipped with Red Hat Enterprise Linux 4, 5, and 6 as this issue is specific to versions of libpurple from 2.7.6 up to 2.7.8. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, or Red Hat Enterprise MRG. Red Hat does not provide support for the IrDA protocol. The Red Hat Security Response Team has rated this issue as having low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and 5 did not include CAN bus subsystem support, and therefore are not affected by this issue. This has been addressed in Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0330.html. A future kernel update in Red Hat Enterprise Linux 6 may address this flaw. This issue leads to a temporary denial of service (high CPU consumption) when a PHP script handles numeric values from untrusted user input. It does not affect the versions of PHP as shipped with Red Hat Enterprise Linux 3, 4 or 5. It did affect the PHP 5.3 (php53) package on Red Hat Enterprise Linux 5. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not backport the upstream commit d03032af that introduced this issue. Future kernel updates in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG may address this flaw. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0927.html and https://rhn.redhat.com/errata/RHSA-2011-0498.html, and https://rhn.redhat.com/errata/RHSA-2011-0330.html. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not backport the upstream commit 59efec7b that introduced this issue. It did not affect the version of Linux kernel as shipped with Red hat Enterprise MRG as it did not provide support for Character device in Userspace (CUSE). A future kernel update in Red Hat Enterprise Linux 6 may address this flaw. Note that, by default, the "/dev/cuse" file in Red Hat Enterprise Linux 6 is only accessible by the root user. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they do not have support for the I/O-Warrior USB devices. This has been addressed in Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0330.html. A future kernel update in Red Hat Enterprise Linux 6 may address this flaw. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw the packages php53 php. The Red Hat Security Response Team has rated this issue as having low security impact, a future update to Red Hat Enterprise Linux 6 may address this flaw. This issue did not affect Red Hat Enterprise Linux 4 or 5. The Red Hat Security Response Team has rated this issue as having moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This flaw has already been fixed in Red Hat Enterprise Linux 4 and 5 by a patch included in RHSA-2010:0519. Not vulnerable. This issue did not affect the versions of libarchive as shipped with Red Hat Enterprise Linux 4, 5, and 6. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not backport the upstream commit c5dec1c3 that introduced the issue. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0007.html and https://rhn.redhat.com/errata/RHSA-2011-0330.html. We do not consider safe_mode / open_basedir restriction bypass issues to be security sensitive. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php Not vulnerable. This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 4, 5, or 6. Red Hat does not consider this issue to be a security vulnerability, rather consider this to be a non-security bug. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 4, 5, or 6. Red Hat does not consider this issue to be a security flaw. For additional details, refer to: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2010-4706 The Red Hat Security Response Team has rated this issue as having low security impact. This issue was addressed in the PAM packages in Red Hat Enterprise Linux 5 via RHSA-2010:0819 and in Red Hat Enterprise Linux 6 via RHSA-2010:0891. A future update may correct this issue in the PAM packages in Red Hat Enterprise Linux 4. Not vulnerable. This issue did not affect Red Hat Directory Server 8 packages. We do not consider a denial of service flaw in a client application such as sftp to be a security issue. Not vulnerable. This issue did not affect the versions of perl as shipped with Red Hat Enterprise Linux 4, 5, or 6 as they did not have asserts enabled. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise MRG as they have already backported the fixes for this issue. Future kernel updates in Red Hat Enterprise Linux 6 may address this flaw. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the version of poppler as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of poppler as shipped with Red Hat Enterprise Linux 7. A future update may address this issue. This issue did not affect the openssl packages shipped with Red Hat Enterprise Linux 5. This issue did not affect the kvm packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue does affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Based on the absence of upstream patch addressing this issue in VIDEOBUF (newer drivers using VIDEOBUF2 are not affected) implementation and that Red Hat Product Security has rated this issue as having Low security impact, this issue is not currently planned to be addressed in future kernel updates for the respective releases. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This flaw affects Red Hat Enteprise Linux 5 and 6 and is not able to be exploited in the default configuration. Administrators would need to replace the init daemon with alternative systems to exploit this system crash correctly. No update is planned to be released for this flaw. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG are not affected by this issue. A future kernel update in Red Hat Enterprise Linux 6 may address this flaw. Not vulnerable. This issue did not affect the versions of sudo as shipped with Red Hat Enterprise Linux 4, 5, or 6. This issue does not affect versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 3, 4, and 5. It was addressed in Red Hat Enterprise Linux 6 via RHSA-2011:0677. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue did not affect the versions of qt shipped with Red Hat Enterprise Linux 4, 5 and 6. Not vulnerable. This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 4, 5, or 6. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 3 or 4 as they did not include support for the LDAP backend. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 3 or 4 as they did not include support for the LDAP backend. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 3, 4, 5 or 6. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of libpng as shipped with Red Hat Enterprise Linux 4, 5, or 6. This issue did not affect the versions of libpng10 as shipped with Red Hat Enterprise Linux 4. This issue affected postfix packages in Red Hat Enterprise Linux 4, 5, and 6. It was corrected via RHSA-2011:0422 and RHSA-2011:0423. This issue did not affect the versions of sendmail as shipped with Red Hat Enterprise Linux 3, 4, 5, or 6, and the versions of exim as shipped with Red Hat Enterprise Linux 4 and 5. Not vulnerable. This issue did not affect the versions of bind as shipped with Red Hat Enterprise Linux 4, 5, or 6. Red Hat does not consider this flaw to be a security issue. The size argument of the grapheme_extract function is unlikely to from an untrusted source unfiltered, therefore the value passed to the function is under the the full control of the script author and no trust boundary is crossed. Not vulnerable. This issue did not affect the versions of evince as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of kbd as shipped with Red Hat Enterprise Linux 4, 5, or 6 as they do not include the affected script. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not provide support for the Oracle Cluster File System (OCFS). Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/CVE-2011-0521 This issue did not affect the version of the Linux kernel as shipped with Red Hat Enterprise Linux 3 as it did not include support for ULE (Unidirectional Lightweight Encapsulation). We have included a fix for this issue in Red Hat Enterprise Linux 4, 5 and Red Hat Enterprise MRG however the affected module is not build by default. Not vulnerable. This issue did not affect the versions of Puppet in any Red Hat product. Not vulnerable. This issue did not affect the versions of openssh as shipped with Red Hat Enterprise Linux 4, 5, or 6. The Red Hat Security Response Team has rated this issue as having low security impact. On Red Hat Enterprise Linux 5 and 6, a user must be a member of the 'fuse' group in order to use FUSE. Due to the risks associated with fixing this bug on Red Hat Enterprise Linux 5, and because of the group restrictions in place, we currently have no plans to fix this flaw in Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this issue as having low security impact. On Red Hat Enterprise Linux 5 and 6, a user must be a member of the 'fuse' group in order to use FUSE. Due to the risks associated with fixing this bug on Red Hat Enterprise Linux 5, and because of the group restrictions in place, we currently have no plans to fix this flaw in Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this issue as having low security impact. On Red Hat Enterprise Linux 5 and 6, a user must be a member of the 'fuse' group in order to use FUSE. Due to the risks associated with fixing this bug on Red Hat Enterprise Linux 5, and because of the group restrictions in place, we currently have no plans to fix this flaw in Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this issue as having no security impact. We do not plan to take any action regarding this flaw at this time. If additional information becomes available at a future date, we will revisit this issue and act accordingly. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0927.html, https://rhn.redhat.com/errata/RHSA-2011-0421.html, and https://rhn.redhat.com/errata/RHSA-2011-0500.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, or Red Hat Enterprise MRG as they did not backport the upstream commit bf5fc093c that introduced this issue. Not vulnerable. This issue did not affect Red Hat Directory Server 8 packages. This issue did not affect the versions of the java-1.6.0-openjdk package as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG as they did not backport the upstream commit eb1d1641 that introduced net/bridge/br_multicast.c. It did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 6 as it did not backport the upstream commit 8ef2a9a5 that introduced this issue. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise MRG as it does not have support for the S390 architecture. A future kernel update in Red Hat Enterprise Linux 6 may address this flaw. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2011-0429.html. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not have support for the XFS file system. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0927.html, https://rhn.redhat.com/errata/RHSA-2011-0498.html, and https://rhn.redhat.com/errata/RHSA-2011-0500.html. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not backport the driver for Native Instruments USB audio devices. It did not affect the Linux kernel as shipped with Red Hat Enterprise MRG as it did not enable support for this driver. This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2011-0498.html. This issue only affects Red Hat Enterprise Linux 6 as we did not properly backport upstream commit b48fa6b9. The versions of the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG are not affected. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG as they did not include support for the bridge snooping functionality. A future update in Red Hat Enterprise Linux 6 may address this flaw. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Future kernel updates in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG may address this flaw. We do not consider this flaw to be a security issue as it is only exploitable by the script author. No trust boundary is crossed. This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 3, 4, or 5 (php). This issue was addressed in the php53 packages as shipped in Red Hat Enterprise Linux 5 before their first release in Red Hat Enterprise Linux 5.6, and it was addressed in the php package in Red Hat Enterprise Linux 6 via RHBA-2011:0615. Red Hat does not consider this issue to be a security vulnerability since no trust boundary is crossed. Any process able to send signals to a running PHP process can terminate it by sending a carefully-chosen signal. Red Hat does not consider this flaw to be a security issue as arguments passed to the mt_rand function are under the full control of the script author. No trust boundary is crossed. This flaw exists in the php53 packages versions as shipped in Red Hat Enterprise Linux 5 and the php packages versions as shipped in Red Hat Enterprise Linux 6. Red Hat does not consider this problem to be a security issue. Input passed to these functions should be under the full control of the script author, therefore no trust boundary is crossed. Not vulnerable. This issue only affected Java versions running on Windows platform. It did not affect the versions of java-1.6.0-openjdk as shipped with Red Hat Enterprise Linux 5 and 6, and the java-1.6.0-sun packages as shipped with Red Hat Enterprise Linux 4 Extras and Red Hat Enterprise Linux 5 and 6 Supplementary. Not vulnerable. This issue only affected Java versions running on Windows platform. It did not affect the versions of java-1.6.0-openjdk as shipped with Red Hat Enterprise Linux 5 and 6, and the java-1.6.0-sun packages as shipped with Red Hat Enterprise Linux 4 Extras and Red Hat Enterprise Linux 5 and 6 Supplementary. This issue only affects Red Hat Enterprise Linux 6. The version of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG as they did not include upstream commit 71e3aac0 that introduced the problem. We have addressed this in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2011-0542.html. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0429.html, https://rhn.redhat.com/errata/RHSA-2011-0542.html and https://rhn.redhat.com/errata/RHSA-2011-0500.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not provide support for the Windows Logical Disk Manager. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5 as they did not include the affected functionality. A future update in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG may address this flaw. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG as they did not backport the upstream commits fff1ce4d and 45e4039c that introduced this issue. This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2011-0498.html. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not provide support for the Windows Logical Disk Manager. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not backport the upstream commit a8f80e8f that introduced this flaw. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0498.html and https://rhn.redhat.com/errata/RHSA-2011-0500.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via RHSA-2012:0007, RHSA-2011:1530 and RHSA-2011:1253 respectively. The version of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and 6 as they did not include upstream commit a1a541d8 and a25ee920 that introduced the problem. This has been addressed in Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1253.html. Notes: This requires debugfs to be mounted on a local system in order to have access to the custom_method file. Debugfs is not mounted by default. You need to run "mount -t debugfs nodev /sys/kernel/debug" as root first. The Linux kernel as shipped with Red Hat Enterprise Linux 4 and Red Hat Enterprise MRG did not include support for the RDS Protocol, and therefore are not affected by this issue. The Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6 are not affected as they did not backport upstream commit 2e7b3b99 and 77dd550e that introduced this issue. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0927.html and https://rhn.redhat.com/errata/RHSA-2011-0498.html, and https://rhn.redhat.com/errata/RHSA-2011-0330.html. Not vulnerable. This issue did not affect Red Hat Directory Server 8 packages. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, or Red Hat Enterprise MRG as they did not backport the upstream commit 4a2d7892 that introduced this issue. This issue does not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5. This was addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0542.html and https://rhn.redhat.com/errata/RHSA-2011-0500.html. This issue affected the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG. It was addressed in Red Hat Enterprise Linux 5 and 6 via RHSA-2012:0150 and RHSA-2012:0862 respectively. There is no plan to address this flaw in Red Hat Enterprise Linux 4. Future updates may address this issue in Red Hat Enterprise MRG. Not vulnerable. This issue did not affect the versions of Apache Tomcat 5 as shipped with Red Hat Enterprise Linux 5, Red Hat Developer Suite 3, Red Hat Certificate System 7.3, Red Hat Network Satellite 5.3.0 and earlier versions and JBoss Enterprise Web Server 1.0. It did not affect the versions of Apache Tomcat 6 as shipped with Red Hat Enterprise Linux 6 and JBoss Enterprise Web Server 1.0. It also did not affect the versions of jbossweb as shipped with JBoss Enterprise Application Platform 4.3.0 and earlier versions, as this flaw only affects Apache Tomcat 7.0.0 to 7.0.10. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not backport the upstream commit 4b580ee3 that introduced this issue. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0429.html, https://rhn.redhat.com/errata/RHSA-2011-0542.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. This issue affects the versions of pidgin package as shipped with Red Hat Enterprise Linux 4, 5 and 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Red Hat does not consider this to be a security issue. Input passed to these functions should be under the full control of the script author, thus no trust boundary is crossed. Additionally, an administrator would have to disable, or excessively increase the memory_limit settings in the PHP configuration file to trigger this bug. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not include support for the DCCP protocol. Future updates in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG may address this flaw. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 4, 5, or 6. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Red Hat Security Response Team has rated this issue as having low security impact. We do not currently plan to fix this flaw. If more information becomes available at a future date, we may revisit the issue. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 4. Red Hat does not consider this flaw to be a security issue. It is improbable that a script would accept untrusted user input or unvalidated script input data as a PHAR archive file name to load. The file name passed to the PHAR-handling functions is therefore under the full control of the script author and no trust boundary is crossed. Not vulnerable. This issue did not affect the versions of logrotate as shipped with Red Hat Enterprise Linux 4 and 5, as they did not support 'shred' logrotate configuration directive yet. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0833.html, https://rhn.redhat.com/errata/RHSA-2011-0542.html, and https://rhn.redhat.com/errata/RHSA-2011-0500.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This issue did not affect the version of vino as shipped with Red Hat Enterprise Linux 4 or 5 as they did not include support for Universal Plug and Play (UPnP). A future update in Red Hat Enterprise Linux 6 may address this flaw. To mitigate this issue, users should ensure that confirmation is requested on each inbound connection attempt, that a password is required to connect, and that automatic network configuration is disabled. This will prevent vino from using UPnP to allow access to the VNC port, and will ensure that any connections require a password and that the user is notified on any connection attempts. This issue did not affect the version of vino as shipped with Red Hat Enterprise Linux 4 or 5 as they did not include support for Universal Plug and Play (UPnP). A future update in Red Hat Enterprise Linux 6 may address this flaw. To mitigate this issue, users should ensure that confirmation is requested on each inbound connection attempt, that a password is required to connect, and that automatic network configuration is disabled. This will prevent vino from using UPnP to allow access to the VNC port, and will ensure that any connections require a password and that the user is notified on any connection attempts. The Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG are not affected as they did not backport upstream commit 719f82d3 that introduced this issue. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Future kernel updates in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG may address this flaw. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Future kernel updates in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG may address this flaw. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Future kernel updates in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG may address this flaw. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 or Red Hat Enterprise MRG. Red Hat does not provide support for the Acorn Econet network protocol. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, or Red Hat Enterprise MRG. Red Hat does not provide support for IrDA. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This was addressed in Red Hat Enterprise Linux 5 and 6 via https://rhn.redhat.com/errata/RHSA-2011-0927.html and https://rhn.redhat.com/errata/RHSA-2011-1189.html. A future kernel update in Red Hat Enterprise MRG may address this flaw. Not vulnerable. This issue did not affect the versions of Apache Tomcat 5 as shipped with Red Hat Enterprise Linux 5, Red Hat Developer Suite 3, Red Hat Certificate System 7.3, Red Hat Network Satellite 5.3.0 and earlier versions and JBoss Enterprise Web Server 1.0. It did not affect the versions of Apache Tomcat 6 as shipped with Red Hat Enterprise Linux 6 and JBoss Enterprise Web Server 1.0. It also did not affect the versions of jbossweb as shipped with JBoss Enterprise Application Platform 4.3.0 and earlier versions, as this flaw only affects Apache Tomcat 7.0.11. Not Vulnerable. These issues do not affect the versions of firefox and thunderbird package, as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of libxslt package as shipped with Red Hat Enterprise Linux 4, 5 and 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not Vulnerable. This issue does not affect the version of conga as shipped with Red Hat Enterprise Linux 5 and Red Hat Cluster Suite EL4 Not vulnerable. This issue did not affect the versions of tetex as shipped with Red Hat Enterprise Linux 4 or 5, and the versions of texlive as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of exim as shipped with Red Hat Enterprise Linux 4 or 5 as they did not include support for DKIM. Not vulnerable. This issue did not affect the versions of Apache Tomcat 5 as shipped with Red Hat Enterprise Linux 5, Red Hat Developer Suite 3, Red Hat Certificate System 7.3, Red Hat Network Satellite 5.3.0 and earlier versions and JBoss Enterprise Web Server 1.0. It did not affect the versions of Apache Tomcat 6 as shipped with Red Hat Enterprise Linux 6 and JBoss Enterprise Web Server 1.0. It also did not affect the versions of jbossweb as shipped with JBoss Enterprise Application Platform 4.3.0 and earlier versions, as this flaw only affects Apache Tomcat 7.0.0 to 7.0.10. Red Hat does not consider this flaw to be a security issue. It is improbable that a script would accept untrusted user input or unvalidated script input data to the strval() function. Input passed to the functions is therefore under the full control of the script author and no trust boundary is crossed. As well, an administrator would have to excessively increase the precision settings in order to trigger this flaw. This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 4 and 5. The getSymbol() and setSymbol() functions are unlikely to ever receive untrusted input as an $attr argument, and it is even less likely that they would receive such input when only a small set of pre-defined constants is expected. As a result, this flaw can only be triggered by the script author and cannot be used to cross trust boundaries. The Red Hat Security Response Team does not consider it to be security-relevant. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 4 and 5. It has been addressed in Red Hat Enterprise Linux 5 (php53) and 6 (php). This issue did not affect the version of php as shipped with Red Hat Enterprise Linux 4. This issue does not affect the version of php shipped with Red Hat Enterprise Linux 4, 5 and 6. This issue does not affect the version of php53 shipped with Red Hat Enterprise Linux 5. This issue affects all of the versions of OpenSSL in Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Low security impact. We currently have no plans to fix this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, or Red Hat Enterprise MRG as they did not backport the PaX patchset. Not vulnerable. This issue did not affect the versions of Apache Tomcat 5 as shipped with Red Hat Enterprise Linux 5, Red Hat Developer Suite 3, Red Hat Certificate System 7.3, Red Hat Network Satellite 5.3.0 and earlier versions and JBoss Enterprise Web Server 1.0. It did not affect the versions of Apache Tomcat 6 as shipped with Red Hat Enterprise Linux 6 and JBoss Enterprise Web Server 1.0. It also did not affect the versions of jbossweb as shipped with JBoss Enterprise Application Platform 4.3.0 and earlier versions, as this flaw only affects Apache Tomcat 7.0.0 to 7.0.11. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not provide support for Open Sound System (OSS). Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not provide support for Open Sound System (OSS). This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not support Generic Receive Offload (GRO). It has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0429.html, https://rhn.redhat.com/errata/RHSA-2011-0421.html and https://rhn.redhat.com/errata/RHSA-2011-1253.html. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0498.html and https://rhn.redhat.com/errata/RHSA-2011-1253.html. The Red Hat Security Response Team has rated this issue as having low security impact, and it did not affect the versions of perl as shipped with Red Hat Enterprise Linux 4 and 5. A future update in Red Hat Enterprise Linux 6 may address this flaw. Not vulnerable. This issue did not affect the versions of rsyslog as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of rsyslog as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of rsyslog as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, or Red Hat Enterprise MRG. Red Hat does not provide support for the ROSE protocol. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not provide support for MPT (Message Passing Technology) based controllers. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0833.html, and https://rhn.redhat.com/errata/RHSA-2011-0542.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not provide support for MPT (Message Passing Technology) based controllers. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0833.html, and https://rhn.redhat.com/errata/RHSA-2011-0542.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. Not vulnerable. This issue affects the GlassFish Server Administration Console, which is not shipped with any Red Hat products. This issue affects the Red Hat HPC Solution which is End of Life. For more information please refer to: https://access.redhat.com/support/policy/updates/hpc/ This issue was addressed in krb5-appl packages in Red Hat Enterprise Linux 6 via RHSA-2011:0920 and krb5 packages in Red Hat Enterprise Linux 5 via RHSA-2012:0306. This issue is not planned to be addressed in Red Hat Enterprise Linux 4, where this issue was rated as having low security impact. Not vulnerable. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 4 or 5. Not vulnerable. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 4 or 5. Not vulnerable. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 4 and 5. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not support SCTP authentication and extended parameters. It did not affect the version of Linux kernel as shipped with Red Hat Enterprise MRG as it has backported the upstream commit a8170c35 that addressed this. This has been addressed in Red Hat Enterprise Linux 5 and 6 via https://rhn.redhat.com/errata/RHSA-2011-0927.html and https://rhn.redhat.com/errata/RHSA-2011-0498.html. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not support Generic Receive Offload (GRO). This has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0927.html and https://rhn.redhat.com/errata/RHSA-2011-1189.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG. This has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0833.html, https://rhn.redhat.com/errata/RHSA-2011-1465.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG as they did not backport the upstream commit bb1d9123 that introduced this issue. A future kernel update in Red Hat Enterprise Linux 6 may address this flaw. Not vulnerable. This issue did not affect the versions of Apache Tomcat 5 as shipped with Red Hat Enterprise Linux 5, Red Hat Developer Suite 3, Red Hat Certificate System 7.3, Red Hat Network Satellite 5.3.0 and earlier versions and JBoss Enterprise Web Server 1.0. It did not affect the versions of Apache Tomcat 6 as shipped with Red Hat Enterprise Linux 6 and JBoss Enterprise Web Server 1.0. It also did not affect the versions of jbossweb as shipped with JBoss Enterprise Application Platform 4.3.0 and earlier versions, as this flaw only affects Apache Tomcat 7.0.12 & 7.0.13. This issue did not affect the versions of the Xen package as shipped with Red Hat Enterprise Linux 4 and 6. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2011-0496.html. This issue did not affect the versions of Linux kernel as shipped in Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG as they did not ship mount.cifs with root setuid set. However, as a preventive meaasure, we have addressed this in Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1386.html and https://rhn.redhat.com/errata/RHSA-2011-1253.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This issue does not affect the version of wireshark package as shipped with Red Hat Enterprise Linux 4 and 5. This issue was fixed in Red Hat Enterprise Linux 6 via RHSA-2012:0509. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 4, 5, or 6. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG. This has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0927.html, https://rhn.redhat.com/errata/RHSA-2011-1189.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and 5 did not include support for the CAN protocol, and therefore are not affected by this issue. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0836.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. We do not consider safe_mode / open_basedir restriction bypass issues to be security sensitive. For more details see https://bugzilla.redhat.com/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php On Red Hat Enterprise Linux, by default, mount.cifs is not provided with the setuid bit enabled. If a user has turned on the setuid bit (via chmod +s /sbin/mount.cifs), they would be affected by this issue, and can work around the problem by removing the setuid bit. Red Hat Enterprise Linux 3 does not provide the mount.cifs program. Not vulnerable. This issue did not affect the versions of gdm as shipped with Red Hat Enterprise Linux 4, 5, or 6. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise 4, 5, 6, and Red Hat Enterprise MRG. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0927.html, https://rhn.redhat.com/errata/RHSA-2011-1350.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise 4, 5, 6, and Red Hat Enterprise MRG. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0927.html, https://rhn.redhat.com/errata/RHSA-2011-1350.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Red Hat Security Response team does not consider this bug to be security relevant one due to the privileges (CAP_SYS_RAWIO) required to exploit this issue. The Linux kernel as shipped with Red Hat Enterprise Linux 3, 4 and 5 did not include support for the CAN protocol, and therefore are not affected by this issue. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0836.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. This issue did not affect the versions of nfs-utils as shipped with Red Hat Enterprise Linux 4 as it did not include include mount.nfs. It was addressed in Red Hat Enterprise Linux 5 and 6 via RHSA-2012:0310 and RHSA-2011:1534 respectively. This issue does not affect versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue only affects Red Hat Enterprise Linux 6. The version of the qemu/kvm as shipped with Red Hat Enterprise Linux 5 is not affected. Vulnerable. This issue has been addressed in Red Hat Network Satellite Server v 5.4.1 via RHSA-2011:0882 https://rhn.redhat.com/errata/RHSA-2011-0882.html and in Red Hat Network Proxy Server v5.4.1 via RHSA-2011:0881 https://rhn.redhat.com/errata/RHSA-2011-0881.html. This issue is not planned to be fixed in Red Hat Network Satellite Server versions 5.0.2, 5.1.1, 5.2.1, 5.3.0 and not planned to be fixed in Red Hat Network Proxy Server versions 5.0.2, 5.1.1, 5.2.1, and 5.3.0. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not provide support for the ARM architecture. Red Hat currently does not plan to address this issue. For details refer to: https://bugzilla.redhat.com/show_bug.cgi?id=700883#c18 Not vulnerable. This issue did not affect the version of libmodplug embedded in gstreamer-plugins as shipped with Red Hat Enterprise Linux 4. This issue only affects Red Hat Enterprise Linux 5 as we did not backport upstream Xen unstable commit 2dcdd2fcb945. The versions of the Linux kernel as shipped with Red Hat Enterprise Linux 4, 6, and Red Hat Enterprise MRG are not affected. Not vulnerable. This issue did not affect the versions of exim as shipped with Red Hat Enterprise Linux 4 or 5 as they did not include support for DKIM. The Linux kernel as shipped with Red Hat Enterprise Linux 4, and 5 did not provide support for Network Namespace, and therefore are not affected by this issue. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0928.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. The Linux kernel as shipped with Red Hat Enterprise Linux 4, and 5 did not provide support for Network Namespace, and therefore are not affected by this issue. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0928.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. This issue does not affect Red Hat Enterprise Linux 4 and 5: Red Hat Enterprise Linux 4 does not provide support for the Datagram Congestion Control Protocol (DCCP), and Red Hat Enterprise Linux 5, which does support DCCP, did not backport the upstream commit that introduced this issue, e77b8363b. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0836.html and https://rhn.redhat.com/errata/RHSA-2011-1253.html. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise Linux MRG as they did not backport the upstream commit cdff08e7 that introduced this issue. Future kernel updates for Red Hat Enterprise Linux 6 may address this flaw. Not vulnerable. This issue did not affect the versions of struts as shipped with Red Hat Enterprise Linux 5, Red Hat Network Satellite 5, JBoss Enterprise Web Server 1, JBoss Enterprise Application Platform 4, JBoss Enterprise Portal Platform 4 and JBoss Operations Network 2. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise 4, 5, 6, and Red Hat Enterprise MRG. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0927.html and https://rhn.redhat.com/errata/RHSA-2011-1189.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Not vulnerable. This issue did not affect the versions of libarchive as shipped with Red Hat Enterprise Linux 4, 5, and 6. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 4, 6, and Red Hat Enterprise MRG. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2011-1065.html. Also, only systems running on x86 architecture with AMD processor and SVM virtualization extension enabled are affected. Not vulnerable. This issue did not affect the versions of ecryptfs-utils as shipped with Red Hat Enterprise Linux 5 or 6. This issue did affect the versions of kernel package as shipped with Red Hat Enterprise Linux 5. This issue did affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. Red Hat cannot backport the fix though as it is too invasive and has a high risk of introducing severe regressions at this point in the Red Hat Enterprise Linux 5 life-cycle. As such, Red Hat recommends that users of KVM on Red Hat Enterprise Linux 5 only use PCI passthrough with trusted guests. This issue did affect the versions of kernel package as shipped with Red Hat Enterprise Linux 6. This issue did not affect the versions of kernel-rt package as shipped with Red Hat Enterprise MRG as it did not provide support for virtualization. For further info please refer to the knowledge base article https://access.redhat.com/knowledge/articles/66747. Not vulnerable. This issue did not affect the versions of bind as shipped with Red Hat Enterprise Linux 4, 5, or 6 as they did not include support for Response Policy Zones (RPZ). This issue did not affect bind packages shipped with Red Hat Enterprise Linux 4 and 5. It affected bind97 packages shipped with Red Hat Enterprise Linux 5 and bind packages shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact. We do not currently plan to fix this flaw in Red Hat Enterprise Linux 4. If more information becomes available at a future date, we may revisit the issue. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG as they did not backport the upstream commit 4a94445c that introduced this issue. The versions of the Linux kernel as shipped with Red Hat Enterprise Linux 4, 6, and Red Hat Enterprise MRG are not affected. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2011-0927.html. Also, only systems running on x86 architecture with Intel processor and VMX virtualization extension enabled are affected. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 4 and 5. It has been addressed in Red Hat Enterprise Linux 5 (php53) and 6 (php). Not vulnerable. This issue did not affect the versions of NetworkManager as shipped with Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 3, 4, 5, or 6, as they do not include the support for the elliptic curve cryptography. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of conga package as shipped with Red Hat Enterprise Linux 5 and with Red Hat Cluster Suite for Red Hat Enterprise Linux 4, as they did not include support for creation of new Plone content. Not Vulnerable. This issue does not affect the version of conga as shipped with Red Hat Enterprise Linux 5 and Red Hat Cluster Suite EL4 Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 4, 5, or 6. This flaw is specific to Wireshark v1.4.5 version. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 4 or 5. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise 4, 5, 6, and Red Hat Enterprise MRG. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0927.html, https://rhn.redhat.com/errata/RHSA-2011-1350.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Not vulnerable. This issue did not affect the versions of struts as shipped with Red Hat Enterprise Linux 5, Red Hat Network Satellite 5, JBoss Enterprise Web Server 1, JBoss Enterprise Application Platform 4, JBoss Enterprise Portal Platform 4 and JBoss Operations Network 2. Not vulnerable. This issue did not affect the versions of struts as shipped with Red Hat Enterprise Linux 5, Red Hat Network Satellite 5, JBoss Enterprise Web Server 1, JBoss Enterprise Application Platform 4, JBoss Enterprise Portal Platform 4 and JBoss Operations Network 2. Not vulnerable. This issue did not affect the versions of openswan as shipped with Red Hat Enterprise Linux 5 or 6. This issue did not affect the version of wireshark as shipped with Red Hat Enterprise Linux 4 and 5. We do not currently plan to fix this issue due to the lack of further information about the flaw and its impact. If more information becomes available at a future date, we may revisit the issue. Not vulnerable. This issue did not affect the version of libvirt as shipped with Red Hat Enterprise Linux 5 and 6 as we did not backport upstream commit d6623003. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not provide support for the Windows Logical Disk Manager. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG do not provide support for KSM (Kernel Samepage Merging). This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2011-1189.html. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG as they did not backport the upstream commit 47a150edc2a that introduced this issue. Not vulnerable. This issue did not affect the versions of xscreensaver as shipped with Red Hat Enterprise Linux 4. This did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not include support for Network Namespaces. A future kernel update in Red Hat Enterprise MRG may address this issue. The risks associated with fixing this flaw outweigh the benefits of the fix, therefore Red Hat does not plan to fix this flaw in Red Hat Enterprise Linux 6. Not vulnerable. The Red Hat Security Response Team has reviewed this bug and determined it has no security impact on the tftp packages as shipped with Red Hat Enterprise Linux 4, 5, and 6. Refer to the following bugzilla for additional details: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-2199 This issue did not affect the versions of Linux kernel as shipped in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as they did not provide support for the Hierarchical File System (HFS). This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2011-1479.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not provide support for the Alpha architecture. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not provide support for the Alpha architecture. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not provide support for the Alpha architecture. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not provide support for the Alpha architecture. This issue only affects Red Hat Enterprise Linux 6. The version of the qemu/kvm as shipped with Red Hat Enterprise Linux 5 is not affected because it does not provide support for indirect descriptors. This issue affects the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0927.html, https://rhn.redhat.com/errata/RHSA-2011-1189.html and https://rhn.redhat.com/errata/RHSA-2011-1253.html. Not vulnerable. This issue affects the GlassFish Server Administration Console, which is not shipped with any Red Hat products. Not Vulnerable. This issue did not affect the version of Firefox as shipped with Red Hat Enterprise Linux 4, 5 or 6. Not vulnerable. This issue did not affect the versions of bind as shipped with Red Hat Enterprise Linux 4, 5, or 6 as they did not include support for Response Policy Zones (RPZ). Red Hat currently does not plan to address this issue. For details refer to: https://bugzilla.redhat.com/show_bug.cgi?id=700883#c18 Red Hat currently does not plan to address this issue. For details refer to: https://bugzilla.redhat.com/show_bug.cgi?id=700883#c18 Red Hat currently does not plan to address this issue. For details refer to: https://bugzilla.redhat.com/show_bug.cgi?id=700883#c18 The versions of the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG are not affected because they do not provide support for THP (Transparent Huge Pages). This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2011-0928.html. This issue did not affect any version of Tomcat shipped in Red Hat products. This flaw only affected Tomcat versions 7.0.0 - 7.0.16. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not backport the upstream commit 3ab224be6d6. It did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 6, and Red Hat Enterprise MRG as they have backported the upstream commit ea2bc483ff5 that Red Hat Enterprise Linux 5 did not. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2011-1212.html. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not provide support for the Taskstats interface. This was fixed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1386.html, https://rhn.redhat.com/errata/RHSA-2011-1350.html and https://rhn.redhat.com/errata/RHSA-2011-1253.html. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This flaw affects Apache CXF (WSS4J) and jbossws-native as shipped with various JBoss products. It does not affect JBoss Enterprise Application Platform 6 and JBoss Application Server 7.1.1 and above. These products include WSS4J 1.6.5, which incorporates a fix for this flaw. On affected products, this flaw can be mitigated by using the RSA-OAEP key wrap algorithm, instead of the default RSA-v1.5 algorithm. To use RSA-OAEP, edit the jboss-ws-security configuration file and add the property keyWrapAlgorithm="rsa_oaep" to the encrypt element. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG. It has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-0927.html, https://rhn.redhat.com/errata/RHSA-2011-1189.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG as they did not backport the upstream commit 66e61a9e that introduced this issue. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not include support for EXT4 filesystem. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not provide support for the Taskstats interface. This has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1479.html, https://rhn.redhat.com/errata/RHSA-2011-1465.html, and https://rhn.redhat.com/errata/RHSA-2012-0010.html. This has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1212.html, https://rhn.redhat.com/errata/RHSA-2011-1189.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not backport the upstream commit 5dee9e7c that introduced this issue. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1189.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG as they did not backport the upstream commit a63d83f4 that introduced this issue. This issue did not affect the versions of nfs-utils as shipped with Red Hat Enterprise Linux 4 and 5. The Red Hat Security Response Team has rated this issue as having low security impact; a future update in Red Hat Enterprise Linux 6 may address this flaw. This issue only affects Red Hat Enterprise Linux 6. The version of the qemu/kvm as shipped with Red Hat Enterprise Linux 5 is not affected. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not provide support for the Linux wireless LAN (802.11) configuration API. This has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1212.html, https://rhn.redhat.com/errata/RHSA-2011-1189.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not provide support for the TOMOYO Linux, Mandatory Access Control (MAC) implementation. This issue only affects Red Hat Enterprise Linux 5. The versions of the Linux kernel-xen as shipped with Red Hat Enterprise Linux 4, 6, and Red Hat Enterprise MRG are not affected. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2011-1212.html. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG as they did not backport the upstream commit 41bf498 that introduced the issue. This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2011-1350.html. Not vulnerable. This issue did not affect the versions of vsftpd as shipped with Red Hat Enterprise Linux 3, 4, 5, or 6. This flaw affects Red Hat Enterprise Linux 4 and 5. It did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as they have already backported the upstream commit 53b0f080 that addressed this flaw. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2011-1065.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Future qemu-kvm updates in Red Hat Enterprise Linux 6 may address this flaw. This issue did not affect the versions of qemu-kvm as shipped with Red Hat Enterprise Linux 5 as it did not include support for "run as" functionality. This issue is compile-time only and does not affect binary dbus packages, shipped in Red Hat Enterprise Linux 5 and 6. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 5 and 6. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not have support for ipt_CLUSTERIP. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via http://rhn.redhat.com/errata/RHSA-2011-0833.html, http://rhn.redhat.com/errata/RHSA-2011-0498.html, and http://rhn.redhat.com/errata/RHSA-2011-0500.html. This issue did not affect the version of wireshark as shipped with Red Hat Enterprise Linux 4 and 5. Not vulnerable. This issue did not affect the versions of openoffice.org and openoffice.org2 packages as shipped with Red Hat Enterprise Linux 4, and the versions of openoffice.org packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and Red Hat Enterprise MRG as they did not provide support for the Global File System 2 (GFS2). This has been addressed in Red Hat Enterprise Linux 5 and 6 via https://rhn.redhat.com/errata/RHSA-2011-1065.html and https://rhn.redhat.com/errata/RHSA-2011-1189.html. Not vulnerable. This issue did not affect the versions of libpng as shipped with Red Hat Enterprise Linux 4, 5, or 6. This issue was found to be a duplicate of CVE-2011-2521. CVE-2011-2521 issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG as they did not backport the upstream commit 41bf498 that introduced the issue. This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2011-1350.html. This has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1386.html, https://rhn.redhat.com/errata/RHSA-2011-1189.html, and https://rhn.redhat.com/errata/RHSA-2011-1253.html. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not include support for EXT4 filesystem. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise MRG as it has backported the fix that addresses this issue. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This has been addressed in Red Hat Enterprise Linux 5 and 6 via https://rhn.redhat.com/errata/RHSA-2011-1386.html and https://rhn.redhat.com/errata/RHSA-2011-1465.html. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not provide support for the Si4713 I2C device. Not vulnerable. This issue did not affect the versions of freeradius as shipped with Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. This issue did not affect the versions of glibc as shipped with Red Hat Enterprise Linux 3, 4, 5, or 6. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and Red Hat Enterprise MRG as they did not provide support for the Xtensa processor architecture. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue results in an OOB read which is not exploitable for arbitrary code execution and can simply cause a crash. We do not consider this as a security issue. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not backport the upstream commit a5b1cf28 that introduced this issue. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1386.html, https://rhn.redhat.com/errata/RHSA-2011-1350.html, and https://rhn.redhat.com/errata/RHSA-2012-0010.html. The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat does not consider this flaw to be a security issue. The flags argument passed to the bsd_glob() function is solely under the control of the script author. This flaw was originally reported as resulting in information disclosure only, and was therefore assessed as having low security impact. On this basis, it was planned that future updates to JBoss products may address this flaw. New research [0] has now shown that this flaw can lead to remote code execution. The security impact has been re-assessed as important, and Red Hat is now working on patches for all affected products. [0] http://danamodio.com/application-security/discoveries/spring-remote-code-with-expression-language-injection/ Not vulnerable. This issue affects the Spring Security package, which is not shipped with any Red Hat products. Not vulnerable. This issue affects the Spring Security package, which is not shipped with any Red Hat products. The default configurations shipped in Red Hat Enterprise Linux 6 and Red Hat Software Collections are not vulnerable to to this flaw. The UserDir option needs to be enabled as well as AllowOverride being set to values other than "None" for this to potentially pose a threat. This issue does not affect the version of libxml2 package as shipped with Red Hat Enterprise Linux 4 and 5. Vulnerable. This issue affects the versions of cups as shipped with Red Hat Enterprise Linux 4, 5, and 6. The Red Hat Security Response Team has rated this issue as having moderate security impact for the cups package. A future update may address this issue in the cups package for Red Hat Enterprise Linux 4, 5, and 6. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not backport the upstream commit 393e52e3 that introduced this flaw. This has been addressed in Red Hat Enterprise Linux 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1350.html and https://rhn.redhat.com/errata/RHSA-2012-0010.html. The versions of the Linux kernel as shipped with Red Hat Enterprise Linux 4, 6, and Red Hat Enterprise MRG are not affected. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2011-1212.html. This issue did not affect Red Hat Enterprise Linux 4 and 5 as they did not include support for perf. This did not affect Red Hat Enterprise MRG as it uses the perf package from Red Hat Enterprise Linux 6. This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2011-1465.html. Not a security issue as privileges equal to root are needed. This issue did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG as they did not provide support for the Comedi drivers. This issue did not affect Red Hat Enterprise Linux 4 and 5 as they did not include support for perf. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1350.html and https://rhn.redhat.com/errata/RHSA-2012-0333.html. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG as they did not provide support for the BeOS file system. Not vulnerable. This issue did not affect the versions of stunnel as shipped with Red Hat Enterprise Linux 4, 5, or 6. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4, 6, and Red Hat Enterprise MRG. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2011-1386.html. Not vulnerable. This issue did not affect the versions of pidgin as shipped with Red Hat Enterprise Linux 4, 5, or 6 as they contained a version of pidgin that did not support /who IRC protocol command. Not vulnerable. This issue did not affect the versions of firefox as shipped with Red Hat Enterprise Linux 5 or 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw in Red Hat Enterprise Linux 4 and 5. Not Vulnerable. This issue does not affect the version of webkitgtk as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of webkitgtk as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of webkitgtk as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of webkitgtk as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of webkitgtk as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of webkitgtk as shipped with Red Hat Enterprise Linux 6. This issue affects the version of webkitgtk as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of webkitgtk as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of webkitgtk as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of webkitgtk as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of webkitgtk as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of webkitgtk as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of webkitgtk as shipped with Red Hat Enterprise Linux 6. This issue affects the version of webkitgtk as shipped with Red Hat Enterprise Linux 6. The versions of the Linux kernel as shipped with Red Hat Enterprise Linux 4, 6, and Red Hat Enterprise MRG are not affected. It has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2011-1386.html. Not affected. This flaw was introduced in CUPS due to an incomplete fix for CVE-2011-2896, which was not applied to any CUPS packages in Red Hat Enterprise Linux. Red Hat does not consider this flaw to be a security issue. It is improbable that a script would accept untrusted user input or unvalidated script input data and use it to malloc memory, without filtering/sanitizing it, therefore the value used to malloc memory is under the the full control of the script author and no trust boundary is crossed. Red Hat does not consider this to be a security flaw. As a malicious MSN server is needed, there are far worlse implications to a user connecting to an untrusted server than a DoS. This issue affects the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG. It has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1386.html, https://rhn.redhat.com/errata/RHSA-2011-1465.html, and https://rhn.redhat.com/errata/RHSA-2012-0010.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 4, 5, or 6. This issue affects the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG. It has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1386.html, https://rhn.redhat.com/errata/RHSA-2011-1465.html, and https://rhn.redhat.com/errata/RHSA-2012-0010.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Before updated packages are deployed, users can deploy configuration changes to mitigate this flaw: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-3192#c18 This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 4 and 5, openssl096b as shipped with Red Hat Enterprise Linux 4, openssl097a as shipped with Red Hat Enterprise Linux 5, or openssl098e as shipped with Red Hat Enterprise Linux 6. This issue did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4, 6, and Red Hat Enterprise MRG, as they either do not have the sample_to_timespec() function, or have already backported upstream commit f8bd2258, which addresses this issue. It was addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2011-1386.html. Not vulnerable. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 3, 4, 5, or 6, as they do not include the support for the elliptic curve cryptography. This issue did not affect the versions of the Xen package as shipped with Red Hat Enterprise Linux 4 and 6. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2011-0496.html. This issue does not affect the version of wireshark shipped with Red Hat Enterprise Linux 4, 5 and 6. Not Vulnerable. This issue did not affect the version of php shipped with Red Hat Enterprise Linux 6. This issue did not affect the version of php53 shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 4, 5, or 6. This issue did not affect the version of php53 as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of libpng as shipped with Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5 as they did not include the upstream commit that introduced this issue. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6, and Red Hat Enterprise MRG as they did not provide support for the Infiniband Sockets Direct Protocol (SDP). This issue only affects qemu as shipped with Red Hat Enterprise Linux 5 xen packages. The versions of the qemu/kvm as shipped with Red Hat Enterprise Linux 5 are not affected. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2011-1386.html. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not include support for ServerEngines' 10Gbps network adapter - BladeEngine. This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2011-1530.html. A future kernel update in Red Hat Enterprise MRG may address this issue. This issue did not affect the versions of httpd as shipped with Red Hat Enterprise Linux 4 and 5 as this flaw was introduced in version 2.2.12. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 as they did not provide support for FUSE. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 as they did not backport the upstream commit 3b463ae0c6264f that introduced this issue. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1465.html and https://rhn.redhat.com/errata/RHSA-2012-0010.html. Not vulnerable. This issue did not affect the versions of evolution as shipped with Red Hat Enterprise Linux 4, 5, or 6. This issue did not affect the version of evolution28 as shipped with Red Hat Enterprise Linux 4. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not provide support for Broadcom 43xx wireless devices. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1465.html, and https://rhn.redhat.com/errata/RHSA-2012-0010.html. Not Vulnerable. This issue does not affect the version of wireshark shipped with Red Hat Enterprise Linux 4, 5 or 6. This issue affects the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1479.html, https://rhn.redhat.com/errata/RHSA-2011-1465.html, and https://rhn.redhat.com/errata/RHSA-2012-0010.html. Not vulnerable. This issue did not affect the versions of NetworkManager as shipped with Red Hat Enterprise Linux 4 or 5 as they did not include support for writing NetworkManager configurations to the standard /etc/sysconfig/network-scripts/ifcfg-* files. Not affected. This flaw did not affect any version of Tomcat shipped in Red Hat products. This flaw only affected Tomcat versions 7.0.0 - 7.0.21. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 4, 5, or 6. Red Hat is aware of, and tracking, the Rizzo/Duong chosen plain text attack on SSL/TLS 1.0, also known as "BEAST". This issue has been assigned CVE-2011-3389. This attack uses web browser extensions to exploit a weakness in SSL/TLS cipher-block chaining (CBC), allowing a man-in-the-middle attacker to recover certain session information, such as cookie data, from what should be a secure connection. The research shows two ways that an attacker could mount an attack. In both cases the attacker needs access to the data stream from the web browser to the server while a user visits a malicious website using a browser. The attacker may then be able to determine a portion of the data the browser sends to the server by making a large number of requests over a period of time. This data could include information such as an authentication cookie. The first method of attack involves using WebSockets. Currently, Red Hat does not ship any products that allow an attack using WebSockets to be successful. We are planning to update Firefox to version 7, which contains protections in the WebSocket code that prevents this particular attack from being effective. The second method of attack involves using a malicious Java applet. In order for the attack to be successful, the attacker would need to circumvent the Same Origin Policy (SOP) controls in Java. The researchers claim to have found a flaw in the Java SOP and we will issue updates to correct this flaw as suitable fixes are available. We are in contact with various upstream projects regarding this attack. As a precautionary measure, we plan to update the Network Security Services (NSS), GnuTLS, and OpenSSL packages as suitable fixes are available. We will continue to track this issue and take any appropriate actions as needed. This statement and any updates to it is available at: https://bugzilla.redhat.com/show_bug.cgi?id=737506 Not vulnerable. This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 4, 5, and 6. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 4, 5, or 6. Oracle OpenSSO is provided as part of the opensso quickstart example application shipped with JBoss Enterprise SOA Platform 5. The CVE-2011-3506, CVE-2011-3517, and CVE-2012-0079 flaws are not exposed unless the opensso quickstart example application is deployed, or you have created and deployed a custom application that is packaged with a copy of Oracle OpenSSO as provided by the opensso quickstart. The opensso quickstart has been removed in JBoss Enterprise SOA Platform 5.3.0 to address these flaws. Users interested in continuing to receive updates for their custom applications using Oracle OpenSSO are advised to contact Oracle as Red Hat is no longer supporting OpenSSO. Oracle OpenSSO is provided as part of the opensso quickstart example application shipped with JBoss Enterprise SOA Platform 5. The CVE-2011-3506, CVE-2011-3517, and CVE-2012-0079 flaws are not exposed unless the opensso quickstart example application is deployed, or you have created and deployed a custom application that is packaged with a copy of Oracle OpenSSO as provided by the opensso quickstart. The opensso quickstart has been removed in JBoss Enterprise SOA Platform 5.3.0 to address these flaws. Users interested in continuing to receive updates for their custom applications using Oracle OpenSSO are advised to contact Oracle as Red Hat is no longer supporting OpenSSO. Not vulnerable. This issue affects the GlassFish Web Container component. This component is not shipped with any Red Hat products. JBoss Web and Tomcat provide the web container used in all JBoss products. Not vulnerable. This issue did not affect the versions of conga as shipped with Red Hat Cluster Suite for Red Hat Enterprise Linux 4 and 5. This issue did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4, 5, and Red Hat Enterprise MRG. It affects the Linux kernel as shipped with Red Hat Enterprise Linux 6 due to incorrect backporting of upstream patches. A future kernel update in Red Hat Enterprise Linux 6 may address this issue. Not vulnerable. This issue did not affect the version of pidgin as shipped with Red Hat Enterprise Linux 6 as it explicitly disables support for the SILC protocol. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not Vulnerable. This issue does not affect the version of radvd package as shipped with Red Hat Enterprise Linux 4, 5 and 6. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. A failure in privsep_init() does not cause radvd to run with full root privileges when invoked with the --username option specifying an unprivileged user. Rather it will run as a single process as the specified (unprivileged) radvd user, causing this issue to have no security impact (no unintended privilege elevation). The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw in radvd. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw in radvd. Not vulnerable. This issue only affects community JBoss AS 7 prior to 7.1.0 Beta 1. It does not affect components shipped with any Red Hat products. Not vulnerable. This issue only affects community JBoss AS 7 prior to 7.1.0 Beta 1. It does not affect components shipped with any Red Hat products. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG as they did not provide support for the AppArmor security module. This flaw only affects the clustered implementation in qpid-cpp (qpidd-cpp-server-cluster) which is only available in Red Hat Enterprise MRG. The qpid-cpp-server as provided with Red Hat Enterprise Linux 6 does not include this functionality, and is thus not affected. This issue does not affect the version of hardlink, as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw in hardlink. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw in hardlink. This issue did not affect the version of the Linux kernel as shipped with Red Hat Enterprise Linux 4, and 6 as it did not backport the upstream commit ec6fd8a4 that introduced this issue. This has been addressed in Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2012-0007.html and https://rhn.redhat.com/errata/RHSA-2012-0010.html. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not include support for EXT4 filesystem. It did not affect the Linux kernel as shipped with Red Hat Enterprise MRG as it has backported the upstream commit 667eff35 that addressed this issue. This has been addressed in Red Hat Enterprise Linux 5 and 6 via https://rhn.redhat.com/errata/RHSA-2012-0107.html and https://rhn.redhat.com/errata/RHSA-2011-1530.html. This issue did not affect the version of firefox and thunderbird packages as shipped with Red Hat Enterprise Linux 4, 5 and 6. This issue did not affect the version of seamonkey package as shipped with Red Hat Enterprise Linux 4. This issue did not affect the version of firefox and thunderbird packages as shipped with Red Hat Enterprise Linux 4, 5 and 6. This issue did not affect the version of seamonkey package as shipped with Red Hat Enterprise Linux 4. This issue did not affect the version of firefox and thunderbird packages as shipped with Red Hat Enterprise Linux 4, 5 and 6. This issue did not affect the version of seamonkey package as shipped with Red Hat Enterprise Linux 4. This issue did not affect the version of firefox and thunderbird packages as shipped with Red Hat Enterprise Linux 4, 5 and 6. This issue did not affect the version of seamonkey package as shipped with Red Hat Enterprise Linux 4. This issue did not affect the version of firefox and thunderbird packages as shipped with Red Hat Enterprise Linux 4, 5 and 6. This issue did not affect the version of seamonkey package as shipped with Red Hat Enterprise Linux 4. This issue did not affect the version of firefox and thunderbird packages as shipped with Red Hat Enterprise Linux 4, 5 and 6. This issue did not affect the version of seamonkey package as shipped with Red Hat Enterprise Linux 4. This issue did not affect the version of firefox and thunderbird packages as shipped with Red Hat Enterprise Linux 4, 5 and 6. This issue did not affect the version of seamonkey package as shipped with Red Hat Enterprise Linux 4. This issue affects the version of libxml2 as shipped with Red Hat Enterprise Linux 4, 5 and 6 and has been addressed via RHSA-2012:0016, RHSA-2012:0017 and RHSA-2012:0018 respectively. This issue affects the version of mingw32-libxml2 as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this issue in Red Hat Enterprise Linux 6. This issue affected the versions of libxml2 as shipped with Red Hat Enterprise Linux 4, 5 and 6 and has been addressed via RHSA-2012:0016, RHSA-2012:0017 and RHSA-2012:0018 respectively. This issue does not affect the version of qt as shipped with Red Hat Enterprise Linux 4 and 5. This issue does not affect the version of qt3 as shipped with Red Hat Enterprise Linux 6. This issue does not affect the version of qt4 as shipped with Red Hat Enterprise Linux 5. This issue affects the version of qt as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having moderate security impact. A future update may address this issue. This issue does not affect the version of pango as shipped with Red Hat Enterprise Linux 4, 5 and 6. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. Not vulnerable. This issue did not affect the versions of libvorbis as shipped with Red Hat Enterprise Linux 4, 5, and 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw in libxslt. Not vulnerable. This issue did not affect the versions of conga as shipped with Red Hat Cluster Suite for Red Hat Enterprise Linux 4 and as shipped with Red Hat Enterprise Linux 5 as they did not include support for CMFEditions. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not include support for XFS filesystem. This has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2012-0007.html, https://rhn.redhat.com/errata/RHSA-2012-0350.html, and https://rhn.redhat.com/errata/RHSA-2012-0333.html. The Red Hat Security Response Team does not consider this to be a security issue. For additional information, refer to: https://bugzilla.redhat.com/show_bug.cgi?id=749324#c1. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Future kernel updates in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG may address this flaw. This issue did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4, and 5 as they did not include support for the GHASH message digest algorithm. This has been addressed in Red Hat Enterprise Linux 6, and MRG via https://rhn.redhat.com/errata/RHSA-2012-0350.html, and https://rhn.redhat.com/errata/RHSA-2012-0010.html. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2012-0107.html, https://rhn.redhat.com/errata/RHSA-2012-0571.html, and https://rhn.redhat.com/errata/RHSA-2012-0670.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Not vulnerable. This issue did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4, 5, and 6 as they did not backport the upstream commit 462fb2af that introduced this issue. It did not affect the Linux kernel as shipped with Red Hat Enterprise MRG as it has already backported the upstream patches f8e9881c, 66944e1c, c65353da, and 10949550 that addressed this issue. Not vulnerable. This issue did not affect the versions of bzip2 as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include the bzexe executable. This issue did not affect the versions of squid as shipped with Red Hat Enterprise Linux 4 and 5 as they did not include IPv6 support. This issue was introduced with the addition of IPv6 support in Squid 3.1 (in the changes made to the idnsGrokReply function). This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and 6 as they did not backport the upstream commit f755a04 that introduced this. This has been addressed in Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2012-0333.html. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 4, 5 and 6, as they did not include support for the CSN.1 dissector. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 4, 5 and 6. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 4 as they do not include support for DTLS protocol. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 4 and 6. This issue affects the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG. This has been addressed in Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1479.html, https://rhn.redhat.com/errata/RHSA-2011-1530.html, and https://rhn.redhat.com/errata/RHSA-2012-0010.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This issue does not affect versions of kvm package as shipped with Red Hat Enterprise Linux 5. Red Hat Security Response team does not consider this bug to be security relevant one due to the privileges required to exploit this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2012-0107.html, https://rhn.redhat.com/errata/RHSA-2011-1849.html, and https://rhn.redhat.com/errata/RHSA-2012-0333.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This issue does not affect the version of gnutls as shipped with Red Hat Enterprise Linux 4. This issue does not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4 as it does not provide support for NFS ACLs. This issue does not affect the Linux kernel as shipped with Red Hat Enterprise Linux 5. This has been addressed in Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2012-0333.html. Future kernel updates in Red Hat Enterprise Linux 6 may address this issue. This issue affects the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG. This has been addressed in Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2012-0007.html, https://rhn.redhat.com/errata/RHSA-2012-0350.html, and https://rhn.redhat.com/errata/RHSA-2012-0010.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. Not vulnerable. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 4, 5 or 6. This issue does affect Red Hat Enterprise Virtualization 2 and 3. Red Hat Enterprise Virtualization 2 is now in Production 2 phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Virtualization Life Cycle: https://access.redhat.com/support/policy/updates/rhev/. This issue did not affect the versions of httpd as shipped with Red Hat Enterprise Linux 4 and 5 due to differences in apr-util's apr_uri_parse() implementation. This issue did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as they did not have the vulnerable code as introduced in history:1a7bc914. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2012-0007.html. Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle, https://access.redhat.com/support/policy/updates/errata/, therefore the fix for this issue is not currently planned to be included in the future updates. This issue did not affect the version of the Linux kernel as shipped with Red Hat Enterprise Linux 4, 6 and Red Hat Enterprise MRG. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2012-0007.html. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not provide support for UDP Fragmentation Offload (UFO) functionality. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2011-1465.html, and https://rhn.redhat.com/errata/RHSA-2012-0010.html. Not vulnerable. This issue did not affect the versions of openssh as shipped with Red Hat Enterprise Linux 4, 5, and 6, as they use a built-in entropy pool to generate and retrieve entropy information when performing host-based authentication. This issue did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as they did not include support for the Hierarchical File System (HFS) file system. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2012-0007.html. Not vulnerable. This issue affects the MyFaces 2 package, which is not shipped with any Red Hat products. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and Red Hat Enterprise MRG as they did not provide support for the KVM subsystem. This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2012-0350.html. A future kvm update in Red Hat Enterprise 5 may address this flaw. This issue did not affect the version of the Linux kernel as shipped with Red Hat Enterprise Linux 4, 6 and Red Hat Enterprise MRG as they were not vulnerable to CVE-2011-2482. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2012-0007.html. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 3, 4, 5, or 6 as they did not include support for the ECDH or ECDHE ciphers. Not vulnerable. This issue affects the Mojarra 2 package, which is not shipped with any Red Hat products. Not vulnerable. This issue did not affect the versions of system-config-printer as shipped with Red Hat Enterprise Linux 4, 5, or 6 as they did not include support for installing driver packages from the OpenPrinting database, only PPDs (with user consent). The ASF Security Team does not consider resource exhaustion caused by .htaccess files to be a security defect. The Red Hat Security Response Team agrees with their assessment and so does not consider this to be a security flaw. The Red Hat Security Response Team has rated this issue as having Low security impact for the jetty-eclipse package in Red Hat Enterprise Linux 6. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of dhcp as shipped with Red Hat Enterprise Linux 4 and 5. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 3, 4 and 5. This issue affects the versions of the acpid package, as shipped with Red Hat Enterprise Linux 4, 5, and 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw in acpid. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5 and Red Hat Enterprise MRG as they did not provide support for the sendmmsg syscall. This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2012-0350.html. This issue affect Red Hat Enterprise Linux 6 and has been addressed via https://rhn.redhat.com/errata/RHBA-2012-0013.html. Red Hat Enterprise Linux 5 is not affected. The Red Hat Security Response Team has rated this issue as having low security impact. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the version of pidgin as shipped with Red Hat Enterprise Linux 6 as it explicitly disables support for the SILC protocol. Not vulnerable. This issue did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG as they did not include support for the BATMAN (Better Approach To Mobile Ad-hoc Networking) out-of-tree kernel module. This issue did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4 and 5 as they did not have support for Performance event. It did not affect Red Hat Enterprise MRG as it did not provide support for PowerPC. This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2012-0350.html. This issue does not affect Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and Red Hat Enterprise MRG as they did not provide support for the KVM subsystem. It has been addressed in Red Hat Enterprise 5 and 6 via https://rhn.redhat.com/errata/RHSA-2012-0051.html and https://rhn.redhat.com/errata/RHSA-2012-0350.html. We do not currently plan to fix this issue due to the lack of further information about the flaw and its impact. If more information becomes available at a future date, we may revisit the issue. We do not currently plan to fix this issue due to the lack of further information about the flaw and its impact. If more information becomes available at a future date, we may revisit the issue. This issue affects the version of php and php53 as shipped with Red Hat Enterprise Linux 5. This issue affects the version of php as shipped with Red Hat Enterprise Linux 6 and 7. The Red Hat Security Response Team has rated this issue as having moderate security impact. This issue is not currently planned to be addressed in future updates. This issue may be mitigated with user code changes as noted in https://wiki.php.net/rfc/strict_sessions#current_solution A buffer overflow flaw was found in the MIT krb5 telnet daemon (telnetd) as shipped with all supported versions of Red Hat Enterprise Linux. A remote attacker who can access the telnet port of a target machine could use this flaw to execute arbitrary code as root. While we are aware of public exploits for this issue that include targets for Red Hat Enterprise Linux 3, we are not aware of any yet which would be successful in gaining arbitrary root code execution in Red Hat Enterprise Linux 4, 5, or 6. However it is plausible that one could be created to do so. Note that the krb5 telnet daemon is not enabled by default in any version of Red Hat Enterprise Linux. In addition, the default firewall rules block remote access to the telnet port. This flaw does not affect the telnet daemon distributed in the telnet-server package. For users who have enabled the krb5 telnet daemon and have it accessible remotely, they should disable it or apply the updates we have released. Since same encryption code is shared between the MIT krb5 telnet daemon and the telnet client, this issue affects the telnet client as well. The updates we have released fixes the issue for both, the telnet daemon and the telnet client. Not vulnerable. This issue did not affect the versions of dhcp as shipped with Red Hat Enterprise Linux 4, 5, and 6 as they did not include support for enhanced DDNS logging. Not vulnerable. Apache ActiveMQ is not shipped with any supported Red Hat products. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, or Red Hat Enterprise MRG. Red Hat does not provide support for the ROSE protocol. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, 6, or Red Hat Enterprise MRG. Red Hat does not provide support for the ROSE protocol. The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this issue in Red Hat Enterprise Linux 4 or 5 (it has been addressed in Red Hat Enterprise Linux 6). For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not Vulnerable. This issue does not affect the version of pidgin as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the version of polkit as shipped with Red Hat Enterprise Linux 6 as it did not include the upstream commit 763faf434b445c20ae9529100d3ef5290976d0c9 that introduced this issue. This issue did not affect the version of cobbler as shipped with Red Hat Network Satellite Server 5.4 as Red Hat Network Satellite Server did not include support for Cobbler web interface. This issue did not affect the version of cobbler as shipped with Red Hat Network Satellite Server 5.4 as it did not include the upstream commit d7b30b5fca5097c544ca37ade8c945a3106b1896 that introduced this flaw. This issue did not affect the version of cobbler as shipped with Red Hat Network Satellite Server 5.4 as it did not include the upstream commit be4fc806637cf8cec275fea80b892182879580eb that introduced this flaw. The Red Hat Security Response Team has rated this issue as having moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the version of memcached as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This issue affects the GlassFish Web Container component. This component is not shipped with any Red Hat products. JBoss Web and Tomcat provide the web container used in all JBoss products. Not Vulnerable. This issue does not affect the versions of struts as shipped with various Red Hat products. This issue affects the versions of nss in Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Low security impact. We currently have no plans to fix this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification This issue was addressed in Red Hat Enterprise Linux 5 openssl packages via RHBA-2011:1010, bug 698175. It did not affect openssl packages shipped with Red Hat Enterprise Linux 6. This bug is not a security issue. For detailed explanation, refer to: https://bugzilla.redhat.com/show_bug.cgi?id=853321#c4 Not Vulnerable. This issue did not affect the version of tetex as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of t1lib and evince as shipped with Red Hat Enterprise Linux 6. Because the advisory released to fix CVE-2010-2642 completely resolved the problem without introducing this flaw. Not vulnerable. This issue did not affect the pacemaker packages shipped by Red Hat as the packages are not built in the /tmp/ directory. This issue affects the version of glibc package as shipped with Red Hat Enterprise Linux 5 and 6. Red Hat Product Security has rated this issue as having Low security impact. A future update in Red Hat Enterprise Linux 6 may address this issue. This issue did not affect the versions of glibc as shipped with Red Hat Enterprise Linux 7. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 7 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6. Future kernel updates for Red Hat Enterprise Linux 6 may address this issue. Not vulnerable. This issue did not affect the versions of httpd as shipped with Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 3, 4, 5 and 6, as they did not include GOST engine support. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not have support for robust futexes. It did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as they have the backported fixes. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2012-0107.html. Not vulnerable. This issue did not affect the versions of emacs as shipped with Red Hat Enterprise Linux 4, 5 or 6 as they did not include support for CEDET. Not vulnerable. This issue did not affect the versions of curl as shipped with Red Hat Enterprise Linux 4, 5 or 6. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not have support for the XFS file system. It did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 5 as it did not backport the upstream commit ef14f0c1 that introduced the vulnerability. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2012-0350.html, and https://rhn.redhat.com/errata/RHSA-2012-0333.html. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 4, 5 and 6. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not backport commit 884840aa that introduced this issue. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 4 and Red Hat Enterprise MRG as they did not provide support for the KVM subsystem. This issue did not affect the versions of kvm as shipped with Red Hat Enterprise Linux 5 as they did not include support for syscall instruction emulation. This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2012-0350.html. Not vulnerable. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 3, 4, 5, and 6. This issue affects httpd packages as shipped with Red Hat Enterprise Linux 3 and 4, which are now in the Extended Life Phase of their life cycle. Therefore this issue is not planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ Not vulnerable. This issue did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4, 5, 6, and Red Hat Enterprise MRG as they did not provide support for overlayfs. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as it did not backport the upstream commit 198214a7ee. This has been addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2012-0052.html and https://rhn.redhat.com/errata/RHSA-2012-0061.html. For more information, please read https://access.redhat.com/kb/docs/DOC-69129. Not vulnerable. This issue did not affect versions of xorg-x11 as shipped with Red Hat Enterprise Linux 4. This issue did not affect versions of xkeyboard-config as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of usbmuxd as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 4, 5, and 6. Oracle OpenSSO is provided as part of the opensso quickstart example application shipped with JBoss Enterprise SOA Platform 5. The CVE-2011-3506, CVE-2011-3517, and CVE-2012-0079 flaws are not exposed unless the opensso quickstart example application is deployed, or you have created and deployed a custom application that is packaged with a copy of Oracle OpenSSO as provided by the opensso quickstart. The opensso quickstart has been removed in JBoss Enterprise SOA Platform 5.3.0 to address these flaws. Users interested in continuing to receive updates for their custom applications using Oracle OpenSSO are advised to contact Oracle as Red Hat is no longer supporting OpenSSO. Not vulnerable. According to the upstream report, this flaw affects MySQL 5.5.x, which is not provided in Red Hat Enterprise Linux 4, 5, or 6. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not backport the upstream commit 5b7c8406. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6, and Red Hat Enterprise MRG, as those versions have a guard page between the end of the user-mode accessible virtual address space and the beginning of the non-canonical area due to CVE-2005-1764 fix, and hardened system call handler due to CVE-2006-0744 fix. This issue did affect the versions of Xen hypervisor as shipped with Red Hat Enterprise Linux 5. A kernel-xen update for Red Hat Enterprise Linux 5 is available to address this flaw. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5 as we did not have support for sysenter and compat (32bit) version of syscall instructions for PV guests running on the Xen hypervisor (introduced in upstream changeset 16207:aeebd173c3fa). This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of gnutls as shipped with Red Hat Enterprise Linux 4, 5 and 6 as they did not include support for DTLS. Not Vulnerable. This issue does not affect the versions of struts as shipped with various Red Hat products. Not Vulnerable. This issue does not affect the versions of struts as shipped with various Red Hat products. Not Vulnerable. This issue does not affect the versions of struts as shipped with various Red Hat products. Not Vulnerable. This issue does not affect the versions of struts as shipped with various Red Hat products. Not vulnerable. This issue did not affect the versions of firefox as shipped with Red Hat Enterprise Linux 4, 5, or 6. Not Vulnerable. These issues do not affect the versions of firefox and thunderbird package, as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. According to the upstream report, this flaw affects MySQL 5.5.x, which is not provided in Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. According to the upstream report, this flaw affects MySQL 5.5.x, which is not provided in Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. According to the upstream report, this flaw affects MySQL 5.5.x, which is not provided in Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. According to the upstream report, this flaw affects MySQL 5.5.x, which is not provided in Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. According to the upstream report, this flaw affects MySQL 5.5.x, which is not provided in Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. According to the upstream report, this flaw affects MySQL 5.5.x, which is not provided in Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. According to the upstream report, this flaw affects MySQL 5.5.x, which is not provided in Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. According to the upstream report, this flaw affects MySQL 5.5.x, which is not provided in Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. According to the upstream report, this flaw affects MySQL 5.5.x, which is not provided in Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. This issue affects the Java Update mechanism which is only available on the Microsoft Windows platform. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6, since MySQL packages in Red Hat Enterprise Linux are linked against OpenSSL, and not against yaSSL. Not vulnerable. Upstream notes this issue only affected MySQL 5.5.x. Red Hat Enterprise Linux 5 and 6 include MySQL versions 5.0.x and 5.1.x respectively, which are not listed as affected. On Red Hat Enterprise Linux 5.10, new MySQL 5.5 packages are available which are not vulnerable to this issue. Future updates for MySQL 5.0 will no longer be made available (mysql-5.0.* and related packages); security advisories will be provided only for MySQL 5.5. Please refer to https://rhn.redhat.com/errata/RHEA-2013-1330.html for further information. The Red Hat Security Response Team has rated this issue as having low security impact. Trousers is only useful on systems with TPM hardware, additionally local access is required to exploit of this issue. Exploitation of this issue only results in a crash of the tcsd daemon which can be restarted. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat does not consider this flaw to be a security issue. The bug can only be triggered by the PHP script author, which does not cross trust boundary. Not Vulnerable. This issue only affects Apache CXF 2.4.5 and 2.5.1. Earlier versions were not affected and later versions include a fix for this issue. This issue does not affect the versions of Apache CXF as shipped with various Red Hat products. Not vulnerable. This issue did not affect the versions of sudo as shipped with Red Hat Enterprise Linux 4, 5, or 6 as they did not include the vulnerable debugging support. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and 6. This has been addressed in Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2012-0333.html. This issue did not affect the versions of openssh as shipped with Red Hat Enterprise Linux 4 and 5. On Red Hat Enterprise Linux 6, configured forced commands are returned in the debugging output for the key that is used when logging in. Not vulnerable. This issue did not affect the versions of samba as shipped with Red Hat Enterprise Linux 4, 5, and 6. This issue did not affect the version of samba3x as shipped with Red Hat Enterprise Linux 5. This issue did not affect the version of samba4 as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of libvpx as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of xchat as shipped with Red Hat Enterprise Linux 4, 5, and 6. This issue does not affect the version of php as shipped with Red Hat Enterprise Linux 5. Not Vulnerable. This issue does not affect the versions of struts as shipped with various Red Hat products. The Red Hat Security Response Team has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Red Hat Security Response Team has rated this issue as having moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does affect Red Hat Enterprise Virtualization 2 and 3. Red Hat Enterprise Virtualization 2 is now in Production 2 phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Virtualization Life Cycle: https://access.redhat.com/support/policy/updates/rhev/. This issue does affect Red Hat Enterprise Virtualization 2 and 3. Red Hat Enterprise Virtualization 2 is now in Production 2 phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Virtualization Life Cycle: https://access.redhat.com/support/policy/updates/rhev/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This flaw has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect samba3x packages as shipped with Red Hat Enterprise Linux 5 and samba packages as shipped with Red Hat Enterprise Linux 6, as it only affected Samba versions prior to 3.4.0. This issue was addressed in samba packages in Red Hat Enterprise Linux 4 and 5 via RHSA-2012:0332. This issue affects the versions of xerces as shipped with Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the Linux kernel as shipped with Red Hat Enterprise Linux 6. This issue does not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not provide support for CLONE_IO. This issue does not affect the Linux kernel as shipped with Red Hat Enterprise MRG as they already contain the fix. This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2012-0481.html. This issue affects the versions of xerces as shipped with Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of xerces as shipped with Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. We do not currently plan to fix this issue due to the lack of further information about the flaw and its impact. If more information becomes available at a future date, we may revisit the issue. Not vulnerable. This issue did not affect the versions of httpd as shipped with Red Hat Enterprise Linux 3, 4, 5 and 6. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 5. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 6. This issue did affect the version of Linux kernel as shipped with Red Hat Enterprise MRG 2. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. Not Vulnerable. This issue only affects the struts-cookbook and struts-examples packages, which are not shipped by Red Hat. It does not affect the struts component as shipped with various Red Hat products. Not vulnerable. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 4 and 5. Not Vulnerable. This issue does not affect the version of krb5 package as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 5 as they did not include support for PKINIT. These issues only affect a script used during package build and do not affect binary iproute packages shipped with Red Hat Enterprise Linux. Therefore, they are not planned to be addressed in iproute packages in Red Hat Enterprise Linux 5 and 6, they are only planned to be addressed in the future Red Hat Enterprise Linux versions. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4 and 5 as they did not backport the commit a6ce4932fbdbcd8f8e8c6df76812014351c32892 that introduced this issue. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise MRG 2. This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2012-0481.html. Not vulnerable. This issue only affects community JBoss AS 7 prior to 7.1.1. It does not affect components shipped with any Red Hat products. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 5 as it did not backport upstream commits 4206d3aa and 5bde4d18. Not vulnerable. This issue did not affect the versions of taglib as shipped with Red Hat Enterprise Linux 6. taglib is only used in client applications. We do not consider a user-assisted crash of a client application such as k3b or Totem to be a security issue. Not vulnerable. This issue did not affect freetype packages as shipped with Red Hat Enterprise Linux 5 and 6, as they do not enable TrueType bytecode interpreter. This bug is not a security issue. For detailed explanation, refer to: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-1129#c5 Not vulnerable. This issue did not affect freetype packages as shipped with Red Hat Enterprise Linux 3, 4, 5, and 6. Not vulnerable. This issue did not affect freetype packages as shipped with Red Hat Enterprise Linux 5 and 6, as they do not enable TrueType bytecode interpreter. Not vulnerable. This issue did not affect freetype packages as shipped with Red Hat Enterprise Linux 5 and 6, as they do not enable TrueType bytecode interpreter. This vulnerability only applies to RHN Satellite 5.4 when running on Red Hat Enterprise Linux 6 under mod_wsgi. As the code uses mod_python when performing these checks on Red Hat Enterprise Linux 5, that version is not vulnerable to this flaw. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 as they did not include support for control groups. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 as they did not include support for memory control groups threshold notifications. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise MRG as they did not include support for memory control groups. Not vulnerable. This issue did not affect the versions of libzip and php as shipped with Red Hat Enterprise Linux 6. This issue did not affect the versions of php53 as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of libzip and php as shipped with Red Hat Enterprise Linux 6. This issue did not affect the versions of php53 as shipped with Red Hat Enterprise Linux 5. This issue did not affect openldap as shipped with Red Hat Enterprise Linux 5 as it did not contain the relevant assertion. This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2012-0899.html We do not consider safe_mode / open_basedir restriction bypass issues to be security sensitive. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php The Red Hat Security Response Team has rated this issue as having moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the version of samba4, openchange and evolution-mapi packages as shipped with Red Hat Enterprise Linux 6. A future security update may address this flaw. Not vulnerable. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5 and 6 as they did not backport the insufficient patch for CVE-2012-0247. Not vulnerable. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5 and 6 as they did not backport the insufficient patch for CVE-2012-0248. The Red Hat Security Response Team has rated this issue as having low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not Vulnerable. This issue did not affect the version of openjpeg as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not Vulnerable. This issue does not affect the version of webkitgtk as shipped with Red Hat Enterprise Linux 6. This issue did not affect the versions of the php and file packages as shipped with Red Hat Enterprise Linux 5 and 7. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 6, and Red Hat Enterprise MRG. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2012-0480.html. A future kernel update for Red Hat Enterprise Linux 4 may address this issue. taglib is only used in client applications. We do not consider a user-assisted crash of a client application such as k3b or Totem to be a security issue. This issue affects the version of samba/samba3x as shipped with Red Hat Enterprise Linux 5. This issue is not currently planned to be addressed in future updates. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise MRG as they did not provide support for the KVM subsystem. This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2012-0571.html. This has been addressed in Red Hat Enterprise Linux 5 via RHSA-2012:0676 https://rhn.redhat.com/errata/RHSA-2012-0676.html. Not vulnerable. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 6 as it did not backport the insufficient patch for CVE-2012-0259. The upstream development team of the JDBC driver for the PostgreSQL database does not consider improper escaping of certain JDBC statement / query parameters, when the JDBC driver of version older than the version of underlying PostgresSQL server is being used, to be a security defect. In general, the JDBC driver for the PostgreSQL database does not promise to work with server releases newer than the driver release. The Red Hat Security Response Team agrees with their assessment and so does not consider this to be a security flaw. Not vulnerable. This issue did not affect the versions of gnutls as shipped with Red Hat Enterprise Linux 4, 5, or 6. Not vulnerable. This issue did not affect the versions of xorg-x11-xfs as shipped with Red Hat Enterprise Linux 5. It does not affect Red Hat Enterprise Linux 6 as it no longer uses or provides the XFS font server. On Red Hat Enterprise Linux 5.10, new MySQL 5.5 packages are available which are not vulnerable to this issue. Future updates for MySQL 5.0 will no longer be made available (mysql-5.0.* and related packages); security advisories will be provided only for MySQL 5.5. Please refer to https://rhn.redhat.com/errata/RHEA-2013-1330.html for further information. This flaw did not affect the versions of PHP in Red Hat Enterprise Linux 3 or 4. Updates were released for Red Hat Enterprise Linux 5 and 6 (RHSA-2012:0546, RHSA-2012:0547), Red Hat Enterprise Linux 5.3 Long Life (RHSA-2012:0568), Red Hat Enterprise Linux 5.6, 6.0, and 6.1 Extended Update Support (RHSA-2012:0568, RHSA-2012:0569), and Red Hat Application Stack v2 (RHSA-2012:0570). This flaw only affected PHP CGI configurations and it did not affect the default configuration in Red Hat Enterprise Linux 5 and 6 using the PHP module for Apache httpd to handle PHP scripts. Note that this issue was not fixed completely the first time, which resulted in the assignment of additional related CVE identifiers - CVE-2012-2311, CVE-2012-2335, and CVE-2012-2336. Refer to the Red Hat CVE Database and the Red Hat Bugzilla for additional information on how those CVEs affect Red Hat products. Not Vulnerable. This issue does not affect the version of Firefox and Thunderbird package as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of Firefox and Thunderbird package as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of Firefox and Thunderbird package as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this issue in Red Hat Enterprise Linux 5 and 6 for Apache Ant. This issue does not affect the Apache commons-compress library as shipped with JBoss Enterprise BRMS Platform 5.2.0 or JBoss Enterprise Portal Platform 5.2.0. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise MRG 2. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5. Red Hat does not consider crash of end user application such as xorg-x11-server caused by local user actions to be a security flaw. This issue does not affect MySQL as shipped with Red Hat Enterprise Linux 4, 5, or 6. For a technical explanation please see https://bugzilla.redhat.com/show_bug.cgi?id=814605#c19 This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4, and 5. This has been addressed in Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2012-0670.html. This has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2012-0743.html. The Red Hat Security Response Team has rated this issue as having moderate security impact in CloudForms 1.1. This issue is not currently planned to be addressed in future updates. The Red Hat Security Response Team has rated this issue as having moderate security impact in CloudForms 1.1. This issue is not currently planned to be addressed in future updates. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and 6 as they did not backport the upstream commit 423e0ab0 that introduced this issue. This issue did not affect Red Hat Enteprise Linux MRG 2. Not vulnerable. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 3, 4, 5 and 6, as there were no updates released with an incomplete CVE-2012-2110 fix. Not vulnerable. This issue did not affect the versions of libsoup as shipped with Red Hat Enterprise Linux 5 and 6, as they do not include support for the SOUP_MESSAGE_CERTIFICATE_TRUSTED feature. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5. Future kernel updates for Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux MRG 2 may address this issue. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG. This issue was addressed in Red Hat Enterprise Linux 6 via RHSA-2012:0743 https://rhn.redhat.com/errata/RHSA-2012-0743.html This issue affects the version of poppler as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue did not affect the version of php as shipped with Red Hat Enterprise Linux 5 as it did not include FreeSec's libcrypt cryptographic algorithms implementation yet. This issue was addressed in php53 package for Red Hat Enterprise Linux 5 via RHSA-2012:1047 and in php package for Red Hat Enterprise Linux 6 via RHSA-2012:1046. The Red Hat Security Response Team has rated this issue as having moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This flaw does not affect any Red Hat JBoss products, it only affects the JBoss AS 7.1.1 community release. We do not currently plan to fix this issue due to the lack of further information about the flaw and its impact. If more information becomes available at a future date, we may revisit the issue. Not Vulnerable. This issue does not affect the version of pidgin as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. Red Hat did not release PHP package updates addressing CVE-2012-1823 that introduce the CVE-2012-2311 issue. Therefore, this CVE does not affect any Red Hat products. This flaw does not affect any Red Hat JBoss products, it only affects the JBoss AS 7 community releases. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG, as those versions do not have CONFIG_HFSPLUS_FS option enabled. The Red Hat Security Response Team has rated this issue as having low security impact. A future kernel updates in Red Hat Enterprise Linux 5 may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 4, 5, or 6. This flaw only affects PHP 5.4.0 through 5.4.2. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 3 and 4. The openssl versions in Red Hat Enterprise Linux 5 and 6 were partially affected, as they support DTLS, but they do not support TLS 1.1 and TLS 1.2. This issue was addressed in Red Hat Enterprise Linux 5 and 6 via RHSA-2012:0699. The mitigation for CVE-2012-2335 is included in the following PHP updates for Red Hat Enterprise Linux 5 and 6, which also address CVE-2012-2336 (BZ#820708): https://rhn.redhat.com/errata/RHSA-2012-1045.html https://rhn.redhat.com/errata/RHSA-2012-1046.html https://rhn.redhat.com/errata/RHSA-2012-1047.html Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux MRG. Future kernel updates for Red Hat Enterprise Linux 5 and 6 may address this issue. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG. Kernel update RHSA-2012:0743 https://rhn.redhat.com/errata/RHSA-2012-0743.html for Red Hat Enterprise Linux 6 did address this issue. Not vulnerable. This flaw is specific to PHP instances, running on Microsoft Windows platform. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue was addressed in Red Hat Enterprise Linux 6 via RHSA-2012:1304 https://rhn.redhat.com/errata/RHSA-2012-1304.html. This issue did not affect the version of php as shipped with Red Hat Enterprise Linux 5 as it did not include support for phar extension yet. This issue was addressed in php53 package for Red Hat Enterprise Linux 5 via RHSA-2012:1047 and in php package for Red Hat Enterprise Linux 6 via RHSA-2012:1046. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 as they did not include the upstream commit 84afd99b that introduced this issue. Future kernel updates for Red Hat Enterprise Linux 6 may address this issue. This has been addressed in Red Hat Enterprise Linux Red Hat Enterprise MRG 2 via https://rhn.redhat.com/errata/RHSA-2012-1150.html Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the version of cobbler as shipped with Red Hat Network Satellite Server 5.3.0, as it did not include the upstream commit 0e5f6f2d50d460f4c6b0c9f62cfed0ff5c546906 that introduced this flaw. This issue affects the version of cobbler as shipped with Red Hat Network Satellite Server 5.4.0. This issue affects the version of the taglib package as shipped with Red Hat Enterprise Linux 6. The taglib library is used in client applications only though. Red Hat Security Response Team does not consider a user-assisted crash of a client application such as k3b or Totem to be a security issue. The Red Hat Security Response Team has rated this issue as having moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Red Hat Security Response Team has rated this issue as having low security impact. This issue is not currently planned to be addressed in future updates for Red Hat Network Proxy or Red Hat Network Satellite. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Red Hat Security Response Team has rated this issue as having moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not Vulnerable. This issue does not affect the versions of Restlet as shipped with various Red Hat products. Red Hat does not consider a user assisted client crash such as this to be a security flaw. Red Hat does not consider a user assisted client crash such as this to be a security flaw. This issue affects the versions of pki-core as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ This issue does affect Red Hat Enterprise Linux 5 and 6. The risks in breaking compatability associated with fixing this flaw outweigh the benefits of the fix, therefore Red Hat does not plan to fix this flaw in Red Hat Enterprise Linux 5 and 6. Please note that the remote DoS issue in the way how Linux kernel treats SYN+FIN flags set is being handled under different CVE, CVE-2012-6638, and is planned to be fixed in all affected Red Hat Enterprise Linux releases. This issue did not affect the version of openldap as shipped with Red Hat Enterprise Linux 5, as it does not use the Mozilla NSS backend. Not vulnerable. This issue did not affect the versions of hypvervkvpd as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of OpenSSL as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include support for TLS 1.2 or 1.1. This issue does affect Red Hat Enterprise Virtualization 2 and 3. Red Hat Enterprise Virtualization 2 is now in Production 2 phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Virtualization Life Cycle: https://access.redhat.com/support/policy/updates/rhev/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This flaw affects various versions of Java as shipped with Red Hat products. A patch is available for Java 7 and Java 8, but not for previous versions of Java shipped with Red Hat products. Although no patch is available for previous versions of Java as shipped with Red Hat products, the impact of this flaw has been addressed in several components that utilize Java HashMap in such a way that may expose a denial of service flaw. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 as they did not include support for netfilter's ipv6 connection tracking module. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux MRG as they already contain the upstream commit that fixes this issue. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 as they did not include support for KEYCTL_SESSION_TO_PARENT keyctl IOCTL as introduced in upstream commit ee18d64c. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux MRG 2 as they already contain the fix. This issue was addressed in Red Hat Enterprise Linux 6 via RHSA-2012:1064 https://rhn.redhat.com/errata/RHSA-2012-1064.html. The Red Hat Security Response Team has rated this issue as having low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affected the version of libxml2 as shipped with Red Hat Enterprise Linux 5 and 6 has been addressed via RHSA-2012:1288. This issue does not affect the version of mingw32-libxml2 as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of mesa as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6, and Red Hat Enterprise MRG, as those versions have a guard page between the end of the user-mode accessible virtual address space and the beginning of the non-canonical area due to CVE-2005-1764 fix. This issue did affect the versions of Xen hypervisor as shipped with Red Hat Enterprise Linux 5. A kernel-xen update for Red Hat Enterprise Linux 5 is available to address this flaw. Not vulnerable. This issue did not affect the version of the oracle-server package as shipped with Red Hat Network Satellite 5.4. On Red Hat Enterprise Linux 5.10, new MySQL 5.5 packages are available which are not vulnerable to this issue. Future updates for MySQL 5.0 will no longer be made available (mysql-5.0.* and related packages); security advisories will be provided only for MySQL 5.5. Please refer to https://rhn.redhat.com/errata/RHEA-2013-1330.html for further information. We do not consider a user-assisted crash of a client application such as Gimp to be a security issue. This issue does not affect the version of rhythmbox as shipped with Red Hat Enterprise Linux 5. This issue affects the version of rhythmbox as shipped with Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG. We do not consider safe_mode / open_basedir restriction bypass issues to be security sensitive. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php This issue affects the version of dtach as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, since updates fixing CVE-2011-1083 contained a corrected patch that did not introduce this regression. This has been addressed in Red Hat Enterprise Linux 5 via https://rhn.redhat.com/errata/RHSA-2012-1061.html, and Red Hat Enterprise Linux Red Hat Enterprise MRG 2 via https://rhn.redhat.com/errata/RHSA-2012-1150.html Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the version of automake15, automake16 and automake17 as shipped with Red Hat Enterprise Linux 5. This issue affects the version of automake15 and automake16 as shipped with Red Hat Enterprise Linux 6. A future update may address this flaw in various affected versions of automake. This issue does affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. The Red Hat Security Response Team has rated this issue as having low security impact. A future kernel updates may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Red Hat Security Response Team has rated this issue as having moderate security impact. A future libtiff package update may address this issue in Red Hat Enterprise Linux 5 and 6. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the version of glibc as shipped with Red Hat Enterprise Linux 5. This issue did not affect the version of glibc as shipped with Red Hat Enterprise Linux 5. Not Vulnerable. This issue does not affect the version of ecryptfs-utils as shipped with Red Hat Enterprise Linux 5 and 6. Red Hat does not consider this do be a security issue. The affected code is present in Red Hat Enterprise Linux 5 and 6, but due to use of FORTIFY_SOURCE protections the impact would be limited to a crash. Therefore, there are no plans to correct this issue in Red Hat Enterprise Linux 5 and 6. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue did not affect the versions of kdepim as shipped with Red Hat Enterprise Linux 5 or 6. The Red Hat Security Response Team has rated this issue as having low security impact. A future kernel updates may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. The versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG are not affected. The versions of the kernel-xen packages as shipped with Red Hat Enterprise Linux 5 are not affected as they implement a different MMIO emulation mechanism. Not vulnerable. The versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG are not affected. The versions of the kernel-xen packages as shipped with Red Hat Enterprise Linux 5 are not affected because we did not provide support for memory sharing functionality. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. CVE-2012-3439 has been rejected. Please see CVE-2012-5885, CVE-2012-5886, or CVE-2012-5887 instead. The versions of libvirt as shipped with Red Hat Enterprise Linux 5 are not affected. Future libvirt updates for Red Hat Enterprise Linux 6 may address this flaw. Red Hat does not consider this flaw to be a security issue. It is improbable that a script would accept untrusted user input or unvalidated script input data which would be treated as SQL prepared statements. Not vulnerable. This issue did not affect the versions of gnome-screensaver as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include the upstream commit 43ee32edaddb9b9b9f4b43c47ca73d7b4eea9fae that introduced this issue. Not vulnerable. This issue did not affect the versions of python-beaker as shipped with Red Hat Enterprise Linux 6 as it did not include support for using python-crypto. Not Vulnerable. This issue does not affect the version of gnome-keyring as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of emacs as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of condor as shipped with Red Hat Enterprise MRG as it does not include the vulnerable code (VMware support is not compiled in). Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5 because we did not support TMEM (Transcendent Memory). This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of httpd as shipped with Red Hat Enterprise Linux 4, 5, and 6, JBoss Enterprise Web Server 1, and JBoss Enterprise Application Server 6. This issue did not affect the version of crypto-utils as shipped with Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this issue in Red Hat Enterprise Linux 6. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The versions of the gdb package, as shipped with Red Hat Enterprise Linux 5 and 6 are vulnerable to the original libiberty integer overflow flaw. But due the way of subsequent processing of the previously insufficiently pre-allocated libiberty buffer within gdb code, the impact of this issue is limited to crash only. Red Hat Security Response Team does not consider crash of end-user application, such as gdb, to be a security flaw. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as they already contain upstream commit f0ec1aaf54cadd that fixed this issue. The Red Hat Security Response Team has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did affect the versions of xen package as shipped with Red Hat Enterprise Linux 5. This issue did affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue did affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6 as they did not backport the commit that introduced this issue. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. Not vulnerable. This issue did not affect the versions of inn as shipped with Red Hat Enterprise Linux 5 as they did not include support for the STARTTLS command. The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This flaw affects Apache Tomcat 6.0.30 - 6.0.36 and 7.0.0 - 7.0.29. It does not affect JBoss Web. Tomcat 5.5 has reached the end of its supported upstream life-cycle, and the Apache Tomcat project no longer tests security flaws to determine whether they affect Tomcat 5.5. Red Hat has tested tomcat 5.5 as shipped with Red Hat Enterprise Linux 5 and JBoss Enterprise Web Server 1, and found that it is affected by this flaw. Patches for tomcat 5.5 to address this flaw have been provided. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue did affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5. This issue did affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterpise MRG 2. Not vulnerable. This issue did not affect the versions of dhcp as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of bind or bind97 as shipped with Red Hat Enterprise Linux 4, 5, and 6. This issue does not affect the version of dhcp as shipped with Red Hat Enterprise Linux 5. Not Vulnerable. This issue does not affect the version of Firefox and Thunderbird as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of Firefox and Thunderbird as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of Firefox and Thunderbird package, as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of Firefox and Thunderbird package, as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of Firefox and Thunderbird package, as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the version of Firefox and Thunderbird packages as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Red Hat Security Response Team has rated this issue as having moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of squashfs-tools as shipped with Red Hat Enterprise Linux 5 as they did not include support for parallel processing and do not make use of queues. Not Vulnerable. This issue does not affect the version of wireshark shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not affected. This flaw does not affect the jclouds Eucalyptus API as shipped with JBoss Fuse 6.0.0 and Fuse ESB Enterprise 7.1.0. Not Vulnerable. This issue does not affect the version of freetype as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2 as they did not provide support for the Diagnostics (DIAG) kernel mode driver for Android. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2 as they did not provide support for the Diagnostics (DIAG) kernel mode driver for Android. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2 as they did not provide support for the Graphics KGSL kernel mode driver for Android. Red Hat Security Response Team does not consider a user assisted denial of service (and potential crash) of end user application, such as tools from LibreOffice productivity suite, to be a security issue. Red Hat does not consider this to be a security flaw. The GIMP scriptfu server works as intended and should not be enabled in production environments as it was not designed to have any kind of security protection. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5 or 6. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5 or 6. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. Not vulnerable. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 5 and 6, and the version of php53 as shipped with Red Hat Enterprise Linux 5 as they did not include the upstream commit 322263 that introduced this issue. This issue does affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enteprise MRG. Future kernel updates may address this flaw. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. This issue affects the version of glibc as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. This issue affects the version of mysql packages shipped in Red Hat Enterprise Linux 5 and 6, the version of mysql55-mysql packages shipped in Red Hat Enterprise Linux 5 and the version of mariadb as shipped in Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact and are currently waiting for upstream to fix this issue. Not Vulnerable. This issue does not affect the version of axis as shipped with JBoss Developer Studio 5 and 6, JBoss Enterprise Portal Platform 5.2.2 and 6.0.0, Red Hat Enterprise Linux 5 and 6, and Red Hat Enterprise Virtualization Manager 3.1. The versions of libvirt as shipped with Red Hat Enterprise Linux 5 are not affected. This issue did affect the versions of the libvirt package as shipped with Red Hat Enterprise Linux 6. This issue affects the version of glibc as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of openslp as shipped with Red Hat Enterprise Linux 6. This issue affects the version of bacula as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue did not affect the versions of tomcat5 as shipped with Red Hat Enterprise Linux 5 and tomcat6 as shipped with Red Hat Enterprise Linux 6 as they did not include the CSRF prevention filter. Not Vulnerable. This issue does not affect the version of wpa_supplicant as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the openCryptoki packages as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of qpid-cpp as shipped with Red Hat Enterprise MRG as asserts are not enabled. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 5. This issue did affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 6. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise MRG 2. The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of ruby as shipped with Red Hat Enterprise Linux 5 and 6 as they did not provide version 1.9.x, which is the vulnerable version of ruby. Not vulnerable. This issue did not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the version of libproxy as shipped with Red Hat Enterprise Linux 6. Not a security flaw. Red Hat Security Response Team does not consider a user-assisted end user application crash (such a konqueror) to be a security issue. Not vulnerable. This issue did not affect the versions of kdelibs as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of ruby as shipped with Red Hat Enterprise Linux 6. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 5. This issue did affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 6. This issue did affect the version of Linux kernel as shipped with Red Hat Enterprise MRG 2. This issue did affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. This issue did affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. This issue does affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7. Due to the lack of upstream patches and the Moderate impact, we are not planning to address this issue in Red Hat Enterprise Linux 7. This issue did not affect JBoss Enterprise Application Platform versions 4.x and 5.x. This issue did not affect JBoss Enterprise Application Platform versions 4.x and 5.x. Not vulnerable. This issue does not affect the versions of GWT shipped with any Red Hat products. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 5. This issue did affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 6. This issue did affect the version of Linux kernel as shipped with Red Hat Enterprise MRG 2. Red Hat Product Security has rated this issue as having Low security impact in Red Hat OpenStack Platform 4.0. This issue is not currently planned to be addressed in future updates. This flaw allowed an attacker to circumvent all restrictions applied by the Java security manager. The Java security manager is used to sandbox Java applets in web browsers, but is also used in a variety of other applications. Red Hat has tested the flaw and confirmed that it affected Java SE 7 provided by OpenJDK 7 (java-1.7.0-openjdk), Oracle Java SE 7 (java-1.7.0-oracle) and IBM Java SE 7 (java-1.7.0-ibm) as shipped with Red Hat Enterprise Linux 6. Updates correcting this issue were released for all affected packages. Not vulnerable. This issue did not affect the versions of Firefox as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include SPDY protocol support. Not vulnerable. Upstream notes this issue only affected MySQL 5.5.x. Red Hat Enterprise Linux 5 and 6 include MySQL versions 5.0.x and 5.1.x respectively, which are not listed as affected. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not Vulnerable. This issue does not affect the version of mesa as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response team does not consider this bug to be security relevant. However, it has been corrected in MRG Grid 2.2 (via RHSA-2012:1278 and RHSA-2012:1281) as a proactive/hardening measure. Not vulnerable. This issue did not affect the versions of condor as shipped with Red Hat Enterprise MRG as it does not include the vulnerable code (VMware support is not compiled in). Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of axis as shipped with JBoss Developer Studio 5 and 6, JBoss Enterprise Portal Platform 5.2.2 and 6.0.0, Red Hat Enterprise Linux 5 and 6, and Red Hat Enterprise Virtualization Manager 3.1. Not vulnerable. The JOSSO server component which exposes this flaw is not shipped in any Red Hat product. The JOSSO agent shipped with JBoss Enterprise Portal Platform does not expose this flaw. Not vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of ruby as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of condor as shipped with Red Hat Enterprise MRG 1 or 2 as they do not provide a vulnerable version of condor. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. This issue did affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. This issue did affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. This issue does affect Red Hat Enterprise Virtualization 2 and 3. Red Hat Enterprise Virtualization 2 is now in Production 2 phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Virtualization Life Cycle: https://access.redhat.com/support/policy/updates/rhev/. This issue did affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 6. This issue did not affect the versions of kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG. Not vulnerable. This issue did not affect the versions of vdsm22 package as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of vdsm package as shipped with Red Hat Enterprise Linux 6. This issue did not affect the hypervisor disk images as shipped with Red Hat Enterprise Virtualization Hypervisor 5 and 6. This issue affects the version of cups as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of gnome-utils as shipped with Red Hat Enterprise Linux 5 and 6 as they used usermode to request privileges, not pkexec. This issue does not affect the version of openssh as shipped with Red Hat Enterprise Linux 5. This issue was addressed in Red Hat Enterprise Linux 6 via RHSA-2013:0519. This issue was corrected in RHN Satellite 5.6; earlier versions of RHN Satellite are affected. As RHN Satellite is now in the Production 2 phase of its support and maintenance life cycle, there are currently no plans to address this in future updates for RHN Satellite 5.5 and earlier. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/site/support/policy/updates/satellite. This issue affects tomcat and jbossweb as shipped in various Red Hat products. This issue can be mitigated using appropriate firewall configuration, as noted here: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2007-6750 This issue can also be partially mitigated by configuring an appropriate timeout using the connectionTimeout property for the relevant Connector(s) defined in server.xml, but testing shows that some variants of the attack may still be effective with this configuration. The tomcat project has advised that although this flaw can affect tomcat, there is no good solution available, and the tomcat security team does not consider it a vulnerability in tomcat or plan to release a patch: http://tomcat.apache.org/security-7.html#Not_a_vulnerability_in_Tomcat The Red Hat Security Response Team has rated this issue as having low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Update Infrastructure 2.1.3 is now in Production 2 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Update Infrastructure Life Cycle: https://access.redhat.com/support/policy/updates/rhui. Red Hat does not consider this to be a security flaw as a user executing these commands will only succeed in preventing service to the current connection, and not to the server as a whole. This issue does not affect the version of ekiga as shipped with Red Hat Enterprise Linux 5. This issue affects the version of ekiga as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of qt and qt4 as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of qt3 and qt as shipped with Red Hat Enterprise Linux 6. Red Hat JBoss BRMS 5; Red Hat JBoss Enterprise Application Platform 4 and 5; Red Hat JBoss Enterprise Portal Platform 5; Red Hat JBoss Enterprise SOA Platform 4 and 5; and Red Hat JBoss Enterprise Web Platform 5 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of ipa-client and ipa as shipped with Red Hat Enterprise Linux 5 or 6. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the version of inkscape as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of x3270 as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include support for SSL certificate verification. This issue did not affect the version of grep as shipped with Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not Vulnerable. This issue did not affect the version of freetype as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of exim as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of bind as shipped with Red Hat Enterprise Linux 4 and 5, nor the versions of bind97 as shipped with Red Hat Enterprise Linux 5, as they did not include support for DNS64. This issue did not affect the versions of bind or bind97 packages as shipped with Red Hat Enterprise Linux 4 and 5. Not vulnerable. This issue only affects axis2 as shipped with Fedora. It does not affect components shipped with any Red Hat products. Not vulnerable. Apache CXF is shipped with several Red Hat products, but the wsdl_first_https sample is not included. Without this sample code, the flaw is not exposed. Not vulnerable. This issue did not affect the versions of lynx as shipped with Red Hat Enterprise Linux 5 and 6 as they were not build against GnuTLS. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not vulnerable. This issue did not affect GUPnP, which is an independent implementation of the UPnP standard, entirely different from libupnp. libupnp, while affected, is not provided by any version of Red Hat Enterprise Linux. Not vulnerable. This issue did not affect GUPnP, which is an independent implementation of the UPnP standard, entirely different from libupnp. libupnp, while affected, is not provided by any version of Red Hat Enterprise Linux. Not vulnerable. This issue did not affect GUPnP, which is an independent implementation of the UPnP standard, entirely different from libupnp. libupnp, while affected, is not provided by any version of Red Hat Enterprise Linux. Not vulnerable. This issue did not affect GUPnP, which is an independent implementation of the UPnP standard, entirely different from libupnp. libupnp, while affected, is not provided by any version of Red Hat Enterprise Linux. Not vulnerable. This issue did not affect GUPnP, which is an independent implementation of the UPnP standard, entirely different from libupnp. libupnp, while affected, is not provided by any version of Red Hat Enterprise Linux. Not vulnerable. This issue did not affect GUPnP, which is an independent implementation of the UPnP standard, entirely different from libupnp. libupnp, while affected, is not provided by any version of Red Hat Enterprise Linux. Not vulnerable. This issue did not affect GUPnP, which is an independent implementation of the UPnP standard, entirely different from libupnp. libupnp, while affected, is not provided by any version of Red Hat Enterprise Linux. Not vulnerable. This issue did not affect GUPnP, which is an independent implementation of the UPnP standard, entirely different from libupnp. libupnp, while affected, is not provided by any version of Red Hat Enterprise Linux. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5 because we did not support TMEM (Transcendent Memory). This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5 because we did not support TMEM (Transcendent Memory). This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5 because we did not support TMEM (Transcendent Memory). This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5 because we did not support TMEM (Transcendent Memory). This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5 because we did not support TMEM (Transcendent Memory). This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5 because we did not support TMEM (Transcendent Memory). This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5 because we did not support TMEM (Transcendent Memory). This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not Vulnerable. This issue does not affect the versions of xulrunner, firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of inkscape as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of rpm as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include the upstream commit e8bc3ff5d780f4ee6656c24464402723e5fb04f4 that introduced this issue. The Red Hat Security Response Team has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Red Hat Security Response Team has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of Qt as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of cups as shipped with Red Hat Enterprise Linux 5 and 6 as they did not use the systemd capability for CUPS socket activation yet. Not vulnerable. This issue did not affect the versions of cronie as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of hplip and hplip3 as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of hplip as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of php as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of php53 as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of rubygem-passenger as shipped with Red Hat OpenShift Enterprise 1.2 do not include the vulnerable code. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Additional information can be found in the Red Hat Knowledgebase article: https://access.redhat.com/solutions/1165533 This issue affects the versions of HttpComponents Client and ModeShape Client as shipped with Red Hat JBoss Data Virtualization 6. However, this flaw is not known to be exploitable under any supported scenario in Red Hat JBoss Data Virtualization 6. A future update may address this issue. This issue did not affect the jakarta-commons-httpclient packages as shipped with Red Hat Enterprise Linux 5, 6, and 7, and httpcomponents-client packages as shipped with Red Hat Enterprise Linux 7. Red Hat JBoss Enterprise Application Platform 4, Red Hat JBoss SOA Platform 4, and Red Hat JBoss Web Server 1 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Important security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ Fuse ESB 4, Fuse Message Broker 5.2, 5.3, 5.4 and Fuse Services Framework 2.3, 2.4 are now in a reduced support phase receiving only Critical impact security fixes. This issue has been rated as having Important security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Fuse Product Life Cycle: https://access.redhat.com/support/policy/updates/fusesource/ Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise MRG 2. This issue did affect the version of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6 . This issue has been addressed in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2013-0744.html. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise MRG 2. This issue affects the version of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. Future kernel updates for Red Hat Enterprise Linux 6 may address this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise MRG 2. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise MRG 2. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. Future kernel updates for Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6 may address this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise MRG 2. This issue did affect the version of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise MRG 2. This issue did affect the version of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6. Future kernel updates for Red Hat Enterprise Linux 6 may address this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Red Hat believes that the flaw described by this CVE never affected augeas and therefore we consider this CVE assignment as invalid. For further details, refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1034243#c1 This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of cloud-init as shipped with Red Hat Enterprise Linux OpenStack Platform 3.0. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and 7, and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of glibc in Red Hat Enterprise Linux 5, 6, or 7. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. This issue affects the version of the kernel package as shipped with Red Hat Enterprise Linux 5 and 6. Future kernel updates for Red Hat Enterprise Linux 5 and 6 may address this issue. Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of ruby193-rubygem-nokogiri as shipped with Red Hat Satellite 6 and Red Hat OpenStack 6. Red Hat Product Security has rated this issue as having moderate security impact. A future update may address this issue. Red Hat Product Security has rated this issue as having no security impact for rubygem-nokogiri as shipped with: Red Hat Enterprise MRG 2.5, Red Hat Subscription Asset Manager 1.3, Red Hat CloudForms Management Engine 5.3.0, Red Hat OpenShift Enterprise 2.2.0; for ruby193-rubygem-nokogiri as shipped with Red Hat Satellite 6, Red Hat Subscription Asset Manager 1.3, Red Hat CloudForms Management Engine 5.3.0, Red Hat OpenStack 4.0, Red Hat OpenStack Foreman, Red Hat OpenStack 6, Red Hat OpenShift Enterprise 2.2.0; and for mingw-rubygem-nokogiri as shipped with Red Hat CloudForms Management Engine 5.3.0. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue has already been addressed in Red Hat Enterprise Linux 5 via http://rhn.redhat.com/errata/RHBA-2013-0022.html and in Red Hat Enterprise Linux 6 via http://rhn.redhat.com/errata/RHBA-2012-0763.html This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2 as the corresponding fix is already present. This issue does not affect the kernels as shipping with Red Hat Enterprise Linux 5, 6, 7, MRG-2 and realtime. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of quagga as shipped with Red Hat Enterprise Linux 5 and 6, since the OSPF protocol implementation in Quagga performs LSA id lookup based on two identifiers - (Router-ID, LS-ID) pair. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. This issue did affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. For details of affected products and workarounds see https://access.redhat.com/knowledge/node/290903 Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6, and Red Hat Enterprise MRG 2. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ This issue affects the versions of the haproxy cartridge as shipped with Red Hat OpenShift Enterprise 1 and 2. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Additionally OpenShift uses a per user poly-instantiated /tmp directory which makes exploitation of this issue very difficult. Red Hat Product Security has rated this issue as having Low security impact. Additionally this issue has been addressed through the removal of all v1 cartridges. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of libvirt as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of samba4 as shipped with Red Hat Enterprise Linux 6 as they did not include support for the Domain Controller components. The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue is resolved in CloudForms 3.0. The maintenance support policy for CloudForms 2.0 only covers critical security issues, meaning this issue is out of scope. Users of CloudForms 2.0 are advised to upgrade to CloudForms 3.0 to address this issue. Not Vulnerable. This issue does not affect the version of squid as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of dnsmasq as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of ipa as shipped with Red Hat Enterprise Linux 6 as they did not include support for Cross-Realm Kerberos trusts with Active Directory. This issue does not affect the version of hplip and hplip3 as shipped with Red Hat Enterprise Linux 5. This issue has been addressed in Red Hat Enterprise Linux 6 via RHSA-2013:0500. This issue affects the version of libarchive as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue did not affect the versions of the xen package as shipped with Red Hat Enterprise Linux 5. This issue did affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. This issue did affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 6. This issue did not affect Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue did affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Red Hat Enterprise Linux 5 and Red Hat Satellite Server 5 are now in Production 3 and Production 2 Phases of the support and maintenance life cycle respectively. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ and the Red Hat Satellite and Proxy Server Life Cycle: https://access.redhat.com/support/policy/updates/satellite. Red Hat JBoss BRMS 5; Red Hat JBoss Enterprise Application Platform 4 and 5; Red Hat JBoss Enterprise Portal Platform 5; Red Hat JBoss Enterprise SOA Platform 4 and 5; and Red Hat JBoss Enterprise Web Server 1 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/. This issue affects the versions of commons-fileupload as shipped with Red Hat Enterprise Virtualization Manager 3 and Red Hat JBoss Fuse Service Works 6. Red Hat Product Security has rated this issue as having Low security impact. A future update to these products may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of curl as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the version of corosync as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of boost as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the version of postgresql, as shipped with Red Hat Enterprise Linux 5. This issue affects the version of postgresql84, as shipped with Red Hat Enterprise Linux 5 and the version of postgresql, as shipped with Red Hat Enterprise Linux 6. Red Hat Security Response Team has rated this issue as having moderate security impact. A future update might address this flaw. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of cumin as shipped with Red Hat Enterprise MRG 1 or 2. This issue did affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of pidgin, as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6. This issue did affect the version of Linux kernel as shipped with Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect Red Hat Enterprise Virtualization Hypervisor 5 and 6. This issue did affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 6. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue did affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 6. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue did affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 6. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, and 6, and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of IPA or 389-ds as shipped with Red Hat Enterprise Linux 5 or 6. Red Hat does not regard this to be a security flaw. The tomcat log directory does not contain any sensitive information, and when sensitive information has been written to log files, this has been considered a security flaw in tomcat (e.g. CVE-2011-2204). This issue was reported to the Apache Tomcat project, and they have not considered it a flaw in any published security advisories. This issue did affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 6. This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. Not vulnerable. Upstream notes this issue only affected MySQL 5.5.x. Red Hat Enterprise Linux 5 and 6 include MySQL versions 5.0.x and 5.1.x respectively, which are not listed as affected. Not vulnerable. Upstream notes this issue only affected MySQL 5.5.x. Red Hat Enterprise Linux 5 and 6 include MySQL versions 5.0.x and 5.1.x respectively, which are not listed as affected. Not vulnerable. Upstream notes this issue only affected MySQL 5.5.x. Red Hat Enterprise Linux 5 and 6 include MySQL versions 5.0.x and 5.1.x respectively, which are not listed as affected. Not vulnerable. Upstream notes this issue only affected MySQL 5.5.x. Red Hat Enterprise Linux 5 and 6 include MySQL versions 5.0.x and 5.1.x respectively, which are not listed as affected. Not vulnerable. This issue did not affect the versions of samba as shipped with Red Hat Enterprise Linux 5 as they did not provide support for SMB2. This issue did not affect the versions of samba3x and samba as shipped with Red Hat Enterprise Linux 6 as they ship newer versions that do not include the vulnerable code. Not Vulnerable. This issue does not affect the version of acroread as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of acroread as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of acroread as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of Adobe Acroread as shipped with Red Hat Enterprise Linux 5 and 6. Updates will be released as soon as they are made generally available by Adobe. This issue affects the version of Adobe Acroread as shipped with Red Hat Enterprise Linux 5 and 6. Updates will be released as soon as they are made generally available by Adobe. Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not Vulnerable. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue has been addressed in firefox 24.2.0-ESR and thunderbird 24.2.0-ESR via RHSA-2013:1812 and RHSA-2013:1823. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 The Red Hat Security Response Team has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Future updates may address this issue. Please note that while a public non-weaponized exploit exists, according to our testing the issue is very hard to hit. The Red Hat Security Response Team has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Red Hat Security Response Team has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the version of icu as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2 may address this issue. Not vulnerable. This issue did not affect the versions of gnome-screensaver as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of xorg-x11-server as shipped with Red Hat Enterprise Linux 5 and 6 as our products did not include the vulnerable patch. The vulnerability was introduced due to a Ubuntu specific patch, which we never used with the xorg-x11-server we ship with our products. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 5 as they did not include support for PKINIT. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 4 and 5. Not vulnerable. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5 because we did not backport CVE-2013-1918 fix. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 because of missing Xen hypervisor support. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 as we did not have support for Xen hypervisor. Not Vulnerable. This issue does not affect the version of python-crypto package as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6, since MySQL packages in Red Hat Enterprise Linux are linked against OpenSSL, and not against yaSSL. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. On Red Hat Enterprise Linux 5.10, new MySQL 5.5 packages are available which are not vulnerable to this issue. Future updates for MySQL 5.0 will no longer be made available (mysql-5.0.* and related packages); security advisories will be provided only for MySQL 5.5. Please refer to https://rhn.redhat.com/errata/RHEA-2013-1330.html for further information. Not vulnerable. This issue affects the GlassFish REST component. This component is not shipped with any Red Hat products. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue affects the GlassFish Administration component. This component is not shipped with any Red Hat products. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. On Red Hat Enterprise Linux 5.10, new MySQL 5.5 packages are available which are not vulnerable to this issue. Future updates for MySQL 5.0 will no longer be made available (mysql-5.0.* and related packages); security advisories will be provided only for MySQL 5.5. Please refer to https://rhn.redhat.com/errata/RHEA-2013-1330.html for further information. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of pixman as shipped with Red Hat Enterprise Linux 5 as it did not contain the vulnerable code. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 or 6. The packages use OpenSSL and not yaSSL. Red Hat OpenShift Enterprise 1.2 is now in Production 1 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat OpenShift Enterprise Life Cycle: https://access.redhat.com/site/support/policy/updates/openshift. We do not consider safe_mode / open_basedir restriction bypass issues to be security sensitive. For more details see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169857#c1 and http://www.php.net/security-note.php This issue affects the versions of python as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. This issue affects the versions of python as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue affects the version of nss as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. Red Hat JBoss SOA Platform 5 is now in Maintenance Support phase receiving only qualified Important and Critical impact security fixes; and Red Hat JBoss SOA Platform 4.3 is now in Extended Life Support phase receiving only Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware Product Life Cycle: https://access.redhat.com/support/policy/updates/jboss_notes/ This issue did not affect the versions of python as shipped with Red Hat Enterprise Linux 5 and 6 as their XMLRPC library did not include support for gzip encoded content. This issue did not affect the version of the stunnel package as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and 6. This issue was addressed in Red Hat Enterprise MRG 2 via RHSA-2013:0622 https://rhn.redhat.com/errata/RHSA-2013-0622.html Not vulnerable. This issue did not affect the version of PackageKit in Red Hat Enterprise Linux, as Zypper support was not included. Not vulnerable. This issue did not affect the versions of the libvirt package as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. This issue did not affect the versions of kernel package as shipped with Red Hat Enterprise Linux 5 and 6. Future kernel updates for Red Hat Enterprise MRG 2 may address this flaw. This issue does not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 5. This issue did affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. Not affected. This flaw does not affect Apache Geronimo as shipped with various Red Hat products, as the affected subsystem is not included in these products. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the version of poppler as shipped with Red Hat Enterprise Linux 5. This issue affects the version of poppler as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG as they did not provide support for the KVM subsystem. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG as they did not provide support for the KVM subsystem. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG as they did not provide support for the KVM subsystem. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Due to it's limited impact, this issue is not currently planned to be addressed in Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect any versions of PHP as shipped with any Red Hat product. Please see https://bugzilla.redhat.com/show_bug.cgi?id=918187#c5 for further details. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise MRG 2. This issue did affect the version of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6, and Red Hat Enterprise MRG as those versions are missing upstream commit 196d6759 that introduced this issue. This issue did not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 because it did not backport the commit 4cf46b67eb that introduced this issue. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 may address this issue. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG 2. This issue did not affect the versions of the Linux kernel as shipped with Fedora 17 and 18 as they were not built with CONFIG_USER_NS configuration option. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 may address this issue. This issue was addressed in the package mysql55-mysql as shipped with Red Hat Enterprise Linux 5 via RHEA-2013:1330. This issue was addressed in the package mysql as shipped with Red Hat Enterprise Linux 6 via RHBA-2013:1647. Not Vulnerable. This issue does not affect the version of samba4 as shipped with Red Hat Enterprise Linux 6. This issue affects the version of pwlib as shipped with Red Hat Enterprise Linux 5. This issue affects the version of ptlib as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue did not affect the versions of librsvg2 as shipped with Red Hat Enterprise Linux 5. Not Vulnerable. This issue does not affect the version of subversion as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of postgresql as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of postgresql84 as shipped with Red Hat Enterprise Linux 5. This issue affects the version of postgresql as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of postgresql84, as shipped with Red Hat Enterprise Linux 5. Red Hat Security Response Team has rated this issue as having low security impact. A future update might address this flaw. Not Vulnerable. This issue does not affect the version of postgresql as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of postgresql84 as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of yum as shipped with Red Hat Enterprise Linux 5 and 6, as yum in those products did not (try to) use filelists metadata yet. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5 as we did not have support for sysenter for 64bit PV guests running on the Xen hypervisor (introduced in upstream changeset 16207:aeebd173c3fa). This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. This issue did affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. The risks associated with fixing this bug are greater than its security impact. This issue is not currently planned to be addressed in future kernel-xen updates for Red Hat Enterprise Linux 5. Using fully virtualized (HVM) guests, or PV guests with trusted kernel/administrator avoids this issue. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5 as it has no support for stub domains. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue does not affect versions of kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect versions of qemu-kvm packages as shipped with Red Hat Enterprise Linux 5 and 6. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6. Future kernel updates for Red Hat Enterprise Linux 6 may address this issue. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. The Red Hat Security Response Team has rated this issue as having low security impact because physical access is needed to exploit this issue. Future kernel updates for Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2 may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue does not affect the versions of KVM package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise MRG 2. Future kvm updates for Red Hat Enterprise Linux 5 may address this flaw. This issue was addresses in Red Hat Enterprise Linux 6 via RHSA-2013:0911 (https://rhn.redhat.com/errata/RHSA-2013-0911.html). Please note that unlike Red Hat Enterprise Linux 6, where a local unprivileged user could use this flaw to escalate their privileges on the system, on Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6.2 EUS, and Red Hat Enterprise Linux 6.3 EUS the impact is limited to potential information leak only. This issue affects the versions of Ruby 193 as shipped with Red Hat OpenShift Enterprise 1. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5 This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. This issue affects the version of subversion as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue does not affect the version of libxml2 as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect version of mingw32-libxml2 as shipped with Red Hat Enterprise Linux 5 and 6. This flaw pertains to the init scripts provided by the RPM distribution of tomcat in various Red Hat products. ZIP distributions do not include init scripts, and are not affected by this flaw. Not vulnerable. This issue did not affect the version of openstack-keystone as shipped with Red Hat OpenStack Folsom. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6. This issue was addressed in Red Hat Enterprise MRG 2 via RHSA-2013:0829 https://rhn.redhat.com/errata/RHSA-2013-0829.html This issue affects the libX11 package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXext package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXfixes package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXi package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXinerama package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXrandr package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXrender package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXRes package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXv package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXvMC package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXxf86dga package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This flaw only affects X clients that connect to malicious X servers. Generally speaking, these will be untrusted/unknown X servers only, as trusted remote X servers should be connected to via SSH (which provides end-point verification and authentication), or the local X server. Because this flaw requires that the X server be changed (recompiled to deviate from a standard X server) in order to impact the X client, it requires root privileges on the X server to effect the change. If this is a system where the X client and server are on the same (local) host, and an attacker is able to replace the X server binary, then they already have root privileges and no trust boundary is crossed. With remote X servers, using SSH with strict host-key checking will prevent the X client from connecting to the X server without intervention, as the user will be alerted to host-key changes. This issue affects the libXi package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libFS package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libX11 package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXi package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXvMC package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXxf86dga package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXxf86vm package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXt package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXcursor package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libX11 package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Low security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXt package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue does not affect the kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the xen package as shipped with Red Hat Enterprise Linux 5. This issue does affect the qemu-kvm package as shipped with Red Hat Enterprise Linux 6. Future qemu-kvm updates in Red Hat Enterprise Linux 6 may address this flaw. Please note that due to differences in upstream and Red Hat Enterprise Linux 6 versions of qemu guest agent this issue has lower security impact on systems running Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5 and qemu-kvm package as shipped with Red Hat Enterprise Linux 6. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the versions of jython as shipped with Red Hat Enterprise Linux version 5 and 6. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Red Hat Security Response Team has rated this issue as having moderate security impact. This issue is not currently planned to be addressed in OpenStack 2.1 (Folsom). For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of python-httplib2 as shipped with Red Hat Update Infrastructure 2.1. Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue is resolved in CloudForms 3.0. The maintenance support policy for CloudForms 2.0 only covers critical security issues, meaning this issue is out of scope. Users of CloudForms 2.0 are advised to upgrade to CloudForms 3.0 to address this issue. This issue is resolved in CloudForms 3.0. The maintenance support policy for CloudForms 2.0 only covers critical security issues, meaning this issue is out of scope. Users of CloudForms 2.0 are advised to upgrade to CloudForms 3.0 to address this issue. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue affects the version of the kernel package as shipped with Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. This issue affects the libXp package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXtst package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the libXv package in Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle: https://access.redhat.com/support/policy/updates/errata/ This flaw allows an attacker to circumvent a session fixation prevention mechanism which was implemented in tomcat 5.5.x >= 5.5.29, 6.0.x >= 6.0.21 and 7.x. Earlier versions of tomcat do not include this mechanism, and are therefore not affected by this flaw. JBoss Web as included in JBoss 5.x products also does not include this mechanism, and is not affected by this flaw. This flaw only affects tomcat 7. Tomcat 5 and 6 are not affected. The jbossweb servlet container is also not affected. Not vulnerable. This issue does not affect the versions of the xen package as shipped with Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not Vulnerable. This issue does not affect the version of subversion as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the kernel packages as shipped with Red Hat Enterprise Linux 5 because we did not backport upstream commit b0a873eb that introduced this issue. This issue was addressed in Red Hat Enterprise Linux 6 via RHSA-2013:0830 (https://rhn.redhat.com/errata/RHSA-2013-0830.html), Red Hat Enterprise Linux 6.1 Extended update support via RHSA-2013:0841 (https://rhn.redhat.com/errata/RHSA-2013-0841.html), Red Hat Enterprise Linux 6.2 Extended update support via RHSA-2013:0840 (https://rhn.redhat.com/errata/RHSA-2013-0840.html), Red Hat Enterprise Linux 6.3 Extended Update Support via RHSA-2013:0832 (https://rhn.redhat.com/errata/RHSA-2013-0832.html), and Red Hat Enterprise MRG 2 via RHSA-2013:0829 (https://rhn.redhat.com/errata/RHSA-2013-0829.html). Red Hat Enterprise Linux 6.0 was not affected by this flaw. Refer to https://access.redhat.com/site/solutions/373743 for further information. The Red Hat Security Response Team has rated this issue as having moderate security impact. This issue is not currently planned to be addressed in OpenStack 2.1 (Folsom). This issue is planned to be addressed in version OpenStack 3.0 (Grizzly). For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of python as shipped with Red Hat Enterprise Linux 5 and 6 as the SSL module there did not implement the match_hostname() routine yet. Red Hat OpenShift Enterprise 1.2 is now in Production 1 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat OpenShift Enterprise Life Cycle: https://access.redhat.com/site/support/policy/updates/openshift. Not Vulnerable. This issue does not affect the version of php as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of php53 as shipped with Red Hat Enterprise Linux 5. Not Vulnerable. This issue does not affect the version of dovecot as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of subversion as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. This issue affects the versions of kdeplasma-addons as shipped with Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the version of libguestfs as shipped with Red Hat Enterprise Linux 6 as it did not include the upstream commit 5a3da366268825b26b470cde35658b67c1d11cd4 that introduced this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6. Future kernel updates for Red Hat Enterprise Linux 6 may address this issue. Red Hat Security Response Team does not consider this flaw to be a security issue, since this is a documented feature of the application. Red Hat Update Infrastructure 2.1.3 is now in Production 2 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Update Infrastructure Life Cycle: https://access.redhat.com/support/policy/updates/rhui. Red Hat JBoss BRMS 5; Red Hat JBoss Enterprise Application Platform 4 and 5; Red Hat JBoss Enterprise Portal Platform 5; and Red Hat JBoss Enterprise SOA Platform 4 and 5 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5 as it has no support for BLKIF_OP_DISCARD. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the version of libimobiledevice as shipped with Red Hat Enterprise Linux 6 as it did not include the upstream commit 825da48d2e9c20086c4e34869da0b28376676b4c that introduced this issue. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 may address this issue. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue affects the version of the kernel package as shipped with Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. The Red Hat Security Response Team has rated this issue as having moderate security impact in OpenStack Essex (1.0) and Openstack Folsom (2.1). A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2 may address this issue. Not vulnerable. This issue did not affect the versions of dbus as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include the upstream commit 7fc9c026669976463adcd1e02ad19c582ed27289 that introduced this issue. Not Vulnerable. This issue does not affect the version of xorg-x11-xdm as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of Tomcat as shipped with Red Hat Enterprise Linux 5, 6 and 7; and Red Hat JBoss Web Server 1 and 2. This issue did not affect the versions of JBoss Web as shipped with Red Hat JBoss BRMS 5; Red Hat JBoss Data Grid 6; Red Hat JBoss Data Virtualization 6; Red Hat JBoss Enterprise Application Platform 4 and 5; Red Hat JBoss Fuse Service Works 6; Red Hat JBoss Operations Network 3; Red Hat JBoss Portal Platform 5; Red Hat JBoss SOA Platform 4 and 5; and Red Hat JBoss Web Platform 5. This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux MRG 2. This issue was addressed in Red Hat Enterprise Linux 6 via RHSA-2013:0911 (https://rhn.redhat.com/errata/RHSA-2013-0911.html). Upstream is not affected. We do not consider a denial of service flaw in a client application such as OpenOffice to be a security issue. Not vulnerable. This issue did not affect the version of clutter as shipped with Red Hat Enterprise Linux 6 as it did not include the upstream commit 1b1e77b46989ba97bfff8abdfa61df0f514a7eae that introduced this issue. This flaw does not affect the HBase ServiceMix bundle as shipped with Red Hat JBoss Fuse 6.0.0 and Fuse ESB Enterprise 7.1.0. The risks associated with fixing this issue are greater than its security impact. This issue is not currently planned to be addressed in future xen updates for Red Hat Enterprise Linux 5. The risks associated with fixing this issue are greater than its security impact. This issue is not currently planned to be addressed in future xen updates for Red Hat Enterprise Linux 5. The risks associated with fixing this issue are greater than its security impact. This issue is not currently planned to be addressed in future xen updates for Red Hat Enterprise Linux 5. This issue does affect Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect Linux kernel packages as shipped with Red Hat Enterprise MRG 2 as they already contain the fix. Not Vulnerable. This issue does not affect the version of glibc as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue does not affect the versions of the xen package as shipped with Red Hat Enterprise Linux 5 as it does not provide support for the libxl toolstack. This issue does not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. This is not a flaw; Nagios upstream implemented this as a feature, as documented in their changelog. This issue affects the version of python-suds as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of libvirt package as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the version of the kernel package as shipped with Red Hat Enterprise MRG 2. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. Future kernel updates for Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6 may address this issue. Not vulnerable. This issue did not affect the versions of libvirt package as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the xen package as shipped with Red Hat Enterprise Linux 5. This issue does affect the qemu-kvm package as shipped with Red Hat Enterprise Linux 6. Future qemu-kvm updates in Red Hat Enterprise Linux 6 may address this flaw. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2 may address this issue. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 may address this issue. This issue has been addressed for Red Hat Enterprise Linux 5 via RHSA-2013:1166 (https://rhn.redhat.com/errata/RHSA-2013-1166.html). This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. This issue has been addressed for Red Hat Enterprise Linux 5 via the advisory RHSA-2013:1166 and Red Hat Enterprise Linux 6 via the advisory RHSA-2013:1173. Not vulnerable. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. Not vulnerable. This issue did not affect the versions of httpd as shipped with Red Hat Enterprise Linux 4, 5, or 6 as they did not include the mod_session_dbd module. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. The Red Hat Security Response Team has rated this issue as having Moderate security impact in RedHat Enterprise OpenStack Platform 3 however fixing this issue would require a change to default behavior. This issue is not currently planned to be addressed in future updates. This issue did not affect the versions of openstack-keystone or python-keystone client as shipped with RedHat Enterprise OpenStack Platform 4. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of bind package as shipped with Red Hat Enterprise Linux 3, 4, and 5. This issue was corrected in bind97 packages in Red Hat Enterprise Linux 5 and bind packages in Red Hat Enterprise Linux 6. Not affected. This flaw does not affect the jclouds Eucalyptus API as shipped with JBoss Fuse 6.0.0 and Fuse ESB Enterprise 7.1.0. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. On Red Hat Enterprise Linux 5.10, new MySQL 5.5 packages are available which are not vulnerable to this issue. Future updates for MySQL 5.0 will no longer be made available (mysql-5.0.* and related packages); security advisories will be provided only for MySQL 5.5. Please refer to https://rhn.redhat.com/errata/RHEA-2013-1330.html for further information. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. On Red Hat Enterprise Linux 5.10, new MySQL 5.5 packages are available which are not vulnerable to this issue. Future updates for MySQL 5.0 will no longer be made available (mysql-5.0.* and related packages); security advisories will be provided only for MySQL 5.5. Please refer to https://rhn.redhat.com/errata/RHEA-2013-1330.html for further information. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of dhcp as shipped with Red Hat Enterprise Linux 5 and 6. Vulnerable. This issue affects the version of privoxy as shipped with Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this flaw. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. These issues do not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. These issues do affect the version of Linux kernel as shipped with Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. These issues do not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. These issues do affect the version of Linux kernel as shipped with Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. These issues do not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. These issues do affect the version of Linux kernel as shipped with Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. Not Vulnerable. This issue does not affect the version of acroread as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of flash-plugin as shipped with Red Hat Enterprise Linux 5 and 6. Updates will be released as soon as they are made generally available by Adobe. This flaw is related to the design of the RC4 protocol and not its implementation. More details and a possible work around is mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=921947#c8. Therefore there are no plans to correct this issue in Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise MRG 2. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5. Future kernel updates for Red Hat Enterprise Linux 5 may address this issue. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue does affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 may address this issue. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue does affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 may address this issue. Not vulnerable. This issue did not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6 as those versions do not provide support for in-kernel iSCSI target. Future kernel updates in Red Hat Enterprise Linux MRG 2 may address this flaw. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5. This issue does affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, and Red Hat Enterprise MRG. Future updates for Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG may address this issue. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5. This issue does affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, and Red Hat Enterprise MRG. Future updates for Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG may address this issue. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Note: user would need physical access to the system to exploit this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6. Future kernel updates for Red Hat Enterprise Linux 6 may address this issue. Note: A user would need physical access to the system in order to exploit this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 may address this issue. Note: user would need physical access to the system to exploit this issue. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue affects the version of the kernel package as shipped with Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. Note: user would need physical access to the system to exploit this issue. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Note: user would need physical access to a system to exploit this flaw. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue affects the version of the kernel package as shipped with Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. Note: user would need physical access to the system to exploit this issue. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue affects the version of the kernel package as shipped with Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. Note: user would need physical access to the system to exploit this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the version of icu as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5 and 6. Fuse ESB Enterprise 7.1.0, Fuse MQ Enterprise 7.1.1, JBoss Fuse 6.0.0 and JBoss A-MQ 6.0.0 all contain the Apache ActiveMQ web console, but it is not deployed by default. The documentation for deploying the web console covers the configuration needed to ensure authentication is enabled, therefore these products are not affected by this flaw. In a future update to these products, the web console will be configured so that authentication is automatically enabled if the web console is deployed, eliminating the need to manually configure it. A future update may address this flaw in Fuse Message Broker 5.5.1. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue affects the version of the kernel package as shipped with Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. Not a security issue. This issue is due to the handling of data types when passing data between rubygem-activerecord and MySQL. Applications that use rubygem-activerecord and MySQL may be affected if written in a way that exposes the issue, however any flaw would be specific to that application. For further information, please refer to https://bugzilla.redhat.com/show_bug.cgi?id=954365#c5 This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2 may address this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2 may address this issue. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 may address this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2 may address this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. This issue affects the version of the kernel package as shipped with Red Hat Enterprise Linux 5. Future kernel updates for Red Hat Enterprise Linux 5 may address this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of phpMyAdmin as shipped with any Red Hat product or Fedora, as those products do not ship phpMyAdmin version 4. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 may address this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This is hardware issue related to Intel VT-d, affecting all hypervisors (such as Xen and KVM) using Intel VT-d for guest PCI passthrough. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue is not planned to be addressed in the version of httpd as shipped with Red Hat Enterprise Linux 5 and 6. More details and possible mitigations are mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=995168#c5 This issue is not a security flaw as, on its own, it does not cross a trust boundary in the system. In order to access the datasource password, you must be logged in to jopr as an administrative user, that has permission to (among other things) execute code, deploy applications and reset the password in question. The administrative user has the privileges to reset the password, hence, this does not expose any information that is not otherwise visible. As administrative interfaces often display or allow the transmission of sensitive information, it is recommended best-practice that SSL is configured for the administrative console, regardless of this issue. We do not consider memory safety hazards caused by malformed php scripts as a security issue. Also (as per upstream) OS-level security should be used to protect systems from memory exhaustion caused by php applications. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. This issue was addressed in the package mysql55-mysql as shipped with Red Hat Enterprise Linux 5 via RHEA-2013:1330. This issue was addressed in the package mysql as shipped with Red Hat Enterprise Linux 6 via RHBA-2013:1647. This issue was addressed in the package mysql55-mysql as shipped with Red Hat Enterprise Linux 5 via RHEA-2013:1330. This issue was addressed in the package mysql as shipped with Red Hat Enterprise Linux 6 via RHBA-2013:1647. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. This issue was addressed in the package mysql55-mysql as shipped with Red Hat Enterprise Linux 5 via RHEA-2013:1330. This issue was addressed in the package mysql as shipped with Red Hat Enterprise Linux 6 via RHSA-2013:0772. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of bind as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of bind97 as shipped with Red Hat Enterprise Linux 5. Fuse ESB Enterprise is now in Maintenance Support phase receiving only qualified Important and Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Fuse Product Life Cycle: https://access.redhat.com/support/policy/updates/fusesource/ Red Hat JBoss BRMS 5; Red Hat JBoss Enterprise Application Server 4 and 5; Red Hat JBoss Enterprise Web Platform 5; Red Hat JBoss SOA Platform 4 and 5; and Red Hat JBoss Web Server 1 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Red Hat Product Security has rated this issue as having Low security impact for Red Hat Enterprise Linux 6. It does not affect the version of wireshark shipped with Red Hat Enterprise Linux 5. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of php54 as shipped with Red Hat Software Collections 1. This issue affects the version of freerdp as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having Moderate security impact, a future update may address this flaw. This issue affects the version of freerdp as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having Moderate security impact, a future update may address this flaw. Not Vulnerable. This issue does not affect the version of cyrus-sasl package as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of subversion, as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of kdebase package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of kdebase-workspace package as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of kdebase package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of kdebase-workspace package as shipped with Red Hat Enterprise Linux 6. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6. This issue does affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 7. Not vulnerable. This issue did not affect the versions of libvirt as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of libvirt as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. We do not consider a denial of service flaw in a client application such as OpenOffice to be a security issue. The Red Hat Security Response Team has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6 may address this issue. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue affects the version of the kernel package as shipped with Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. This issue did not affect the versions of ruby as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This flaw only affected GDM in Red Hat Enterprise Linux 5 and does not affect Red Hat Enterprise Linux 6. This flaw does not affect Google Web Toolkit (GWT) as shipped with any Red Hat products. Red Hat products either do not include GWT applications that depend on the JUnit module, or do not include a vulnerable version of GWT. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of abrt as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG 2. This issue affects the versions of glibc as shipped with Red Hat Enterprise Linux 5. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle, https://access.redhat.com/support/policy/updates/errata/ This issue does not affect the version of python as shipped with Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of libvirt package as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of gnupg as shipped with Red Hat Enterprise Linux 5. This issue affects the version of libgcrypt as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. More technical details on this flaw are available at https://bugzilla.redhat.com/show_bug.cgi?id=988589#c12 Not vulnerable. This issue did not affect the versions of subversion as shipped with Red Hat Enterprise Linux 5 or 6, as they did not ship the vulnerable versions of subversion. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the version of php as shipped with Red Hat Enterprise Linux 5 or the version of php54 as shipped with Red Hat Software Collections 1. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of subversion as shipped with Red Hat Enterprise Linux 5 or 6, as they did not ship the vulnerable versions of subversion. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of lcms package as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw. The Red Hat Security Response Team does not consider this issue to be a security flaw. For technical details please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1000202#c10 Not vulnerable. Red Hat did not release the incomplete fix for CVE-2013-2256 in any products. Red Hat Storage 2 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/site/support/policy/updates/rhs Red Hat OpenShift Enterprise 1.2 is now in Production 1 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat OpenShift Enterprise Life Cycle: https://access.redhat.com/site/support/policy/updates/openshift. Not vulnerable. This issue does not affect the version of openjpeg as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue does not affect the version of openjpeg as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of libvirt package as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of libvirt as shipped with Red Hat Enterprise Linux 5 and 6 as they did not ship the vulnerable version. Not vulnerable. This issue did not affect the versions of libvirt package as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of ImageMagick as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7, and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue did not affect the versions of pyOpenSSL as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. Not vulnerable. This issue does not affect the versions of the xen package as shipped with Red Hat Enterprise Linux 5 as it does not provide support for the libxl toolstack. This issue does not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does affect the qemu-kvm package as shipped with Red Hat Enterprise Linux 6. Future qemu-kvm updates in Red Hat Enterprise Linux 6 may address this flaw. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2 may address this issue. This issue does not affect Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. Future Linux kernel updates for Red Hat Enterprise Linux MRG 2 might address this issue. Not vulnerable. This issue did not affect the versions of icedtea-web as shipped with Red Hat Enterprise Linux 6. The CVE-2012-4540 issue was previously corrected via RHSA-2012:1434. The risks associated with fixing this bug in Red Hat Enterprise Linux 5 and 6 are greater than its security impact. This issue is not currently planned to be addressed in future kernel updates for Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of httpd as shipped with Red Hat Enterprise Linux 5 and 6 as only httpd version 2.4.6 included the vulnerable code. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 5 and earlier. This issue does affect the version of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. This issue does not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the Linux kernel package as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as it does not have support for Xen hypervisor. This issue has already been addressed in Red Hat Enterprise Linux 5 via http://rhn.redhat.com/errata/RHBA-2013-0022.html and in Red Hat Enterprise Linux 6 via http://rhn.redhat.com/errata/RHBA-2012-0763.html This issue does not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the Linux kernel package as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as it does not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of rubygems as shipped with various Red Hat products. On OpenShift Enterprise 2.1 the broker and node should be installed on separate systems, as such there should not be any local untrusted users on the broker system(s). This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect Red Hat Enterprise Virtualization Manager 3. Not vulnerable. This issue does not affect the versions of the xen package as shipped with Red Hat Enterprise Linux 5 as it does not provide support for the libxl toolstack. This issue does not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of the xen package as shipped with Red Hat Enterprise Linux 5 as it does not provide support for the ocaml toolstack. This issue does not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of the xen package as shipped with Red Hat Enterprise Linux 5 as it does not provide support for the libxl toolstack. This issue does not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of the xen package as shipped with Red Hat Enterprise Linux 5 as it does not provide support for the qdisk PV backend. This issue does not affect the versions of qemu-kvm as shipped with Red Hat Enterprise Linux 6 as they did not include the upstream commit that introduced this flaw. This issue does not affect Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the version of qemu-kvm as shipped in Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 may address this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of rubygem-actionmailer as shipped with Red Hat Subscription Asset Manager 1 as they do not include support for sending email using user supplied addresses. Not vulnerable. This issue did not affect the versions of libvirt package as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of libvirt package as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of libvirt package as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of samba as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue does not affect the versions of the xen package as shipped with Red Hat Enterprise Linux 5 as it does not provide oxenstored. This issue does not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. This issue affects the version of libtar as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue is resolved in CloudForms 3.0. Not Vulnerable. This issue did not affect the versions of Tomcat and JBoss Web as shipped with any Red Hat product, as this flaw was handled by Red Hat as CVE-2013-2185. This flaw is to be considered a duplicate of CVE-2013-4444. OpenShift Enterprise 1.2 is in a lifecycle phase that only provides Critical and Important security updates, as this issue is rated Moderate this issue will not be fixed. For additional information, refer to the Red Hat OpenShift Enterprise Life Cycle: https://access.redhat.com/support/policy/updates/openshift. This issue affects the versions of glibc as shipped with Red Hat Enterprise Linux 5. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle, https://access.redhat.com/support/policy/updates/errata The Red Hat Security Response Team has rated this issue as having moderate security impact. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of gnutls as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include support for DANE protocol. The Red Hat Security Response Team has rated this issue as having moderate security impact. This issue only affects systems that implemented the fix for CVE-2013-2096 (Bz963462) which fails to completely address the problem. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. Not Vulnerable. This issue does not affect the version of poppler as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of poppler as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of poppler as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the samba package in Red Hat Enterprise Linux 5. This issue was addressed for the samba3x package in Red Hat Enterprise Linux 5 and the samba package in Red Hat Enterprise Linux 6 via https://rhn.redhat.com/errata/RHSA-2013-1806.html, and the samba package in Red Hat Storage via https://rhn.redhat.com/errata/RHSA-2014-0009.html Not vulnerable. This issue did not affect the versions of samba or samba3x as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include support for acting as an Active Directory Domain Controller. This issue does affect Linux kernel packages as shipped with Red Hat Enterprise Linux 6. Future kernel updates for respective releases may address this issue. Not Vulnerable. Zanata is not shipped in any supported Red Hat products. Not vulnerable. This issue did not affect the versions of gnutls as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include support for DANE protocol. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of Subversion in Red Hat Enterprise Linux 5 and 6. Not vulnerable to the issues affecting AMD Au1100 and AMD Au1200 SOCs framebuffer drivers. These issues do not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Fuse ESB 4, Fuse Message Broker 5.2, 5.3, 5.4, Fuse Mediation Router 2.7, 2.8 and Fuse Services Framework 2.3, 2.4 are now in a reduced support phase receiving only Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Fuse Product Life Cycle: https://access.redhat.com/support/policy/updates/fusesource/ Fuse ESB Enterprise is now in Maintenance Support phase receiving only qualified Important and Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Fuse Product Life Cycle: https://access.redhat.com/support/policy/updates/fusesource/ Red Hat JBoss BRMS 5; Red Hat JBoss Enterprise Application Platform 4; Red Hat JBoss Enterprise Data Services Platform 5; Red Hat JBoss Enterprise Portal Platform 4 and 5; and Red Hat JBoss Enterprise SOA Platform 4 and 5 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ Red Hat Update Infrastructure 2.1.3 is now in Production 2 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Update Infrastructure Life Cycle: https://access.redhat.com/support/policy/updates/rhui. Not vulnerable. This issue was corrected in Red Hat Enterprise Linux 5 via RHSA-2012:1265. It did not affect Red Hat Enterprise Linux 6. Not vulnerable. This flaw does not affect RichFaces as shipped with various JBoss products. These products use JBoss RichFaces, which is covered by CVE-2013-2165. This flaw pertains specifically to Nuxeo RichFaces. Not vulnerable. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6 This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6 Not vulnerable. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6 Not vulnerable. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6 Not vulnerable. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6 Not vulnerable. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6 This issue does affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 7. This issue does affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 7. Not vulnerable. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6 Not vulnerable. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6 Not vulnerable. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6 Not vulnerable. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6 This issue does affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 7. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 7. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of curl as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of openssh as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include support for AES-GCM cipher suites. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 as we did not have support for Xen hypervisor. This issue did affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5, however please note that none of the guest operating system supported in Red Hat Enterprise Linux 5 are using the vulnerable set of rings of protection for privilege separation. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of Subversion in Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the grub or grub2 packages shipped in Red Hat products. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of kvm packages as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise 6. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise MRG 2 as they did not provide support for the KVM subsystem. The Red Hat Security Response Team does not consider this issue to be a security flaw. Please see http://seclists.org/oss-sec/2014/q1/174 for CVE REJECT request and further information. This issue did not affect JBoss Web, as shipped with various Red Hat JBoss products. This issue does affect Tomcat 5 as shipped by Red Hat Enterprise Linux 5. The risks in breaking compatibility associated with fixing this flaw outweigh the benefits of the fix, therefore Red Hat does not plan to fix this flaw in Red Hat Enterprise Linux 5. Additionally, note that Red Hat Enterprise Linux 5 is currently in reduced support phase, receiving only Critical security updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/site/support/policy/updates/errata#Production_3_Phase This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. Not Vulnerable. This issue does not affect the version of php as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of php53 as shipped with Red Hat Enterprise Linux 5. Not Vulnerable. This issue does not affect the version of php as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of php53 as shipped with Red Hat Enterprise Linux 5. Not Vulnerable. This issue does not affect the version of file-roller as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not Vulnerable. This issue does not affect the version of rsyslog as shipped with Red Hat Enterprise Linux 5 and 6. Not affected. This flaw does not affect the jclouds Eucalyptus API as shipped with JBoss Fuse 6.0.0 and Fuse ESB Enterprise 7.1.0. This issue did not affect the versions of OpenIPMI or freeipmi as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Security Response Team has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates for Red Hat Enterprise Linux 5 and 6. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ . CVE-2013-4810 refers to the exposure of unauthenticated JMXInvokerServlet and EJBInvokerServlet interfaces on HP ProCurve Manager (PCM). These servlets are also, however, exposed without authentication on older, unsupported community releases of JBoss AS (WildFly) 4.x and 5.x. All supported Red Hat JBoss products that include the JMXInvokerServlet and EJBInvokerServlet interfaces apply authentication by default and are not affected by this issue. Community releases of JBoss AS (WildFly) 7.x are also not affected by this issue. Users of older, unsupported community releases of JBoss AS (WildFly) are advised to follow the instructions available here to apply authentication to the invoker servlet interfaces: https://community.jboss.org/wiki/SecureJboss/ Note: Red Hat has been aware of this issue since 2012, as identified in CVE-2012-0874, and addressed the issue for supported Red Hat JBoss products based on JBoss AS 4.x and 5.x. This issue did not affect the versions of bind as shipped with Red Hat Enterprise Linux 5. It does affect the versions of bind97 as shipped with Red Hat Enterprise Linux 5 and the versions of bind as shipped with Red Hat Enterprise Linux 6. This did not affect the version of nmap as shipped with Red Hat Enterprise Linux 5, as it did not have support for NSE scripts. This issue affects the version of nmap as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. Not Vulnerable. This issue does not affect the version of wireshark, as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark, as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark, as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark, as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark, as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark, as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark, as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark, as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark, as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark, as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Low security impact in Subscription Asset Manager 1. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact in Red Hat OpenStack Platform 4.0. This issue is not currently planned to be addressed in future updates. Not vulnerable. This issue did not affect the versions of openswan as shipped with Red Hat Enterprise Linux 5 or 6 as they did not include the problematic newline checks when validating ASN.1 length. This issue affects the versions of the mongo cartridge as shipped with Red Hat OpenShift Enterprise Linux 2. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Additionally OpenShift uses a strong file permission and SELinux permission model minimizing the amount of data that can be viewed. This issue affects the versions of the mongo cartridge as shipped with Red Hat OpenShift Enterprise Linux 2. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the default configuration of ntp packages shipped with Red Hat Enterprise Linux, which does not allow remote ntpd control queries. User changing ntpd access control configuration should consider reviewing additional information provided via https://bugzilla.redhat.com/show_bug.cgi?id=1047854#c27 to avoid exposing their systems to this traffic amplification issue. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not Vulnerable. This issue does not affect the version of firefox and thunderbrid shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of libvirt package as shipped with Red Hat Enterprise Linux 5 and 6. Red Hat does not currently plan to change the default value of the slip parameter of the DNS response rate limiting (DNS RRL) feature in bind packages shipped with Red Hat Enterprise Linux. Refer to Red Hat Bugzilla bug 1038750 for additional details. Not Vulnerable. The SonarQube plug-in for Jenkins is not shipped by Red Hat. This issue affects the versions of the httpd package as shipped with Red Hat JBoss Enterprise Application Platform 6; and Red Hat JBoss Web Server 2. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Certificate System does not use the mod_headers module, even when installed, and is thus not affected by this flaw. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat JBoss Enterprise Application Platform 5 and Red Hat JBoss Web Server 1 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of Java as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of Java as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of mysql55-mysql package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of mysql as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of mysql55-mysql package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of mysql as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of mysql55-mysql package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of mysql as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of mysql55-mysql package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of mysql as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of quagga as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of openjpeg as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of openswan as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of openswan as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the version of firefox as shipped with Red Hat Enterprise Linux 5 and 6. Upstream does not include moderate impact fixes in the Extended Support Releases. This issue will be addressed in the next ESR rebase. Not vulnerable. This issue did not affect the versions of dovecot as shipped with Red Hat Enterprise Linux 5, 6 and 7. Not vulnerable. This flaw only affected BIND on Microsoft Windows platforms with a flawed WinSock call. This vulnerability does not affect BIND on Linux or Unix platforms. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise MRG 2 as they did not provide support for the KVM subsystem. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise MRG 2 as they did not provide support for the KVM subsystem. This issue did not affect the versions of jbigkit as shipped with Red Hat Enterprise Linux 7, as the issue was corrected before the release of Red Hat Enterprise Linux 7. Red Hat OpenShift Enterprise 1.2 is now in Production 1 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat OpenShift Enterprise Life Cycle: https://access.redhat.com/site/support/policy/updates/openshift. Not affected. This issue did not affect Jenkins as shipped with various Red Hat products, as they do not include the Jenkins Exclusion plugin. Not affected. This issue did not affect Jenkins as shipped with various Red Hat products, as they do not include the Jenkins Build Failure Analyzer plugin. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of kvm packages as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise 6. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise MRG 2 as they did not provide support for the KVM subsystem. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. The Red Hat Security Response Team does not consider this issue to be a security flaw due to the full root-like privileges (CAP_SYS_ADMIN) needed for successful exploitation. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise MRG 2. Please note that this issue only affects s390x architecture. The Red Hat Security Response Team does not consider this issue to be a security flaw due to the full root-like privileges (CAP_SYS_ADMIN) needed for successful exploitation. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. The Red Hat security response team has rated this issue as having low security impact in Red Hat Enterpise MRG 1 and 2, CloudForms 3, and Red Hat Network Satellite 5. This issue is not currently planned to be addressed in future updates. The Red Hat security response team has rated this issue as having low security impact in Red Hat Update Infrastructure. A future update may address this issue. The Red Hat security response team has rated this issue as having moderate security impact in Subscription Asset Manager 1. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ The Red Hat Security Response Team has rated this issue as having Moderate security impact in Red Hat Enterprise Linux OpenStack Platform 3 however fixing this issue would require a change to default behavior. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 as we did not have support for Xen hypervisor. Not Vulnerable. This issue does not affect the version of hplip as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of hplip3 as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of rubygem-actionpack as shipped with various Red Hat products. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of curl as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of hplip and hplip3 in Red Hat Enterprise Linux 5 and 6. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the libvirt packages as shipped with Red Hat Enterprise Linux 5 and 6. Red Hat Product Security has rated this issue as having moderate security impact in Red Hat OpenStack Platform 3.0. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of libvirt (which includes lxc) as shipped with Red Hat Enterprise Linux 6 as they do not include the template file lxc-sshd.in. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects Seam 3 remoting, but Seam 3 is not shipped with any Red Hat products, and Seam 3 development has been terminated. This issue is not currently planned to be addressed in a future update to Seam 3. Red Hat JBoss BRMS 5; Red Hat JBoss Enterprise Application Platform 4 and 5; Red Hat JBoss Enterprise Portal Platform 5; Red Hat JBoss Enterprise SOA Platform 4 and 5; and Red Hat JBoss Enterprise Web Platform 5 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ Red Hat JBoss BRMS 5; Red Hat JBoss Enterprise Application Platform 4 and 5; Red Hat JBoss Enterprise Portal Platform 5; Red Hat JBoss Enterprise SOA Platform 4 and 5; and Red Hat JBoss Enterprise Web Platform 5 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 5 and earlier. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 5 and earlier. Red Hat Enterprise Linux 5 is now in Production 3 phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect jBPM KIE Workbench as shipped with Red Hat JBoss BPM Suite 6.0.0. It may affect earlier versions of the upstream jBPM Console NG project. This issue does not affect RTgov as shipped with Red Hat JBoss Fuse Service Works 6. It may affect earlier versions of the upstream JBoss Overlord RTGov project. In Red Hat JBoss Fuse Service Works 6, this flaw is mitigated by configuration options that either remove the vulnerable interface, or constrain it using a Java Security Manager policy. These options are documented in the Installation and Security Guides for the product. Not vulnerable. This issue did not affect the version of Jenkins as shipped with Red Hat OpenShift Enterprise 1.2 or 2.0. Red Hat JBoss Enterprise Application Platform 6 prior to 6.1.1 and Red Hat JBoss Portal Platform 6 prior to 6.1.0 are affected by this flaw. All users of vulnerable versions are advised to update to 6.1.1 or later of Red Hat JBoss Enterprise Application Platform 6 and 6.1.0 or later of Red Hat JBoss Portal Platform 6 Not Vulnerable. This issue only affects versions of v8 that support typed arrays. This issue does not affect the versions of v8 as shipped with various Red Hat products. Red Hat Product Security has rated this issue as having Low security impact in Red Hat Enterprise Linux OpenStack Platform. This issue is not currently planned to be addressed in a future security update. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not Vulnerable. This issue does not affect the version of firefox and thunderbrid shipped with Red Hat Enterprise Linux 5 and 6. This issue was resolved in the version of thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 via RHSA-2013:1823. This issue did not affect the php packages as shipped with Red Hat Enterprise Linux 5. This issue did not affect the php packages as shipped with Red Hat Enterprise Linux 7. The Red Hat Security Response Team does not consider this issue to be a security flaw; however, we are in the process of discussing the issue with other vendors. We will revisit our decision not to classify this issue as a security flaw if needed. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This hardware issue is affecting certain AMD processors. Please consult your hardware vendor for any potential firmware updates providing a workaround for this issue. Not Vulnerable. This issue does not affect the version of openjpeg as shipped with Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of CUPS as shipped with Red Hat Enterprise Linux 5 and 6 as they did not ship with an suid-root lppasswd binary. Not Vulnerable. This issue does not affect the version of libpng as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Red Hat Security Response Team has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. The Red Hat Security Response Team does not consider this issue to be a security flaw. For more details please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1040010#c1 This issue affects the version of python as shipped with Red Hat Enterprise Linux 5 and 6. There are currently no plans to fix this issue. For more details please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1039915#c4 This issue affects the versions of pam as shipped with Red Hat Enterprise Linux 5 and 5. The Red Hat Security Response Team has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ . Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of php or php53 as shipped with Red Hat Enterprise Linux 5 and 6, and the versions of php54-php as shipped with Red Hat Software Collections 1, as they did not include the vulnerable function (it was introduced in PHP 5.5.0). This issue also did not affect the versions of gd as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of memcached package as shipped with Red Hat Enterprise Linux 5 and 6, since its not compiled with SASL support. This issue affects the version of kdebase-runtime package as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. The Red Hat Security Response Team has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not Vulnerable. This issue does not affect the version of poppler as shipped with Red Hat Enterprise Linux 5 and 6. Not affected. Spring MVC as shipped in various Red Hat products does not include the vulnerable org.springframework.http.converter.xml.Jaxb2CollectionHttpMessageConverter class. Not vulnerable. This issue did not affect the versions of php or php53 as shipped with Red Hat Enterprise Linux 5 and 6, and the versions of php54-php as shipped with Red Hat Software Collections 1, as they did not include the vulnerable function (it was introduced in PHP 5.5.0). This issue also did not affect the versions of gd as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of php or php53 as shipped with Red Hat Enterprise Linux 5 and 6, and the versions of php54-php as shipped with Red Hat Software Collections 1, as they did not include the vulnerable function (it was introduced in PHP 5.5.0). This issue also did not affect the versions of gd as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of libvirt package as shipped with Red Hat Enterprise Linux 5 and 6 (since http://rhn.redhat.com/errata/RHBA-2013-1581.html, Red Hat Enterprise Linux 6.5 GA). This issue did not affect the versions of python as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of file as shipped with Red Hat Enterprise Linux 5, 6, and 7, the versions of php as shipped with Red Hat Enterprise Linux 5 and 6, and the versions of php53 as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issued does not affect Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the version of libpng as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue does not affect the version of libpng as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of nodejs-connect as shipped with Red Hat OpenShift Enterprise 2. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of subversion as shipped with Red Hat Enterprise Linux 5 or 6, as they did not ship the vulnerable versions of subversion. This issue did not affect the versions of the kernel as shipped with Red Hat Enterprise Linux 4, 5, and 6. This issue affects the versions of the Linux as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of glibc as shipped with Red Hat Enterprise Linux 5 as they did not include the vulnerable code, which was introduced in later versions. This issue does not affect the version of libX11 package as shipped with Red Hat Enterprise Linux 7. This issue was was fixed in Red Hat Enterprise Linux 6 via the following security advisory: https://rhn.redhat.com/errata/RHSA-2014-1436.html This issue affects the version of libX11 package as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. This issue affects the versions of python27-python-pip, python-pymongo and python-virtualenv as shipped with Red Hat OpenShift 2.x and Satellite 6. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect versions of sqlite as shipped with Red Hat Enterprise Linux 5, 6 and 7, since they did not include the commit that introduced this flaw. This issue does not affect Linux kernels as shipped with Red Hat Enterprise linux 5,7, MRG-2 and realtime kernels. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 6 and may be addressed in a future update. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having security impact of Low. Further, home directories are not world readable on RHEL distributions (by default). This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the tigervnc packages as shipped with Red Hat Enterprise Linux 6, and the vnc packages as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of python-jinja2 as shipped with Red Hat Enterprise Linux 6 as it did not include the patch that introduced this flaw. This issue affects the version of curl as shipped with Red Hat Enterprise Linux 5 and 7. The Red Hat Security Response Team has rated this issue as having Moderate security impact, a future update may address this flaw. Not vulnerable. This issue does not affect the version of stunnel package as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of libssh2 package as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having Low security impact on OpenShift Enterprise, a future update may address this flaw. This issue did not affect the versions of yum as shipped with Red Hat Enterprise Linux 6 and 7. This issue affects the script provided on the OpenShift website. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of katello-headpin as shipped with Red Hat Subscription Asset Manager 1. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the libvirt packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect JBoss Web, as shipped with various Red Hat JBoss products. The disableURLRewriting property was introduced in Apache Tomcat 6.0.30. All versions of Apache Tomcat prior to 6.0.30 are not affected by this flaw, as the affected feature is not present. Tomcat 6 as shipped with Red Hat JBoss Web Server 2.0.0 and above is affected by this flaw. Tomcat 6 as shipped with Red Hat JBoss Web Server 1.0.2 is not affected by this flaw. Tomcat 6 as shipped with Red Hat JBoss Web Server prior to 1.0.2 is not affected by this flaw, as the disableURLRewriting property is not supported. Tomcat 6 as shipped with Red Hat Enterprise Linux 6 is based on Apache Tomcat 6.0.24 and is not affected by this flaw, as this flaw was introduced only in Apache Tomcat 6.0.33. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5 as they did not backport the upstream kvm commit that introduced this issue. This issue did not affect the versions of Linux kernel as shipped Red Hat Enterprise Linux 6 as they did not backport the upstream kvm commit that introduced this issue. This issue did not affect the versions of Linux kernel as shipped Red Hat Enterprise MRG as they did not provide support for the KVM subsystem. The Red Hat Security Response Team has rated this issue as having Moderate security impact. OpenShift Enterprise 1 is currently in the Production 1 phase of its lifecycle, as such this issue is not currently planned to be addressed in future updates. For additional information, refer to the Satellite Life Cycle: https://access.redhat.com/site/support/policy/updates/openshift page. This issue does not affect Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6. Future kernel updates for Red Hat Enterprise Linux 6 may address this issue. Not vulnerable. This issue did not affect postgresql packages as shipped with Red Hat Enterprise Linux and Red Hat Software Collections. Refer to bug 1065863 for further details: https://bugzilla.redhat.com/show_bug.cgi?id=1065863 Not vulnerable. This issue did not affect the versions of openshift-origin-node-util as shipped with any current versions of Red Hat Open Shift Enterprise as they do not include the watchman code. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5. This issue does affect JBossWeb as shipped in Red Hat JBoss Enterprise Application Platform 5. Red Hat Product Security has rated this issue as having Moderate security impact. Red Hat JBoss Enterprise Application Platform 5 is currently in reduced support phase (Phase 2: Maintenance Support), receiving only Critical and Important security updates, hence this issue is not currently planned to be addressed in future updates for Red Hat Enterprise Application Platform 5. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ and the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue does not affect the version of openssl and openssl097a as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of openssl and openssl098e as shipped with Red Hat Enterprise Linux 6 or 7. This issue does not affect Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of rubygem-activerecord as shipped with CloudForms, OpenShift Enterprise 1 and 2, Red Hat Enterprise Linux OpenStack Platform 3 and 4, Red Hat Software Collections 1 and Subscription Asset Manager as they did not include the vulnerable code. Red Hat OpenShift Enterprise 1.2 is now in Production 1 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat OpenShift Enterprise Life Cycle: https://access.redhat.com/site/support/policy/updates/openshift. Red Hat OpenShift Enterprise 1.2 is now in Production 1 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat OpenShift Enterprise Life Cycle: https://access.redhat.com/site/support/policy/updates/openshift. Not vulnerable. This issue did not affect the versions of rubygem-net-ldap as shipped with Red Hat Subscription Asset Manager, CloudForms Management Engine and Red Hat OpenStack 3 and 4 as they did not include support for the password salting feature. This flaw only affects Apache Zookeeper in conjunction with Fuse Fabric. Fuse Fabric was storing cleartext passwords, which would appear as cleartext in Apache Zookeeper's log files. Fuse Fabric now encrypts passwords by default. Not vulnerable. This issue did not affect the versions of foreman as shipped with Red Hat Enterprise Linux OpenStack Platform 3 or 4. The Red Hat Security Response Team has rated this issue as having Low security impact in Red Hat Enterprise Linux OpenStack Platform 3 and 4. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. A similar issue exists in struts 1, identified by CVE-2014-0114. Applications using a third-party struts 2 library, deployed to Red Hat JBoss products, may be affected. Additional information can be found in the Red Hat Knowledgebase article: https://access.redhat.com/site/solutions/800293 This flaw does not affect Apache Tomcat as shipped by any Red Hat product as it was introduced in Apache Tomcat 8.0.0-RC2 and did not affect earlier versions. This issue does affect JBossWeb as shipped in Red Hat JBoss Enterprise Application Platform 5. Red Hat Product Security has rated this issue as having Low security impact. Red Hat JBoss Enterprise Application Platform 5 is currently in reduced support phase (Phase 2: Maintenance Support), receiving only Critical and Important security updates, hence this issue is not currently planned to be addressed in future updates for Red Hat Enterprise Application Platform 5. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ and the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not Vulnerable. This issue does not affect Spring as shipped with various Red Hat products. This issue does affect JBossWeb as shipped in Red Hat JBoss Enterprise Application Platform 5. Red Hat Product Security has rated this issue as having Moderate security impact. Red Hat JBoss Enterprise Application Platform 5 is currently in reduced support phase (Phase 2: Maintenance Support), receiving only Critical and Important security updates, hence this issue is not currently planned to be addressed in future updates for Red Hat Enterprise Application Platform 5. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ and the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of Linux kernel package as shipped with Red Hat Enterprise Linux 5 and 6 as they did not backport the commit that introduced this issue. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5. Future kernel updates for Red Hat Enterprise MRG 2 may address this issue. This issue did not affect the versions of Linux kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2 as they did not backport the commit that introduced this issue. This issue did not affect the version of fence-agent as shipped with Red Hat Enterprise Linux 7. It does affect the versions of fence-agents as shipped with Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the version of sudo package as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. A similar issue exists in struts 1, identified by CVE-2014-0114. Applications using a third-party struts 2 library, deployed to Red Hat JBoss products, may be affected. Additional information can be found in the Red Hat Knowledgebase article: https://access.redhat.com/site/solutions/800293 Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. Applications using a third-party struts 2 library, deployed to Red Hat JBoss products, may be affected. Additional information can be found in the Red Hat Knowledgebase article: https://access.redhat.com/site/solutions/800293 This flaw allows attackers to manipulate ClassLoader properties on a vulnerable server. The impact of this depends on which ClassLoader properties are exposed. Exploits that lead to remote code execution have been published. These exploits rely on ClassLoader properties that are exposed on Tomcat 8, which is not included in any supported Red Hat products. However, some Red Hat products that ship Struts 1 do expose ClassLoader properties that could potentially be exploited. Additional information can be found in the Red Hat Knowledgebase article: https://access.redhat.com/site/solutions/869353 Not Vulnerable. This issue only affects struts 2, it does not affect the versions of struts as shipped with various Red Hat products. Applications using a third-party struts 2 library, deployed to Red Hat JBoss products, may be affected. This issue did not affect the versions of httpd as shipped with Red Hat Enterprise Linux 5 and 6, Red Hat JBoss Web Server, and Red Hat JBoss Enterprise Application Platform. These products include httpd 2.2, and only httpd versions 2.4.6 through 2.4.9 include the vulnerable code. Not vulnerable. This issue only affects Red Hat JBoss Fuse 6.1.0 Beta. It is resolved in the general availability release of Red Hat JBoss Fuse 6.1.0. Earlier versions of Red Hat JBoss Fuse are not affected, as they did not include the hawtio-karaf-terminal component. Not vulnerable. This issue only affects Red Hat JBoss Fuse 6.1.0 Beta. It is resolved in the general availability release of Red Hat JBoss Fuse 6.1.0. Earlier versions of Red Hat JBoss Fuse are not affected, as they did not include the hawtio-karaf-terminal component. This issue did not affect the versions of squid as shipped with Red Hat Enterprise Linux 5 as they did not include support for SSL-bump. This issue does not affect Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the Linux kernel package as shipped with Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Low security impact. The risks and engineering effort associated with fixing this bug are greater than its security impact. This issue is not currently planned to be addressed in future kernel updates for Red Hat Enterprise Linux 6. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the version of curl as shipped with Red Hat Enterprise Linux 5 and 7. The Red Hat Security Response Team has rated this issue as having Moderate security impact, a future update may address this flaw. This issue did not affect the versions of curl as shipped with Red Hat Enterprise Linux 6 and 7 because it uses the NSS backend, not OpenSSL. It does affect Red Hat Enterprise Linux 5 which uses the OpenSSL backend. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6. This issue affects the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6. This issue affects the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6. This issue affects the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6. This issue affects the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6. This issue affects the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6. Red Hat JBoss Enterprise Application Platform 4 and 5; Red Hat JBoss Enterprise Portal Platform 5; and Red Hat JBoss Enterprise SOA Platform 4 and 5 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ This issue does not affect the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does affect the qemu-kvm package as shipped with Red Hat Enterprise Linux 6. Future qemu-kvm updates in Red Hat Enterprise Linux 6 may address this flaw. Not vulnerable. This issue did not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6. This issue did not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2 as they did not provide support for the KVM subsystem. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6.4 and earlier, Red Hat JBoss Enterprise Application Platform 5 and 6, and Red Hat JBoss Web Server 1 and 2. This issue does affect Red Hat Enterprise Linux 7 Beta, Red Hat Enterprise Linux 6.5, Red Hat Enterprise Virtualization Hypervisor 6.5, and Red Hat Storage 2.1, which provided openssl 1.0.1e. Errata have been released to correct this issue. Additional information can be found in the Red Hat Knowledgebase article: https://access.redhat.com/site/announcements/781953 This issue affects the versions of rubygem-openshift-origin-node as shipped with Red Hat OpenShift Enterprise 2. Red Hat Product Security has rated this issue as having Important security impact, however this issue only affects systems using a non supported configuration (e.g. broker and node on the same host, or untrusted users on the broker servers). A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The fix for this flaw has been determined to be an addition to documentation. An admonition has been added to the relevant documentation that explain security domain usage in Red Hat JBoss Enterprise Application Platform 6. No security advisory will be published for this fix. This issue does not affect the version of samba as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of samba3x as shipped with Red Hat Enterprise Linux 5. This issue affects the version of samba4 as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having Low security impact, a future update may address this flaw. This issue affects the versions of libvirt as shipped with Red Hat Enterprise Linux 5, however the impact is limited to denial of service since it does not support fine grained access control. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 7. This issue affects the versions of katello as shipped with Red Hat Subscription Asset Manager 1.4. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the php and php53 packages as shipped with Red Hat Enterprise Linux 5. This issue is not planned to be addressed in the php packages in Red Hat Enterprise Linux 6 and 7. Refer to https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-0185 for further details. This issue affects the versions of qt4 as shipped with Red Hat Enterprise Linux 5 , qt3 as shipped with Red Hat Enterprise Linux 6 and 7 and qt as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the version of openssl as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of openssl098e as shipped with Red Hat Enterprise Linux 6. This issue did not affect the versions of the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue affected the versions of the Linux kernel packages as shipped with Red Hat Enterprise Linux 6 prior to version kernel-2.6.32-358.6.1.el6, released via RHSA-2013:0744 (https://rhn.redhat.com/errata/RHSA-2013-0744.html). That update added a backport of the upstream commit c56a00a165, which avoided this issue. This flaw requires local system access to be exploited. We are currently not aware of any working exploit for Red Hat Enterprise Linux 6 or Red Hat Enterprise MRG 2. This issue did not affect the openssl packages shipped with Red Hat Enterprise Linux 5. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 7 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of openstack-keystone as shipped with Red Hat Enterprise Linux OpenStack Platform 3 and 4. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG-2. Future Linux kernel updates for Red Hat Enterprise Linux 6 may address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the file, php, or php53 packages in Red Hat Enterprise Linux 5 and 6. This issue affects the file package in Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact, a future update my address this flaw. Not vulnerable. This issue did not affect the versions of qpid-cpp as shipped with Red Hat Enterprise Linux 6; Red Hat Enterprise MRG 2; and Red Hat Enterprise MRG Messaging 3. Red Hat OpenShift Enterprise 1.2 is now in Production 1 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat OpenShift Enterprise Life Cycle: https://access.redhat.com/site/support/policy/updates/openshift. Not vulnerable. This issue did not affect the versions of file, php, and php53 as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the php and the file packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of file as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the php and the file packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of file as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue does not affect the version of samba as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of samba3x as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of samba4 as shipped with Red Hat Enterprise Linux 6. Red Hat Update Infrastructure 2.1.3 is now in Production 2 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Update Infrastructure Life Cycle: https://access.redhat.com/support/policy/updates/rhui. This bug is not a security issue. For a detailed explanation, refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1101393#c5 This issue affects the version of sssd package as shipped with Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this issue as having Low security impact, a future update may address this flaw. This issue affects the version of freerdp as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having Moderate security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of libpng as shipped with Red Hat Enterprise Linux 5 or 6. Not vulnerable. This issue did not affect the versions of Oracle JDK as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of OpenJDK and Oracle JDK as shipped with Red Hat Enterprise Linux 5 and 6. Not Vulnerable. This issue does not affect the version of mysql55-mysql package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of mysql as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of mysql55-mysql package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of mysql as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of mysql55-mysql package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of mysql as shipped with Red Hat Enterprise Linux 6. Not Vulnerable. This issue does not affect the version of mysql55-mysql package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of mysql as shipped with Red Hat Enterprise Linux 6. This issue affects the versions of lcms as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue is a duplicate of the libjpeg CVE-2013-6629 issue. The versions of java-1.6.0-openjdk and java-1.7.0-openjdk as shipped with Red Hat Enterprise Linux 5 and 6 were not affected by this issue, as they do not use bundled libjpeg version. This issue did not affect the versions of a2ps as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the version of mutt package as shipped with Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not Vulnerable. This issue does not affect the linux version of the flash-plugin package. This issue does not affect the version of bind and bind97 as shipped with Red Hat Enterprise Linux 5. For a technical explanation please see https://bugzilla.redhat.com/show_bug.cgi?id=1051717#c25 This issue affects the version of freerdp as shipped with Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this issue as having Moderate security impact, a future update may address this flaw. This issue affects the versions of the graphviz package as shipped with Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Low security impact and therefore it is not planned to be addressed in future updates. This issue did not affect the versions of the graphviz package as shipped with Red Hat Enterprise Linux 7. This is a test of the new CVE-ID syntax. Red Hat Product Security has rated this issue as having security impact of Low. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not affected. Red Hat JBoss SOA Platform 4.3 and 5.3 support the SOAPClient action, which will use the SoapUI library to make calls to external web services. However, these products use SoapUI 1.7.1, while the vulnerable property expansion feature was not introduced until SoapUI 2.5. Therefore no Red Hat products are affected by this flaw. Not vulnerable. This issue did not affect the versions of graphviz as shipped with Red Hat Enterprise Linux 6 as it did not include the patch that introduced this flaw. This issue affects the versions of the graphviz package as shipped with Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Low security impact and therefore it is not planned to be addressed in future updates. This issue did not affect the versions of the graphviz package as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of libvirt as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 Not vulnerable. This issue does not affect the version of firefox and thunderbird package as shipped with Red Hat Enterprise Linux 5 and 6 because these packages are not updated via online updates from upstream sources. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of cairo as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of firefox as shipped with Red Hat Enterprise Linux 5 and 6 This issue does not affect the version of thunderbird as shipped with Red Hat Enterprise Linux 5 and 6, or the version of firefox as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue does not affect the version of thunderbird as shipped with Red Hat Enterprise Linux 5 and 6, or the version of firefox as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue does not affect the version of thunderbird as shipped with Red Hat Enterprise Linux 5 and 6, or the version of firefox as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue does not affect the version of thunderbird as shipped with Red Hat Enterprise Linux 5 and 6, or the version of firefox as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of thunderbird as shipped with Red Hat Enterprise Linux 5 and 6, or the version of firefox as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue does not affect the version of thunderbird as shipped with Red Hat Enterprise Linux 5 and 6, or the version of firefox as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue does not affect the version of thunderbird as shipped with Red Hat Enterprise Linux 5 and 6, or the version of firefox as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue does not affect the version of thunderbird as shipped with Red Hat Enterprise Linux 5 and 6, or the version of firefox as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 as we did not have support for Xen hypervisor. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. Not vulnerable. This issue did not affect the versions of openssh as shipped with Red Hat Enterprise Linux 4, 5, or 6, as the code for J-PAKE support is not compiled into the Red Hat shipped binaries. Red Hat Product Security has rated this issue as having Low security impact in Red Hat Enterprise Linux OpenStack Platform. This issue is not currently planned to be addressed in a future security update. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. This issue did not affect the versions of python-requests as shipped with Red Hat Enterprise Linux 7 as they included a fix for this issue at GA. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not affected. Restlet as shipped with various Red Hat products does not include any of the extensions affected by this flaw. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 as we did not have support for Xen hypervisor. Not vulnerable. This issue does not affect the versions of the xen package as shipped with Red Hat Enterprise Linux 5 as it does not provide oxenstored. This issue does not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. The Red Hat Security Response Team has rated this issue as having Moderate security impact. OpenShift Enterprise 1 is currently in the Production 1 phase of its lifecycle, as such this issue is not currently planned to be addressed in future updates. For additional information, refer to the Satellite Life Cycle: https://access.redhat.com/site/support/policy/updates/openshift page. Fuse ESB Enterprise is now in Maintenance Support phase receiving only qualified Important and Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Fuse Product Life Cycle: https://access.redhat.com/support/policy/updates/fusesource/ This issue did not affect the versions of python as shipped with Red Hat Enterprise Linux 5 as they did not include the vulnerable socket.recvfrom_into() function. This issue was also corrected in the version of python shipped with Red Hat Enterprise Linux 7.0 prior to release. The Red Hat Security Response Team has rated this issue as having Moderate security impact. A future update may address this issue in Red Hat Software Collections. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the php packages as shipped with Red Hat Enterprise Linux 5. This issue did not affect the php packages as shipped with Red Hat Enterprise Linux 7. The Red Hat Security Response Team has rated this issue as having moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of gnutls as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of freeradius2 as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of freeradius as shipped with Red Hat Enterprise Linux 5 and 7. This issue was resolved in the version of thunderbird as shipped with Red Hat Enterprise Linux 5 and 6 via RHSA-2013:1823. Not vulnerable. This issue did not affect the versions of php or php53 as shipped with Red Hat Enterprise Linux 5 and 6, and the versions of php54-php as shipped with Red Hat Software Collections 1, as they did not include the vulnerable function (it was introduced in PHP 5.5.0). Not vulnerable. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of freetype as shipped with Red Hat Enterprise Linux 5, 6 and 7. Not vulnerable. This issue did not affect the versions of freetype as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the php packages as shipped with Red Hat Enterprise Linux 5. This issue did not affect the php packages as shipped with Red Hat Enterprise Linux 7. This issue affects the versions of perltidy as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ Not vulnerable. This issue does not affect the version of wireshark package as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of net-snmp as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of net-snmp as shipped with Red Hat Enterprise Linux 6. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. The Red Hat Security Response Team does not consider this issue to be a security flaw. For more information please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1074631#c3 This issue is a duplicate of the libpng CVE-2013-6954 issue. The versions of java-1.6.0-openjdk and java-1.7.0-openjdk as shipped with Red Hat Enterprise Linux 5 and 6 were not affected by this issue, as they do not use bundled libpng version. This issue is a duplicate of CVE-2014-0001. See information for CVE-2014-0001 for additional details on errata that corrected this issue in Red Hat products. Not vulnerable. This issue is reported to only affect MySQL 5.6, which is not currently shipped as part of any Red Hat product. Not vulnerable. This issue is reported to only affect MySQL 5.6, which is not currently shipped as part of any Red Hat product. This issue affects the versions of gd as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue is only exposed via readline's debugging/tracing code and is not used by readline or any other application in Red Hat Enterprise Linux. The tracing functions are defined in a private header file and are only meant for the readline library's internal use. In general use, there is no exposure of this insecure temporary file issue, and while this does affect the versions of readline as shipped with Red Hat Enterprise Linux 5, 6 and 7 it is not currently planned to be addressed in future updates. Red Hat Product Security has rated this issue as having Low security impact. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the version of openssh as shipped with Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this issue as having Low security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle, https://access.redhat.com/support/policy/updates/errata/ This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue does not affect versions of Linux kernel packages as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 as they do not have support for Xen hypervisor. This issue affects the versions of pam as shipped with Red Hat Enterprise Linux 5 and 6. Red Hat Security Response Team has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 as we did not have support for Xen hypervisor. The Red Hat Security Response Team has rated this issue as having Moderate security impact. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle, https://access.redhat.com/support/policy/updates/errata/ Not vulnerable. This issue did not affect the versions of python as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of PostgreSQL as shipped with Red Hat Enterprise Linux 5 and 6. This issued does not affect Red Hat Enterprise Linux 5 because we do not provide support for Atheros 9k wireless network adapters. This issue does not affect Red Hat Enterprise Linux 5 and 6 because we do not provide support for Transactional Memory on Power PC architecture. This issue does not affect Red Hat Enterprise MRG 2 because we do not support Power PC architecture. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of cups-filters as shipped with Red Hat Enterprise Linux 7. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect Linux kernel packages as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of rsync as shipped with Red Hat Enterprise Linux 5 and 6. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle, https://access.redhat.com/support/policy/updates/errata/ Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Not vulnerable. This issue did not affect the versions of openswan as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of Exim as shipped with Red Hat Enterprise Linux 5 as they did not include the experimental DMARC support. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue affects the version of castor as shipped with Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat JBoss SOA Platform 4 is now in Phase 3, Extended Life Support, of its life cycle. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ Fuse ESB Enterprise 7 is now in Maintenance Support phase receiving only qualified Important and Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Fuse Product Life Cycle: https://access.redhat.com/support/policy/updates/fusesource/ The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw in the packages python-imaging, python-pillow. On Subscription Asset Manager (SAM) 1, the elasticsearch service is only bound to the loopback interface by default. To exploit this issue on a SAM 1 system, an attacker must have local access to the system. On Red Hat JBoss Fuse and Red Hat JBoss A-MQ, the elasticsearch service is only started if the insight-elasticsearch feature is installed. This feature is not installed by default. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6. Future kernel updates for Red Hat Enterprise Linux 6 may address this issue. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue requires local system access to be exploited. We are currently not aware of any working exploit for Red Hat Enterprise Linux 6 or Red Hat Enterprise MRG 2. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of ppp as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/clasification/. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2 may address this issue. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2 may address this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue did not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 may address this issue. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the version of the kernel package as shipped with Red Hat Enterprise Linux 7. Future kernel updates for Red Hat Enterprise Linux 7 may address this issue. This issue affects the versions of webkitgtk and webkitgtk3 as shipped with Red Hat Enterprise Linux 6 and 7 respectively. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue does not affect the version of webkitgtk as shipped with Red Hat Enterprise Linux 6 and 7. This issue does not affect the version of webkitgtk3 as shipped with Red Hat Enterprise Linux 7. This issue affects the versions of webkitgtk and webkitgtk3 as shipped with Red Hat Enterprise Linux 6 and 7 respectively. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ldns as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of bind or bind97 as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Network Satellite 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/site/support/policy/updates/satellite. This issue did not affect the versions of Puppet, Mcollective, Facter, or Hiera as shipped with various Red Hat Enterprise products as they all run on top of Ruby 1.9.3 or later. Not vulnerable. This issue did not affect the versions of puppet as shipped with Red Hat Subscription Asset Manager 1.3 as they did not include puppet-server. Red Hat OpenShift Enterprise 2 is now in Production 1 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat OpenShift Enterprise 2 Life Cycle: https://access.redhat.com/support/policy/updates/openshift. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6 and 7. This issue did not affect the versions of gnutls as shipped with Red Hat Enterprise Linux 4, 5, and 6. This issue does not affect the version of openssl and openssl097a as shipped with Red Hat Enterprise Linux 5. This issue does not affect the openssl098e as shipped with Red Hat Enterprise Linux 6. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 7. This issue affect the dbus package in Red Hat Enterprise Linux 5, 6, 7. Red Hat Product Security has rated this issue as having Moderate security impact, a future update my address this flaw in Red Hat Enterprise Linux 6 and 7. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle, https://access.redhat.com/support/policy/updates/errata/ This issue did not affect the versions of file, php, and php53 as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of file as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the php and the file packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of file as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the php and the file packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of file as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect CloudForms 5 as it does not use the "bitstring" data type anywhere in the product. This issue did not affect the versions of file, php, and php53 as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of file as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Netty versions as shipped by Red Hat products are not affected by this flaw. This issue affects the versions of samba3x as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of samba and samba4 as shipped with Red Hat Enterprise Linux 6. This issue affects the versions of samba as shipped with Red Hat Enterprise Linux 7. This issue did not affect the versions of samba as shipped with Red Hat Enterprise Linux 5. This did not affect openssl packages in Red Hat Enterprise Linux 5 (based on upstream 0.9.8e) and openssl 1.0.0 packages in Red Hat Enterprise Linux 6 (i.e. packages released before RHBA-2013:1585, which rebased openssl from 1.0.0 to 1.0.1e). The issue was introduced upstream in versions 0.9.8o and 1.0.0a. Not vulnerable. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 5, 6 and 7, Red Hat Enterprise Virtualization 3, and Red Hat Enterprise Storage 2, as they do not enable Secure Remote Password (SRP) support. All other supported Red Hat products that include openssl use older versions that are not affected by this issue. This issue did not affect the versions of OpenSSL as shipped with Red Hat Enterprise Linux 5, Red Hat JBoss Enterprise Application Platform 5 and 6, and Red Hat Enterprise JBoss Enterprise Web Server 1 and 2. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not the versions of subversion as shipped with Red Hat Enterprise Linux 5, 6, and 7, as they do not use the Serf RA layer. Not affected. This issue did not affect the versions of httpd as shipped with Red Hat Enterprise Linux 5, 6 and 7, Red Hat JBoss Web Server 1 and 2, and Red Hat JBoss Enterprise Application Platform 5 and 6. This flaw only affects httpd running on Microsoft Windows. Red Hat JBoss Web Server 1 and 2, and Red Hat JBoss Enterprise Application Platform 5 and 6 can be run on Microsoft Windows. However, these products provide httpd 2.2, which is not affected by this flaw. Not vulnerable. This issue does not affect the version of OpenOffice as shipped in Red Hat Enterprise Linux 5. This issue does not affect the version of LibreOffice as shipped in Red Hat Enterprise Linux 6 and 7. This issue did not affect the versions of spring-security-cas provided by jasperreports-server-pro as shipped with Red Hat Enterprise Virtualization Manager 3 as they did not include support for CAS Proxy Service URL configuration via request parameters. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has determined that CVE-2014-3529 is not exploitable by default in JBoss Portal Platform as provided by Red Hat. This flaw would only be exploitable if the Apache POI library provided by JBoss Portal Platform were used by a custom application to process user-supplied XML documents. This flaw could allow remote, unauthenticated attackers to read files accessible to the user running the application server, and potentially perform other more advanced XXE attacks. All systems hosting PicketLink applications using SAML Identity Providers and Service Providers may be affected. It is strongly advised that anyone running an affected system applies patches to address this flaw. This issue was fixed in current releases of foreman on Satellite 6. This issue did not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 7 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6. Future kernel updates for Red Hat Enterprise Linux 6 may address this issue. This issue affects Red Hat Cloud Forms 5. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Please note that a fix for this issue may also be documented in the CFME hardening guide. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle, https://access.redhat.com/support/policy/updates/errata/ MITRE has rejected this CVE ID, favoring the use of CVE-2014-0114. This flaw was the root cause of CVE-2014-0114, a flaw in Apache Struts 1 that could lead to unauthenticated remote code execution under certains conditions. Other frameworks built on commons-beanutils, such as Apache Stripes, are likely to expose similar issues. commons-beanutils 1.9.2 has now shipped, including a specialized BeanIntrospector implementation that allows suppressing properties. Frameworks built on commons-beantutils can make use of the new pre-configured SuppressPropertiesBeanIntrospector to address this flaw. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of nginx as shipped with Red Hat Software Collections 1 for Red Hat Enterprise Linux 6 and 7. This issue did not affect the versions of samba or samba3x as shipped with Red Hat Enterprise Linux 5, and the versions of samba as shipped with Red Hat Enterprise Linux 6, as it only affected Samba 4.0.0 and higher. Inktank Ceph Enterprise 1.2 only receives qualified Important and Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Inktank Ceph Enterprise Support Matrix: http://www.inktank.com/enterprise/support/ Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of net-snmp as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. This issue affects the version of openssl as shipped with Red Hat Enterprise Linux 5, 6 and 7, Red Hat JBoss Enterprise Application Platform 5 and 6, and Red Hat JBoss Web Server 1 and 2, Red Hat Enterprise Virtualization Hypervisor 6.5, and Red Hat Storage 2.1. This issue affects the version of nss as shipped with Red Hat Enterprise Linux 5, 6 and 7. Additional information can be found in the Red Hat Knowledgebase article: https://access.redhat.com/articles/1232123 This issue does not affect the version of openssl shipped with Red Hat Enterprise Linux 5; Red Hat JBoss Enterprise Application Server 5 and 6; and Red Hat JBoss Enterprise Web Server 1 and 2 because openssl-0.9.8e does not include support for session tickets. Not vulnerable. The versions of openssl package as shipped in Red Hat Enterprise Linux 5, 6 and 7; Red Hat JBoss Enterprise Application Platform 5 and 6; and Red Hat JBoss Enterprise Web Server 1 and 2 are not build with the "no-ssl3" option and therefore are not vulnerable to this security flaw. Not vulnerable. The versions of openssl package as shipped in Red Hat Enterprise Linux 5, 6 and 7; Red Hat JBoss Enterprise Application Platform 5 and 6; and Red Hat JBoss Enterprise Web Server 1 and 2 are not vulnerable to CVE-2014-3568, therefore does not have CVE-2014-3568 fix applied, and therefore are not vulnerable to this security flaw. This issue affects the version of openssl098e as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Low security impact and does not plan to address this flaw for the above components in any future security updates. This issue affects the version of openssl and openssl097a as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the version of openssl097a as shipped with Red Hat Enterprise Linux 5. This issue affects the version of openssl098e as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact and does not plan to address this flaw for the above components in any future security updates. This issue affects the version of openssl as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the version of openssl and openssl097a as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of openssl098e as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has determined that CVE-2014-3574 is not exploitable by default in JBoss Portal Platform as provided by Red Hat. This flaw would only be exploitable if the Apache POI library provided by JBoss Portal Platform were used by a custom application to process user-supplied XML documents. This issue affects the version of OpenOffice.org as shipped in Red Hat Enterprise Linux 5, and the version of LibreOffice as shipped in Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Moderate security impact and is not planned to be addressed in any future updates. Additional information can be found in the Red Hat Knowledgebase article: https://access.redhat.com/solutions/1165533 This issue affects the versions of HttpComponents Client as shipped with Red Hat JBoss Data Grid 6 and Red Hat JBoss Data Virtualization 6; and ModeShape Client as shipped with Red Hat JBoss Data Virtualization 6. However, this flaw is not known to be exploitable under any supported scenario in Red Hat JBoss Data Grid 6 and JBoss Data Virtualization 6. A future update may address this issue. Red Hat JBoss Enterprise Application Platform 4, Red Hat JBoss SOA Platform 4, and Red Hat JBoss Web Server 1 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Important security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ Fuse ESB 4, Fuse Message Broker 5.2, 5.3, 5.4 and Fuse Services Framework 2.3, 2.4 are now in a reduced support phase receiving only Critical impact security fixes. This issue has been rated as having Important security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Fuse Product Life Cycle: https://access.redhat.com/support/policy/updates/fusesource/ Not vulnerable. Apache ActiveMQ Apollo is not shipped with any supported Red Hat product. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of httpd as shipped with Red Hat Enterprise Linux 5 and 6, JBoss Enterprise Web Server 1 and 2, and JBoss Application Platform 6. Not vulnerable. This issue did not affect the versions of httpd as shipped with Red Hat Enterprise Linux 5, 6 and 7, Red Hat Software Collections 1, Red Hat JBoss Web Server 1 and 2, and Red Hat JBoss Enterprise Application Platform 6. This issue did not affect Apache CXF as shipped with Red Hat JBoss Enterprise Application Platform 5 and 6; Red Hat JBoss Enterprise Web Platform 5; Red Hat JBoss SOA Platform 5; Red Hat JBoss Fuse Service Works 6; Red Hat JBoss BRMS 5 and 6; Red Hat JBoss BPM Suite 6; Red Hat JBoss Data Virtualization 6; Red Hat JBoss Operations Network 3 and Red Hat JBoss Portal Platform 6 as the REST Web Services endpoints are not available. Fuse ESB Enterprise 7 is now in Maintenance Support phase receiving only qualified Important and Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Fuse Product Life Cycle: https://access.redhat.com/support/policy/updates/fusesource/ This issue did not affect the php and the file packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of file as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of python-imaging as shipped with Red Hat Enterprise Linux 5 and 6, and versions of python-pillow as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of foreman as shipped with Red Hat Satellite 6. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having low security impact, a future update may address this flaw in the libgcrypt and gnupg2 packages. Note that Axis 1 is EOL upstream, and the incomplete patch for CVE-2012-5784 was never merged upstream. It was, however, shipped by various vendors, including Debian and Red Hat. Additional information can be found in the Red Hat Knowledgebase article: https://access.redhat.com/solutions/1164433 This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of python-imaging as shipped with Red Hat Enterprise Linux 5 and 6, and the versions of python-pillow as shipped with Red Hat Enterprise Linux 7, as they did not include the affected Jpeg2KImagePlugin module. Not Vulnerable. HornetQ REST is not provided by any Red Hat product. Fuse ESB 4 and Fuse Message Broker 5.2, 5.3, 5.4 are now in a reduced support phase receiving only Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Fuse Product Life Cycle: https://access.redhat.com/support/policy/updates/fusesource/ Fuse ESB Enterprise is now in Maintenance Support phase receiving only qualified Important and Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Fuse Product Life Cycle: https://access.redhat.com/support/policy/updates/fusesource/ Red Hat JBoss SOA Platform 4 is now in Phase 3, Extended Life Support, of its respective life cycles. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ Red Hat OpenShift Enterprise 1 and 2 are now in Production 1 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat OpenShift Enterprise Life Cycle: https://access.redhat.com/site/support/policy/updates/openshift/ This issue did not affect the Linux kernel versions as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Future kvm updates for Red Hat Enterprise Linux 5 and Linux kernel updates for Red Hat Enterprise Linux 6 may address this issue. This issue did not affect the versions of OpenSAML Java as shipped with Red Hat JBoss Data Virtualization 6, Red Hat JBoss Data Grid 6, Red Hat JBoss Enterprise Application Platform 5 and 6, Red Hat JBoss JBoss Operations Network 3, and Red Hat JBoss Portal 6. These products use a version of Jakarta Commons HttpClient that contains a fix for CVE-2012-5783. Fuse ESB 4 and Fuse Services Framework 2.3 and 2.4 are now in a reduced support phase receiving only Critical impact security fixes. This issue has been rated as having Important security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Fuse Product Life Cycle: https://access.redhat.com/support/policy/updates/fusesource/ Red Hat JBoss SOA Platform 4 is now in Phase 3, Extended Life Support, of its life cycle. This issue has been rated as having Important security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ Not Vulnerable. This issue only affects vtldap/ldaptive, which is not included in any supported Red Hat products. This issue does not affect Linux kernel packages as shipped with Red Hat Enterprise Linux 6 and 7. Future kvm package updates for Red Hat Enterprise Linux 5 may address this issue. This issue does affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6 and 7. This issue does affect the kvm packages as shipped with Red Hat Enterprise Linux 5. Future updates may address this issue in the respective Red Hat Enterprise Linux releases. This issue affects the versions of curl as shipped with Red Hat Enterprise Linux 5 and is not planned to be corrected in future updates. Inktank Ceph Enterprise 1.1 and 1.2 receives only qualified Important and Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Inktank Ceph Enterprise Support Matrix: http://www.inktank.com/enterprise/support/ This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5 or the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6. Red Hat Storage 2.1 receives only qualified Important and Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Support Matrix: https://access.redhat.com/support/policy/updates/rhs This issue did not affect the versions of curl as shipped with Red Hat Enterprise Linux 5, 6, or 7. Not vulnerable. This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 5, 6, and 7, and Red Hat Software Collections 1. Fuse ESB Enterprise 7 is now in Maintenance Support phase receiving only qualified Important and Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Fuse Product Life Cycle: https://access.redhat.com/support/policy/updates/fusesource/ Red Hat JBoss SOA Platform 5 and Red Hat JBoss BRMS 5 are now in Maintenance Support phase receiving only qualified Important and Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware Product Life Cycle: https://access.redhat.com/support/policy/updates/jboss_notes/ This issue may affect the versions of hadoop as shipped with Red Hat Enterprise Virtualization Manager. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 7 may address this issue. This issue does not affect the versions of libvirt packages as shipped with Red Hat Enterprise Linux 5. This issue does affect the versions of libvirt packages as shipped with Red Hat Enterprise Linux 6 and 7. Future updates may address this issue in the respective Red Hat Enterprise Linux releases. This issue did not affect the kvm package as shipped with Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Low security impact. Future qemu-kvm updates for Red Hat Enterprise Linux 6 and 7 may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6 and 7. Future updates may address this issue in the respective Red Hat Enterprise Linux releases. This issue does affect the kvm packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 6 and 7. Future updates may address this issue in the respective Red Hat Enterprise Linux releases. This issue does affect the kvm packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7. Future kernel updates may address this issue. This issue does affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6. The risks associated with fixing this bug are greater than its security impact. This issue is not currently planned to be addressed in future kernel updates for Red Hat Enterprise Linux 6. This issue does affect the kvm packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not Vulnerable. Aerogear is not provided by any Red Hat product. Not Vulnerable. Aerogear is not provided by any Red Hat product. This issue does not affect any supported Red Hat products. This issue does not affect any supported Red Hat products. This issue does not affect any supported Red Hat products. This issue does not affect the versions of libvirt packages as shipped with Red Hat Enterprise Linux 5. This issue does affect the versions of libvirt packages as shipped with Red Hat Enterprise Linux 6 and 7. Future updates may address this issue in the respective Red Hat Enterprise Linux releases. This issue did not affect the php packages as shipped with Red Hat Enterprise Linux 5. This issue does affect Red Hat Enterprise Linux 5. This has been rated as having Important security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does affect Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG. Future Linux kernel updates for the respective releases will address this issue. This issue did not affect the versions of sysklogd and rsyslog packages as shipped with Red Hat Enterprise Linux 5, 6, and7. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5 and 6. This issue does affect Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG. Future Linux kernel updates for the respective releases will address this issue. This issue does affect Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG. Future Linux kernel updates for the respective releases will address this issue. Not vulnerable. This issue does not affect the qemu packages as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6 and 7. Future updates may address this issue in the respective Red Hat Enterprise Linux releases. This issue does affect the kvm packages as shipped with Red Hat Enterprise Linux 5, even though the impact is limited. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of libreoffice as shipped with Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. Red Hat does not currently ship eNovance edeploy in a product form and as such this issue has been filed upstream. Red Hat does not currently ship eNovance edeploy in a product form and as such this issue has been filed upstream. Red Hat does not currently ship eNovance edeploy in a product form and as such this issue has been filed upstream. Red Hat does not currently ship eNovance edeploy in a product form and as such this issue has been filed upstream. This issue affects the versions of ovirt-engine as shipped with Red Hat MRG 3. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of curl as shipped with Red Hat Enterprise Linux 5. Note that there are no applications provided with Red Hat Enterprise Linux that use the vulnerable CURLOPT_COPYPOSTFIELDS option, except PHP which could only be affected if used in an extremely unlikely scenario or via the script's author. This issue does not affect any supported Red Hat products. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of bind or bind97 as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of ruby as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects the 64-bit Windows platform. This issue did not affect the versions of sosreport as shipped with Red Hat Enterprise Linux 6. This issue did not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of sendmail as shipped with Red Hat Enterprise Linux 4, 5, 6, and 7. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2 as we did not have support for Xen hypervisor. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect binary PHP packages as shipped with Red Hat Enterprise Linux and Red Hat Software Collections. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. It does affect the versions of wireshark as shipped with Red Hat Enterprise Linux 7. The Red Hat Security Response Team has rated this issue as having Moderate security impact, a future update may address this flaw. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5 because we do not support ARM architecture. This issue did not affect Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG as we do not have support for Xen hypervisor. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of Linux kernel package as shipped with Red Hat Enterprise Linux 6 and 7. Future kernel updates for Red Hat Enterprise Linux 6 and 7 may address this issue. This issue affects the versions of powerpc-utils as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Red Hat Security Response Team has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates for Red Hat Enterprise Linux 4 and 5. A future update may address this flaw in Red Hat Enterprise Linux 6 or 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue affects the version of the kernel package as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2 may address this issue. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of open-vm-tools as shipped with Red Hat Enterprise Linux 7 and Red Hat CloudForms 4. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of open-vm-tools as shipped with Red Hat Enterprise Linux 7 and Red Hat CloudForms 4. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue is reported to only affect MySQL 5.6, which is not currently shipped as part of any Red Hat product. Not vulnerable. This issue is reported to only affect MySQL 5.6, which is not currently shipped as part of any Red Hat product. Not vulnerable. This issue is reported to only affect MySQL 5.6, which is not currently shipped as part of any Red Hat product. Not vulnerable. This issue is reported to only affect MySQL 5.6, which is not currently shipped as part of any Red Hat product. This issue affects the version of mysql55-mysql as shipped with Red Hat Enterprise Linux 5 and the version of mariadb as shipped with Red Hat Enterprise Linux 7. This issue affects the version of mysql55-mysql and mariadb55-mariadb as shipped with Red Hat Software Collections 1. The Red Hat Security Response Team has rated this issue as having Low security impact, a future update may address this flaw. This issue affects the versions of perl as shipped with Red Hat Enterprise Linux 6 and the versions of perl-Data-Dumper as shipped with Red Hat Enterprise Linux 7. A future update may address this issue. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue did not affect the versions of cups-filters as shipped with Red Hat Enterprise Linux 7. This issue did not affect the version of krb5 as shipped with Red Hat Enterprise Linux 5. This issue did not affect the version of krb5 as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of phpMyAdmin as shipped with any Red Hat product. Not vulnerable. This issue did not affect the versions of phpMyAdmin as shipped with any Red Hat product. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2 only support 64-bit architectures. Since exploiting this issue on 64-bit platforms is not feasible given the amount of input data that is necessary to trigger the integer overflow, we are currently not planning planning to fix this issue in Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the version of qffmpeg as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of gstreamer-plugins-good as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of gstreamer1-plugins-good as shipped with Red Hat Enterprise Linux 7. Not vulnerable. This issue does not affect the kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise Linux MRG 2. This issue affects the versions of python as shipped with Red Hat Enterprise Linux 7, the versions of python-simplejson as shipped with Red Hat Enterprise Linux 5 and 6, and the versions of python33-python and python33-python-simplejson as shipped with Red Hat Software Collections. Red Hat Product Security has rated this issue as having Moderate security impact. Future updates may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of gnupg2 as shipped with Red Hat Enterprise Linux 5, 6 and 7 and gnupg as shipped with Red Hat Enterprise Linux 5. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of python as shipped with Red Hat Enterprise Linux 5 and 7 as well as Red Hat Software Collections. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for the respective releases may address this issue. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 may address this issue. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 may address this issue. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5 may address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of nagios-plugins as shipped with Red Hat Enterprise Linux OpenStack Platform. This issue did not affect the versions of nagios-plugins as shipped with Red Hat Enterprise Linux OpenStack Platform. This issue did not affect the versions of nagios-plugins as shipped with Red Hat Enterprise Linux OpenStack Platform. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Red Hat classifies this as a security issue, however it is suggested that a properly secured PHP install should disable the phpinfo() function. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. Please note that on Red Hat Enterprise Linux 6 pppol2tp module is not automatically loaded when AF_PPPOX/PX_PROTO_OL2TP socket is created as Red Hat Enterprise Linux 6 lacks upstream commit 9395a09d05a23bb and default modprobe configuration as shipped with module-init-tools package does not contain the alias for pppol2tp protocol either. As a result, pppol2tp module has to be explicitly enabled and/or loaded by the system administrator. This issue did not affect the versions of ruby as shipped with Red Hat Enterprise Linux 5 and 6. This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle, https://access.redhat.com/support/policy/updates/errata/ This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle, https://access.redhat.com/support/policy/updates/errata/ This issue is not planned to be fixed in Red Hat Enterprise Linux 5 as it is now in Production 3 Phase of the support and maintenance life cycle, https://access.redhat.com/support/policy/updates/errata/ This issue does not affect Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. Future Linux kernel updates for Red Hat Enterprise Linux 6 and 7 may address this issue. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 as it doesn't provide support for AUTH chunks. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and 7. Future kernel updates for Red Hat Enterprise Linux 6 and 7 may address this issue. This issue has been fixed in Red Hat Enterprise MRG via RHSA-2014:1083. We do not consider a user-assisted crash of a client application such as Wireshark to be a security issue. For more information please see https://bugzilla.redhat.com/show_bug.cgi?id=1124500#c5 This issue does not affect the current php and php53 packages in Red Hat Enterprise Linux 5 and 6, as it was previously corrected as part of the fix for CVE-2006-7243. Not vulnerable. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 5, 6 and 7, Red Hat Enterprise Virtualization 3, and Red Hat Enterprise Storage 2, as they do not enable Secure Remote Password (SRP) support. All other supported Red Hat products that include openssl use older versions that are not affected by this issue. Not vulnerable. This issue does not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue does not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of wireshark as shipped with Red Hat Enterprise Linux 7. A future update may address this issue. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of wireshark as shipped with Red Hat Enterprise Linux 7. A future update may address this issue. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of wireshark as shipped with Red Hat Enterprise Linux 7. A future update may address this issue. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of wireshark as shipped with Red Hat Enterprise Linux 7. A future update may address this issue. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of wireshark as shipped with Red Hat Enterprise Linux 7. A future update may address this issue. This issue affects the versions of libvirt as shipped with Red Hat Enterprise Linux 5, however the impact is limited to denial of service since it does not support fine grained access control. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of kernel as shipped with Red Hat Enterprise Linux 5, 6, 7, and Red Hat Enterprise Linux MRG 2. Not vulnerable. This issue did not affect the versions of kernel as shipped with Red Hat Enterprise Linux 5, 6, 7, and Red Hat Enterprise Linux MRG 2. This issue does not affected openstack-keystone as shipped with Red Hat Enterprise Linux OpenStack Platform 4.0. This issue does not affected openstack-keystone as shipped with Red Hat Enterprise Linux OpenStack Platform 4.0. This issue does not affected openstack-keystone as shipped with Red Hat Enterprise Linux OpenStack Platform 4.0. Red Hat Product Security has rated this issue as having Low security impact in Red Hat Enterprise Linux OpenStack Platform. This issue is not currently planned to be addressed in a future security update. Not vulnerable. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5 and versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6 because they did not backport the commit that introduced this issue. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 7 because the layout of qemu-kvm binary does not allow successful exploitation of this flaw. This issue affects the versions of libgcrypt as shipped with Red Hat Enterprise Linux 6 and 7. A future update may address this issue. This issue affects the version of gnupg and libgcrypt as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the version of krb5 package as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This issue is not planned to be addressed in Red Hat Enterprise Linux 5. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue does not affect the version of krb5 package as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of qemu-kvm package as shipped with Red Hat Enterprise Linux 6 and 7. This issue did not affect the versions of php-pear as shipped with Red Hat Enterprise Linux 5, 6 and 7 as well as Red Hat Software Collections as they do not use a world-writable directory for storing PEAR cache data. This issue affects the versions of lua as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5. Future kernel updates for Red Hat Enterprise Linux 5 may address this issue. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5. Future kernel updates for Red Hat Enterprise Linux 5 may address this issue. This issue affects the version of glibc package as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of squid as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of libevent as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This issue is not planned to be addressed in Red Hat Enterprise Linux 5. For additional information, refer to the Red Hat Enterprise Linux Life Cycle:https://access.redhat.com/support/policy/updates/errata/. Red Hat no longer considers this bug to be a security issue. The change introduced in bash errata RHSA-2014:1306, RHSA-2014:1311 and RHSA-2014:1312 removed the exposure of the bash parser to untrusted input, mitigating this problem to a bug without security impact. Red Hat no longer considers this bug to be a security issue. The change introduced in bash errata RHSA-2014:1306, RHSA-2014:1311 and RHSA-2014:1312 removed the exposure of the bash parser to untrusted input, mitigating this problem to a bug without security impact. This issue affects the versions of Docker as shipped with Red Hat Enterprise Linux 7. However, this flaw is not known to be exploitable under any supported scenario. A future update may address this issue. Red Hat does not support or recommend running untrusted images. This issue did not affect the version of Docker as shipped with Red Hat Enterprise Linux 7. The next current release of Docker is < 1.30 and the next release will be based off of 1.3.2 or greater. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 may address this issue. This issue did not affect the versions of the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 (as they did not include support for this feature). This issue did not affect the versions of the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7.0 and Red Hat Enterprise MRG 2 (as they did not include support for this feature). This issue did not affect the versions of the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7.0 and Red Hat Enterprise MRG 2 (as they did not include support for this feature). This issue affects the versions of elasticsearch as shipped with Red Hat Satellite 6.x and Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5, 6, and 7, as they use system OpenSSL library rather than yaSSL. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5, 6, and 7, as they use system OpenSSL library rather than yaSSL. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5, 6, and 7, as they use system OpenSSL library rather than yaSSL. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5, 6, and 7, as they use system OpenSSL library rather than yaSSL. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5, 6, and 7, as they use system OpenSSL library rather than yaSSL. This issue did not affect the versions of mysql as shipped with Red Hat Enterprise Linux 5, 6, and 7, as they use system OpenSSL library rather than yaSSL. Not vulnerable. This issue did not affect the versions of OpenJDK as shipped with Red Hat Enterprise Linux. This issue did not affect the versions of squid as shipped with Red Hat Enterprise Linux 5, 6, and 7 as they do not provide the vulnerable program "pinger". This issue did not affect the versions of squid as shipped with Red Hat Enterprise Linux 5, 6, and 7 as they do not provide the vulnerable program "pinger". Not vulnerable. This issue did not affect the versions of python-twisted-web as shipped with Red Hat Enterprise Linux 6 and 7. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 7. Future kernel updates for Red Hat Enterprise Linux 7 may address this issue. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of python as shipped with Red Hat Enterprise Linux 7. A future update may address this issue. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. A patch for this issue was applied to the bash packages in Red Hat Enterprise Linux via RHSA-2014:1306, RHSA-2014:1311, and RHSA-2014:1312. The errata do not mention the CVE in the description, as the CVE was only assigned after those updates were released. Red Hat Product Security does not consider this bug to have any security impact on the bash packages shipped in Red Hat Enterprise Linux. A fix for this issue was applied as a hardening in RHSA-2014:1306, RHSA-2014:1311, and RHSA-2014:1312. Not vulnerable. This issue does not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This package is not shipped with any versions of Red Hat Enterprise Linux. Red Hat Software Collections Library components shipping in version 2.2 are affected. This issue did not affect the versions of zeromq as shipped with Inktank Ceph Enterprise 1.2 and 1.3. This issue did not affect the versions of zeromq as shipped with Inktank Ceph Enterprise 1.2 and 1.3. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and 7. Not vulnerable. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Not Vulnerable. This issue only affects struts 2; it does not affect the versions of struts as shipped with various Red Hat products. This issue affects the versions of cfme as shipped with Red Hat CloudForms 3. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the kvm package as shipped with Red Hat Enterprise Linux 5. Future qemu-kvm updates for Red Hat Enterprise Linux 6 and 7 may address this issue. Not vulnerable. This issue does not affect any Red Hat product. This issue affects the version of glibc package as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for the respective releases may address this flaw. This issue does not affect the versions of libvirt packages as shipped with Red Hat Enterprise Linux 5. This issue does affect the versions of libvirt packages as shipped with Red Hat Enterprise Linux 6 and 7. Future updates may address this issue in the respective Red Hat Enterprise Linux releases. Not vulnerable. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue does affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for the respective releases may address this issue. Note that the impact on Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2 is limited to local denial of service. Privilege escalation is not possible. Red Hat JBoss BRMS 5; Red Hat JBoss Enterprise Application Platform 4 and 5; Red Hat JBoss Enterprise Portal Platform 5; Red Hat JBoss Enterprise SOA Platform 4 and 5; and Red Hat JBoss Enterprise Web Platform 5 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ This issue did not affect the versions of IPA as shipped with Red Hat Enterprise Linux 5, 6, or 7 as they did not include support for OTP. Red Hat Web Framework Kit has moved out of maintenance phase and is no longer supported by Red Hat Product Security. This issue is not currently planned to be addressed in any future updates. For additional information, refer to the Red Hat JBoss Middleware Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ This issue affects the qemu-kvm packages as shipped with Red Hat Enterprise Linux 5, 6 and 7. Future updates for the respective releases may address this issue. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue does affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for the respective releases may address this issue. This issue did not affect the kvm packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of Red Hat JBoss Enterprise Application Platform before 6.2.0 as they did not include support for role-based access control (RBAC). This issue did not affect the versions of IPA as shipped with Red Hat Enterprise Linux 6 or 7 as they do not include the vulerable Web UI code. This issue did not affect the versions of librsvg2 as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of librsvg2 as shipped with Red Hat Enterprise Linux 7. Not vulnerable. This issue does not affect the version of chromium-browser as shipped with Red Hat Enterprise Linux 6. This issue affects the versions of webkitgtk and webkitgtk3 as shipped with Red Hat Enterprise Linux 6 and 7 respectively. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of webkitgtk and webkitgtk3 as shipped with Red Hat Enterprise Linux 6 and 7 respectively. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of librsvg2 as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue affects the versions of webkitgtk and webkitgtk3 as shipped with Red Hat Enterprise Linux 6 and 7 respectively. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ Red Hat JBoss SOA Platform 5 is now in Maintenance Support phase receiving only qualified Important and Critical impact security fixes; and Red Hat JBoss SOA Platform 4.3 is now in Extended Life Support phase receiving only Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware Product Life Cycle: https://access.redhat.com/support/policy/updates/jboss_notes/ This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue affects the version of the kernel package as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2 may address this issue. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ Red Hat JBoss SOA Platform 5 is now in Maintenance Support phase receiving only qualified Important and Critical impact security fixes; and Red Hat JBoss SOA Platform 4.3 is now in Extended Life Support phase receiving only Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware Product Life Cycle: https://access.redhat.com/support/policy/updates/jboss_notes/ This issue affects the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, a future update may address this flaw. This issue affects the kvm packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This issue is currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of subversion as shipped with Red Hat Enterprise Linux 5 and 6. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates of Red Hat Enterprise Application Platform 4 and 5, and Red Hat JBoss Web Server 1. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ and Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/. This issue did not affect Red Hat JBoss Web Server 3.x. This issue does affect Red Hat JBoss Web Server 2.x; a future update may address this issue. This issue did not affect the versions of 389-ds-base as shipped with Red Hat Enterprise Linux 6. Red Hat JBoss BRMS 5 is now in Phase 3, Extended Life Support, of its life cycle. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ This issue does not affect the version of rpm package as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of glibc as shipped with Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This issue has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat JBoss BRMS 5; Red Hat JBoss Enterprise Application Platform 5; and Red Hat JBoss Enterprise SOA Platform 4 and 5 are now in Phase 3, Extended Life Support, of their respective life cycles. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat JBoss Middleware and Red Hat JBoss Operations Network Product Update and Support Policy: https://access.redhat.com/support/policy/updates/jboss_notes/ Red Hat Product Security has rated this issue as having low security impact, a future update may address this flaw in libtiff. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having low security impact, a future update may address this flaw in libtiff. Red Hat Product Security has rated this issue as having low security impact, a future update may address this flaw in libtiff. Not vulnerable. This issue does not affect the versions of libvirt packages as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise Linux MRG 2. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 7, and Red Hat Enterprise Linux MRG 2. This issue affects the versions of libvirt as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates in Red Hat Enterprise Linux 5. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates in Red Hat Enterprise Linux 5. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ This issue did not affect the versions of unzip as shipped with Red Hat Enterprise Linux 5 as they did not include support for Zip64. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 5 and 6 or the versions of php53 as shipped with Red Hat Enterprise Linux 5. The PHP manual documents that using unserialize() on untrusted user input is unsafe and not recommended. Not vulnerable. This issue did not affect the versions of samba as shipped with Red Hat Enterprise Linux 5, 6 and 7, and Red Hat Storage 2.1 and 3.0, versions of samba3x as shipped with Red Hat Enterprise Linux 5, versions of samba4 as shipped with Red Hat Enterprise Linux 6, as they did not include support for Samba Active Directory Domain Controller. All shipped Samba versions are using MIT Kerberos implementation as its Kerberos infrastructure of choice. The Samba builds shipped are using MIT Kerberos implementation in order to allow system-wide interoperability between both desktop and server applications running on the same machine. This issue affects the versions of sox as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue did not affect the versions of curl as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they do no use DarwinSSL library as TLS backend. Not vulnerable. The 2.0.x versions of Apache Santuario XML Security for Java are not shipped in any Red Hat product as of January 2015. Not vulnerable. This issue did not affect the versions of openstack-neutron as shipped with Red Hat Enterprise Linux OpenStack Platform 4 or 5. Not vulnerable. This issue does not affect the version of vala package as shipped with Red Hat Enterprise Linux 7. This issue did not affect the version of gnutls package as shipped with Red Hat Enterprise Linux 7. This issue affects the version of gnutls as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, and 7, and Red Hat Enterprise MRG 2. This issue has been addressed in the respective releases. This issue affects the versions of vdsm as shipped with Red Hat Enterprise Vitalization 3.x. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects Red Hat Satellite 6. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Please note that a fix for this issue may also be documented in the Satellite documentation. This issue does not affect the version of autofs package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of ovirt-node as shipped with Red Hat Enterprise Virtualization 3. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel versions as shipped with Red Hat Enterprise Linux 5. This issue does affect the Linux kernel versions as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future updates may address this issue in the respective releases. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue does affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future updates for the respective releases may address this issue. Red Hat does not currently ship eNovance edeploy in a product form and as such this issue has been filed upstream. This issue does NOT affect the version of OpenSSL package as shipped with Red Hat Enterprise Linux 5. This issue is exploitable by malicious Docker images. Red Hat supports images from it's own registry, ISV images certified by the Red Hat certification program, and images using qualified customer content. This issue is exploitable by malicious Docker images. Red Hat supports images from it's own registry, ISV images certified by the Red Hat certification program, and images using qualified customer content. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5,6. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. This has been rated as having Low security impact as exploiting it requires privileged access and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the version of tigervnc as shipped with Red Hat Enterprise Linux 5 and 6. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 5 and 6. This issue affects the version of tigervnc as shipped with Red Hat Enterprise Linux 5 and 6. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 5 and 6. Not vulnerable. These issues do not affect Red Hat Enterprise Linux 5, 6 and 7. This issue affects the version of openssl098e as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Low security impact and does not plan to address this flaw for the above components in any future security updates. This issue affects the version of openssl097a as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the Linux kernel versions as shipped with Red Hat Enterprise Linux 5, 7 and Red Hat Enterprise MRG 2. Future Linux kernel updates for Red Hat Enterprise Linux 6 may address this issue. Not Vulnerable. This issue does not affect the linux version of the flash-plugin package. These issues do not affect Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. These issues do not affect kvm packages as shipped with Red Hat Enterprise Linux 5. These issues do not affect Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. These issues do not affect kvm packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue affects the version of the kernel package as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Future kernel updates for the respective releases may address this issue. This issue does not affect the version of gnutls as shipped with Red Hat Enterprise Linux 5 and 6, since it does not have support for ECC (Elliptic Curve Cryptography). This issue affects the versions of mod_wsgi as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect php53 packages in Red Hat Enterprise Linux 5, php packages in Red Hat Enterprise Linux 6 and 7, and php54-php and php55-php packages in Red Hat Software Collections 1. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. Not vulnerable. This issue did not affect the versions of bind or bind97 as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the version of the kernel package as shipped with Red Hat Enterprise MRG 2. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the verison of wireshark as shipped with Red Hat Enterprsie Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. This issue did not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 This issue affects the verison of wireshark as shipped with Red Hat Enterprsie Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. This issue affects the verison of wireshark as shipped with Red Hat Enterprsie Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. This issue did not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 Red Hat Product Security has rated this issue as having low security impact, a future update may address this flaw in ImageMagick. Not vulnerable. This issue does not affect the version of openssl, nss and gnutls as shipped in Red Hat Enterprise Linux 5, 6 and 7. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having low security impact, a future update may address this flaw in tcpdump. Red Hat Product Security has rated this issue as having low security impact, a future update may address this flaw in tcpdump. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue does affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. Future kernel-xen updates for Red Hat Enterprise Linux 5 may address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6 and 7 may address this issue. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise Linux MRG 2 because they do not have support for the x86-64 version of ESPfix functionality. The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw in libreoffice. This issue affects the versions of util-linux as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. Because exploitability of this issue requires conditions unlikely to occur, this issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having moderate security impact, a future update may address this flaw in tcpdump. This issue affects the versions of the graphviz package as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Low security impact and therefore it is not planned to be addressed in future updates. This issue did not affect the versions of strongimcv as shipped with Red Hat Enterprise Linux 7 as they did not include support for strongswan IKEv1/IKEv2. This issue did not affect the versions of ntpd as shipped with Red Hat Enterprise Linux 4 and 5. It has been addressed in Red Hat Enterprise Linux 6 and 7 via RHSA-2014:2024. This issue affects the versions of ntp as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. A mitigation for Red Hat Enterprise Linux 6 and 7 is available at: https://bugzilla.redhat.com/show_bug.cgi?id=1184573#c16 This issue affects the versions of ntp as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. To mitigate this issue, you may use the ip6tables command to prevent spoofing of local addresses on any network interface other than the loopback interface. Refer to the Mitigation section on our KBase article: https://access.redhat.com/articles/1305723 This issue does affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 4, 5, 6, and 7, and Red Hat Enterprise MRG 2. Future Linux kernel updates for the respective releases will address this issue. Red Hat Product Security has rated this issue as having low security impact, a future update may address this flaw in libtiff. This issue affects the versions of Docker as shipped with Red Hat Enterprise Linux 7. However, this flaw is not known to be exploitable under any supported scenario. A future update may address this issue. Red Hat does not support or recommend running untrusted images. This issue affects the versions of Docker as shipped with Red Hat Enterprise Linux 7. However, this flaw is not known to be exploitable under any supported scenario. A future update may address this issue. Red Hat does not support or recommend running untrusted images. This flaw is only exploitable when the local git repository is stored on a case-insensitive filesystem. By default, Red Hat Enterprise Linux uses case-sensitive filesystems (such as ext2/3/4, XFS, etc.) and as such is not vulnerable to this flaw. A non-standard system configuration ("networks: file dns" in /etc/nsswitch.conf) and possibly a DNS spoofing attack is required to exploit this flaw. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 7 may address this issue. This issue has been rated as having Low security impact and is not currently planned to be addressed in future updates for Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for the respective releases may address this issue. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 5 and 6 as the flaw was introduced in a later version (1.11). Not vulnerable. This issue does not affect the version of OpenSSL package as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of php and php53 as shipped with Red Hat Enterprise Linux 5, and the versions of php as shipped with Red Hat Enterprise Linux 7. This flaw requires that a user is able to upload arbitrary PHP code on the system, be a local user able to execute arbitrary PHP code, or have the ability to modify existing PHP code on the system. It also requires that the modified/arbitrary PHP code is executed with the php-cgi program, and the net result is that php-cgi crashes, effectively resulting in a self-denial of service. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2, as they did not include support for the B.A.T.M.A.N. protocol. The Red Hat Security Response Team has rated this issue as having moderate security impact, a future update may address this flaw in exiv2. Red Hat Product Security has rated this issue as having moderate security impact. This issue is not currently planned to be addressed in future updates. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue does not affect the version of libpng as shipped with Red Hat Enterprise Linux 5, 6 and 7. For a more detailed explanation please refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1177327#c1 This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for the respective releases may address this issue. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for the respective releases may address this issue. Red Hat Enterprise Linux 5 is now in Production 3 phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2 may address this issue. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of xdg-utils as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having a security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of Jenkins as shipped with Red Hat OpenShift Enterprise 2. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of Jenkins as shipped with Red Hat OpenShift Enterprise 2. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates in Red Hat Enterprise Linux 5. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of the kernel as shipped with Red Hat Enterprise Linux 4, 5, and 6. This issue affects the versions of the Linux as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of busyboxas shipped with Red Hat Enterprise Linux 4, 5 and 6. Red Hat Product Security has rated this issue as having a low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the version of libtiff package as shipped with Red Hat Enterprise Linux 5, 6 and 7. A further update may address this flaw in Red Hat Enterprise Linux 6 and 7. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. This issue did not affect the versions of freetype as shipped with Red Hat Enterprise Linux 5, 6, and 7. Not vulnerable. This issue did not affect the versions of freetype as shipped with Red Hat Enterprise Linux 5, 6 and 7. Not vulnerable. This issue did not affect the versions of freetype as shipped with Red Hat Enterprise Linux 5, 6 and 7. Not vulnerable. This issue did not affect the versions of freetype as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of freetype as shipped with Red Hat Enterprise Linux 5, 6, and 7. Not vulnerable. This issue did not affect the versions of freetype as shipped with Red Hat Enterprise Linux 5, 6 and 7. Not vulnerable. This issue did not affect the versions of freetype as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue affects the version of cups package as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. This issue did not affect the default sudo configuration in Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 7; and kernel-rt packages as shipped with Red Hat Enterprise MRG 2 and Red Hat Enterprise Linux 7. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6 and 7. Future kernel updates for Red Hat Enterprise Linux 7 may address this issue. Given the Moderate impact and the fact that BRTFS file system is no longer Technology preview in Red Hat Enterprise Linux 6 this issue is not currently planned to be addressed in future releases of Red Hat Enterprise Linux 6. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue did not affect the versions of the kvm package as shipped with Red Hat Enterprise Linux 5 and the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6. This issue affects the version of the qemu-kvm package as shipped with Red Hat Enterprise Linux 7, a future update may address this flaw. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue affects the versions of ntp as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. A mitigation for Red Hat Enterprise Linux 6 and 7 is available at: https://bugzilla.redhat.com/show_bug.cgi?id=1184573#c16 This issue affects the versions of ntp as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. To mitigate this issue, you may use the ip6tables command to prevent spoofing of local addresses on any network interface other than the loopback interface. Refer to the Mitigation section on our KBase article: https://access.redhat.com/articles/1305723 This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux and realtime kernels. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7, MRG-2. This has been rated as having Moderate security impact and is planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of binutils as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Low security impact. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2, as the code with the flaw is not present or is not built and so is not shipped in the products listed. This issue did not affect the versions of glibc as shipped with Red Hat Enterprise Linux 5 as they did not include support for netgroups. Red Hat Enterprise Linux 6 and 7 already include the fixed version of the package. Not vulnerable. The 4.x versions of Spring Framework are not shipped in any Red Hat product as of March 2015. Not vulnerable. This issue did not affect the versions of subversion as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include support for additional level of caching for the DAG nodes, which cause excessive memory use due to the cached nodes not being deallocated in a timely manner. This issue affects versions of openssl as shipped with Red Hat Enterprise Linux 5, 6 and 7. Errata have been released to correct this issue. This issue affects the version of openssl098e as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact and does not plan to address this flaw for the openssl098e component in any future security updates. This issue affects the version of openssl097a as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the version of openssl and openssl097a as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of openssl098e as shipped with Red Hat Enterprise Linux 6 and 7. This issue does not affect the version of openssl and openssl097a as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of openssl098e as shipped with Red Hat Enterprise Linux 6 and 7. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the version of httpd package as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 5 and 6 or the versions of php53 as shipped with Red Hat Enterprise Linux 5 as the original flaw (CVE-2014-8142) did not affect these versions. This issue affects the versions of 389-admin as shipped with Red Hat Directory Server 9.1. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of pki-core as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ovirt-engine-backend as shipped with Red Hat Enterprise Virtualization 3. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of selinux-policy as shipped with Red Hat OpenShift 2. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the kvm packages as shipped with Red Hat Enterprise Linux 5 as they lack support for sysenter instruction emulation. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7. A future update may address this issue. Please note that the Red Hat Enterprise Linux with KVM certified guest operating systems do initialize the SYSENTER MSRs and are thus not vulnerable to this issue when running on KVM hypervisor. This issue does not affect the version of samba package as shipped with Red Hat Enterprise Linux 4 and 5. It does affect the version of samba as shipped with Red Hat Enterprise Linux 6 and 7, as well as the version of samba3x shipped with Red Hat Enterprise Linux 5 and the version of samba4 as shipped with Red Hat Enterprise Linux 6. Red Hat Product Security has determined that this vulnerability has Important impact on Red Hat Enterprise Linux 7 because the Samba version shipped in this version of the operating system only executes the vulnerable code after a memory allocation failure, making it more difficult to exploit this flaw. Not vulnerable. This issue does not affect the version of the postgresql package shipped in Red Hat Enterprise Linux 5, 6, and 7 because it does not use the vulnerable implementation of the snprintf() function provided by postgresql; the glibc implementation of this function, which is not vulnerable to this issue, is used instead. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects e2fsprogs packages as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. This issue affects e4fsprogs packages as shipped with Red Hat Enterprise Linux 5. The issue is not planned to be addressed in Red Hat Enterprise Linux 5. This issue did not affect e2fsprogs packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of httpd as shipped with Red Hat Enterprise Linux 4, 5, 6, and 7; JBoss Enterprise Web Server 1 and 2; JBoss Web Server 3; and JBoss Enterprise Application Platform 6. Users of EAP 6.x and 7.0 should upgrade to at least 6.4.9 and pass the following system property on startup to prevent XXE attacks in JSTL: org.apache.taglibs.standard.xml.accessExternalEntity=false For more details please see refer to this KCS solution: https://access.redhat.com/solutions/1584363 Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of xen as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 5 as they did not include the vulnerable code. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise 5 and 6. This issue does affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Future kernel updates for the respective releases may address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue does affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Future updates in the respective releases may address this issue. This issue did not affect any version of Red Hat JBoss Enterprise Application Platform 5 as they did not include the vulnerable version of the RichFaces component. JBoss EAP 5.x includes versions 3.3.1.x of RichFaces; this vulnerability was introduced in version 4.x of RichFaces. This issue did not affect the version of gnutls package as shipped with Red Hat Enterprise Linux 7. This issue affects the version of gnutls package as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue affects the version of gnutls package as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. This issue affects the version of gnutls package as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of Qt as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue does not affect the kernel-xen packages as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects MySQL 5.6.x which are not shipped with these versions of Red Hat Enterprise Linux. Not vulnerable. This issue did not affect the versions of OpenJDK and Oracle JDK as shipped with Red Hat Enterprise Linux. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects MySQL 5.6.x which are not shipped with these versions of Red Hat Enterprise Linux. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects MySQL 5.6.x which are not shipped with these versions of Red Hat Enterprise Linux. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects MySQL 5.6.x which are not shipped with these versions of Red Hat Enterprise Linux. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects MySQL 5.6.x which are not shipped with these versions of Red Hat Enterprise Linux. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects MySQL 5.6.x which are not shipped with these versions of Red Hat Enterprise Linux. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects MySQL 5.6.x which are not shipped with these versions of Red Hat Enterprise Linux. This issue affects the versions of mysql and mysql55 packages as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue affects the version of mariadb and mariadb55 packages as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact, a future update may address this flaw. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects MySQL 5.6.x which are not shipped with these versions of Red Hat Enterprise Linux. This issue affects the versions of mysql and mysql55 packages as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue affects the version of mariadb and mariadb55 packages as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact, a future update may address this flaw. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects MySQL 5.6.x which are not shipped with these versions of Red Hat Enterprise Linux. This issue affects the versions of mysql and mysql55 packages as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue affects the version of mariadb and mariadb55 packages as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact, a future update may address this flaw. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects MySQL 5.6.x which are not shipped with these versions of Red Hat Enterprise Linux. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects MySQL 5.6.x which are not shipped with these versions of Red Hat Enterprise Linux. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects MySQL 5.6.x which are not shipped with these versions of Red Hat Enterprise Linux. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects MySQL 5.6.x which are not shipped with these versions of Red Hat Enterprise Linux. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue affects the verison of wireshark as shipped with Red Hat Enterprsie Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. This issue did not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the verison of wireshark as shipped with Red Hat Enterprsie Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of thunderbird package as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of thunderbird package as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having low security impact, a future update may address this flaw in the libgcrypt and gnupg2 packages. This issue affects the version of hplip as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Low security impact, a future update may address this flaw. Furthermore there is currently no upstream patch available to address this issue. This issue did not affect the versions of squid as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Enterprise Linux 6 ships version 3.1.10 and Red Hat Enterprise Linux 7 ships version 3.3.8 of squide, both of which include the fix for this issue. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue does not affect the version of libpng as shipped with Red Hat Enterprise Linux 5, 6 and 7. For a more detailed explanation please refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1177327#c1 This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the version of cups package as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Important security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the version of cups package as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Important security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. The fix for CVE-2014-9493 is complete and openstack-glance for Red Hat Enterprise Linux Open Stack Platform 4.0 and 5.0 is not affected by this issue. This issue did not affect the version of openstack-glance as shipped with Red Hat Enterprise Linux Open Stack Platform 6.0. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of webkitgtk and webkitgtk3 as shipped with Red Hat Enterprise Linux 6 and 7 respectively. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of webkitgtk and webkitgtk3 as shipped with Red Hat Enterprise Linux 6 and 7 respectively. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having moderate security impact, a future update may address this flaw in libvpx. This issue did not affect the versions of icu as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of icu as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Low security impact. Not vulnerable. This issue does not affect the version of chromium-browser package as shipped with Red Hat Enterprise Linux 6 since this flaw only affects Android versions of the browser. Not vulnerable. This issue did not affect the version of unzip as shipped in Red Hat Enterprise Linux 5, 6, and 7. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code with the flaw is not present in the products listed. This issue did not affect versions of grep as shipped in Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 ships with both bind (9.3) packages which are not affected by this issue, and bind97 packages, which are affected by this issue. Red Hat Enterprise Linux 5 is now in Production Phase 3 of the support and maintenance life cycle. This issue is not currently planned to be addressed in future bind97 updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7 and MRG 2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This problem does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG-2 kernels. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future Linux kernel updates for the respective releases may address this issue. This issue did not affect the versions of facter as shipped with various Red Hat products as they do not use puppet and facter to control Amazon EC2 instances directly. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue did not affect the versions of glibc as shipped with Red Hat Enterprise Linux 5 and 6 as they did use different memory allocation algorithm in swscanf() function. This issue does not affect the version of glibc package as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of openldap as shipped with Red Hat Enterprise Linux 5, 6, and 7 as they did not include support for the deref overlay. Red Hat Product Security has rated this issue as having moderate security impact, a future update may address this flaw in libtiff. This issue did not affect the versions of xen as shipped with Red Hat Enterprise Linux 5. This issue affects e2fsprogs packages as shipped with Red Hat Enterprise Linux 6 and 7. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects e4fsprogs packages as shipped with Red Hat Enterprise Linux 5. The issue is not planned to be addressed in Red Hat Enterprise Linux 5. This issue did not affect e2fsprogs packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6 (as they did not include support for netfilter tables API). This issue affects the versions of the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG 2. Future kernel updates for the respective releases may address this issue. This issue does affect the Linux kernel versions as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates in the respective releases may address this issue. This issue does affect the Linux kernel versions as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rhn-client-tools as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the kvm and qemu-kvm packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of ovirt-engine-backend as shipped with Red Hat Enterprise Virtualization 3. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 5, 6, and 7. Not vulnerable. This issue does not affect the versions of openssl package as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does NOT affect the version of OpenSSL package as shipped with Red Hat Enterprise Linux 5. This issue does NOT affect the version of OpenSSL package as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue does not affect any version of the OpenSSL package as shipped with Red Hat Enterprise Linux 4, 5, 6 and 7, JBoss Enterprise Application Platform 6, Red Hat JBoss Enterprise Web Server 1 and 2, and Red Hat JBoss Web Server 3 because they did not include support for alternative certificate chains. This issue does not affect the version of OpenSSL as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of glusterfs as shipped with Red Hat Enterprise Linux 6, and 7. This issue did not affect the version of ntp as shipped with Red Hat Enterprise Linux 5 This issue does affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, and 7, and Red Hat Enterprise MRG 2. Future Linux kernel updates for the respective releases will address this issue. Red Hat Product Security has rated this issue as having low security impact, a future update may address this flaw in libxml2. Not Vulnerable. This issue only affects struts 2; it does not affect the versions of struts as shipped with various Red Hat products. This issue did not affect versions of salt as shipped with Red Hat Red Hat Ceph Storage as they did not include the vulnerable module. This issue did not affect versions of salt as shipped with Red Hat Red Hat Ceph Storage as they did not include the vulnerable module. Red Hat Product Security has rated this issue as having Important security impact, a future update will address the flaw. As a mitigation against this issue, any system deployed using the affected component should have the 'hacluster' password changed before being placed into production or on an untrusted network. An article with more detailed information is available to customers here: https://access.redhat.com/articles/1396123 Red Hat Product Security has rated this issue as having Low security impact in all supported versions of Red Hat Enterprise Linux OpenStack Platform. While this issue is present, we do not believe the code path is currently reachable in an attacker exploitable fashion. A future update may address this flaw. This issue does not affect the version of 389-ds-base package as shipped with Red Hat Enterprise Linux 6. This issue affects the versions of Ruby as shipped with Red Hat Enterprise Linux 5, 6, and 7, and Red Hat Software Collections. Red Hat Product Security has rated this issue as having Moderate security impact. A future updates may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue does not affect the version of abrt package as shipped with Red Hat Enterprise Linux 6 and 7. Additional information about this is available at https://bugzilla.redhat.com/show_bug.cgi?id=1211223#c7 This issue did not affect the wpa_supplicant versions as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of xdg-utils as shipped with Red Hat Enterprise Linux 6 and 7. CVE-2015-1926 did not affect JBoss Portal Platform as provided by Red Hat. For further detail, refer to the knowledge base article at https://access.redhat.com/solutions/1488163 This issue does not affect the versions of the kernel as shipped with Red Hat Enterprise Linux 5, 6 and 7, MRG and realtime kernels. This issue affects the versions of the kernel as shipped with Red Hat Enterprise Linux 5 and 6 . Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue does not affect the Xen hypervisor as shipped with Red Hat Enterprise Linux 5. This issue does affect the Xen hypervisor as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of libidn as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of jetty as shipped with Red Hat Enterprise Linux 7, versions of openshift-origin-cartridge-fuse as shipped with Red Hat OpenShift Enterprise 2.1, and versions of nutch as shipped with Red Hat Satellite 5. This issue does affect the Dom0 Xen kernel as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does affect the Xen hypervisor packages as shipped with Red Hat Enterprise Linux 5. Future Xen hypervisor packages updates might address this issue. Not vulnerable. This issue did not affect the versions of xen as shipped with Red Hat Enterprise Linux 5 as they did not include affected libxc library. This issue did not affect the versions of pngcrush as shipped with Red Hat Enterprise Linux 7. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6 and 7. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, and 6. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6 and 7. Not vulnerable. The 1.7 and 1.8 versions of Django are not shipped in any Red Hat product as of March 2015. Not vulnerable. This issue did not affect the versions of cups-filters as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of pcre as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of pcre as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue affects the version of webkitgtk3 package as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact, a future update may address this flaw. This issue does not affect the version of webkitgtk package as shipped with Red Hat Enterprise Linux 6. This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 5, 6 and 7, and the versions of libzip as shipped with Red Hat Enterprise Linux 6 and 7. This issue does not affect the current php and php53 packages in Red Hat Enterprise Linux 5 and 6, as it was previously corrected as part of the fix for CVE-2006-7243. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects MySQL 5.6.x which are not shipped with these versions of Red Hat Enterprise Linux. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6 or 7 as it only affects MySQL 5.6.x which are not shipped with these versions of Red Hat Enterprise Linux. This issue affects the versions of mysql and mysql55 packages as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue affects the version of mariadb and mariadb55 packages as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact, a future update may address this flaw. This issue did not affect the versions of mysql or mysql55 as shipped with Red Hat Enterprise Linux 5, 6, or 7 as it only affects MySQL versions shipped on Microsoft Windows. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enteprise MRG 2. Future kernel and kernel-rt updates for Red Hat Enterprise Linux 7 may address this issue. Not vulnerable. This issue does not affect the Linux kernel packages as shipped with Red Hat Entereprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the Linux kernel packages as shipped with Red Hat Entereprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the version of krb5 package as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of krb5 as shipped with Red Hat Enterprise Linux 4, 5, 6, and 7. Not vulnerable. This issue does not affect the version of Firefox and Thunderbird package, as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue affects the version of expat package as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact, a future update may address this flaw. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of thunderbird package, as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of thunderbird package, as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of thunderbird package, as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of thunderbird package, as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of thunderbird package, as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of thunderbird package, as shipped with Red Hat Enterprise Linux 5, 6 and 7. Not vulnerable. This issue does not affect the kernel-xen packages as shipped with Red Hat Enterprise Linux 5. This issue dos affect the kernel-xen packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue dos affect the xen packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of byzanz as shipped with Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having low security impact, a future update may address this flaw in the libtasn1 packages. This flaw is related to the design of the RC4 protocol and not its implementation. Therefore there are no plans to correct this issue in Red Hat Enterprise Linux 5, 6 and 7. Future updates may disable the use of RC4 in various components. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for the respective releases may address this issue. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux Kernel as shipped with Red Hat Enterprise Linux 4, 5, 6 and 7. Red Hat Product Security has rated this issue as having Low security impact. Additionally a workaround is available. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 may address this issue. Red Hat Enterprise Linux 5 is now in Production 3 phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6 and 7 and Red Hat Enterprise MRG 2. Future kernel updates for the respective releases may address this issue. Not vulnerable. This issue did not affect the versions of tcpdump as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include vulnerable code. This issue affects the version of curl package as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This issue is not planned to be addressed in a future update for Red Hat Enterprise Linux 5. Not vulnerable. This issue does not affect the version of curl as shipped with Red Hat Enterprise Linux 5, 6 and 7. Not vulnerable. This issue does not affect the version of curl as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue affects the version of curl package as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This issue is not planned to be addressed in a future update for Red Hat Enterprise Linux 5. This issue affects all versions of mysql and mariadb as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact and are currently awaiting upstream patch to resolve this flaw. Not vulnerable. This issue did not affect the versions of xorg-x11-server as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This flaw has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This flaw has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This flaw has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue does not affect the version of sos package as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect versions of subversion as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of subversion as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the version of OpenSSL as shipped with Red Hat Enterprise Linux 5, 6 and 7. This security flaw can only be exploited when a malicious client negotiates SSLv2 ciphers and completes a SSLv2 handshake. This flaw cannot be actively exploited by a Man-In-The-Middle attacker. All versions of OpenSSL shipped with Red Hat Enterprise Linux enable SSLv2 protocol, but disable SSLv2 ciphers by default (in Red Hat Enterprise Linux 6 and later), therefore are vulnerable to this flaw. Red Hat Product Security has rated this issue as having Low security impact, a future update may address this flaw. SSLv2 suffers from a number of security flaws allowing attackers to capture and alter information passed between a client and the server. Therefore we strongly recommend that SSLv2 should be disabled on all the SSL/TLS servers. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of python-kerberos as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Moderate security impact. Additionally this issue is difficult to exploit in most common scenarios (due to the need for a valid Kerberos TGT)c For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7 as they do not enable the pcnet backend driver. This issue does not affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5, the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. Future updates for the respective releases may address this flaw. Please note that AMD PCNet adapter has to be explicitly enabled per-guest as it is not enabled in default configuration and is not supported by Red Hat in Red Hat Enterprise Linux 6 (for a list of supported devices please consult https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/sect-whitelist-device-options.html). This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the qemu and qemu-kvm packages as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does affect the Red Hat Enterprise Linux 7 qemu-kvm and Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. Future updates for the respective releases may address this flaw. Please note that by default QEMU/KVM guests use in-kernel (KVM) PIT emulation in which case the following applies: This issue does not affect the Linux kernel versions as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise Linux MRG 2. This issue does affect the kvm package as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does affect the virtio-win packages as shipped with Red Hat Enteprise Linux 6 and 7. Future updates for the respective releases will address this issue. This issue does not affect the version of OpenSSL package as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of polkit as shipped with Red Hat Enterprise Linux 6. This issue affects the versions of polkit as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue was correct in Red Hat Enterprise Linux 7 via RHBA-2015:1554. It did not affect the versions of 389-ds-base as shipped with Red Hat Enterprise Linux 6. This issue did not affect the versions of curl as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of curl as shipped with Red Hat Enterprise Linux 5, 6, and 7, as they did not include support for SMB/CIFS. This issue affects the versions of rsyslog as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Additionally a workaround is available (https://bugzilla.redhat.com/show_bug.cgi?id=1232826#c3). Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This vulnerability has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of libuser as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This vulnerability has been rated as having Important security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the version of openhpi as shipped with Red Hat Enterprise Linux 5 and 6. This issue has been rated as having Low security impact and is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 5 and 6. Not vulnerable. This issue does not affect the Xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of openldap package as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of mod_nss as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect any versions of openstack-glance as shipped with any currently supported releases of Red Hat Enterprise Linux OpenStack Platform. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6 since they did not backport the nested NMI handler and espfix64 functionalities. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2 since they did not backport the espfix64 functionality and also did not backport upstream commit e00b12e64be9a3 that allowed an unprivileged local user to re-enable NMIs from the NMI handler. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6 as they did not backport the nested NMI handler functionality. This issue does affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. This issue affected all versions of PHP shipped in various Red Hat products, except version PHP 5.1.x that is shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of gnutls as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of gnutls as shipped with Red Hat Enterprise Linux 7. A further update may address this flaw. This issue affects the versions of the abrt package as shipped with Red Hat Enterprise Linux 6 and 7. This issue did not affect PHP packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6 may address this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue affects the versions of elasticsearch as shipped with Red Hat Satellite 6.x and Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 7 and MRG-2. This issue is not currently planned to be addressed in future Red Hat Enterprise Linux 5 kernel updates. Future Linux kernel updates for other releases may address this issue. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of xen as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of ntp as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of xorg-x11-server as shipped with Red Hat Enterprise Linux 5 and 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue for Red Hat Enterprise Linux 7. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. This issue did not affect the versions of dovecot as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue affects the versions of perl-XML-LibXML as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of squid as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5, the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6 and 7, and the versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. Future updates for the respective releases will address this flaw. Red Hat Product Security has rated this issue as having moderate security impact, a future update may address this flaw in the libtasn1 packages. This issue does not affect the Linux kernel as shipped with Red Hat Enterprise Linux 5. This issue does affect the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for the respective releases will address this issue. Please note that on x86-64 architecture systems the impact is limited to local Denial of Service and that the ping sockets functionality is disabled by default (net.ipv4.ping_group_range sysctl is "1 0"). Not vulnerable. This issue did not affect the versions of stunnel as shipped with Red Hat Enterprise Linux 5, 6, and 7. While this issue does occur in openstack-keystone packages as shipped in Red Hat Enterprise Linux OpenStack Platform versions 5 and 6 it is not believed to be exploitable as access to the keystone logs is restricted with file-system permissions. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of rubygems as shipped with Red Hat Enterprise Linux 6, Red Hat Enterprise MRG 2.5, Red Hat Satellite 6, Red Hat Openstack 5, Red Hat Openshift Enterprise 2 as they did not include support for getting API endpoint using SRV DNS records. This issue did not affect the versions of ruby as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include support for getting API endpoint using SRV DNS records. The issue did not affect version of ruby as shipped with Red Hat Enterprise Linux 7, as the support for getting API endpoint using SRV DNS records is included, but inactive. This issue did not affect the versions of ruby193-ruby as shipped with Red Hat Subscription Asset Manager and Red Hat Software Collections as they did not include support for getting API endpoint using SRV DNS records. The issue did not affect version of ruby200-ruby as shipped with Red Hat Software Collections, as the support for getting API endpoint using SRV DNS records is included, but inactive. Red Hat Product Security has rated this issue as having moderate security impact, a future update may address this flaw in t1utils. Not vulnerable. The 1.8 version of Django is not shipped in any Red Hat product. This issue affects the version of openssl and nss libraries as shipped with Red Hat Enterprise Linux 4, 5, 6 and 7. More information about this flaw is available at: https://bugzilla.redhat.com/show_bug.cgi?id=1223211#c4 and https://bugzilla.redhat.com/show_bug.cgi?id=1223211#c5. Red Hat Enterprise Linux 4 is in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 4. This issue did not affect the versions of rubygems as shipped with Red Hat Enterprise Linux 6, Red Hat Enterprise MRG 2.5, Red Hat Satellite 6, Red Hat Openstack 5, Red Hat Openshift Enterprise 2, as the packages did not include the incomplete fix. This issue did not affect the versions of ruby as shipped with Red Hat Enterprise Linux 5, 6 and 7, Red Hat Subscription Asset Manager and Red Hat Software Collections, as the packages did not include the incomplete fix. This issue affects the versions of xz as shipped with Red Hat Enterprise Linux 5 and 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and 7, and Red Hat Enterprise MRG as they do not have CONFIG_VHOST_SCSI directive enabled in the build configuration. This issue affects the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5, the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6 and 7, and the versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ This issue does affect then Xen packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does affect then Xen packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does affect then Xen packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does affect then Xen packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux versions 5, 6, and 7. Not vulnerable. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6, and 7. Not vulnerable. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6, and 7. Not vulnerable. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6, and 7. Not vulnerable. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6, and 7. Not vulnerable. This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5. This issue does affect the Xen hypervisor packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of elasticsearch as shipped with Red Hat Satellite 6.x and Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6. This issue affects the Linux kernel packages kernel as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. This issue did not affect the versions of strongimcv as shipped with Red Hat Enterprise Linux 7 as they did not include support for IKEv2. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6, MRG-2, realtime and arm-kernels. The issue is not currently planned to be addressed in Red Hat Enterprise Linux 7. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6, 7, MRG-2, realtime and arm-kernels. This issue affects the versions of rubygem-moped as shipped with Red Hat OpenShift Enterprise 2.x. Red Hat Product Security has rated this issue as having Low security impact on Red Hat OpenShift Enterprise 2. Additionally access to the component using rubygem-moped is restricted, only trusted users and systems can send messages, thus no trust boundary violation occurs and this issue can not easily be used to create an exploitable security vulnerability on Red Hat OpenShift Enterprise 2. This issue affects the versions of rubygem-moped as shipped with Red Hat OpenShift Enterprise 2.x. Red Hat Product Security has rated this issue as having Low security impact. Additionally access to the component using rubygem-moped is restricted, only trusted users and systems can send messages, thus no trust boundary violation occurs and this issue can not easily be used to create an exploitable security vulnerability on Red Hat OpenShift Enterprise 2. This issue affects the versions of rubygem-bson as shipped with Red Hat OpenShift Enterprise 2.x. Red Hat Product Security has rated this issue as having Low security impact on Red Hat OpenShift Enterprise 2. Additionally access to the component using rubygem-moped is restricted, only trusted users and systems can send messages, thus no trust boundary violation occurs and this issue can not easily be used to create an exploitable security vulnerability on Red Hat OpenShift Enterprise 2. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of gdk-pixbuf as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of bind packages as shipped with Red Hat Enterprise Linux 4 and 5. This issue affects the versions of bind97 packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Important security impact and is not currently planned to be addressed in future bind97 packages updates in Red Hat Enterprise Linux 5. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not planned to be corrected in future updates for php packages in Red Hat Enterprise Linux 6 and 7, and php53 packages in Red Hat Enterprise Linux 5. The php packages in Red Hat Enterprise Linux 5 were not affected by this issue. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the version of the kernel package as shipped with Red Hat Enterprise Linux 7. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5 and 6 as it does not contain the affected code. This does not affect the Red Hat Enterprise MRG 2 as it does not enable the affected code at compile time. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 7. This issue did not affect the versions of flash-plugin as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the version of python-django as included with Red Hat Enterprise Linux OpenStack Platform 5 and 6 however there is no known security impact in a supported use-case at this time. A future update may address this issue. This issue affects the versions of foreman as shipped with Red Hat Satellite 6 and OpenStack. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5, the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6 and the Red Hat Enterprise Linux 6 based qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3, because they did not backport the upstream commit that introduced this issue. This issue does affect the versions of qemu-kvm packages as shipped with Red Hat Enterprise Linux 7 and versions of Red Hat Enterprise Linux 7 based qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. Future updates for the respective releases will address this flaw. This issue did not affect the Linux kernel packages as shipped with Red Hat Enterprise MRG 2. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future updates in the respective releases may address this flaw. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the versions of kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6 and 7. This issue does not affect the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates of Enterprise Linux 6. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6 and 7. This issue affects the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ This issue does not affect the versions of kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6. This issue does not affect the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue does not affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the qemu-kvm-rhev packages as shipped with any currently supported versions of Red Hat Enterprise Linux OpenStack Platform. This issue affects the versions of sblim-sfcb as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue was fixed in RHSA-2015-2527 (https://rhn.redhat.com/errata/RHEA-2015-2527.html) in the rhev-hypervisor package. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of util-linux as shipped with Red Hat Enterprise Linux 5 and 7. This issue does not affect the versions of util-linux-ng as shipped with Red Hat Enterprise Linux 6. This issue does not affect the versions of kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6 and 7. This issue does not affect the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. Future updates for this release may address this flaw. This issue affects the versions of kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6 and 7. This issue affects the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. A malicious message producer needs to authenticate to EAP in order to send messages. Also, the use of JMS ObjectMessage needs to be chosen by the developer of the application. Therefore this issue is rated as moderate. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6 and 7. This issue affects the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the versions of kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6. This issue affects the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue does not affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the versions of foreman as shipped with Red Hat Satellite 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6 and 7. Due to the limited security impact the issue is currently not planned to be addressed in Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of ipa as shipped with Red Hat Enterprise Linux 6 and 7 as they did not include the affected KRA subsystem. This issue affects the versions of vdsm as shipped in Red Hat Enterprise Virtualization 3.x. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the version of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6 and 7. Future kernel updates for the respective releases may address this issue. Red Hat Enterprise Linux 5 is now in Production Phase 3 of the support and maintenance life cycle. Thus it is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Not vulnerable. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6, and 7 as they do not include the WNM functionality. This issue affects the versions of libvirt as shipped with Red Hat Enterprise Linux version 7 and Red Hat Gluster Storage 3.1. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6, and 7. Not vulnerable. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2, as the code introduced the flaw is not present in these products. This issue does not affect the version of openssh package as shipped with Red Hat Enterprise Linux 7. This issue affects the version of openssh package as shipped with Red Hat Enterprise Linux 5 and 6. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. This issue affects the versions of elasticsearch as shipped with Red Hat Satellite 6.x and Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of nodejs as shipped with various Red Hat Enterprise products. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of tidy as shipped with Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of tidy as shipped with Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of elasticsearch as shipped with Red Hat Satellite 6.x and Subscription Asset Manager 1.x. This issue does not affect the default OpenSSH sshd configuration in Red Hat Enterprise Linux 4, 5, 6 and 7. This issue has been fixed in all versions of Dojo in all Red Hat products. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6, 7, MRG-2 and realtime and may be addressed in a future update. This issue does not affect any shipping versions of Red Hat Enterprise Linux kernels. The patch causing the incorrect "double put" condition is not applied to any shipping kernel. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 6, 7 MRG-2 and realtime kernels and does not plan be addressed in a future update. This issue does not affect the versions of kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6 and 7. This issue affects the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of Bind as shipped with Red Hat Enterprise Linux 4, 5, 6 and 7 as they did not include support for fromwire_openpgpkey(). This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue affects the verison of wireshark as shipped with Red Hat Enterprsie Linux 5 and 6. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 5 and 6. This issue did not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5. This issue affects the verison of wireshark as shipped with Red Hat Enterprise Linux 6. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 6. This issue did not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5. This issue affects the verison of wireshark as shipped with Red Hat Enterprise Linux 6. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 6. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue affects the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of gnutls as shipped with Red Hat Enterprise Linux 4, 5, and 6. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5. This issue has been rated as having Low impact, affects the Linux kernels as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2 and is currently not planned to be addressed in a future updates. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 7 and may be addressed in a future update. This issue did not affect the versions of php and php53 as shipped with Red Hat Enterprise Linux 5 and the versions of php as shipped with Red Hat Enterprise Linux 6 and 7. This issue did not affect the versions of openssh as shipped with Red Hat Enterprise Linux 5, 6, and 7. Not vulnerable. This issue did not affect the versions of openjpeg as shipped with Red Hat Enterprise Linux 6 and 7. Not vulnerable. This issue does not affect the Xen hypervisor packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect Red Hat Enterprise Linux 6, 7 or any other Red Hat supported product because of the lack of Xen hypervisor support. This issue did not affect the versions of nodejs as shipped with Red Hat Enterprise Software Collections version 2, Red Hat OpenStack Platform and Red Hat Openshift Enterprise and Openshift Online as they do not include the vulnerable version of nodejs. This issue affects the versions of kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6 and 7. This issue affects the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue did not affect the versions of PHP as shipped with Red Hat Enterprise Linux 5 and 6. This issue is not currently planned to be corrected in future updates in Red Hat Enterprise Linux 7 and Red Hat Software Collections. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6 and 7. This issue affects the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue did not affect kernel, kernel-rt, and realtime-kernel versions shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG as they do not include the Reliable Datagram Sockets (RDS) protocol implementation. This issue did not affect the versions of sqlite as shipped with Red Hat Enterprise Linux 5 and 6. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of firefox as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue affects the versions of kvm package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6 and 7. This issue affects the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. Not vulnerable. This issue does not affect the versions of the xen package as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of Node.js as shipped in any Red Hat product. This issue affects the Apache commons-collections library as shipped with Fuse 6.2.0 and A-MQ 6.2.0. However, this flaw is not known to be exploitable under supported scenarios in these product versions, and so has been assigned an impact of Important for these products and their respective errata. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7 as they do not enable the pcnet backend driver. This issue does not affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5, the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. Future updates for the respective releases may address this flaw. Please note that AMD PCNet adapter has to be explicitly enabled per-guest as it is not enabled in default configuration and is not supported by Red Hat in Red Hat Enterprise Linux 6 (for a list of supported devices please consult https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/sect-whitelist-device-options.html). Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. Though this has been rated as having Important security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This problem did not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. This issue is not planned to be corrected in future updates for Red Hat Enterprise Linux 5. This issue is rated low as exploiting it requires physical (to plug in specially prepared usb disk) or root (to mount specially prepared filesystem) access to the system. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. This issue did not affect the versions of systemd as shipped with Red Hat Enterprise Linux 7. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7 as they do not enable the pcnet backend driver. This issue does not affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5, the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. Future updates for the respective releases may address this flaw. Please note that AMD PCNet adapter has to be explicitly enabled per-guest as it is not enabled in default configuration and is not supported by Red Hat in Red Hat Enterprise Linux 6 (for a list of supported devices please consult https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/sect-whitelist-device-options.html). Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. Though this has been rated as having Important security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2, as the driver with the flaw is present in the products listed. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. After updating the glibc package on affected systems, it is strongly recommended to reboot the system or restart all the affected services. For more information please refer to: https://access.redhat.com/articles/2161461 This issue does not affect the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue affects the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 5,6 and 7 and may be addressed in a future update. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect Red Hat Enterprise Linux 5 and 6. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 7, kernel-rt and Red Hat Enterprise MRG 2 and may be addressed in a future update. This issue affects the versions of giflib as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7, and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat MRG 2 kernels. Future kernel updates for the respective releases may address this issue. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6.4, as they do not include support for KoD packets. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact as privileged access is required to exploit it, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 7, kernel-rt and MRG-2. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6, and 7, as they do not include the affected functionality. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6, and 7 as these version do not include the affected code. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue only affected OpenVMS operating systems, which use characters other than "/" and "\" for directory separation, allowing exploitation of this flaw. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6, and 7 as they do not include the custom refclock driver. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6, and 7 as they do not include support for the mrulist feature, which exposes the decodenetnum() function. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 6 , 7 and Red Hat MRG 2. Future updates for the respective releases may address this flaw. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code with the flaw is not present in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code with the flaw is not present in the products listed. This issue affects the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue in Red Hat Enterprise Linux 6 and 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6, and 7 as they do not include the affected code, which was introduced in version 4.2.8 of NTP. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue in Red Hat Enterprise Linux 6 and 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue in Red Hat Enterprise Linux 6 and 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue in Red Hat Enterprise Linux 6 and 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects Red Hat enterprise Linux 5 and 6. The affected code is not available in 7, MRG and realtime kernels. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2, as the code introduced the flaw is not present in these products. This issue did not affect the versions of strongimcv as shipped with Red Hat Enterprise Linux 7, as they did not include support for the eap-mschapv2 plugin. This issue did not affect the versions of nodejs as shipped with Red Hat Enterprise Software Collections version 2, Red Hat OpenStack Platform and Red Hat Openshift Enterprise and Openshift Online as they do not include the vulnerable version of nodejs. This issue did not affect the versions of libxml2 as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include support for LZMA compression support. Not vulnerable. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6 and 7. Not vulnerable. This issue did not affect the versions of cyrus-imapd as shipped with Red Hat Enterprise Linux 5, 6 and 7, as they did not include the patch to fix CVE-2015-8076, which introduced the CVE-2015-8077 issue. Not vulnerable. This issue did not affect the versions of cyrus-imapd as shipped with Red Hat Enterprise Linux 5, 6 and 7, as they did not include the patch to fix CVE-2015-8076, which introduced the CVE-2015-8078 issue. This issue affects the version of the kvm & xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6 and 7. Future kernel updates for the respective releases may address this issue. Red Hat Enterprise Linux 5 is now in Production Phase 3 of the support and maintenance life cycle. Thus it is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5 as they do not include the affected code, which was introduced in version 4.2.6 of NTP. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2 as this flaw was fixed in the recent releases. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6. Future updates for the respective releases may address the issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 5. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This problem did not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 7 and MRG-2. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, and 7, Red Hat Enterprise MRG 2, and realtime kernels. At the time of writing, XEN on Red Hat Enterprise Linux 5 did not support ARM guests. XEN was not available on versions Red Hat Enterprise Linux 6 and 7, Red Hat Enterprise MRG 2, and realtime kernels. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7, MRG-2 and realtime kernels. At this time, there is no plans to fix this issue, if you feel that this issue is affecting your deployment and have an EUS subscription, please contact support to have this issue correctly prioritized This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7, MRG-2 and realtime kernels. At this time, there is no plans to fix this issue, if you feel that this issue is affecting your deployment and have an EUS subscription, please contact support to have this issue correctly prioritized This issue affects the kvm package as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6 and 7. This issue affects the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6 and is not currently planned to be addressed in future updates. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue affects the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4 and 5. This issue does affect the kernels shipped with Red Hat Enterprise Linux 6, 7, MRG-2 and realtime kernels and plans to be addressed in a future update. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future updates for the respective releases may address the issue. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 5. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does affect the Dom0 Xen kernel as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue does not affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue affects the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue affects the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue affects the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue is not planned to be addressed in the dhcp packages as shipped with Red Hat Enterprise Linux 5, 6, or 7, as the problem can not be triggered with those packages. For further technical details, refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1297314#c5 This issue does not affect the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue affects the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue affects the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2 as the due updates to fix this issue have been shipped now. This issue does not affect the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue does not affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue does not affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue affects the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue does not affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ This issue does not affect the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue does not affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue does not affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future updates for the respective releases may address the issue. Red Hat Enterprise Linux OpenStack Platform does not support the Xen hypervisor, and is therefore not affected by this flaw in any supported configuration. This issue did not affect the versions of jasper as shipped with Red Hat Enterprise Linux 6 and 7 as it was already fixed via CVE-2008-3520. This issue affects the version of freeradius as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. This issue affects the version of freeradius as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. This issue affects the version of freeradius as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2 and may be addressed in future updates. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 6 and 7 and does not plan to be fixed in future updates. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code with the flaw is not present in the products listed. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6 and 7 and Red Hat Enterprise MRG 2 and realtime kernels and may be addressed in a future update. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates in Red Hat Enterprise Linux 5 and 6 . For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7, and Red Hat Enterprise MRG 2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, as the related AIO vector code is not present in this product. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 7 and MRG-2 kernels. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5 and 6, This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 7 and MRG-2 realtime kernels. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ . This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5 and 6, This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 7 and MRG-2 realtime kernels. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ . Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue doesn't affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5,6,7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect any shiping version of Red Hat Enterprise Linux. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. 6, 7 and Red Hat Enterprise MRG-2 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG-2. Future Linux kernel updates for the respective releases might address this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG 2.x. This issue has been rated as having moderate security impact. This issue affects the Linux kernel shipping with Red Hat Enterprise Linux 6. Future updates for the respective releases may address the issue. This issue does not not affect Red Hat Enterprise Linux 5, 7, MRG-2 kernels. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 5. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG-2 as the code with the flaw is not built in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as code with the flaw is not present in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG-2 as code with the flaw is not built and shipped in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code with the flaw is not present in this product. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2 as the fix for this flaw is already present in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux. The xslt random function provided by libxslt does not offer any security or cryptography guarantees. Applications using libxslt that rely on non-repeatable randomness should be seeding the system PRNG (srand()) themselves, as they would if calling rand() directly. The Red Hat Product Security Team does not consider this issue as a security flaw because specially crafted PHP scripts (containing embedded operating system commands) are required to trigger this flaw. This issue affects the versions of libXcursor as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2, as the code with the flaw is not present in the products listed. OpenSSL 1.0.2 provides support for generating X9.42 style parameter files. This feature does not exist in any previous versions of OpenSSL. Therefore versions of OpenSSL shipped with Red Hat Enterprise Linux 5, 6, and 7, and JBoss EAP and JBoss Web Server are not vulnerable to this security flaw. Versions of OpenSSL shipped in Red Hat Enterprise Linux do not enable the SSL_OP_SINGLE_DH_USE option. However, most applications do not use SSL_CTX_set_tmp_dh()/SSL_set_tmp_dh(). Most of them use SSL_CTX_set_tmp_dh_callback()/SSL_set_tmp_dh_callback() without setting the key. This has the same effect as setting SSL_OP_SINGLE_DH_USE. This issue is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 6, as the web UI functionality is disabled by default in pcsd. This issue is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 6, as the web UI functionality is disabled by default in pcsd. This issue affects kernels in Red Hat Enterprise Linux 5, 6 and 7. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6, or 7. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5 and 6. Refer to https://access.redhat.com/node/2131021 for further information. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. This issue does not affect the version OpenSSH as shipped with Red Hat Enterprise Linux 4, 5 and 6. This issue affects the version of OpenSSH as shipped with Red Hat Enterprise Linux 7 in a non-default configuration. For more information please refer to https://access.redhat.com/articles/2123781 Only Wildfly application servers running on Windows operating systems are affected; no versions of Red Hat JBoss EAP or layered products are affected. This issue does not affect the version of OpenSSL shipped with Red Hat Enterprise Linux 5, 6 and 7, since these packages are compiled without SRP support. The original issue fixed by OpenSSL upstream contains two distinct fixes. The first one is a format string flaw in the internal fmtstr functions, which may result in a OOB read flaw when printing very large string. This issue was assigned CVE-2016-0799 The second issue relates to the internal doapr_outch function of OpenSSL. It can result in an OOB write, or cause memory leaks. This issue has been assigned CVE-2016-2842 by MITRE as is now tracked as https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-2842 This issue affects versions of the kernel shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 realtime kernels. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ . This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5. This has been rated as having Low security impact and is not currently planned to be addressed in future updates of 6, 7, and MRG-2. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ . Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of nodejs-ws as shipped with Red Hat OpenShift Enterprise 2. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue is addressed through the Apache HTTPD update for CVE-2016-5387 which prevent the Proxy header from automatically being converted into the HTTP_PROXY environmental variable. Unless the "FcgidPassHeader Proxy" is used mod_fcgid is not vulnerable to this attack when used with updated HTTPD. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of python-twisted as shipped with Red Hat Satellite 6.x. However due to the manner in which python-twisted is used exploitation of this issue by an attacker would require significant access to the server, or be able to modify requests from other users via additional vulnerabilities. A future update may address this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Low. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Low. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. In order to exploit this flaw, the attacker needs to have control of the forwarded agent-socket and the ability to write to the filesystem of the host running ssh-agent. Because of this restriction for successful exploitation, this issue has been rated as having Moderate security impact. A future update may address this flaw. It seems that this flaw is not practically exploitable, the leak of host private key material to the privilege-separated child processes is theoretical. No such leak was observed in practice for normal-sized keys, nor does a leak to the child processes directly expose key material to unprivileged users. Because of the this restriction for successful exploitation, this issue has been rated as having Low security impact. A future update may address this flaw. In order to exploit this flaw, the attacker needs to first compromise the sandboxed privilege-separation process by using another security flaw. Because of this restriction for successful exploitation, this issue has been rated as having Low security impact. A future update to Red Hat Enterprise Linux 7 will address this flaw. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code which can trigger the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This flaw resides in the XML Security Library (xmlsec1) and will be updated there; Red Hat OpenStack Platform is not affected. This issue affects the Linux kernel shipping with Red Hat Enterprise Linux 7 and MRG-2 prior to 2.6.32-440. Versions after this release have the solution applied. This issue also affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6. Future updates for the respective releases may address the issue. This issue does not not affect Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 5. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG-2 as the flaw is not present in the products listed. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygem-archive-tar-minitar as shipped with Red Hat Satellite 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update will not address this issue as the software is planned to be removed in a future version of Satellite 6. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7, MRG-2 and realtime kernels. This has been rated as having Moderate security impact and is currently planned to be addressed in future updates. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code that introduced the flaw is not present in these products. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7, Red Hat Enterprise MRG 2, and realtime kernels as these contain the fixed commit. This issue does not affect Red Hat Enterprise Linux 5, 6 and 7, MRG and realtime kernels. This issue does not appear to affect the versions of Kibana as shipped with Red Hat Openshift Enterprise. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ and Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The fibjs NPM module is not used in any Red Hat products. This issue affects the versions of openssh as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7 (versions 7.3 and earlier). For Red Hat Enterprise Linux 7 (versions 7.4 and later), this issue was fixed by the Security Advisory RHSA-2017:2029. For Red Hat Enterprise Linux 6, Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of evolution-data-server as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include the vulnerable code. This issue affects the version of struts shipped with Red Hat Enterprise Linux 5, which is currently in Extended Life Phase. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification https://access.redhat.com/security/updates/classification/ and the Red Hat Enterprise Linux Life Cycle https://access.redhat.com/support/policy/updates/errata/. This issue affects the version of struts shipped with Red Hat Enterprise Linux 5, which is currently in Extended Life Phase. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification https://access.redhat.com/security/updates/classification/ and the Red Hat Enterprise Linux Life Cycle https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect any of Red Hat's shipping products. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the version of exim as shipped with Red Hat Enterprise Linux 4 and 5. However, the default configurations are not affected, as they do not use 'perl_startup' directive. Red Hat Enterprise Linux 4 is now in Extended Life Cycle phase of the support and maintenance life cycle, and Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Low security impact: to exploit this issue, an attacker must have access to a trustedkey if one is configured in the /etc/ntp.key file. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6, and 7 as the Linux kernel drops packets from 127.0.0.0/8, mitigating this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Not vulnerable. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 5 and 6 and may addressed in a future update. This issue does not affect the versions of the kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6, and the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 7. This issue affects the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the versions of Firefox shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue affects the versions of kvm and xen packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the qemu-kvm packages as shipped with Red Hat Enterprise Linux 6 and 7. This issue affects the Red Hat Enterprise Linux 6 based versions of qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This issue affect the Red Hat Enterprise Linux 7 based versions of the qemu-kvm-rhev packages as shipped with Red Hat Enterprise Virtualization 3. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of libdwarf as shipped with Red Hat Enterprise Linux 7. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4, 5 and 6. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 7, MRG and realtime kernels. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code with the flaw is not present in the products listed. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4,5 and 6. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 7 and kernel-rt packages and does not plan to be addressed in a future update. This issue did not affect the versions of bind97 as shipped with Red Hat Enterprise Linux 5 and bind as shipped with Red Hat Enterprise Linux 5, 6, and 7 as they did not include support for DNS cookies. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code with the flaw is not present in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 6 as the suspected driver does not advertise that it has scatter-gather feature, which presence is essential for the flaw. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2, namely the [atl2] Ethernet driver which is the only driver affected. Future Linux kernel updates for the respective releases might address this issue. Red Hat Enterprise Linux 5, 6 and 7 are not affected by this flaw because we do not ship Samba with the AD DNS Server, which is the vulnerable component. This issue affects the versions of qpid-proton as shipped with Red Hat Satellite version 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. OpenSSL security update RHSA-2016:1940 mitigates this issue by lowering priority of DES cipher suites so they are not preferred over cipher suites using AES. For compatibility reasons, DES cipher suites remain enabled by default and included in the set of cipher suites identified by the HIGH cipher string. Future updates may move them to MEDIUM or not enable them by default. NSS addressed this issue by implementing limits on the amount of plain text which can be encrypted by using the same key. Once the limit is reached, the keys will need to be re-negotiated manually. This change will be available in nss-3.27. GnuTLS is not affected by this issue, since it prioritizes AES before 3DES in the cipher list. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Important security impact. For additional information, refer to the Red Hat Knowledgebase article: https://access.redhat.com/articles/2201201 Red Hat Product Security has rated these issues as having Important security impact. For additional information, refer to the Red Hat Knowledgebase article: https://access.redhat.com/articles/2201201 This issue did not affect the versions of ruby as shipped with Red Hat Enterprise Linux or Red Hat Software Collections as they did not include support for OLE. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2, as the code with the flaw is not present in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future updates for the respective releases may address the issue. This issue did not affect the versions of squid as shipped with Red Hat Enterprise Linux versions 5, 6 and 7, as they are not shipped with a vulnerable version of squid, and no currently backported patch would introduce the bug. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Low security impact. Additionally nodejs-hawk is only present as a BuildRequires dependency in the nodejs-request package, the actual hawk functionality is not used in OpenShift Enterprise 3. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security does not consider this to be a security issue. An authenticated user could use various other means to disable access to an NTP server (for example, using the 'restrict' command). To mitigate this issue, disable remote configuration of NTP, or restrict this ability to trusted users. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2, as the flaw was already fixed in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. This issue affects the versions of polkit as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of util-linux as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of coreutils as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of Puppet as shipped with various Red Hat products as they did not include support Puppet 3.x (using Passenger 4.x). This issue affects Red Hat Enterprise OpenShift 2. Red Hat Product Security has rated this issue as having Moderate security impact. A futur e update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future updates for the respective releases may address the issue. Not Vulnerable. This issue affects Struts 2 only; it does not affect the versions of struts as shipped with various Red Hat products. Not Vulnerable. This issue affects Struts 2 only; it does not affect the versions of struts as shipped with various Red Hat products. Not Vulnerable. This issue affects Struts 2 only; it does not affect the versions of struts as shipped with various Red Hat products. Not Vulnerable. This issue affects Struts 2 only; it does not affect the versions of struts as shipped with various Red Hat products. This issue affects the versions of qpid-java as shipped with Red Hat Satellite 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of pulp as shipped with Red Hat Satellite 6.x and Red Hat Update Infrastructure 2.x as they did not include support for pulp-gen-ca-certificate. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6. This issue is not currently planned to be addressed in future updates, as user namespaces which the flaw affects are not supported in these products. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, as the code with the flaw is not present in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2, as 32-bit versions of the products listed are not shipped by the Red Hat. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates, as the Linux containers which the flaw affects are not supported in these products. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the Xen hypervisor packages as shipped with Red Hat Enterprise Linux 5. This issue does not affect the Xen hypervisor packages as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of giflib as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 6 and 7. This issue did not affect the versions of compat-libtiff3 as shipped with Red Hat Enterprise Linux 7, as they did not include the bmp2tiff tool. This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 6 and 7. This issue did not affect the versions of compat-libtiff3 as shipped with Red Hat Enterprise Linux 7, as they did not include the bmp2tiff tool. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of compat-libtiff3 as shipped with Red Hat Enterprise Linux 7. This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of compat-libtiff3 as shipped with Red Hat Enterprise Linux 7. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue affects the Linux kernel-rt packages as shipped with Red Hat Enterprise Linux 7 and MRG-2 and may be addressed in a future update. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. It is not feasible to correct this issue with a code change as client SSL certificates need to be created in order to support client authentication. The installation documentation notes how to mitigate this through the creation of certificates to support SSL authentication. This mitigation is the best way to correct this issue and, as a result, we will not be releasing any patches to correct the issue. This issue affects Red Hat Enterprise Linux 6 and 7 kernels. This issue was fixed in a version 6 prior to this issue being raised. As this issue is rated as important, it has been scheduled to be fixed in a future version of Red Hat Enterprise Linux 7. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. 6, 7 and Red Hat Enterprise MRG-2 as the code with the flaw is not present in the products listed. This issue did not affect the versions of squid as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include support for ICMP pinging and the 'pinger' binary. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having low security impact, a future update may address this flaw in libksba. Red Hat Product Security has rated this issue as having moderate security impact, a future update may address this flaw in libksba. Red Hat Product Security has rated this issue as having moderate security impact, a future update may address this flaw in libksba. Red Hat Product Security has rated this issue as having moderate security impact, a future update may address this flaw in libksba. Red Hat Product Security has rated this issue as having Low security impact, a future update may address this flaw. This issue did not affect the versions of the qpid -java broker as shipped with Red Hat MRG 2 and 3 and Satellite 6 as they did not use the access feature (e.g. Satellite 6 relies on client certificate authentication to control access). This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ and Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 6 and may be addressed in a future update. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2 as the due updates to fix this issue have been shipped now. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. When a specially-crafted XML file is parsed via an application compiled against libxml2, this can cause the application to crash. (No code execution) In Red Hat Enterprise Linux and Fedora, the scripts used during boot time to ask for user password and decrypt the drive are part of the dracut package. They used to generate the Initial ramdisk (initramfs) and are a part of the initramfs image file. The attacker needs to have physical access to the machine in order to exploit this flaw. The attack consists of gaining access to the shell after wrong luks password has been entered during the boot process. Once shell access is obtained various brute force attacks (both manual and automated) can be carried out. The contents of the drive can also be copied off to do conduct offline brute force attacks on another computer. Red Hat Product Security encourages users of Red Hat Enterprise Linux 6 and 7 to use the mitigation described in the link below. No updated packages are currently available. For more information please refer to: https://access.redhat.com/articles/2786581 This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the related code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4, 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, as there is no user namespace support in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4, 5 and 6. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 7 and MRG-2 and may be addressed in a future update. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 6, 7 realtime and MRG-2 kernels and does not plan to be addressed in a future update This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2, as there is no code which introduced the flaw in the products listed. This issue did not affect the versions of ntp as shipped with any Red Hat Enterprise Linux version as they already included a fix for this issue in the patch provided to fix the CVE-2015-7979 issue. The fix for this issue (developed by Red Hat) was different from the one provided by upstream, and thus ntp versions in RHEL are not affected by CVE-2016-4953. This issue did not affect the versions of ntp as shipped with any Red Hat Enterprise Linux version as they did not include the same upstream fix for CVE-2016-1547 that introduced the issue. The fix developed by Red Hat for CVE-2016-1547 did not include this issue. Red Hat OpenStack Platform and Red Hat Enterprise Linux OpenStack Platform do not include or support openstack-murano, and are therefore not affected by this flaw in any supported configuration. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 7, MRG-2 and realtime and will be addressed in a future update. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG 2.x. This issue has been rated as having Important security impact. Updates for each affected version are in progress and will be released as soon as possible. Shipping versions of Fedora are affected and Fedora is aware of this flaw. For additional information about this flaw, please see https://access.redhat.com/security/vulnerabilities/2706661 This issue does not affect Red Hat Enterprise Linux 5,6 or 7 kernels as it does not contain the code that has introduced the flaw. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 5 and 6 and will not be addressed in a future update. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 7, Realtime and Red Hat Enterprise MRG 2. This has been rated as having low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ . This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This is a protocol flaw which affects IKEv1. All complaint implementations are therefore affected by this flaw. Red Hat Product Security team, does not consider IKEv2 to be affected. For more details please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1308508#c2 libthrift is a library used by OpenDaylight which is shipped with Red Hat OpenStack. Whilst the version of the library used contains the vulnerable code it is not used by OpenDaylight and hence not exposed. JBoss fuse 6.3 ships libthrift via insight-activemq fabric-8 profile, however the vulnerable code is not used by fabric-8 so fuse 6.3 is not affected. Red Hat Enterprise Linux is not affected by this flaw as this module is not available in shipping source code. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the version of the kernel packages as shipped with Red Hat Enterprise Linux 7. Future kernel updates for Red Hat Enterprise Linux 7 may address this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4 and 5. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4, 5, 6, 7 and Red Hat Enterprise MRG 2. This issue did not affect the versions of kexec-tools as shipped with Red Hat Enterprise Linux 5, 6, and 7. The versions of PHP package shipped with Red Hat Enterprise Linux, do not have support for mcrypt. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the version of the kernel packages as shipped with Red Hat Enterprise Linux 7. Future kernel updates for Red Hat Enterprise Linux 7 may address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2 and may be addressed in future updates. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7. This security flaw is addressed by the patch released for CVE-2016-5320. Therefore Red Hat Enterprise Linux packages are not affected. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and 7. This has been rated as having Moderate security impact and is planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. This issue does not affect Red Hat Enterprise Linux products as they have not included this feature in any shipping products. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux is not affected by this flaw as CONFIG_SECURITY_APPARMOR is not enabled in any current shipping kernels. This issue is not present in the Linux kernel packages as shipped with Red Hat Enterprise Linux versions 5 and 6. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. This issue is not present in the Linux kernel packages as shipped with Red Hat Enterprise Linux versions 5 and 6. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. This issue in OpenSSH is mitigated by the usage of SELinux in Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as of now due to the absence of unprivileged mount name spaces support. Nevertheless, the unprivileged mount name spaces might be added to a future RHEL-7 version as a supported feature, so future Linux kernel updates for the respective releases might address this issue. Not vulnerable. This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 4, 5, 6, and 7, as they did not include support for MDC-2. TLS server applications using OpenSSL versions in Red Hat Enterprise Linux 6 and 7 are only affected if they enable OCSP stapling support. Applications not enabling OCSP stapling support are not affected. Few applications implement OCSP stapling support and typically do not enable it by default. This issue did not affect any Red Hat product as they do not yet include OpenSSL 1.1.0. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact, a future update may address this flaw. This issue did not affect the versions of star as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue affects Red Hat Enterprise Linux 7 and MRG-2 kernels and will be addressed in a future update. This issue does not affect Red Hat Enterprise Linux 5 and 6 systems. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue was fixed in EAP 7.1.0, but was not fixed in 7.0.7 This issue affects the versions of RESTEasy as shipped with Red Hat Satellite 6. Red Hat Product Security has rated this issue as having a security impact of Moderate. Additionally Red Hat Satellite does not use the default ExceptionMapper, and the custom exception handler does not allow return type of text/html. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG-2 as the products listed does not contain the code (kernel mediatek driver) with the flaw. This issue in OpenSSH is mitigated by the usage of SELinux in Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7. All MySQL and MariaDB packages in Red Hat Enterprise Linux and Red Hat Software Collections install the my.cnf configuration file in /etc as root-owned and not writeable to mysqld's mysql user. This default configuration stops the published exploit for this issue. All MySQL and MariaDB packages for Red Hat Enterprise Linux 7 (either those directly included in Red Hat Enterprise Linux 7 or from Red Hat Software Collections for Red Hat Enterprise Linux 7) run mysqld_safe with mysql user privileges and not root privileges, limiting the potential impact to code execution as mysql system user. The MySQL 5.1 packages in Red Hat Enterprise Linux 6 do not implement support for library preloading, completely preventing the remote attack vector used by the published exploit. For additional details, refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1375198#c12 This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG-2 as the flaw was already fixed in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG-2 as the flaw was already fixed in the products listed. This issue affects the versions of groovy as shipped with Red Hat Satellite 6.0 and 6.1. Red Hat Satellite 6.2 and later do not ship groovy, as such they are not affected by this vulnerability. Applying the fix provided to mitigate this issue may cause Tomcat to return 400 status after updating. For more information, refer to https://access.redhat.com/solutions/2891171 Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG-2. Future Linux kernel updates for the respective releases might address this issue. In order to exploit this flaw, the attacker needs to be have local (shell) access to the machine where the message is being signed using the ECDSA algorithm with a P-256 elliptic curve key. Then using cache timing attacks (which needs precise timing), on multiple signature runs, the private key could be obtained. Based on the factor that exploitation is difficult, Red Hat Product Security Team has rated this flaw as having Moderate impact. A further security release may address this flaw. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Satellite 5 is now in phase 3 of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Satellite 5 Life Cycle: https://access.redhat.com/support/policy/updates/satellite. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6, 7, MRG-2 and realtime and may be addressed in a future update. This issue did not affect the versions of calamari-server as shipped with Red Hat Ceph Storage 1.3 and 2.0 as they did not include support for google analytics with Django. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. 6, 7 and Red Hat Enterprise MRG-2 as only the privileged user can exploit the flaw. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include support for mrulist. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7, as they did not include support for the RGF format. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code which can trigger the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2 are not planning to be updated to address this issue. If this affects you please lodge a support request. Red Hat Enterprise Linux 5 is now in Production 3 phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG-2 as the code with the flaw is not present in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6 as the code with the flaw is not present in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG-2 as the flaw was already fixed in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG-2 as the flaw was already fixed in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG-2 as code with the flaw is not present in the products listed. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of kdepim as shipped with Red Hat Enterprise Linux 5, 6 or 7 as they did not include support for kmail, or are not shipped with vulnerable versions. This issue did not affect the versions of kdepim as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue did not affect the versions of kdepim as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. None of the Red Hat's products are affected as the flaw was found in the Intel network card Non-Volatile Flash Memory (NVM) image (firmware). No currently supported version of Red Hat OpenStack Platform or Red Hat Enterprise Linux OpenStack Platform is affected by this flaw. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6 and is planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue doesn't affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 7 and MRG-2. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This flaw affects applications that are compiled against OpenSSL or GnuTLS and do not allocate an extra thread for processing ClientHello messages. Nginx is affected by this issue; Apache httpd is not affected by this issue. This issue has been rated as having a security impact of Moderate. It requires an attacker to send a very large amount of SSL ALERT messages to the host network connection. This issue can also be mitigated by configuring firewalls to limit the number of connections per IP address, or use deep packet inspection to reject these type of alert packets. A future update may address this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 7. Future kernel updates for Red Hat Enterprise Linux 7 may address this issue. This issue is rated as important. The affected code is not enabled on Red Hat Enterprise Linux 6 and 7 or MRG-2 kernels. The commit introducing the comment was not included in Red Hat Enterprise Linux 5. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG 2.x. This issue has been rated as having Moderate security impact. Future Linux kernel updates for the respective releases might address this issue. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux as they did not include the software implementation of the RDMA protocol over infiniband. Red Hat OpenStack Platform versions 5, 6 and 7 are now in Phase 2 of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat OpenStack Platform Life Cycle: https://access.redhat.com/support/policy/updates/openstack/platform/ This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code which can trigger the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code creating this issue is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7, MRG-2 and realtime kernels. This issue does not affect kernels that ship with Red Hat Enterprise Linux 5. This issue does not affect Red Hat Enterprise Linux 5 and 6. This issue does affect Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Future updates for the respective releases will address this issue. In a default or common use of Red Hat Enterprise Linux 7 this issue does not allow an unprivileged local user elevate their privileges on the system. In order to exploit this issue the attacker needs CAP_NET_RAW capability, which needs to be granted by the administrator to the attacker's account. Since Red Hat Enterprise Linux 7 does not have unprivileged user namespaces enabled by default, local unprivileged users also cannot abuse namespaces to grant this capability to themselves and elevate their privileges. It was found that a variant of the Tomcat CVE-2016-1240 exploit is also applicable to Red Hat JBoss Enterprise Application Platform 5, 6, and 7. CVE-2016-8656 addresses these problems with JBoss EAP. The issue is now corrected in the various versions of Red Hat JBoss Enterprise Application Platform including EAP 6.4.13 and EAP 7.0.5. For further information please refer to https://access.redhat.com/articles/3016681 It was found that a variant of the Tomcat CVE-2016-6325 exploit is also applicable to Red Hat JBoss Enterprise Application Platform 5 and 6. CVE-2016-8567 addresses these problems with JBoss EAP. The complexity is high as EAP has many files and configuration options. The issue is now corrected in JBoss Enterprise Application Platform EAP 6.4.14. For further information please refer https://access.redhat.com/articles/3016681 This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code with the flaw is not present in the products listed. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The versions of memcached as shipped with Red Hat OpenStack Platform 7, 8 and 9 are affected by this issue however will not be updated. The latest version of memcached from Red Hat Enterprise Linux 7 can safely be allowed to supersede the earlier versions provided in the Red Hat OpenStack Platform channels. The versions of memcached as shipped with Red Hat OpenStack Platform 7, 8 and 9 are affected by this issue however will not be updated. The latest version of memcached from Red Hat Enterprise Linux 7 can safely be allowed to supersede the earlier versions provided in the Red Hat OpenStack Platform channels. The version of memcached as shipped with Red Hat OpenStack Platform 9 is affected by this issue however will not be updated. The latest version of memcached from Red Hat Enterprise Linux 7 can safely be allowed to supersede the earlier versions provided in the Red Hat OpenStack Platform channels. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The Red Hat Product Security Team does not consider this issue to be a security flaw, for more information please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1384860#c5 This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the version of firefox and thunderbird as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7. This has been rated as having Moderate security impact and is currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7. This has been rated as having Moderate security impact and is currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code which can trigger the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue only affected ntpd running on the Windows OS. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5,6 and 7 as the code with the flaw is not present in the products listed. This is an Out-of-bounds read flaw in the libtiff library. A specially-crafted image can cause an application linked with the libtiff library to crash. This issue affects the Linux kernels as shipped with Red Hat Enterprise Linux 5, 6, 7, MRG-2 and realtime and will be addressed in future updates. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code which can trigger the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code with the flaw is not present in this product. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. Red Hat Satellite 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/satellite YamlProvider was removed the default list of providers to prevent a malicous user from requesting a payload be marshalled with Yaml. If marshalling of Yaml content is desired, add, or append a file with the name 'META-INF/services/javax.ws.rs.ext.Providers' to your WAR, or JAR with the contents 'org.jboss.resteasy.plugins.providers.YamlProvider' If YamlProvider is re-added to the default list of providers it's recommended to add authentication, and authorization to the endpoint expecting Yaml content to prevent exploitation of this vulnerablilty. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6 and 7. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 5,6 and 7 kernels. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 7. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: -> https://access.redhat.com/support/policy/updates/errata/ This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the kernels as shipping with Red Hat Enterprise Linux 5 and 6. This issue does affect kernels 7, MRG-2 and realtime kernels and plans to be fixed in a future update. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG-2 as the flaw was already fixed in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG-2 as the code with the flaw is not present in the products listed. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This flaw does not affect the version of Exim shipped with Red Hat Enterprise Linux 5 because it is not built with DKIM (DomainKeys Identified Mail) support. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux, as they did not include support for Android kernel performance subsystem. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux, as they did not include support for Android kernel sound subsystem. This vulnerability exists in the DTD validation functionality of libxml2. Applications that do not attempt to validate untrusted documents are not impacted. Red Hat CloudForms 4shipped the vulnerable paperclip ruby gem, however this ruby gem was removed in CloudForms 5.8. As this issue has been addressed in CloudForms 5.8, and the issue is only rated moderate Red Hat Security will not be fixing this issue in CloudForms 5.7. This issue affects the versions of ruby as shipped with Red Hat Enterprise Linux 7 and the versions of rh-ruby22-ruby and rh-ruby23-ruby as shipped with Red Hat Software Collections. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ruby as shipped with Red Hat Enterprise Linux 6, and 7 and the versions of rh-ruby22-ruby and rh-ruby23-ruby as shipped with Red Hat Software Collections. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ruby as shipped with Red Hat Enterprise Linux 6, and 7 and the versions of rh-ruby22-ruby and rh-ruby23-ruby as shipped with Red Hat Software Collections. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ruby as shipped with Red Hat Enterprise Linux 6, and 7 and the versions of rh-ruby22-ruby and rh-ruby23-ruby as shipped with Red Hat Software Collections. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ruby as shipped with Red Hat Enterprise Linux 6, and 7 and the versions of rh-ruby22-ruby and rh-ruby23-ruby as shipped with Red Hat Software Collections. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of rubygems as shipped with Red Hat Enterprise Linux 6. This issue affects the versions of ruby as shipped with Red Hat Enterprise Linux 7 and the versions of rh-ruby22-ruby and rh-ruby23-ruby as shipped with Red Hat Software Collections. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. For more information on the impact of numeric usernames in Red Hat Enterprise Linux, please see https://access.redhat.com/solutions/3103631 This issue affects the versions of jenkins-plugin-subversion as shipped with Red Hat OpenShift Enterprise 3. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of jenkins-plugin-pipeline-build-step as shipped with Red Hat OpenShift Enterprise 3. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of jenkins-plugin-git as shipped with Red Hat OpenShift Enterprise 3. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of jenkins-plugin-script-security as shipped with OpenShift Enterprise 3. However, this flaw is of low impact under the supported scenarios in OpenShift Enterprise 3. A future update may address this issue. This issue affects the versions of jenkins-plugin-workflow-cps as shipped with Red Hat OpenShift Enterprise 3. However, this flaw is of low impact under the supported scenarios in OpenShift Enterprise 3. A future update may address this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Deferred (Low security impact) ======================================= This issue affects the versions of jenkins-plugin-script-security as shipped with Red Hat OpenShift Enterprise. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Deferred (Low security impact) ======================================= This issue affects the versions of jenkins-plugin-script-security as shipped with Red Hat OpenShift Enterprise. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7, and MRG-2. Future Linux kernel updates for the respective releases may address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5,6, 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. This issue affects the versions of python as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7, and python27-python, rh-python34-python, and rh-python35-python as shipped with Red Hat Software Collections 3. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of evince as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of lynx as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of lynx as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of ldns as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having security impact of Low for: * Red Hat Enterprise Linux OpenStack Platform 7.0 (Kilo) for RHEL 7 * Red Hat OpenStack Platform 8.0 (Liberty) * Red Hat OpenStack Platform 9.0 (Mitaka) * Red Hat OpenStack Platform 10.0 (Newton) * Red Hat OpenStack Platform 11.0 (Ocata) * Red Hat OpenStack Platform 12.0 (Pike) Although the affected code is present in shipped packages, python-pysaml2 is included only as a dependency of other packages. The affected code cannot be reached in any supported configuration of Red Hat OpenStack Platform. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5. This issue affects the version of the kernel packages as shipped with Red Hat Enterprise Linux 6 and 7, and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise MRG 2 will address this issue. For further information please refer to the vulnerability article in the Customer Portal: https://access.redhat.com/security/vulnerabilities/blueborne This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 7. Future kernel updates for Red Hat Enterprise Linux 7 may address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 prior to kernel version 3.10.0-693, that is Red Hat Enterprise Linux 7.4 GA kernel version. Kernel versions after 3.10.0-693 contain the fix and are thus not vulnerable. This issue affects the Linux kernel-rt packages prior to the kernel version 3.10.0-693.rt56.617 (Red Hat Enteprise Linux for Realtime) and 3.10.0-693.2.1.rt56.585.el6rt (Red Hat Enterprise MRG 2). The latest Linux kernel-rt packages as shipped with Red Hat Enterprise Linux for Realtime and Red Hat Enterprise MRG 2 are not vulnerable. Future Linux kernel updates for the respective releases will address this issue. This issue does not affect the Linux kernel and kernel-rt packages as shipped with Red Hat Enterprise Linux 5, 6, and 7. Because the odl-l2switch-switch feature has never been packaged for Red Hat OpenStack Platform, this flaw does not affect any RHOSP version. This issue affects OpenDaylight in Red Hat OpenStack Platform 12.0 (Pike). However, OpenDaylight is only supported in segregated management networks; by default, at worst, this flaw would only be exposed on an admin network. For this reason, Red Hat Product Security has rated this issue as having security impact of Low. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects OpenDaylight in Red Hat OpenStack Platform 12.0 (Pike). However, OpenDaylight is only supported in segregated management networks; by default, at worst, this flaw would only be exposed on an admin network. For this reason, Red Hat Product Security has rated this issue as having security impact of Low. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2, as the code with the flaw is not built and shipped with the products listed. This is a kernel-side mitigation. For a related glibc mitigation please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-1000366 . This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5,6, 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. This is a glibc-side mitigation. For a related kernel mitigation please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-1000364 . Exim itself is not vulnerable to privilege escalation, but this particular flaw in exim can be used by the stackguard vulnerability (https://access.redhat.com/security/vulnerabilities/stackguard) to achieve privilege escalation. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2 as the i686 architecture is not supported by this kernel. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. At this time there is no plan to release an update to fix this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7, MRG-2 and realtime kernels. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. Future Linux kernel updates for the respective releases may address this issue. This issue was part of the stack guard fixes that was fixed along side the CVE-2017-1000364 flaw. This issue has previously affected Red Hat Enterprise Linux 5,6,7 and MRG-2. This issue is currently fixed in most versions of shipping products. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of this product due to its life cycle. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2 may address this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of erlang as shipped with Red Hat CloudForms 4. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. From the initial flaw description released, this issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. They do not contain the upstream commit (8310d48b125d19fcd9521d83b8293e63eb1646aa) which allows the race condition. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 for ARM and Red Hat Enterprise Linux for Power LE. Future Linux kernel updates for the respective releases may address this issue. For further information please refer to the vulnerability article in the Customer Portal: https://access.redhat.com/security/vulnerabilities/3253921 This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 6 and 7. Future kernel updates for Red Hat Enterprise Linux 6 and 7 may address this issue. This issue did not affect the versions of glibc as shipped with Red Hat Enterprise Linux 5, 6 and 7 after CVE-2017-1000366 fix: https://access.redhat.com/security/cve/cve-2017-1000366 This issue did not affect the versions of glibc as shipped with Red Hat Enterprise Linux 5, 6 and 7 after CVE-2017-1000366 fix: https://access.redhat.com/security/cve/cve-2017-1000366 This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue. OpenDaylight was released as a technical preview in Red Hat Openstack Platform versions 12 and under. Additionally, upstream have released an advisory outlining recommended actions, they will not be patching against this Denial of Service vector. Red Hat Product Security has rated this issue as having security impact of Low for: * Red Hat Enterprise Linux OpenStack Platform 7.0 (Kilo) for RHEL 7 * Red Hat OpenStack Platform 8.0 (Liberty) * Red Hat OpenStack Platform 9.0 (Mitaka) * Red Hat OpenStack Platform 10.0 (Newton) * Red Hat OpenStack Platform 11.0 (Ocata) * Red Hat OpenStack Platform 12.0 (Pike) Although the affected code is present in shipped packages, python-pysaml2 is included only as a dependency of other packages. The affected code cannot be reached in any supported configuration of Red Hat OpenStack Platform. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 6 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Satellite 5 is now in Production 3 Phase of the support and maintenance life cycle. The cobbler API has a user associated with it however the password is a randomly generated 64 character string, making the API inaccessible. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of plexus-utils as shipped with Red Hat Enterprise Linux 7 as well as Red Hat Satellite 6.0 and 6.1. Red Hat Satellite 6.2 and later do not ship plexus-utils, as such they are not affected by this vulnerability. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of jenkins-plugin-script-security as shipped with Red Hat Enterprise OpenShift Enterprise 3. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This flaw allows a pod to mount any part of the host filesystem. The pod will run with the security contraints placed on the user but could read anything with o=rx mode and appropriate SELinux label. This issue affects the versions of libdb as shipped with Red Hat Satellite 6.0, 6.1 and 6.2. This package no longer ships with Satellite 6.3. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect Red Hat Enterprise Linux 5 as the code with the flaw is not present in the products listed. This issue affects Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future updates for the respective releases may address this issue. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 as the code with the flaw is not built and shipped with the products listed. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 as the code with the flaw is not built and shipped with the products listed. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat considers this issue as a duplicate of CVE-2017-10684. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having security impact of Low. This issue affects the versions of puppet as shipped with: * Red Hat Satellite 6. A future update may address this issue. * Red Hat OpenStack Platform versions 6-12. Although the affected code is present in shipped packages, the affected code can only be exploited by deploying unsupported custom puppet modules. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of puppet-agent as shipped with Red Hat Enterprise Satellite 6.3 and later. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ruby as shipped with Red Hat Enterprise Linux 5, 6, and 7, as well as the versions of rh-ruby22-ruby and rh-ruby23-ruby as shipped with Red Hat Software Collections 3. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Satellite 5 is now in phase 3 of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Satellite 5 Life Cycle: https://access.redhat.com/support/policy/updates/satellite. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 7. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This flaw requires particular preconditions to be exploitable, which are not common in supported deployments of fluentd. The vulnerable system must have all of: 1. A filter_parser enabled in fluentd.conf 2. Fluentd running in non-daemon mode or a bad syslog server that doesn't sanitise escape sequences (rsyslog does) 3. A vulnerable terminal that happens to be running fluentd or manipulating the fluentd log file (for example tailing it) This issue affects the versions of fluentd as shipped with Red Hat OpenShift Enterprise 3. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the version of MIT Kerberos implementation as shipped with Red Hat Enterprise Linux. This issue also does not affect the version of Samba as shipped with Red Hat Enterprise Linux. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5,6,7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. The version of strongimcv package shipped with Red Hat Enterprise Linux 7, does not enable the gmp plugin and therefore is not affected by this flaw. This security issue does not exist in IPA / FreeIPA. FreeIPA server correctly rejects the HTTP request for "user_unlock" method with 401 Unauthorized HTTP code when the attacker tries to reuse an older browser session. Therefore, we do not consider this report as a valid security concern. We have submitted a request to MITRE to reject this CVE ID. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of exiv2 as shipped with Red Hat Enterprise Linux 6 and 7. This issue did not affect any of the Red Hat products as they did not include the gnome-exe-thumbnailer package. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Additionally, the security impact of this flaw is disputed by the upstream Ruby project. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 as the code with the flaw is not present in the products listed. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates of the Red Hat products. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Gluster Storage 3 does not ship check-mk-multisite rpm, and is therefore not affected by this flaw. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed or is not exploitable. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Future kernel updates for these products may address this issue. NSS uses a local DBM database to store configuration and security (Certificates etc) information. These database files are created by NSS during startup and is used during its normal operation. These files are not read/retrieved from an external source. This flaw is related to specially-crafted NSS DBM files. So the only way to exploit this flaw is to replace the local NSS db with these files which require local user access on the machine running NSS. Therefore Red Hat Product Security does not consider this as a security flaw. NSS uses a local DBM database to store configuration and security (Certificates etc) information. These database files are created by NSS during startup and is used during its normal operation. These files are not read/retrieved from an external source. This flaw is related to specially-crafted NSS DBM files. So the only way to exploit this flaw is to replace the local NSS db with these files which require local user access on the machine running NSS. Therefore Red Hat Product Security does not consider this as a security flaw. NSS uses a local DBM database to store configuration and security (Certificates etc) information. These database files are created by NSS during startup and is used during its normal operation. These files are not read/retrieved from an external source. This flaw is related to specially-crafted NSS DBM files. So the only way to exploit this flaw is to replace the local NSS db with these files which require local user access on the machine running NSS. Therefore Red Hat Product Security does not consider this as a security flaw. NSS uses a local DBM database to store configuration and security (Certificates etc) information. These database files are created by NSS during startup and is used during its normal operation. These files are not read/retrieved from an external source. This flaw is related to specially-crafted NSS DBM files. So the only way to exploit this flaw is to replace the local NSS db with these files which require local user access on the machine running NSS. Therefore Red Hat Product Security does not consider this as a security flaw. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue only affects systems which use a remote recursive resolver and enable EDNS0, either with the “edns0” option in /etc/resolv.conf, or using the RES_USE_EDNS0 or RES_USE_DNSSEC resolver flags. The underlying issue affects recursive resolvers such as BIND and Unbound as well, and has to be fixed separately there. This issue does not affect the versions of gcc compiler shipped with Red Hat Enterprise Linux, because The patch for CVE-2016-4429 was not backported for those versions of glibc. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code with the flaw is not present in the products listed. Red Hat JBoss Enterprise Application Platform 6 and 7 do not ship the http invoker so they are not affected. The samba4 package in Red Hat Enterprise Linux 6, is a tech preview and by default uses the SMB1 protocol, therefore though affected by this flaw, will not be addressed in a security update. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 as the code with the flaw is not present in this product. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Red Hat Enterprise Linux 6 and Satellite 5 are now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of sssd as shipped with Red Hat Satellite version 6.0. More recent versions of Satellite no longer ships sssd. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This is not currently planned to be addressed in future updates of the product due to its life cycle. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future updates for the respective releases may address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases will address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7,MRG-2 and realtime kernels. Future Linux kernel updates for the respective releases may address this issue. This issue did not affect the versions of rsyslog as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect any of the Red Hat products as they did not include the Apache Struts 2 package. Furthermore, Red Hat Enterprise Linux versions 6 and 7 do not ship any Struts packages. This flaw affects Tomcat on Red Hat Enterprise Linux only when a specific context is configured with readonly=false. The default configuration has a readonly context, so it is not affected. VirtualDirContext is not designed to be used in production, but only to ease development with IDEs without needing to fully republish jars in WEB-INF/lib. This flaw affects Tomcat on Red Hat Enterprise Linux only when a specific context is configured with readonly=false. The default configuration has a readonly context, so it is not affected. Red Hat Enterprise MRG and MRG-Messaging are currently in Maintenance phase. This issue has been rated as having Moderate security impact, and is not currently planned to be addressed in future releases of MRG or MRG-Messaging. For more information, refer to the Issue Severity Classification and the Life Cycle and Update Policies: https://access.redhat.com/security/updates/classification https://access.redhat.com/support/policy/update_policies/ The following products are not affected by this flaw, as they do not use the vulnerable functionality of either aspect of the issue. Red Hat JBoss Enterprise Application Platform 6 Red Hat JBoss BPM Suite Red Hat JBoss BRMS Red Hat Enterprise Virtualization Manager Red Hat Single Sign-On 7 Red Hat JBoss Portal Platform 6 Red Hat JBoss Enterprise Application Platform 7 is not affected by this flaw. However, it does ship the vulnerable Lucene class in a dependency to another component. Customers who reuse the lucene-queryparser jar in their applications may be vulnerable to the External Entity Expansion aspect of this flaw. This will be patched in a forthcoming release. Red Hat JBoss Fuse is not affected by this flaw, as it does not use the vulnerable functionality of either aspect of this flaw. Fuse customers who may be running external Solr servers, while not affected from the Fuse side, are advised to secure their Solr servers as recommended in the mitigation provided. The following products ship only the Lucene components relevant to this flaw, and are not vulnerable to the second portion of the vulnerability, the code execution exploit. As such, the impact of this flaw has been determined to be Moderate for these respective products: Red Hat JBoss Data Grid 7 Red Hat Enterprise Linux 6 Red Hat Software Collections 2.4 This issue did not affect the versions of lucene as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect perl versions older than 5.18. Perl as shipped in Red Hat Enterprise Linux 7 and older are not affected by this vulnerability. Perl as shipped in Red Hat Enterprise Linux 7 and older have not been found to be vulnerable. This vulnerability was not present in perl versions older than 5.20. This issue affects the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue affects the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6, and 7, as CONFIG_IEEE80211W was not enabled. This issue affects the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6, and 7, as CONFIG_IEEE80211W was not enabled. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 7. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6, and 7, as wpa_supplicant's implementation of the PeerKey handshake mechanism is incomplete and does not allow the installation of a key into the driver. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5 and 6, as it does not support TDLS. This issue affects the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 7. This issues affects the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 6 and 7. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 7. This issue affects the versions of wget as shipped with Red Hat Enterprise Linux 7. This issue did not affect the versions of wget as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of wget as shipped with Red Hat Enterprise Linux 7. This issue did not affect the versions of wget as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager version 1 and Satellite version 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6, and kernel-alt packages. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7, MRG-2 and real-time kernels. Future Linux kernel updates for the respective releases may address this issue. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ The Red Hat Security Response Team has rated this issue as having moderate security impact. The risks associated with fixing this bug are greater than the moderate severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 5,6,7 and Red Hat Enterprise MRG. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ The Red Hat Security Response Team has rated this issue as having moderate security impact. The risks associated with fixing this bug are greater than the moderate severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 5,6,7 and Red Hat Enterprise MRG. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ The Red Hat Security Response Team has rated this issue as having moderate security impact. The risks associated with fixing this bug are greater than the moderate severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 5,6,7 and Red Hat Enterprise MRG. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 as the code with the flaw is not present or is already fixed in the products listed. This issue did not affect the versions of ruby as shipped with Red Hat Enterprise Linux 5 and 6, and the versions of rh-ruby24-ruby. This issue affects the versions of ruby as shipped with Red Hat Enterprise Linux 7 and the versions of rh-ruby22-ruby and rh-ruby23-ruby as shipped with Red Hat Software Collections 3. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This flaw is not planned to be addressed in future releases of the products listed as the flaw is not exploitable by a non-privileged user. This issue did not affect the versions of ruby as shipped with Red Hat Enterprise Linux 5, and 6. These versions do not include the JSON module. This issue affects the versions of ruby as shipped with Red Hat Enterprise Linux 7, as well as the versions of rh-ruby22-ruby and rh-ruby23-ruby as shipped with Red Hat Software Collections. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 7 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 as the code with the flaw is not built in these products due to theirs build configuration. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux MRG-2. Future updates for the respective releases may address this issue. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 as the code with the flaw is not present in this product. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future updates for the respective releases may address this issue. Red Hat OpenStack Platform includes the dnsmasq-utils RPM which does not contain this flaw's affected code-paths; Red Hat OpenStack Platform is therefore listed as not affected. However, because all versions of Red Hat OpenStack Platform are based on Red Hat Enterprise Linux, all Red Hat OpenStack Platform users should absolutely upgrade the dnsmasq RPM from Red Hat Enterprise Linux as a matter of urgency using standard update mechanisms (such as 'yum update' or 'openstack overcloud update'). Red Hat OpenStack Platform includes the dnsmasq-utils RPM which does not contain this flaw's affected code-paths; Red Hat OpenStack Platform is therefore listed as not affected. However, because all versions of Red Hat OpenStack Platform are based on Red Hat Enterprise Linux, all Red Hat OpenStack Platform users should absolutely upgrade the dnsmasq RPM from Red Hat Enterprise Linux as a matter of urgency using standard update mechanisms (such as 'yum update' or 'openstack overcloud update'). Red Hat OpenStack Platform includes the dnsmasq-utils RPM which does not contain this flaw's affected code-paths; Red Hat OpenStack Platform is therefore listed as not affected. However, because all versions of Red Hat OpenStack Platform are based on Red Hat Enterprise Linux, all Red Hat OpenStack Platform users should absolutely upgrade the dnsmasq RPM from Red Hat Enterprise Linux as a matter of urgency using standard update mechanisms (such as 'yum update' or 'openstack overcloud update'). Red Hat OpenStack Platform includes the dnsmasq-utils RPM which does not contain this flaw's affected code-paths; Red Hat OpenStack Platform is therefore listed as not affected. However, because all versions of Red Hat OpenStack Platform are based on Red Hat Enterprise Linux, all Red Hat OpenStack Platform users should absolutely upgrade the dnsmasq RPM from Red Hat Enterprise Linux as a matter of urgency using standard update mechanisms (such as 'yum update' or 'openstack overcloud update'). Red Hat OpenStack Platform includes the dnsmasq-utils RPM which does not contain this flaw's affected code-paths; Red Hat OpenStack Platform is therefore listed as not affected. However, because all versions of Red Hat OpenStack Platform are based on Red Hat Enterprise Linux, all Red Hat OpenStack Platform users should absolutely upgrade the dnsmasq RPM from Red Hat Enterprise Linux as a matter of urgency using standard update mechanisms (such as 'yum update' or 'openstack overcloud update'). Red Hat OpenStack Platform includes the dnsmasq-utils RPM which does not contain this flaw's affected code-paths; Red Hat OpenStack Platform is therefore listed as not affected. However, because all versions of Red Hat OpenStack Platform are based on Red Hat Enterprise Linux, all Red Hat OpenStack Platform users should absolutely upgrade the dnsmasq RPM from Red Hat Enterprise Linux as a matter of urgency using standard update mechanisms (such as 'yum update' or 'openstack overcloud update'). This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code with the flaw is not present in this product. This issue affects the versions of the go in-ldap package as shipped with Red Hat OpenShift Enterprise. However OpenShift explicitly checks for blank passwords in order to prevent anonymous LDAP binds, as such the OpenShift product itself is not directly affected by this vulnerability. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security is not aware of any supported product that ships the affected component. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code with the flaw is not present in the products listed. Red Hat Gluster Storage 3 is not affected because affected code is not shipped in the product. Affected code is present in check-mk-multisite rpm which is not shipped in this product. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as a code with the flaw is not present in the products listed. This issue affects the versions of krb5 as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of jackson-databind (in Satellite 6.0 and 6.1) and candlepin (which embeds a copy of jackson-databind in Satellite 6.2) as shipped with Red Hat Satellite 6.x. However the affected code is NOT used at this time: Candlepin currently uses the default type resolution configuration for the ObjectMappers it creates/uses. Nowhere in candlepin do we enable global polymorphic deserialization via enableDefaultTyping(...), therefore based on the documentation sited BZ 1462702 , candlepin should not be affected. However as the vulnerable software ships with the product we have marked them as vulnerable to ensure the issue is tracked. JBoss EAP 7.x only uses the vulnerable Jackson Databind library for marshalling and unmarshalling of JSON objects passed to JAX-RS webservices. Some advise about how to remain safe when using JAX-RS webservices on JBoss EAP 7.x is available here: https://access.redhat.com/solutions/3279231 Red Hat Enterprise Linux 6 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of rh-postgresql94-postgresql, rh-postgresql95-postgresql, and rh-postgresql96-postgresql as shipped with Red Hat Software Collections 3. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rh-postgresql95-postgresql, and rh-postgresql96-postgresql as shipped with Red Hat Software Collections 3. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of foreman as shipped with Red Hat Satellite version 6 and Ceph Storage version 1.3. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2, as this flaw was fixed in 7.4 release. This issue affects the versions of unbound as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Versions of Dnsmasq shipped with Red Hat Enterprise Linux are built without DNSSEC support, so they are not affected by this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having security impact of Low. This issue may be fixed in a future version of Red Hat Enterprise Linux. OpenStack users please note, this issue is present in: * Red Hat OpenStack Platform 9.0 (Mitaka) * Red Hat OpenStack Platform 10.0 (Newton) * Red Hat OpenStack Platform 11.0 (Ocata) If a fixed version of keycloak-httpd-client-install is made available in Red Hat Enterprise Linux, OpenStack customers should consume this package directly from the Red Hat Enterprise Linux channel (this occurs during normal updates). Red Hat Product Security has rated this issue as having security impact of Low. This issue may be fixed in a future version of Red Hat Enterprise Linux. OpenStack users please note, this issue is present in: * Red Hat OpenStack Platform 9.0 (Mitaka) * Red Hat OpenStack Platform 10.0 (Newton) * Red Hat OpenStack Platform 11.0 (Ocata) If a fixed version of keycloak-httpd-client-install is made available in Red Hat Enterprise Linux, OpenStack customers should consume this package directly from the Red Hat Enterprise Linux channel (this occurs during normal updates). This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6 as a code with the flaw is not present in the products listed. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6 and kernel-alt. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 7 for ARM and Red Hat Enterprise Linux 7 for Power LE. This issue affects the versions of the Linux kernel as shipped with 6, 7 and Red Hat Enterprise MRG 2. Future updates for the respective releases may address this issue. This issue affects the versions of cfme as shipped with Red Hat CloudForms 4. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7, realtime, MRG-2 prior to version kernel-3.10.0-781. The kernel-alt package already as shipped contains this fix. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6 and kernel-alt. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7, realtime and MRG-2. Future Linux kernel updates for the respective releases may address this issue. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6 as the code with the flaw is not present in the products listed. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future updates for the respective releases may address this issue. The OpenShift Enterprise cluster-read can access webhook tokens, [1], which would allow an attacker with cluster-reader permissions, [2], or project viewer, [3], to view confidential webhook tokens. [1] https://docs.openshift.com/container-platform/3.7/dev_guide/builds/triggering_builds.html#webhook-triggers [2] https://docs.openshift.com/container-platform/3.7/admin_guide/manage_rbac.html [3] https://docs.openshift.com/container-platform/3.7/admin_solutions/user_role_mgmt.html#adding-a-role-to-a-user With this update, disabled zero-padding is no longer the default for new volumes. Users can override this behavior by setting the new configuration item, "sio_allow_non_padded_volumes=True". However, the default should not be overridden if multiple tenants will be using volumes from a shared Storage Pool. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 6 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 6 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5,6, 7, realtime and MRG-2. Red Hat Enterprise Linux 5 has transitioned to Production phase 3. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle Future Linux kernel updates for the respective releases may address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5,6,7, MRG-2 and realtime kernels. Red Hat Enterprise Linux 5 has transitioned to Production phase 3. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. At this time this bug is not meet this critera and is unlikley to be fixed for these releases. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle Future Linux kernel updates for the products in production phase 1 and 2, namely Red Hat Enterprise Linux 6, 7 and MRG-2 may address this issue. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6, as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future updates for the respective releases may address this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6 as a code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future updates for the respective releases may address this issue. This issue affects the versions of lucene (which contains an embedded copy of uima) as shipped with Red Hat Satellite 6.0 and 6.1. Red Hat Satellite 6.2 and later do not include lucene and are not vulnerable to this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect any of the Red Hat products as they did not include the Apache Struts 2 package. The "FilesMatch" directive is not enabled in the default httpd configuration as shipped with Red Hat Enterprise Linux, and needs to be explicitly enabled. Therefore this flaw has no impact on the default versions of the httpd package as shipped with Red Hat Enterprise Linux. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 6 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 6 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of irssi as shipped with Red Hat Enterprise Linux 6 and 7. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 and 6, as namespaces feature, which is required for an attack, is not present in these products. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE, as this flaw was already fixed in this products. This issue did not affect the versions of systemd as shipped with Red Hat Enterprise Linux 7 as they did not include the vulnerable code. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG 2 as a code with the flaw is not present in the products listed. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rh-nodejs4-nodejs-debug, rh-nodejs6-nodejs-debug, and rh-nodejs8-nodejs-debug as shipped with Red Hat Software Collections 3. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The upstream fix requires RequestSpec, which was introduced in OSP10. Patching versions, prior to version 10, comes with a considerable risk of introducing new bugs. Based on the impact of this vulnerability it was determined that OSP6 to 9 would not be fixed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2, as a code with the flaw is not built in these products. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7, its real-time kernel, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, as a code with the flaw is not present in this product. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, as a code with the flaw is not present in this product. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, as a code with the flaw is not present in this product. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, as a code with the flaw is not present in this product. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2, as a code with the flaw is not present or is not built in the products listed. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7, its real-time kernel, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, as a code with the flaw is not present in this product. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, as a code with the flaw is not present in this product. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This is not currently planned to be addressed in future updates of the product due to its life cycle. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, as a code with the flaw is not present in this product. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, as a code with the flaw is not present in this product. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This flaw cannot be exploited through email in Thunderbird as scripting is disabled in this for email content. It may be possible to exploit through Feeds (Atom or RSS) or other browser-like contexts. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of libXcursor as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of libXcursor as shipped with Red Hat Enterprise Linux 6. Red Hat Enterprise Linux 6 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of libXcursor as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, as a code with the flaw is not present or is not built in the products listed. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE, as a code with the flaw is not present or is not built in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7, MRG-2 and real-time kernels. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux kernel-alt package. Future Linux kernel updates for the respective releases may address this issue. Condor in Red Hat Enterprise MRG is built with both GSI and VOMS disabled and therefore is not affected by this issue. This issue affects the versions of procmail as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of procmail as shipped with Red Hat Enterprise Linux 6. Red Hat Enterprise Linux 6 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Important security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, and 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE, as the code with the flaw is not enabled and is not built in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE, as the code with the flaw is not enabled and is not built in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, and 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64, and Red Hat Enterprise Linux 7 for Power 9 LE, as the code with the flaw is not enabled and is not built in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, and 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64, and Red Hat Enterprise Linux 7 for Power 9 LE, as the code with the flaw is not enabled and is not built in the products listed. This issue affects the versions of rubygem-nokogiri as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of libxml2 as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygem-nokogiri on CloudForms 5 as it uses the Red Hat Enterprise copy of libxml2 as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygem-nokogiri on Satellite 6.0, 6.1 and 6.2 as it uses the Red Hat Enterprise copy of libxml2 as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Please note that Satellite version 6.3 no longer ships rubygem-nokogir, but instead uses a version of rubygem-nokogiri from another software channel. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 6 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of rubygem-nokogiri as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of libxml2 as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygem-nokogiri on CloudForms 5 as it uses the Red Hat Enterprise copy of libxml2 as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygem-nokogiri on Satellite 6.0, 6.1 and 6.2 as it uses the Red Hat Enterprise copy of libxml2 as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Please note that Satellite version 6.3 no longer ships rubygem-nokogir, but instead uses a version of rubygem-nokogiri from another software channel. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 6 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue affects the version of the kernel package as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2 may address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2, as a code with the flaw is not present in the products listed. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7 for ARM and Red Hat Enterprise Linux 7 for Power LE in the "kernel-alt" packages. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue affects the versions of rubygem-yard as shipped with Red Hat Subscription Asset Manager 1.x and Message Routing and Grid 2.x. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This vulnerability was caused by the fix for a prior vulnerability (CVE-2017-16239). No patches for the earlier vulnerability were released for Red Hat OpenStack before the discover of the new vulnerability. Therefore, current versions of Red Hat OpenStack are not affected by this vulnerability. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, and 7, its real-time kernel, Red Hat Enterprise MRG 2, as the code with the flaw is not present in the products listed. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future updates for the respective releases may address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE, as a code with the flaw is not present or is not built in the products listed. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ruby as shipped with Red Hat Subscription Asset Manager 1 and CloudForms 5. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2, as a code with the flaw is not present or is not built in the products listed. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7, its real-time kernel, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6, as a code with the flaw is not present or is not built in the products listed. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2, as a code with the flaw is not present or is not built in the products listed. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of mercurial as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of openjpeg as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 6 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of openjpeg as shipped with Red Hat Enterprise Linux 6 and 7, as they did not include support for jp3d. This issue did not affect the versions of icu as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Whilst the package shipped with Red Hat OpenStack contains the vulnerable code, the packages that use HDF5 do not expose the vulnerable functionality. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Whilst the package shipped with Red Hat OpenStack contains the vulnerable code, the packages that use HDF5 do not expose the vulnerable functionality. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Whilst the package shipped with Red Hat OpenStack contains the vulnerable code, the packages that use HDF5 do not expose the vulnerable functionality. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Whilst the package shipped with Red Hat OpenStack contains the vulnerable code, the packages that use HDF5 do not expose the vulnerable functionality. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Whilst the package shipped with Red Hat OpenStack contains the vulnerable code, the packages that use HDF5 do not expose the vulnerable functionality. This issue did not affect the versions of texlive as shipped with Red Hat Enterprise Linux 6 and 7. This issue affects the versions of fontforge as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. As per upstream, "exploitation is impossible because the code relies on subprocess.Popen and the default shell=False setting". On testing it seems, upstream has correctly concluded the non-security nature of this bug. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This is not currently planned to be addressed in future updates of the product due to its life cycle. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue. The research paper talks about use of HTML as a back channel to create an oracle for modified encrypted emails. HTML emails which use external links like "<img href="tla.org/TAG"/>" can cause security issues if they are honored by the MUAs. Due to flaws in MIME parsers many MUAs seem to concatenate decrypted HTML mine parts which makes it easy to plan such snippets in HTML emails. Please refer to https://lists.gnupg.org/pipermail/gnupg-users/2018-May/060315.html about how GnuPG can mitigate this flaw. The research paper talks about use of HTML as a back channel to create an oracle for modified encrypted emails. HTML emails which use external links like "<img href="tla.org/TAG"/>" can cause security issues if they are honored by the MUAs. Due to flaws in MIME parsers many MUAs seem to concatenate decrypted HTML mine parts which makes it easy to plan such snippets in HTML emails. Please refer to https://lists.gnupg.org/pipermail/gnupg-users/2018-May/060315.html about how GnuPG can mitigate this flaw. For Thunderbird, this vulnerability was known as CVE-2018-5162 and resolved in 52.8. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 as they do not contain the upstream commit (c008ba5bdc9f) that allows this issue to be exploited. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 for ARM and Red Hat Enterprise Linux for Power LE. Future Linux kernel updates for the respective releases may address this issue. This issue affects the versions of rubygem-net-ldap as shipped with Red Hat Subscription Asset Manager 1 and Satellite version 6. Red Hat Product Security has rated this issue as having Moderate security impact. No update is planned at this time however a future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of Exiv2 as shipped with Red Hat Enterprise Linux 6 and 7 as they did not include support for BigTIFF images. This issue did not affect the versions of Exiv2 as shipped with Red Hat Enterprise Linux 6 and 7. This issue did not affect the versions of Exiv2 as shipped with Red Hat Enterprise Linux 6 and 7 as they did not include support for printing IPTC Photo Metadata. This issue did not affect the versions of Exiv2 as shipped with Red Hat Enterprise Linux 6 and 7 as they did not include support for ICC profiles. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise MRG 2. This issue affects the versions of Linux kernel as shipped with Red Hat Enterprise Linux 6 and 7. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of ruby as shipped with Red Hat CloudForms 4. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ruby as shipped with Red Hat Subscription Asset Manager 1. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of opencv as shipped with Red Hat Enterprise Linux 6 and 7. This issue affects the versions of ruby as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code with the flaw is not present in the products listed. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64, and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, and 7, its real-time kernel and Red Hat Enterprise MRG 2. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This is not currently planned to be addressed in future updates of the product due to its life cycle. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7, MRG-2 and real time kernels as the code which can trigger the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This is not currently planned to be addressed in future updates of the product due to its life cycle. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, and 7, its real-time kernel and Red Hat Enterprise MRG 2, as the code with the flaw is not enabled and is not built in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not exploitable in the default configuration Red Hat Enterprise Linux. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7, its real-time kernel and Red Hat Enterprise MRG 2. At this time there are no plans to fix this issue. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and 7, and Red Hat Enterprise MRG as they did not include the vulnerable code. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE, as the code with the flaw is not built and shipped in the products listed. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE, as the code with the flaw is not built and shipped in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, as the code with the flaw is not present in this product. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE, as the code with the flaw is not built and shipped in the products listed. This issue affects the versions of momentjs as shipped with Red Hat Enterprise Satellite 5. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of exempi as shipped with Red Hat Enterprise Linux 6 as they did not include the vulnerable code. This issue did not affect the versions of Exempi as shipped with Red Hat Enterprise Linux 6 and 7 as they did not include support for Web/P images. This issue did not affect the versions of Exempi as shipped with Red Hat Enterprise Linux 6 and 7 as they did not include support for PostScript format. This issue did not affect the versions of Exempi as shipped with Red Hat Enterprise Linux 6 as they did not include the vulnerable code. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include support for OpenCL. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include support for OpenCL. This issue did not affect the versions of xdg-utils as shipped with Red Hat Enterprise Linux 6 and 7. This issue did not affect the versions of glibc and compat-glibc as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include the vulnerable code. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7. PyYAML in channels for Red Hat MRG Messaging 2 should no longer be used, as a newer version is now available in Red Hat Enterprise Linux. Newer packages should be consumed from Red Hat Enterprise Linux channels. This issue affects the versions of the PyYAML package as shipped with Red Hat Satellite 5. However, this flaw is not known to be exploitable under any supported scenario in Satellite 5. A future update may address this issue. This issue affects Red Hat Satellite 6.1 and 6.2. Red Hat Product Security has rated this issue as having Low security impact. Red Hat Satellite 6.3 is not affected by this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7. Future kernel updates for Red Hat Enterprise Linux 7 may address this issue. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the version of Linux kernel as shipped with Red Hat Enterprise Linux 7. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ Red Hat Product Security has rated this issue as having Low security impact, a future update may address this flaw. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 due to a missing commit ( bb646cdb12e75d82258c2f2e7746d5952d3e321a ) which enabled changed system behavior. This issue does affect Red Hat Enteprise Linux 7 and MRG-2 kernels. A future Linux kernel updates for the respective releases may address this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects Red Hat Enterprise Linux 5 kernel. This issue was fixed in a versions 6 and 7 prior to this issue being raised. Future Linux kernel updates for Red Hat Enterprise Linux 5 may address this issue. This issue does not affect libvirt as shipped with Red Hat Enterprise Linux 5, 6 and 7 as it does not contain the affected code. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue does affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. As this issue is rated as Important, it has been scheduled to be fixed in future updates for the respective releases. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code which can trigger the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue did not affect the versions of subscription-manager as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include support for the DBus interface. This issue affects the versions of rubygem-hammer_cli as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Versions of dovecot shipped in Red Hat Enterprise Linux 5, 6 and 7 are not affected by this vulnerability. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. Red Hat Product Security has rated this issue as having Low security impact in Red Hat OpenStack Platform. While the code is present in the python-tablib package, it is not reachable in any supported configuration. There is currently no plan to address this flaw in any supported version of Red Hat OpenStack platform. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the libsoup packages as shipped with Red Hat Enterprise Linux 7. However, these packages have been compiled with additional security mitigation techniques ("stack smashing protection"), which makes exploitation significantly harder. Thus, in most cases an exploitation attempt should be mitigated to a mere crash. However, successful exploitation to execute arbitrary code can't be ruled out entirely. This issue did not affect the versions of SDL as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue does not affect bind as shipped with Red Hat Enterprise Linux 5, 6 and 7 as it does not contain the affected code. This issue affected only the BIND versions as shipped with Red Hat Enterprise Linux 6. This issue did not affect any upstream versions of BIND. This issue does not affect BIND configurations which have DNSSEC validation turned off. This issue did not affect the versions of BIND as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of mysql-connector-java as shipped with Red Hat Enterprise Linux 6 and 7. This issue affects the versions of mysql-connector-java as shipped with Red Hat Enterprise Linux 6 and 7. This issue affects the versions of mysql-connector-java as shipped with Red Hat Enterprise Linux 6 and 7. This flaw only exhibits itself when: 1. OpenSSL is used to display details of a local or a remote certificate. 2. The certificate contains the uncommon RFC 3779 IPAddressFamily extension. The maximum impact of this flaw is garbled information being displayed, there is no impact on the availability of service using such a certificate. Also this flaw can NOT be used to create specially-crafted certificates. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects rabbitmq-server plugins as shipped with: * Red Hat Storage Console 2 * Red Hat Enterprise Linux OpenStack Platform 5,6,7 * Red Hat OpenStack Platform 8,9,10,11 Although RabbitMQ plugins are shipped in these products, no plugins are enabled or used by default. To verify your environment's plugin usage, run: # rabbitmq-plugins list A future update may address this issue. Red Hat Product Security has rated this issue as having Moderate security impact. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects rabbitmq-server plugins as shipped with: * Red Hat Storage Console 2 * Red Hat Enterprise Linux OpenStack Platform 5,6,7 * Red Hat OpenStack Platform 8,9,10,11 Although RabbitMQ plugins are shipped in these products, no plugins are enabled or used by default. To verify your environment's plugin usage, run: # rabbitmq-plugins list A future update may address this issue. Red Hat Product Security has rated this issue as having Moderate security impact. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects rabbitmq-server plugins as shipped with: * Red Hat Storage Console 2 * Red Hat Enterprise Linux OpenStack Platform 5,6,7 * Red Hat OpenStack Platform 8,9,10,11 Although RabbitMQ plugins are shipped in these products, no plugins are enabled or used by default. To verify your environment's plugin usage, run: # rabbitmq-plugins list A future update may address this issue. Red Hat Product Security has rated this issue as having Moderate security impact. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of spring-webflow as shipped with Red Hat Enterprise Virtualization 3. Red Hat Product Security has rated this issue as having (Low|Moderate) security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux as they did not include the upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4c48abe91be03d191d0c20cc755877da2cb35622 that introduced this issue. This issue did not affect the versions of the salt as shipped with Red Hat Ceph Storage 1.3, Red Hat Ceph Storage 2, and Red Hat Storage Console 2 as salt-api and salt-ssh are not shipped with these products. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of the salt as shipped with Red Hat Ceph Storage 1.3, Red Hat Ceph Storage 2, and Red Hat Storage Console 2 as salt-api and salt-ssh are not shipped with these products. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This is a heap-based buffer overflow in the tiffcp utility of libtiff. A specially-crafted image when processed via the tiffcp binary, could cause it to crash or execute arbitrary code with the permissions of the user running the utility. This issue did not affect the versions of icoutils as shipped with Red Hat Enterprise Linux 7 as they did not backport the vulnerable patches provided to fix a previous flaw (CVE-2017-5208). Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The security flaw exists in NSS library Base64 encoder/decoder code. Any application which uses NSS library to parse base64 encoded data could possibly be affected by the flaw. For example: 1. Servers compiled against NSS which parse untrusted certificates or any other base64 encoded data from its users. 2. Utilities like curl etc which use NSS to parse user provided base64 encoded certificates. 3. Applications like Firefox which use NSS to parse client-certificates before passing them to the web server. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Moderate security impact. These issues may be fixed in a future minor release of Red Hat Enterprise Linux 7. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of jasperreports as shipped with Red Hat Enterprise Virtualization 3. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of jasperreports as shipped with Red Hat Enterprise Virtualization 3. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This flaw was fixed in the Red Hat products as a part of the CVE-2016-7097 fix. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code with the flaw is not present in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code with the flaw is not present in the products listed. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification. Since pear's purpose is to download libraries for inclusion in an application, any use of `pear install` or `pear download` implicitly trusts the server. This vulnerability does not significantly extend the trust already given to pear and to servers used with it. This issue did not affect any of the Red Hat products as they did not include the Apache Struts 2 package. Additionally it does not appear that struts 1 is affected by this vulnerability (the affected code does not appear to be present in struts 1). Additionally it does not appear that Red Hat has backported any code from struts 2 to struts 1 as the code bases are quite different and backporting any significant code would be a major effort with questionable results due to compatibility issues. The fop packager is no longer used or required by the Red Hat Virtualization Manager. Red Hat recommends removing it after upgrading to Red Hat Virtualization 4.1. The batik package is no longer used or required by the Red Hat Virtualization Manager. Red Hat recommends removing it after updating to Red Hat Virtualization 4.1. This flaw can be triggered for static error pages only if the readonly property for the DefaultServlet is set to false in the $CATALINA_HOME/conf/web.xml file. The default for readonly is true. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG-2 as the flaw can only be exploited by a privileged user. Red Hat Product Security is aware of this issue. Updates will be released as they become available. For additional information, please refer to the Red Hat Knowledgebase article: https://access.redhat.com/security/vulnerabilities/speculativeexecution Red Hat Product Security is aware of this issue. Updates will be released as they become available. For additional information, please refer to the Red Hat Knowledgebase article: https://access.redhat.com/security/vulnerabilities/speculativeexecution Red Hat Product Security is aware of this issue. Updates will be released as they become available. For additional information, please refer to the Red Hat Knowledgebase article: https://access.redhat.com/security/vulnerabilities/speculativeexecution Meltdown patches for 32-bit Red Hat Enterprise Linux 5 ------------------------------------------------------ Red Hat has no current plans to provide mitigations for the Meltdown vulnerability in 32-bit Red Hat Enterprise Linux 5 environments. Following many hours of engineering investigation and analysis, Red Hat has determined that introducing changes to the Red Hat Enterprise Linux 5 environment would destabilize customer deployments and violate our application binary interface (ABI) and kernel ABI commitments to customers who rely on Red Hat Enterprise Linux 5 to be absolutely stable. Although Red Hat has delivered patches to mitigate the Meltdown vulnerability in other supported product offerings, the 32-bit Red Hat Enterprise Linux 5 environment presents unique challenges. The combination of limited address space in 32-bit environments plus the mechanism for passing control from the userspace to kernel and limitations on the stack during this transfer make the projected changes too invasive and disruptive for deployments that require the highest level of system stability. By contrast, 32-bit Meltdown mitigations have been delivered for Red Hat Enterprise Linux 6, where the changes are far less invasive and risky. Red Hat Enterprise Linux 5 and 6 are not affected as they do not include this code. Red Hat Enterprise Linux 7, MRG and realtime kernels contain the code, but are not affected. At this time we do not believe there is a denial of service, memory leak, privilege escalation or trust barrier crossed. The kernel may attribute errors in system logs to the wrong tunnel. If you believe this is in error and have evidence or thoughts to the contrary please contact Red Hat Security Team. This issue did not affect the versions of bash as shipped with Red Hat Enterprise Linux as they did not include the commit which introduced it. This issue affects the versions of rubygem-rubyzip as shipped with Red Hat Quick Cloud Installer. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Recovery mode is not intended for use with untrusted input. Users invoking xmllint --recover may experience a crash, but applications processing documents from possibly malicious sources should not be exposed to this flaw. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code which can trigger the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue affects Red Hat Enterprise Linux 5,6, 7 and MRG-2 kernels. Red Hat has no plans to fix this issue at this time. While performance enhancements have been made upstream, Red Hat Product Security believes the report to be invalid and able to be mitigated with synproxy. This flaw is currently under investigation for validity and Red Hat is asking to revoke the CVE. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and MRG-2. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7. This flaw may affect multiple containers running on this system. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the perf subsystem where the flaw was found is not present in this product. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue was made easier to exploit, causing a denial of service when the patch for CVE-2016-6816 was present and the patch that corrected this flaw was not.  The issue was not classified as a security flaw upstream. It was corrected in products like Red Hat Enterprise Linux 6 and 7 and JBoss Enterprise Web Server 3 prior to the fix for CVE-2016-6816 being applied. This was not the case for JBoss Enterprise Application Server 6.  As a result, only EAP 6.4.13 is vulnerable to this issue and 6.4.14 corrects it.  For further information, refer to https://access.redhat.com/articles/2991951 This issue affects Red Hat Enterprise Linux 5, 6, 7, and Red Hat Enterprise MRG 2 kernels. As this issue is rated as Important, it has been scheduled to be fixed in a future version of Red Hat Enterprise Linux 5, 6, 7, and Red Hat Enterprise MRG 2 kernels. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue affects the versions of gdk-pixbuf2 as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ and Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2, as the kernel module 'llc2.ko' with this security flaw is not shipped with the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6 as the code which can trigger the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. This issue does not affect the Linux kernels as shipped with Red Hat Enterprise Linux 4,5,6,7 and MRG-2. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code with the flaw is not present in the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2, as the problem code is not presented in the products listed. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux. The security assessment from cure53 clarifies that this issue (identified as NTP-01-0004) is not a vulnerability per se, but a weakness in ntp's internal coding style that may cause a vulnerability if particularly long variable names are defined at compile time. No such variable names are defined in upstream source code, nor in Fedora or Red Hat Enterprise Linux versions of ntp. This issue did not affect the versions of ntp as shipped with Red Hat Enterprise Linux. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ and Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux and Red Hat Enterprise MRG as they did not include the vulnerable code. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. In a default or common use of Red Hat Enterprise Linux 7 and MRG-2 this issue does not allow an unprivileged local or remote user to elevate their privileges on the system. In order to exploit this issue the attacker needs CAP_NET_ADMIN capability, which needs to be granted especially by the administrator to the attacker's process. This in turn requires granting CAP_NET_ADMIN capability to the process' binary and/or attacker's account. Another possibility to obtain CAP_NET_ADMIN capability in Red Hat Enterprise Linux 7 for an attacker is running a process inside a user+network namespace with mapped root privileges inside the namespace. Since Red Hat Enterprise Linux 7 does not have unprivileged user namespaces enabled by default, local or remote unprivileged users also cannot abuse namespaces to grant this capability to themselves and elevate their privileges. Given the severity of this issue, future Linux kernel updates for the Red Hat Enterprise Linux 7 and MRG-2 products are planned to address it. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, as the change that introduced the flaw is not present in the code of these products. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. Because the Image Service APIv1 was deprecated in Newton and because a workaround is possible, no fix is being made available. For impacted products and the recommended mitigation, see the Knowledge Base article for this issue: https://access.redhat.com/security/vulnerabilities/2999581 This issue affects the versions of python-django as shipped with Red Hat Satellite 6. Please note that python-django, as used by Pulp does not make use of the Pulp doesn't use "is_safe_url" directly or the "i18n" views or the "django.contrib.auth" Login view. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code with the flaw is not present in this product. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code where the flaw was found is not present in these products. MITRE has rejected this CVE as the flaw was not confirmed: https://nvd.nist.gov/vuln/detail/CVE-2017-7286 https://bugzilla.novell.com/show_bug.cgi?id=1033458#c5 None of the Red Hat products is vulnerable to this not-a-flaw. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code where the flaw was found is not present in this product. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. This issue does not affect Red Hat Enterprise Linux 5. In a default or common use of Red Hat Enterprise Linux 6 and 7 this issue does not allow an unprivileged local user elevate their privileges on the system. In order to exploit this issue the attacker needs CAP_NET_RAW capability, which needs to be granted by the administrator to the attacker's account. Since Red Hat Enterprise Linux 6 does not have namespaces support and Red Hat Enterprise Linux 7 does not have unprivileged user namespaces enabled by default, local unprivileged users also cannot abuse namespaces feature to grant this capability to themselves and elevate their privileges. So, this issue does not affect Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2 in the default configuration. Future updates for the respective releases will address this issue to secure non-default configurations. In the non-default configuration mentioned above only Red Hat Enterprise Linux 7 is vulnerable to a privilege escalation. Red Hat Enterprise Linux 6 is vulnerable only to a denial of service (DoS) due to a system crash, hence the impact on Red Hat Enterprise Linux 6 is rated as being Moderate. MITRE has rejected this CVE as the flaw was not confirmed: https://nvd.nist.gov/vuln/detail/CVE-2017-7319 https://bugzilla.novell.com/show_bug.cgi?id=1033438#c4 None of the Red Hat products is vulnerable to this not-a-flaw. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code where the flaw was found is not present in this product. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code where the flaw was found is not present in these products. This issue affects the versions of spacewalk-backend as shipped with Red Hat Satellite version 5. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code with the flaw is not present in this product. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue. Red Hat OpenStack Platform will no longer be updating the Ansible package in: * Red Hat OpenStack Platform 10 (Newton) * Red Hat OpenStack Platform 11 (Ocata) As of Red Hat Enterprise Linux 7.4, customers can consume an updated Ansible package directly from the extras-rhel-7.4 channel. For more information, refer to Red Hat Enterprise Linux release information. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 starting with the version kernel-3.10.0-514.el7, that is with Red Hat Enterprise Linux 7.3 GA. Prior Red Hat Enterprise Linux 7 kernel versions are not affected. In order to exploit this issue, the system needs to be manually configured by privileged user. The default Red Hat Enterprise Linux 7 configuration is not vulnerable. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5,6 and 7 as the module is not enabled on these systems. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise MRG-2. Future Linux kernel updates for the respective releases may address this issue. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 as the code with the flaw is not shipped with the products listed. After further analysis of this issue, it was determined that the flaw was in the XML Frameworks implementation on EAP 7, not in RESTEasy. If you use a javax.xml.transform.TransformerFactory to process a javax.xml.transform.Source instance please be aware of this outstanding issue with that functionality on EAP 7.0.x: https://bugzilla.redhat.com/show_bug.cgi?id=1451960 This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. fs Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. JBoss 4.x is not supported by Red Hat This issue does not affect Red Hat Enterprise Linux 5, 6 and 7 as OpenVPN is not included in any of Red Hat's supported products. Red Hat Satellite 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7. Future kernel updates for Red Hat Enterprise Linux 7 may address this issue. This issue did not affect the versions of ceph as shipped with Red Hat Ceph Storage 1.3 and 2 as they did not ship libradosstriper. This issue does not affect Red Hat Enterprise Linux 5, 6 and 7 as OpenVPN is not included in any of Red Hat's supported products. This issue does not affect Red Hat Enterprise Linux 5, 6 and 7 as OpenVPN is not included in any of Red Hat's supported products. This issue does not affect Red Hat Enterprise Linux 5, 6 and 7 as OpenVPN is not included in any of Red Hat's supported products. This issue affects the versions of jackson-databind (in Satellite 6.0 and 6.1) and candlepin (which embeds a copy of jackson-databind in Satellite 6.2) as shipped with Red Hat Satellite 6.x. However the affected code is NOT used at this time: Candlepin currently uses the default type resolution configuration for the ObjectMappers it creates/uses. Nowhere in candlepin do we enable global polymorphic deserialization via enableDefaultTyping(...), therefore based on the documentation sited BZ 1462702 , candlepin should not be affected. However as the vulnerable software ships with the product we have marked them as vulnerable to ensure the issue is tracked. JBoss EAP 7.x only uses the vulnerable Jackson Databind library for marshalling and unmarshalling of JSON objects passed to JAX-RS webservices. Some advise about how to remain safe when using JAX-RS webservices on JBoss EAP 7.x is available here: https://access.redhat.com/solutions/3279231 Although JBoss Fuse ships the vulnerable version of jackson-databind, it does not call on enableDefaultTyping() for any polymorphic deserialization operations which is the root cause of this vulnerability. We have raised a Jira tracker to ensure that jackson-databind will be upgraded for Fuse 7.0, however due to feasibility issues jackson-databind cannot be upgraded in JBoss Fuse 6.3. This side-channel attack requires that the attacker can run arbitrary software on the hardware where the private RSA key is used. Allowing execute access to a box with private keys should be considered as an unsafe security practice, anyway. Thus in practice there are easier ways to access the private keys than to mount this side-channel attack. However, on boxes with virtual machines this attack may be used by one VM to steal private keys from another VM. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7.0 and 7.1 as the code with the flaw is not present in the products listed. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7.2 and newer and Red Hat Enterprise MRG 2. Future kernel updates for these products may address this issue. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5 as the code with the flaw is not present in the products listed. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for these products may address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and does not qualify for inclusion as part of the Red Hat Enterprise Linux 5 lifecycle. For more information on the lifecycle see https://access.redhat.com/support/policy/updates/errata Red Hat Satellite 5 are is in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Satellite 5 are is in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat OpenStack Platform will no longer be updating the Ansible package in: * Red Hat OpenStack Platform 10 (Newton) * Red Hat OpenStack Platform 11 (Ocata) As of Red Hat Enterprise Linux 7.4, customers can consume an updated Ansible package directly from the extras-rhel-7.4 channel. For more information, refer to Red Hat Enterprise Linux release information. This issue does not affect Red Hat Enterprise Linux 5 and 6 as the code with the flaw is not present in the products listed. This issue affects Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Future updates for the respective releases may address this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 on ppc64 and ppc64le platforms. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6 and 7 on ppc64 and ppc64le platforms. Future Linux kernel updates for the respective releases might address this issue. Only ppc64 and ppc64le hardware platforms are vulnerable. The Linux kernel packages for other platforms which Red Hat ships (i386, x86_64, s390x) are not vulnerable to this security flaw. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux MRG-2 as this product is shipped for x86_64 hardware platform only. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code where the flaw was found is not present in these products. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2 may address this issue. Red Hat Product Security has rated this issue as having a security impact of Moderate, and a future update may address this flaw. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This is not currently planned to be addressed in future updates of the product due to its life cycle. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2 may address this issue. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. We recommend avoiding usage of the functions gdImageCreateFromGifCtx() and imagecreatefromstring() as they can lead to stack data leak. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 may address this issue. This issue did not affect the versions of ghostscript as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of ghostscript as shipped with OpenShift Enterprise 2. This issue affects the versions of spring-webflow as shipped with Red Hat Enterprise Virtualization 3. Red Hat Product Security has rated this issue as having (Low|Moderate) security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. While there might be compatibility issues upgrading Spring REST Data independently of the Spring Boot version we recommend that customers make sure they are using a fixed version of Spring Data REST 2.6.9, or 3.0.1. RHOAR has now upgraded to version 1.5.10 of Spring Boot which is compatible with fixed versions of Spring DATA Rest. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of the salt as shipped with Red Hat Ceph Storage 1.3, Red Hat Ceph Storage 2, and Red Hat Storage Console 2 as salt-ssh is not used with these products. This issue is a duplicate of CVE-2016-7117; refer to that CVE for details. It has already been fixed in all supported Red Hat products. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. In the default system configuration, with the sysctl variable vm.overcommit_memory set to either 0 (the default) or 1, an attack would take a not-insignificant amount of time to exhaust the system's memory. If vm.overcommit_memory is set to a value of 2, the time required to exhaust system memory is sufficiently reduced. It was further noticed that, a 32-bit system would have its memory exhausted faster than a 64-bit system. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 as the code with the flaw is not present in the products listed. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Future kernel updates for these products may address this issue. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7, Red Hat Enterprise MRG 2 and real-time kernels. Future updates for the respective releases may address this issue. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 for ARM and Red Hat Enterprise Linux 7 for Power LE. This issue does not affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, as the code with the flaw is not present in this product. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of this product due to its life cycle. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2 may address this issue. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates of the Red Hat products. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of strongimcv as shipped with Red Hat Enterprise Linux 7, as they did not include support for the gmp plugin. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This vulnerability exists in the DTD validation functionality of libxml2. Applications that do not attempt to validate untrusted documents are not impacted. This vulnerability exists in the DTD validation functionality of libxml2. Applications that do not attempt to validate untrusted documents are not impacted. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of this product due to its life cycle. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2 may address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of this product due to its life cycle. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2 may address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of this product due to its life cycle. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2 may address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of this product due to its life cycle. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2 may address this issue. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of php as shipped with Red Hat Enterprise Linux 6 and 7 (versions 5.3.3 and 5.4.16, respectively). This issue did not affect the versions of the kernel as shipped with Red Hat Enterprise Linux 5, 6,7 and MRG2/realtime kernels. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated these issues as having Low security impact. These issues are not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of systemd as shipped with Red Hat Enterprise Linux 7. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. This issue does not affect the versions of OpenLDAP as shipped with Red Hat Enterprise Linux 6 and 7 as they don't use the affected MDB backend in their default configurations. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of systemd as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of libgcrypt as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include support for EdDSA cipher. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code where the flaw was found is not present in this product. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ This issue is present in a Struts 1 plugin for Apache Struts 2.3.x. It is not present in Apache Struts 1. This issue did not affect any of the Red Hat products as they did not include the Apache Struts 2 package. This issue did not affect any of the Red Hat products as they did not include the Apache Struts 2 package. This issue affects the versions of httpd as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue affects the versions of httpd24-httpd as shipped with Red Hat Software Collections. Product Security has rated this issue as having Moderate security impact. In order to be vulnerable, .htaccess files need to contain an invalid or not globally registered HTTP method in a "Limit" directive. This issue did not affect the versions of Apache Solr as shipped with in Red Hat products. This issue did not affect any of the Red Hat products as they did not include the Apache Struts 2 package. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of curl/libcurl as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include the vulnerable code. This issue did not affect the versions of curl/libcurl as shipped with Red Hat Software Collections 3 as they did not include the vulnerable code. This flaw only affects the openssl code which is compiled by the HP-UX assembler, so that only HP-UX PA-RISC arches are affected. Red Hat Enterprise Linux does not support this architecture, and therefore is not affected. This issue affects the version of Linux kernel package as shipped with Red Hat Enterprise Linux 5. This is not currently planned to be addressed in future updates of the product due to its life cycle. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue. This issue affects the versions of curl as shipped with Red Hat Enterprise Linux 5, 6, and 7, as well as the versions of httpd24-curl as shipped with Red Hat Software Collections. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Released versions of Red Hat Enterprise Virtualization were not impacted by this issue in practice as the passwords were not saved in the answerfile during provisioning. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6, as supported configurations are not affected. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue. Versions of Python 2 included in Red Hat Enterprise Linux 6 and 7 are affected by this issue. Reading concurrently from the same file handle in multiple threads is inherently unstable, and should not be relied upon in any real program. This issue is not planned to be fixed in future releases. This issue did not affect the versions of unzip as shipped with Red Hat Enterprise Linux 5, 6, and 7, as they did not include support for set_zipfn_sgmnt_name function. This issue did not affect the versions of unzip as shipped with Red Hat Enterprise Linux 5, 6, and 7, as they did not include the function charset_to_intern, or the code is different and does not contain the vulnerable part. This issue did not affect the versions of unzip as shipped with Red Hat Enterprise Linux 5, 6, and 7, as they did not include support for ef_scan_for_stream function. This issue did not affect the versions of unzip as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not contain vulnerable code. This issue affects the versions of unzip as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygems as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygems as shipped with Red Hat Satellite version 6 on Red Hat Enterprise Linux version 5. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygems as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygems as shipped with Red Hat Satellite version 6 on Red Hat Enterprise Linux version 5. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygems as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having security impact of Low. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygems as shipped with Red Hat Satellite version 6 on Red Hat Enterprise Linux version 5. Red Hat Product Security has rated this issue as having security impact of Low. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygems as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygems as shipped with Red Hat Satellite version 6 on Red Hat Enterprise Linux version 5. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygems as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygems as shipped with Red Hat Satellite version 6 on Red Hat Enterprise Linux version 5. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygems as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygems as shipped with Red Hat Satellite version 6 on Red Hat Enterprise Linux version 5. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygems as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of rubygems as shipped with Red Hat Satellite version 6 on Red Hat Enterprise Linux version 5. Red Hat Product Security has rated this issue as having a security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat is aware of traffic amplification distributed denial of service (DDoS) attacks that take advantage of the insecurely configured memcached servers reachable from the public Internet. The default configuration of memcached as shipped in Red Hat products makes it possible to abuse them for these DDoS attacks if memcached is exposed to connections from the public Internet. Refer to the Red Hat Knowledgebase article 3369081 for instructions on how to properly secure memcached installations to prevent them from being used in the attack. https://access.redhat.com/solutions/3369081 This issue affects the versions of rubygem-rack-protection as shipped with Red Hat Satellite 6. Red Hat Product Security has rated this issue as having security impact of Low. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having security impact of Low for: * Red Hat OpenStack Platform 9.0 (Mitaka) * Red Hat OpenStack Platform 10.0 (Newton) * Red Hat OpenStack Platform 11.0 (Ocata) * Red Hat OpenStack Platform 12.0 (Pike) Although the affected code is present in shipped packages, data returned by Jolokia is correctly processed and invalid data is not used. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having security impact of Low for: * Red Hat OpenStack Platform 9.0 (Mitaka) * Red Hat OpenStack Platform 10.0 (Newton) * Red Hat OpenStack Platform 11.0 (Ocata) * Red Hat OpenStack Platform 12.0 (Pike) Although the affected code is present in shipped packages, proxy mode is not enabled by default. The affected code is not used in any supported configuration of Red Hat OpenStack Platform. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Virtualization does not use the UnboundID SDK in synchronous mode, and hence does not expose this vulnerability in its default configuration. This issue did not affect the versions of NetworkManager as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include support for dnsmasq DNS resolver. This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. This issue affects the version of the kernel package as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2 may address this issue. This issue did not affect the versions of cobbler as shipped with Red Hat Satellite 5 as it does not ship cobbler-web. The most sensitive function not requiring a valid token is modify_settings(), which is not part of cobbler-2.0.7, the versions shipped Red Hat Enterprise Satellite 5. As such, the flaw is considered with a Medium severity rating on cobbler versions as shipped in Red Hat Enterprise Satellite 5. A future update may address this issue. The XMSS/XMSS^MT algorithms were first introduced in upstream bouncycastle version 1.57. Versions prior to this, that have not had the new algorithms back-ported, are not affected. This issue affects the versions of python-flask as shipped with Red Hat Enterprise Linux 7. This issue did not affect the versions of python as shipped with Red Hat Enterprise Linux 5, 6 and 7 as Linux does not use the vulnerable code. This flaw is a user authentication bypass in the SSH Server functionality of paramiko (normally used by subclassing `paramiko.ServerInterface`). Where paramiko is used only for its client-side functionality (e.g. `paramiko.SSHClient`), the vulnerability is not exposed and thus cannot be exploited. The following Red Hat products use paramiko only in client-side mode. Server side functionality is not used. * Red Hat Ceph Storage 2 * Red Hat CloudForms 4 * Red Hat Enterprise Linux 7 * Red Hat Enterprise Virtualization * Red Hat Gluster Storage 3 * Red Hat Openshift Container Platform * Red Hat Quick Cloud Installer * Red Hat Satellite 6 * Red Hat Storage Console 2 * Red Hat OpenStack Platform * Red Hat Update Infrastructure Kubernetes support is moving from Red Hat Enterprise Linux to OpenShift Container Platform. Kubernetes and its dependencies will no longer be updated through the Extras channel. Instead, the Red Hat customers are advised to use Red Hat's supported Kubernetes-based products such as Red Hat OpenShift Container Platform. While Red Hat Mobile Application Platform (RHMAP) does include the vulnerable library, it does not use the vulnerable methods extract* fixed in the library, [1]. RHMAP upgrade the vulnerable library in a future version. [1] https://github.com/cthackers/adm-zip/commit/6f4dfeb9a2166e93207443879988f97d88a37cde This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Moderate, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of lrzsz as shipped with Red Hat Enterprise Linux 5, 6, and 7. A patch was already applied for this vulnerability. Red Hat Product Security has rated this issue as having a security impact of Moderate, and a future update may address this flaw. This issue only affects applications which have the YamlProvider explicitly enabled by adding or appending a file with the name 'META-INF/services/javax.ws.rs.ext.Providers' to your WAR, or JAR with the contents 'org.jboss.resteasy.plugins.providers.YamlProvider' resteasy-base as shipped in Red Hat Enterprise Linux 7 does not include YamlProvider. Red Hat Subscription Asset Manager version 1 is now in a reduced support phase receiving only Critical impact security fixes. This issue has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. This issue affects the versions of resteasy as shipped with Red Hat Satellite version 6, however Satellite version 6 does not use the affected functionality. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of PostgreSQL as shipped with Red Hat Satellite 5 and CloudForms 5 as they use PostgreSQL version 9.x and this vulnerability is specific to PostgreSQL 10.x. This issue affects the versions of PostgreSQL 9.x as shipped with Red Hat Satellite 5.x and CloudForms 5.x. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Linux 6 is now in Maintenance support 2 Phase of the support and maintenance life cycle. This issue has been rated as having a security impact of Moderate, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ Red Hat Enterprise Linux 6 is now in Maintenance support 2 Phase of the support and maintenance life cycle. This issue has been rated as having a security impact of Moderate, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/ Red Hat Product Security has rated this issue as having a security impact of Low, and a future update may address this flaw. This issue affects the versions of advancecomp as shipped with Red Hat Satellite 6. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The versions of samba shipped with Red Hat Enterprise Linux 6 and 7 do not support Active Directory Domain Controller (AD-DC) mode. Therefore this flaw does not affect Red Hat Enterprise Linux 6 and 7. This issue affects the versions of Postgresql as shipped with Red Hat Satellite 5. Red Hat Product Security has rated this issue as having security impact of Low. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat OpenStack Platform versions 7 to 9 provided openvswitch-dpdk as a technical preview for customers, it was provided without support and is not intended on being deployed in production. Red Hat Ceph Storage version 3 provides ceph bundled with DPDK as a technical preview for customers. It was provided without support and is not intended on being deployed in production. Red Hat Product Security does not consider this issue as a vulnerability. The default installation are by default secured which means that management interfaces are set to have an authentication mechanism. Even without security on the management interfaces there are other approaches that could be taken, as an example a proxy fronting the server could be taking over the configuration. A second one could be the application server is running on an isolated device that does not allow network connections to it so only a local trusted process can communicate with it. Our default out of the box security considers that the server could be installed on a multi-user server so other users could inadvertently gain access if we had no security. However in many cases the server will be installed on a single user workstation for developer use, in that case being able to switch off security is desirable so the admin console can be accessed without the need for user accounts. As we switch to the Elytron configuration it is also possible for an administrator to define anonymous authentication policies even if sasl-authentication-factory is not referenced. HTTP remains the same, it is either on or off, a user could however still implement a custom anonymous mechanism. Red Hat Product Security does not consider this issue to be a vulnerability. The default installation are by default secured and set to have an authentication mechanism in place. It is possible to explicitly remove the realm from the configuration files when needed. For example, in case there's need to run in single user mode for development use, ability to switch off security is desirable so the admin console can be accessed without the need for user accounts. There is adequate mechanism in place to secure the WildFly environment. Red Hat Product Security has rated this issue as having a security impact of Low, and a future update may address this flaw. Red Hat Product Security has rated this issue as having a security impact of Low, and a future update may address this flaw. This issue affects the versions of spacewalk as shipped with Red Hat Satellite 5. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of pkicore as shipped with Red Hat Certificate System 9. Red Hat Product Security has rated this issue as having security impact of Low. Please also note that all instances of "authz.evaluateOrder" are set to "deny,allow" by default. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of strongimcv as shipped with Red Hat Enterprise Linux 7 as they did not include support for IKE features. Red Hat Enterprise Linux 6, 7 are not affected by this flaw as it only affects glusterfs-server package. Red Hat Virtualization Hypervisor is not impacted by this flaw, as it uses gluster in a controlled manner via vdsm. This issue affects Openshift Container Platform (OCP) only if you use the container installation method. The container installation method is tech preview in 3.7.1. This issue affected all users who did a containerized etcd in OCP versions 3.7.1-3.6. If etcd is installed via RPM and run via '/usr/bin/etcd' it's not affected by this flaw. You can check if etcd is being run from '/usr//bin/etcd' using a 'ps' command such as this on the master nodes. If Installed via RPM you should get output similar to: ps -ef | grep etcd $/usr/bin/etcd --name=master-0.example.com --data-dir=/var/lib/etcd/ --listen-client-urls=https://10.0.1.1:2379 If etcd is installed via the container method running 'docker ps' on the master will show a container running the registry.access.redhat.com/rhel7/etcd image, eg: sudo docker ps --filter name=etcd_container $704effa9b0cc registry.access.redhat.com/rhel7/etcd "/usr/bin/etcd" 56 minutes ago Up 56 minutes etcd_container This vulnerability can only be exploited by users with deployment permissions. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG 2. This issue affects the version of the kernel package as shipped with Red Hat Enterprise Linux 7. Future kernel updates for Red Hat Enterprise Linux 7 may address this issue. This vulnerability affects gluster servers that have, or have previously had, Gluster volume snapshot scheduling enabled from the CLI. Red Hat Enterprise Virtualization supports volume snapshot scheduling from the Web UI, which uses a distinct mechanism that is not subject to this vulnerability. VM snapshots are not impacted by this flaw. For more information, please see the Vulnerability Article linked under External References. This issue did not affect the versions of glusterfs as shipped with Red Hat Enterprise Linux 6, and 7 because only gluster client is shipped in these products. CVE-2018-1088 affects glusterfs-server package as shipped with Red Hat Gluster Storage 3. Red Hat Enterprise Virtualization includes reposync as a component from the base Enterprise Linux system. It is not used by virtualization or management components, and it is not generally useful to mirror untrusted repositories to either Hypervisor or Management Appliance. For Red Hat Enterprise Virtualization, this issue affects only unlikely configurations and thus is rated as Moderate. This issue affects the versions of pulp as shipped with Red Hat Satellite 6. Red Hat Product Security has rated this issue as having security impact of (Low|Moderate). A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of pulp as shipped with Red Hat Subscription Asset Manager. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This flaw affects all current shipping releases of Red Hat Enterprise Linux. This flaw requires real or emulated midi hardware available in the system. Fixes will be delivered when available. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. For Red Hat Virtualization, Product Security has rated this flaw as Moderate. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of fuse as shipped with Red Hat Enterprise Linux 6 as they did not consider escaped characters when checking mount options. This issue is present in fuse packages included with Red Hat Virtualization, however it is not exploitable under any supported configuration. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. For Red Hat Virtualization, Product Security has rated this flaw as Moderate. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Enterprise Virtualization 3 is now in Extended Life Phase of the support and maintenance lifecycle. Red Hat Product Security has rated this issue as having a security impact of Moderate, and it is not currently planned to be addressed in future updates of Red Hat Virtualization 3. For additional information, refer to the Red Hat Virtualization Life Cycle: https://access.redhat.com/support/policy/updates/rhev/ This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. For Red Hat Virtualization, Product Security has rated this flaw as Moderate. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. This vulnerability is only exploitable where an attacker can provide or influence connection parameters to a PostgreSQL client application using libpq. Contrib modules "dblink" and "postgres_fdw" are examples of applications affected by this flaw. Red Hat Virtualization includes vulnerable versions of postgresql. However this flaw is not known to be exploitable under any supported configuration of Red Hat Virtualization. A future update may address this issue. This issue affects the versions of the rh-postgresql95-postgresql package as shipped with Red Hat Satellite 5.7 and 5.8. However, this flaw is not known to be exploitable under any supported scenario in Satellite 5. A future update may address this issue. Red Hat Enterprise Virtualization Hypervisor includes only selected components of pulp, which are not affected by this flaw. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. For Red Hat Virtualization, Product Security has rated this flaw as Moderate. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of glusterfs as shipped with Red Hat Enterprise Linux 6 and 7, and Red Hat Gluster Storage 3. Red Hat Virtualization includes vulnerable versions of postgresql. However this flaw is not known to be exploitable under any supported configuration of Red Hat Virtualization. A future update may address this issue. This issue affects the versions of the postsgresql package as shipped with Red Hat Satellite 5.8. However, this flaw is not known to be exploitable under any supported scenario in Satellite 5.8. A future update may address this issue. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. For Red Hat Virtualization, Product Security has rated this flaw as Moderate. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. For Red Hat Virtualization, Product Security has rated this flaw as Moderate. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. For Red Hat Virtualization, Product Security has rated this flaw as Moderate. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. For Red Hat Virtualization, Product Security has rated this flaw as Moderate. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. For Red Hat Virtualization, Product Security has rated this flaw as Moderate. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having a security impact of Low, and a future update may address this flaw. This vulnerability affects libssh shipped in Red Hat Enterprise Linux 7 Extras. No libssh packages are included in Red Hat Enterprise Linux 6 and earlier. This issue does not affect libssh2 or openssh. This issue can only be affect applications that use libssh to implement an SSH server; SSH client functionality is not affected. No packages in Red Hat products use libssh to implement an SSH server. Therefore, no package from Red Hat that uses the libssh library is affected by this flaw. The libssh library is available for customer or third party code to use. Such code that is linked against libssh and uses the `ssh_bind*` functions may be affected by this flaw. This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include the vulnerable code. This issue affects the versions of foreman as shipped with Red Hat Enterprise Satellite 6. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat has been made aware of a vulnerability affecting the DHCP client packages as shipped with Red Hat Enterprise Linux 6 and 7. This vulnerability CVE-2018-1111 was rated as having a security impact of Critical. A malicious DHCP server, or an attacker on the local network able to spoof DHCP responses, could use this flaw to execute arbitrary commands with root privileges on systems using NetworkManager and configured to obtain network configuration using the DHCP protocol. Red Hat Enterprise Virtualization 4.1 includes the vulnerable components, but the default configuration is not impacted because NetworkManager is turned off in the Management Appliance, and not used in conjunction with DHCP in the Hypervisor. Customers can still obtain the updated packages from Red Hat Enterprise Linux channels using `yum update`, or upgrade to Red Hat Enterprise Virtualization 4.2, which includes the fixed packages. Red Hat Enterprise Virtualization 3.6 is not vulnerable as it does not use DHCP. This vulnerability affects gluster servers that use 'auth.allow' to restrict access to gluster volumes. Gluster servers using TLS to authenticate gluster clients are not affected by this. This vulnerability allows any client to connect to any gluster volume which only uses auth.allow to restrict access. This issue did not affect the versions of glusterfs as shipped with Red Hat Enterprise Linux 6 and 7 because only gluster client is shipped in these products. CVE-2018-1112 affects glusterfs-server package as shipped with Red Hat Gluster Storage 3. Preventing a user from accessing the system without deleting their account is not a simple matter. For utmost security, the account should be deleted. Short of this, we recommend a three-pronged approach: * change the user's login shell to a harmless command that is not in "/etc/shells" (for example "/bin/false") to prevent commands being run on their behalf * lock the user's password with "usermod -L" to prevent authentication with pam services * prevent access to the user's home directory with "chmod 0" or "chown root" and "chmod 700" to prevent authentication with ssh keys etc This issue does not appear to affect the versions of postgresql as shipped with Red Hat Satellite version 5, CloudForms version 4, Red Hat Single Sign-On 7, and Fuse Service Works 6. The /proc filesystem is not a reliable mechanism to account for processes running on a system, as it is unable to offer snapshot semantics. Short-lived processes have always been able to escape detection by tools that monitor /proc. This CVE simply identifies a reliable way to do so using inotify. Process accounting for security purposes, or with a requirement to record very short-running processes and those attempting to evade detection, should be performed with more robust methods such as auditd(8) (the Linux Audit Daemon) or systemtap. This issue did not affect the versions of git as shipped with Red Hat Enterprise Linux 6 and 7 as they did not include the vulnerable code. This issue did not affect the versions of git as shipped with Red Hat Enterprise Linux 6 as they did not include the vulnerable code. If using OCP 3.6 make sure atomic-openshift-3.6.173.0.128-1.git.0.8da0828.el7 or later is installed on the master. Red Hat Product Security has rated this issue as having a security impact of Moderate, and a future update may address this flaw. SDNInterface has been deprecated in OpenDayLight since it was last used in the final Carbon series release. In addition to the component not being included in OpenDayLight in newer releases, the SDNInterface component is not included in the RHOSP package for opendaylight This flaw only affects libldb/samba when configured as Active Directory Domain Controller. Versions of samba in Red Hat Enterprise Linux 6 and 7 do not support this configuration and therefore are not affected by this flaw. This issue did not affect the version of Liblouis as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having a security impact of Moderate, and a future update may address this flaw. This issue did not affect the versions of giflib as shipped with Red Hat Enterprise Linux 5, 6, an 7. This issue did not affect the versions of giflib as shipped with Red Hat Enterprise Linux 5, 6, an 7. This issue did not affect the versions of libjpeg-turbo as shipped with Red Hat Enterprise Linux 6 and 7. This issue did not affect the versions of exiv2 as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Product Security has rated this issue as having security impact of Low, and a future update may address this flaw. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having security impact of Low, a future update may address this flaw. This issue affects the versions of squid and squid34 as shipped with Red Hat Enterprise Linux 6. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat does not ship struts2 in any product. The source distribution for Red Hat JBoss Fuse Service Works 6 includes struts2 jars; however, they are not used during builds of the product, nor are they included in the distribution, so they are never deployed or used on systems where Fuse Service Works 6 is installed. This issue affects the versions of libjpeg as shipped with Red Hat Enterprise Linux 4 and 5. This issue affects the versions of libjpeg-turbe as shipped with Red Hat Enterprise Linux 6 and 7. However, the problem is limited to the "cjpeg" utility and does not affect the library itself. Red Hat Product Security has rated this issue as having a security impact of Important, and a future update may address this flaw. Openshift Container Platform 3.x versions are potentially vulnerable via the nodejs-slave-jenkins and nodejs-node-jenkins components. However a build would have to occur with a malicious jenkins pipeline, or nodejs source code supplied by an attacker, reducing the impact of this flaw to moderate. This issue affects the versions of ntp as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having a security impact of Low. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ntp as shipped with Red Hat Enterprise Linux 6. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Low, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of ntp as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This flaw cannot be exploited through email in Thunderbird as scripting is disabled in this for email content. It may be possible to exploit through Feeds (Atom or RSS) or other browser-like contexts. This flaw cannot be exploited through email in Thunderbird as scripting is disabled in this for email content. It may be possible to exploit through Feeds (Atom or RSS) or other browser-like contexts. This flaw cannot be exploited through email in Thunderbird as scripting is disabled in this for email content. It may be possible to exploit through Feeds (Atom or RSS) or other browser-like contexts. This flaw cannot be exploited through email in Thunderbird as scripting is disabled in this for email content. It may be possible to exploit through Feeds (Atom or RSS) or other browser-like contexts. Upstream decided to not fix this issue in Firefox ESR 60.2 given the low impact. A future ESR update may correct this flaw. This flaw would impact users who had saved passwords from Firefox 58 or earlier that were not protected by a master password (resulting in an un-encrypted `key3.db`), but set a master password when using Firefox 59 or newer (resulting in an encrypted `key4.db`). The old key file was kept around to facilitate downgrading to Firefox 58. This flaw cannot be exploited through email in Thunderbird as scripting is disabled in this for email content. It may be possible to exploit through Feeds (Atom or RSS) or other browser-like contexts. This flaw cannot be exploited through email in Thunderbird as scripting is disabled in this for email content. It may be possible to exploit through Feeds (Atom or RSS) or other browser-like contexts. This issue does not affect the following Red Hat products, as they do not include the vulnerable version of the RichFaces component: Red Hat JBoss EAP 5.2 Red Hat JBoss Data Virtualization 6.4 Red Hat JBoss BRMS 5.3 Red Hat JBoss Operations Network 3.3 While the affected artifact is being shipped in Fuse 6.3 via camel-vertx component, the vulnerable code is not being used, therefore Fuse 6.3 is not affected. This issue did not affect the versions of rubygem-passenger as shipped with Red Hat Update Infrastructure as they did not include the vulnerable code, which was introduced in a newer version of the package. This issue did not affect the versions of exempi as shipped with Red Hat Enterprise Linux 6 and 7 as they did not include support for WEBP format in the code of which the vulnerability exists. No Red Hat products are directly affected by this flaw; the products that package some parts of the Spring Framework either do not ship the affected messaging component, or use an older version that is not affected. Fuse 6.3 and Fuse Integration Services 2.0 are both not directly affected by the flaw, but both point to the affected versions in their respective Camel-Springboot Maven repository BOMs. Fixes for those repository links will be addressed in advisories via regular patch cycle; customers using Spring stomp messaging from these Maven repositories are advised to update to the new BOMs when available. This issue did affect the versions of gimp as shipped with Red Hat Enterprise Linux 7. However, as this is an issue in a unit test, it is not a problem if you are using the precompiled gimp package. This is only a problem if you recompile gimp using the src.rpm/SPEC file. Even then it's only a problem if you do not make use of isolating build tools like mock, but instead use rpmbuild directly. This issue did not affect the versions of httpd as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include mod_session module. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. The versions of httpd package shipped with Red Hat Enterprise Linux are by default configured in prefork MPM mode, which means that this flaw can result in a crash of child process. The main web server process will not be killed. Also, though the module is loaded by default, it needs to be specifically enabled in order to be exposed to the security flaw. No Red Hat products are affected by CVE-2018-1307. The "AuthType Digest" directive is not enabled in the default httpd configuration as shipped with Red Hat Enterprise Linux, and needs to be explicitly enabled. Therefore this flaw has no impact on the default versions of the httpd package as shipped with Red Hat Enterprise Linux. Also upstream discourages the use of mod_auth_digest because of its inherent security weaknesses and recommends the use of mod_ssl. This issue did not affect the versions of libsndfile as shipped with Red Hat Enterprise Linux 6. This issue affects the versions of libsndfile as shipped with Red Hat Enterprise Linux 7. This issue affects the versions of lucene4 as shipped with Red Hat Enterprise Satellite 6.0 and 6.1. Red Hat Satellite 6.2 and later do not include the lucene4 component and are not affected. This issue did not affect the versions of zsh as shipped with Red Hat Enterprise Linux 5 as scripts were directly handled by the kernel and not special-handled by zsh itself. This issue did not affect any of the Red Hat products as they did not include the Apache Struts 2 package. This issue affects the versions of tika which is embedded in the nutch package as shipped with Red Hat Satellite 5. The tika server is not exposed, as such exploitation is difficult, Red Hat Product Security has rated this issue as having security impact of Low. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Fuse 6.3 and 7 standalone distributions ship but do not use tomcat, and as such are not affected by this flaw; however, Fuse Integration Services 2.0 and Fuse 7 on OpenShift provide the affected artifacts via their respective maven repositories, and will provide fixes for this issue in a future release. This issue affects the versions of tika which is embedded in the nutch package as shipped with Red Hat Satellite 5. The tika server is not exposed, as such exploitation is difficult, Red Hat Product Security has rated this issue as having security impact of Low. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of tika which is embedded in the nutch package as shipped with Red Hat Satellite 5. The tika server is not exposed, as such exploitation is difficult, Red Hat Product Security has rated this issue as having security impact of Low. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having a security impact of Low, and a future update may address this flaw. Red Hat Product Security has rated this issue as having a security impact of Low, and a future update may address this flaw. This issue did not affect the versions of soundtouch as shipped with Red Hat Enterprise Linux 7 as they did not include the vulnerable code. This issue did not affect the versions of libpng as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include the vulnerable code. This issue did not affect the versions of exiv2 as shipped with Red Hat Enterprise Linux 6 and 7. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 6 and 7 (versions 1.8.10 and 1.10.14, respectively). This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 6 and 7 (versions 1.8.10 and 1.10.14, respectively). This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 6 and 7 (versions 1.8.10 and 1.10.14, respectively). This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 6 and 7 (versions 1.8.10 and 1.10.14, respectively). This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 6 and 7 (versions 1.8.10 and 1.10.14, respectively). This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 6 and 7 (versions 1.8.10 and 1.10.14, respectively). This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 6 and 7 (versions 1.8.10 and 1.10.14, respectively). This issue affects the versions of libxml2 as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of libxml2 as shipped with Red Hat Enterprise Linux 6. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Moderate, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of libxml2 as shipped with Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having a security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Virtualization images include wpa_supplicant as a component from the base Red Hat Enterprise Linux operating system, but use of Red Hat Virtualization on a wireless network is neither recommended nor supported. A future update may address this issue. This issue affects the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Moderate, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of libpng as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include the vulnerable code. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this flaw as having Low impact. A future update may address this issue. This issue did not affect the versions of python-django as shipped with Red Hat Update Infrastructure 3 as the vulnerable code was introduced in a newer version of the package. This issue did not affect the versions of libX11 as shipped with Red Hat Enterprise Linux 5 as they did not include the vulnerable code. This issue did not affect the versions of libX11 as shipped with Red Hat Enterprise Linux 5 as they did not include the vulnerable code. A multi-master Openshift Container Platform cluster is more resilient, however a sustained attack would still have an important impact. This issue does not affect 32-bit systems as they do not have a large enough address space to exploit this flaw. Systems with less than 32GB of memory are very unlikely to be affected by this issue due to memory demands during exploitation. This issue does not affect the versions of Linux kernel as shipped with Red Hat Enterprise Linux 5. This issue affects the version of the kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2 will address this issue. HTTP/2 support was added to haproxy in version 1.8, therefore OpenShift Container Platform (OCP) 3.7 and earlier are unaffected by this flaw. OCP 3.11 added a configuration option to ose-haproxy-router that made enabling HTTP/2 support easy, [2]. Prior to that, in versions OCP 3.9 and 3.10, an administrator had to customize the haproxy router configuration to add HTTP/2 support, [3]. OCP 3.9, and 3.10 are rated as moderate because HTTP/2 support was not a standard configuration option, and therefore unlikely to be enabled. Versions of haproxy included in Red Hat Enterprise Linux 6 and 7, excluding rh-haproxy18-haproxy in Red Hat Software Collections, are unaffected as they package versions of haproxy before 1.7. [1] http://www.haproxy.org/news.html [2] https://github.com/openshift/origin/pull/19968 [3] https://docs.openshift.com/container-platform/3.10/install_config/router/customized_haproxy_router.html This issue affects the versions of ceph-iscsi-cli as shipped with Red Hat Ceph Storage 2 and 3. This flaw does not affect python-werkzeug library. It depends on if application uses python-werkzeug library with debug mode enabled. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. This issue did not affect the versions of xorg-x11-server as shipped with Red Hat Enterprise Linux 5 and 6, as well as Red Hat Enterprise Linux 7 prior to 7.4, as they did not allow the use of vulnerable command line options when running with elevated privileges. The default X server configuration in Red Hat Enterprise Linux only allows users logged in on the system's physical console to run Xorg X server. Therefore, users which only have remote access to the the system (for example using SSH) can not exploit this flaw. This issue affects the versions of libmspack as shipped with Red Hat Enterprise Linux 7. This issue affects the versions of libmspack as shipped with Red Hat Enterprise Linux 7. This issue affects the versions of libmspack as shipped with Red Hat Enterprise Linux 7. This issue affects the versions of libmspack as shipped with Red Hat Enterprise Linux 7. This issue did not affect the versions of libreoffice as shipped with Red Hat Enterprise Linux 5, 6 and 7. This issue affects the versions of squirrelmail as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of squirrelmail as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of squirrelmail as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of squirrelmail as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of squirrelmail as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of squirrelmail as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of pango as shipped with Red Hat Enterprise Linux 5, 6, and 7 as they did not include support for emojis. This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Product Security has rated this issue as having Low severity. An attacker could use this flaw to determine whether given usernames exist or not on the server, but no further information is disclosed and there is no availability or integrity impact. A future update may address this issue. This issue affects the version of the kernel package as shipped with Red Hat Enterprise Linux 5. This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 6, 7 and Red Hat Enterprise MRG 2. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of ImageMagick as shipped with Red Hat Enterprise Linux 6. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Low, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of systemd as shipped with Red Hat Enterprise Linux 7 as the vulnerable code was introduced in a newer version of the package. This issue affects the versions of systemd-networkd as shipped with Red Hat Enterprise Linux 7, however the packet is available only through the rhel-7-server-optional-rpms repository and it cannot be exploited unless the interface is explicitly configured to use DHCP. This issue affects the versions of NetworkManager as shipped with Red Hat Enterprise Linux 7 because the package includes some parts of the systemd-networkd code, which present the same vulnerability. NetworkManager is vulnerable to this flaw only when configured to use the internal DHCP, which is not the default. However, when it is, the flaw may be triggered by a connection where either ipv6.method is set to dhcp or it is set to auto, which is the default value. This flaw only affects openswan versions compiled without NSS. When NSS is used as cryptographic library, the RSA routines from NSS are used instead of the custom openswan RSA code that contains the vulnerability. Red Hat Enterprise Linux has only ever shipped with NSS enabled openswan versions, so no Red Hat products are vulnerable to this bug. This issue affects the versions of ghostscript as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Important, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did affect the versions of ghostscript as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Moderate, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5 as they did not include the vulnerable code. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include the vulnerable code. This issue did affect the versions of ghostscript as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of ghostscript as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of ghostscript as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue affects the versions of ghostscript as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Moderate, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of ghostscript as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Important, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of ghostscript as shipped with Red Hat Enterprise Linux 5, 6, and 7. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Important, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of ghostscript as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Important, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of mgetty as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include the scrts binary, which is found in the contribs directory of the upstream source code. This issue did not affect the versions of mgetty as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include the patched login binary provided by mgetty. This issue affects the versions of ghostscript as shipped with Red Hat Enterprise Linux 7. This issue did not affect the versions of ghostscript as shipped with Red Hat Enterprise Linux 5 and 6. This issue did not affect the versions of soundtouch as shipped with Red Hat Enterprise Linux 7 as they did not include the vulnerable code. OpenShift Container Platform (OCP) source-to-image uses the git client packaged with the OCP container images. Since RHEL7 and its associated images are impacted, source-to-image is also impacted. The atomic-openshift package running on the masters controls the code that determines the source-to-image build image in use, therefore a cluster update is required to patch this issue. Full instructions will be provided in Security Errata provided for this issue. In OCP 3.6 and earlier, source-to-image executes in a privileged container on the node. Therefore the severity of this CVE is important for these versions. OCP 3.7 and later execute source-to-image git pulls in an unprivileged init container. The version of rubygem-asciidoctor included in Red Hat Virtualization is affected by this flaw, however it is not exposed to user input in such a way that the vulnerability could be exploited by an attacker. Users of OpenShift Container Platform 3.x should upgrade to 3.11 to pick up a fix for this issue. Not vulnerable. This issue did not affect the versions of kernel as shipped with any Red Hat product. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 may address this issue. Red Hat Product Security is aware of this issue. Updates will be released as they become available. For additional information, please refer to the Red Hat Knowledgebase article: https://access.redhat.com/security/vulnerabilities/ssbd This is a hardware issue and is not currently planned to be mitigated in software (in the Linux kernel). As such, we do not plan to provide mitigations for this issue in the kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7, and Red Hat Enterprise MRG 2. Future CPU vendor microcode updates may address this issue. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 may address this issue. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7, and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 6, 7, and Red Hat Enterprise MRG 2 may address this issue. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2 may address this issue. This issue affects the versions of kibana as shipped with Red Hat OpenShift Enterprise Linux. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of kibana as shipped with Red Hat OpenShift Enterprise Linux. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of kibana as shipped with Red Hat OpenShift Enterprise Linux. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of kibana as shipped with Red Hat OpenShift Enterprise Linux. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of cups as shipped with Red Hat Enterprise Linux as cups on Linux does not support the Sandbox feature. This issue did not affect the versions of cups as shipped with Red Hat Enterprise Linux as cups on Linux does not support the Sandbox feature. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. The affected code is present in esc and xulrunner, however esc has no support for audio, and xulrunner is limited to using only local content that an attacker can not control. These components are not impacted by this vulnerability. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future Linux kernel updates for the respective releases may address this issue. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 7, its real-time kernel, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE, as a code with the flaw is not built and shipped with the products listed. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This is not currently planned to be addressed in future updates of the product due to its life cycle. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future Linux kernel updates for the respective releases may address this issue. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 7, its real-time kernel, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE, as a code with the flaw is not built and shipped with the products listed. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases may address this issue. This vulnerability affects Quagga versions after 1.1.0. Versions 0.99.x, included with Red Hat Enterprise Linux, are not affected by this issue. Glibc's heap protection mitigations render this issue more difficult to exploit, though bypasses may still be possible. Red Hat Product Security has given this vulnerability a rating of Low. We believe the potential for a crash on supported architectures is very small. Red Hat Product Security has rated this issue as having security impact of Low. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. PSK based authentication should only be used when the randomness and confidentially of the shared secret can be guaranteed. PSKs should also not be used as Group Secrets, where the security of the PSK is only as strong as the weakest participant in the group. Public Key or EAP authentication methods should be used whenever possible. If PSK must be used, it is essential to ensure the shared secret has a high degree of randomness and is not derived from a password with low entropy, as specified clearly in the IKEv2 specification in RFC 7296. To use passwords for authentication of IKE/IPsec peers, the IKEv2 protocol supports various methods that are not based on (inherently weak) PSKs and which are not vulnerable to offline dictionary attacks: RFC 5998: EAP-Only Authentication in IKEv2 RFC 6617: Secure Pre-Shared Key (PSK) Authentication for IKE RFC 6631: Password Authenticated Connection Establishment with IKEv2 RFC 6628: Efficient Augmented Password-Only Authentication and Key Exchange for IKEv2 As implementations supporting IKE assume the security of provided PSKs, and no mechanism within the protocol allows for password-stretching, we do not anticipate any software fixes becoming available. The research paper that describes the problems of using weak PSKs also listed another security issue with respect to RSA keys that has different CVE numbers. Libreswan is not vulnerable to those attacks as it requires IKEv1 using either ("Encryption with RSA" (value 5) or "Revised encryption with RSA" (value 6). Both of these modes are not implemented by libreswan. Red Hat Product Security is aware of this issue. Updates will be released as they become available. For additional information, please refer to the Red Hat Knowledgebase article: https://access.redhat.com/articles/3553061 This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64, and Red Hat Enterprise Linux 7 for Power 9. Future kernel updates for the respective releases will address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, but to a lesser degree. As such, the issue severity for RHEL5 is considered Moderate. This is not currently planned to be addressed in future updates of the product due to its life cycle and the issue severity. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Product Security is aware of this issue. Updates will be released as they become available. For additional information, please refer to the Red Hat Knowledgebase article: https://access.redhat.com/articles/3553061 This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64, and Red Hat Enterprise Linux 7 for Power 9. Future kernel updates for the respective releases will address this issue. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, but to a lesser degree. As such, the issue severity for RHEL5 is considered Moderate. This is not currently planned to be addressed in future updates of the product due to its life cycle and the issue severity. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This is a flaw in the Intel processor execution engine sharing on SMT (e.g. Hyper-Threading) architectures. It can result in leakage of secret data in applications such as OpenSSL that has secret dependent control flow at any granularity level. In order to exploit this flaw, the attacker needs to run a malicious process on the same core of the processor as the victim process. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, and 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. The code of in-kernel TLS implementation with the flaw is not enabled and is not built in the products listed. This is essentially an integer truncation issue, and not an integer overflow. We have determined that this should not affect any other data allocated close to the 16-bit integer in question "dbentry-> n_key_data". Red Hat Product Security does not consider this issue as a security flaw. This issue did not affect the versions of bind as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include the vulnerable code. This issue is the same as CVE-2017-3139. For more information, refer to CVE-2017-3139. This security flaw only affects bind versions 9.12.0 and 9.12.1. Since Red Hat Enterprise Linux does not ship any of these bind versions, it is not affected. This security flaw only affects bind versions 9.12.0 and 9.12.1. Since Red Hat Enterprise Linux does not ship any of these bind versions, it is not affected. The "deny-answer-aliases" configuration option is not enabled in default configurations of bind. Upstream states that this option is very rarely used. As such, if customers have not specifically enabled this option in configurations, the risk should be mitigated. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG 2, as KASLR feature is not present or enabled in these products. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7, its real-time kernel, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue. This issue affects the versions of rsync as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise Linux 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of exiv2 as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7. This issue did not affect the versions of LibRaw as shipped with Red Hat Enterprise Linux 7 as they did not include the vulnerable code. This issue did not affect the versions of dcraw as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include the vulnerable code. This issue did not affect the versions of libkdcraw as shipped with Red Hat Enterprise Linux 7 as they did not include the vulnerable code. This issue did not affect the versions of dcraw as shipped with Red Hat Enterprise Linux 5 as they did not include the vulnerable code. This issue affects the versions of dcraw as shipped with Red Hat Enterprise Linux 6. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Moderate, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of dcraw as shipped with Red Hat Enterprise Linux 5 and 6 as they did not include the vulnerable code. This issue did not affect the versions of LibRaw as shipped with Red Hat Enterprise Linux 7 as they did not include the vulnerable code. This issue did not affect the versions of LibRaw as shipped with Red Hat Enterprise Linux 7 as they did not include the vulnerable code. This issue did not affect the versions of LibRaw as shipped with Red Hat Enterprise Linux 7 as they did not include the vulnerable code. This issue affects the versions of LibRaw as shipped with Red Hat Enterprise Linux 7. This issue did not affect the versions of LibRaw as shipped with Red Hat Enterprise Linux 7. This issue did not affect the versions of LibRaw as shipped with Red Hat Enterprise Linux 7. JBoss EAP 7.x only uses the vulnerable Jackson Databind library for marshalling and unmarshalling of JSON objects passed to JAX-RS webservices. Some advice about how to remain safe when using JAX-RS webservices on JBoss EAP 7.x is available here: https://access.redhat.com/solutions/3279231 This issue affects the versions of jackson-databind (in Satellite 6.0 and 6.1) and candlepin (which embeds a copy of jackson-databind in Satellite 6.2) as shipped with Red Hat Satellitw 6.x. However the affected code is NOT used at this time: Candlepin currently uses the default type resolution configuration for the ObjectMappers it creates/uses. Nowhere in candlepin do we enable global polymorphic deserialization via enableDefaultTyping(...), therefore based on the documentation sited BZ 1462702 , candlepin should not be affected. However as the vulnerable software ships with the product we have marked them as vulnerable to ensure the issue is tracked. Red Hat Subscription Asset Manager version 1 is now in a reduced support phase receiving only Critical impact security fixes. This issue has been rated as having Important security impact and is not currently planned to be addressed in future updates. This issue affects the versions of libtasn1 as shipped with Red Hat Satellite version 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of python-django as shipped with Red Hat Satellite version 6. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of python-django as shipped with Red Hat Subscription Asset Manager version 1. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE, as the code with the flaw is not built and is not shipped with the products listed. This issue affects the versions of glibc and compat-glibc as shipped with Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of puppet-agent as shipped with Red Hat Satellite 6 as this issue is specific to Windows platform only. This issue did not affect the versions of puppet-agent as shipped with Red Hat Satellite 6 as this issue is specific to Windows platform only. This issue did not affect the versions of binutils as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of glibc and compat-glibc as shipped with Red Hat Enterprise Linux 5, 6, and 7. This issue did not affect the versions of cups as shipped with Red Hat Enterprise Linux as they did not include support for AppArmor. Red Hat Satellite 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/satellite/. This issue affects the versions of golang as shipped with Red Hat OpenShift Enterprise 3. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of sblim-sfcb as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7. This issue affects the versions of Exim as shipped in Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is already in the Extended Life Phase of its life cycle and Exim is not on the list of components supported via Red Hat Enterprise Linux 5 Extended Life-cycle Support (ELS) add-on, therefore there's currently no plan to address this issue in Red Hat Enterprise Linux 5. For more information about Red Hat Enterprise Linux 5 life cycle and ELS add-on scope of support, see: https://access.redhat.com/support/policy/updates/errata/#Extended_Life_Cycle_Phase https://access.redhat.com/articles/2901071 The Exim mail server is not shipped in Red Hat Enterprise Linux 6 and 7. This issue did not affect the versions of kdebase-runtime as shipped with Red Hat Enterprise Linux 6. This issue did not affect the versions of kde-runtime as shipped with Red Hat Enterprise Linux 7. Versions of the perl interpreter older than 5.18 are not vulnerable. As a result, the versions of perl as shipped in Red Hat Enterprise Linux version 7, 6 and 5 are not affected by this vulnerability. Versions of the perl interpreter older than 5.22 are not vulnerable. As a result, the versions of perl as shipped in Red Hat Enterprise Linux version 7, 6 and 5, as well as the versions of rh-perl520-perl as shipped with Red Hat Software Collections are not affected by this vulnerability. This is not a security flaw in libgcrypt. However if an application uses The El-gamal algorithm implemented by libgcrypt in a particular way than the application would be vulnerable to security flaw(s). More detailed explanation is available at: https://lists.gnupg.org/pipermail/gcrypt-devel/2018-February/004401.html Red Hat Product Security has rated this issue as having security impact of Low. This issue does not affect the versions of ZZIPlib as shipped in Red Hat Enterprise Linux 7, unless the package is recompiled with Address Sanitizer. The flaw is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. The 64-bit versions of perl have not been found to be affected. As a result, this issue did not affect the versions of perl as shipped with Red Hat Enterprise Linux 7, and the versions of rh-perl526-perl, rh-perl524-perl and rh-perl520-perl as shipped with Red Hat Software Collections. This issue affects the 32bit versions of perl as shipped with Red Hat Enterprise Linux 6. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Low, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue may affect the versions of perl as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Extended Life Cycle phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of ruby as shipped with Red Hat CloudForms 4. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ruby as shipped with Red Hat Subscription Asset Manager 1. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5. This is not currently planned to be addressed in future updates of the product due to its life cycle. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue. This issue did not affect the versions of Irssi as shipped with Red Hat Enterprise Linux 6 and 7 as they did not include support for SASL. This issue did not affect the versions of Irssi as shipped with Red Hat Enterprise Linux 6 and 7, since the affected code was introduced in Irssi version 1.0.0. This issue did not affect the versions of shadow-utils as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not provide newgidmap program. This issue did not affect the versions of libvncserver as shipped with Red Hat Enterprise Linux 6 and 7. This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG 2, as KASLR feature is not present or enabled in these products. This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7, its real-time kernel, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE, as the code with the flaw is not present in the products listed. Subscription Asset Manager is now in a reduced support phase receiving only Critical impact security fixes. This issue has been rated as having a security impact of Important, and is not currently planned to be addressed in future updates. Satellite 6.2 does not support c3p0 classes. Since the latter are required for this flaw, therefore Satellite 6.2 is not affected. Satellite 6.3 and 6.4 are not affected because Candlepin does not use polymorphic deserialization. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2. Future Linux kernel updates for the respective releases may address this issue. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 7, its real-time kernel, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE, as a code with the flaw is not built and shipped with the products listed. This issue affects the versions of django as shipped with Red Hat Subscription Asset Manager. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of django as shipped with Red Hat Subscription Asset Manager. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64 and Red Hat Enterprise Linux 7 for Power 9 LE. Future Linux kernel updates for the respective releases may address this issue. This issue did not affect the versions of Exempi as shipped with Red Hat Enterprise Linux 6 and 7 as they did not include support for WebP file format. This issue did not affect the versions of util-linux as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include support for umount autocompletion. This flaw is a user authentication bypass in the SSH Server functionality of paramiko (normally used by subclassing `paramiko.ServerInterface`). Where paramiko is used only for its client-side functionality (e.g. `paramiko.SSHClient`), the vulnerability is not exposed and thus cannot be exploited. The following Red Hat products use paramiko only in client-side mode. Server side functionality is not used. * Red Hat Ceph Storage 2 * Red Hat CloudForms 4 * Red Hat Enterprise Linux 7 * Red Hat Enterprise Virtualization * Red Hat Gluster Storage 3 * Red Hat Openshift Container Platform * Red Hat Quick Cloud Installer * Red Hat Satellite 6 * Red Hat Storage Console 2 * Red Hat OpenStack Platform * Red Hat Update Infrastructure Zookeeper is not designed to run as a publicly available service and it always needs to be deployed and operated in a secured environment. As a result it is assumed that no zookeeper ports are available publically, so with this assumption JBoss Fuse is not affected by this issue. Tomcat 6, and Red Hat products shipping it, are not affected by this CVE. Tomcat 7, 8, and 9, as well as Red Hat Products shipping them, are affected. Affected products, including Red Hat JBoss Web Server 3 and 5, Enterprise Application Server 6, and Fuse 7, may provide fixes for this issue in a future release. While Fuse 6.3 and Fuse 7.0 ship vulnerable artifact via camel-pdfbox, however, the flawed code is not being used therefore no execution path leads to an exposure to this vulnerability, so both Fuse 6.3, 7 standalone are not affected. However, Fuse 7.0 on OpenShift ship vulnerable artifact via maven BOM, so setting Fuse 7.0 as affected for this reason only. This issue affects the versions of rubygem-loofah as shipped with Red Hat CloudForms 4. Red Hat Product Security has rated this issue as having a security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ Subscription Asset Manager is now in a reduced support phase receiving only Critical impact security fixes. This issue has been rated as having a security impact of Important, and is not currently planned to be addressed in future updates. This issue did not affect the versions of Candlepin as shipped with Red Hat Satellite 6 as Candlepin uses slf4j-api and not the affected slf4j-ext (which is not on the Candlepin classpath). Red Hat Enterprise Virtualization Manager 4.1 is affected by this issue. Updated packages that address this issue are available through the Red Hat Enterprise Linux Server channels. Virtualization Manager hosts should be subscribed to these channels and obtain the updates via `yum update`. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life cycle: https://access.redhat.com/support/policy/updates/errata/. This issue did not affect the versions of elfutils as shipped with Red Hat Enterprise Linux 5, 6, and 7 as they did not include the vulnerable commit. This issue did not affect the versions of elfutils as shipped with Red Hat Developer Toolset 6 and 7 as they did not include the vulnerable commit. This issue affects the versions of ruby as shipped with Red Hat CloudForms 4. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ruby as shipped with Red Hat Subscription Asset Manager 1. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ruby as shipped with Red Hat CloudForms 4. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ruby as shipped with Red Hat Subscription Asset Manager 1. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue did not affect the versions of ruby as shipped with Red Hat Enterprise Linux 5 and 6. This issue affects the versions of ruby as shipped with Red Hat CloudForms 4. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. This issue affects the versions of ruby as shipped with Red Hat Subscription Asset Manager 1. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. Red Hat Product Security has rated this issue as having a security impact of Low, and a future update may address this flaw. This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7, and Red Hat Enterprise MRG 2. Future kernel updates for Red Hat Enterprise Linux 5, 6, 7, and Red Hat Enterprise MRG 2 may address this issue. This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6, and 7. The following products are now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates of these products. * Red Hat Enterprise Linux 5 * Red Hat Enterprise Virtualization 3 For additional information, please refer to the Life Cycle and Update Policies: https://access.redhat.com/support/policy/update_policies/ This issue did not affect the versions of ImageMagick as shipped with Red Hat Enterprise Linux 5, 6 and 7 as they did not include the vulnerable code. This issue did not affect the versions of Exiv2 as shipped with Red Hat Enterprise Linux 6 and 7. This issue did not affect the versions of libxml2 as shipped with Red Hat Enterprise Linux 5, 6, and 7. The following products are now in Extended Life Phase of the support and maintenance life cycle. * Red Hat Enterprise Linux 5 * Red Hat Enterprise Virtualization 3 The following products are now in Maintenance Phase 2 of the support and maintenance life cycle. * Red Hat Enterprise Linux 6 This issue is not currently planned to be addressed in future updates of these products. For additional information, please refer to the Life Cycle and Update Policies: https://access.redhat.com/support/policy/update_policies/ This issue did not affect the versions of Exiv2 as shipped with Red Hat Enterprise Linux 6 and 7 as they did not include support for BigTIFF images. This issue did not affect the versions of Exiv2 as shipped with Red Hat Enterprise Linux 6 and 7 as they did not include support for BigTIFF images. This issue did not affect the versions of Exiv2 as shipped with Red Hat Enterprise Linux 6 and 7, up to 7.4, as they did not include support for printing IPTC Photo Metadata. https://access.redhat.com/kb/docs/DOC-30741 http://www.ocert.org/advisories/ocert-2010-001.html https://www.openssl.org/news/secadv_20140605.txt http://web.mit.edu/kerberos/advisories/MITKRB5-SA-2011-006.txt http://web.mit.edu/kerberos/advisories/MITKRB5-SA-2011-006.txt http://web.mit.edu/kerberos/advisories/MITKRB5-SA-2011-006.txt http://web.mit.edu/Kerberos/advisories/MITKRB5-SA-2011-007.txt http://www.adobe.com/support/security/bulletins/apsb11-21.html http://www.adobe.com/support/security/bulletins/apsb11-21.html http://www.adobe.com/support/security/bulletins/apsb11-21.html http://www.adobe.com/support/security/bulletins/apsb11-21.html http://www.adobe.com/support/security/bulletins/apsb11-21.html http://www.adobe.com/support/security/bulletins/apsb11-21.html http://www.adobe.com/support/security/bulletins/apsb11-21.html http://www.adobe.com/support/security/bulletins/apsb11-21.html http://www.adobe.com/support/security/bulletins/apsb11-21.html http://www.adobe.com/support/security/bulletins/apsb11-21.html http://www.adobe.com/support/security/bulletins/apsb11-21.html http://www.adobe.com/support/security/bulletins/apsb11-21.html http://www.adobe.com/support/security/bulletins/apsb11-21.html http://www.adobe.com/support/security/bulletins/apsb11-21.html http://www.adobe.com/support/security/bulletins/apsb11-28.html http://www.adobe.com/support/security/bulletins/apsb11-28.html http://www.adobe.com/support/security/bulletins/apsb11-28.html http://www.adobe.com/support/security/bulletins/apsb11-28.html http://www.adobe.com/support/security/bulletins/apsb11-28.html http://www.adobe.com/support/security/bulletins/apsb11-28.html http://www.adobe.com/support/security/bulletins/apsb11-28.html http://www.adobe.com/support/security/bulletins/apsb11-28.html http://www.adobe.com/support/security/bulletins/apsb11-28.html http://www.adobe.com/support/security/bulletins/apsb11-28.html http://www.adobe.com/support/security/bulletins/apsb11-28.html http://www.php.net/security/crypt_blowfish.php https://www.nds.ruhr-uni-bochum.de/research/publications/breaking-xml-encryption-pkcs15/ http://sources.redhat.com/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=ed51cfa24ca27746ab09b59280b94117dd58cba3 http://git.kernel.org/linus/17dd759c67f21e34f2156abcf415e1f60605a188 http://www.mozilla.org/security/announce/2011/mfsa2011-43.html http://www.mozilla.org/security/announce/2012/mfsa2012-11.html http://www.rsyslog.com/potential-dos-with-malformed-tag/ http://www.openssl.org/news/secadv_20110906.txt http://httpd.apache.org/security/vulnerabilities_22.html#2.2.21 http://www.contextis.com/research/blog/reverseproxybypass/ http://www.openswan.org/download/CVE-2011-3380/CVE-2011-3380.txt http://www.oracle.com/technetwork/topics/security/cpuoct2011-330135.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/cpuoct2011-330135.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html http://www.oracle.com/technetwork/topics/security/javacpufeb2012-366318.html http://www.oracle.com/technetwork/topics/security/javacpufeb2012-366318.html http://www.mozilla.org/security/announce/2011/mfsa2011-46.html http://www.mozilla.org/security/announce/2011/mfsa2011-47.html http://www.mozilla.org/security/announce/2011/mfsa2011-49.html http://www.mozilla.org/security/announce/2012/mfsa2012-04.html http://www.mozilla.org/security/announce/2012/mfsa2012-02.html http://puppetlabs.com/security/cve/cve-2011-3848/ http://puppetlabs.com/security/cve/cve-2011-3869/ http://puppetlabs.com/security/cve/cve-2011-3870/ http://puppetlabs.com/security/cve/cve-2011-3871/ http://www.puppetlabs.com/security/cve/cve-2011-3872/ http://lists.freedesktop.org/archives/xorg-announce/2011-October/001744.html http://lists.freedesktop.org/archives/xorg-announce/2011-October/001744.html http://openswan.org/download/CVE-2011-4073/CVE-2011-4073.txt http://www.wireshark.org/security/wnpa-sec-2011-17.html http://www.wireshark.org/security/wnpa-sec-2011-18.html http://www.wireshark.org/security/wnpa-sec-2011-19.html http://web.mit.edu/kerberos/advisories/MITKRB5-SA-2011-006.txt https://www.isc.org/software/bind/advisories/cve-2011-4313 https://deepthought.isc.org/article/AA-00549 https://community.qualys.com/blogs/securitylabs/2011/11/23/apache-reverse-proxy-bypass-issue http://java.net/jira/browse/JAVASERVERFACES-2247 http://www.jakobk.com/2011/11/jsf-value-expression-injection-vulnerability/ http://www.adobe.com/support/security/bulletins/apsb12-08.html http://www.adobe.com/support/security/bulletins/apsb12-08.html http://www.adobe.com/support/security/bulletins/apsb12-08.html http://www.adobe.com/support/security/bulletins/apsb12-08.html http://research.cs.wisc.edu/condor/security/vulnerabilities/CONDOR-2012-0001.html https://code.google.com/p/memcached/issues/detail?id=192 http://insecurety.net/?p=872 http://vsecurity.com/resources/advisory/20120324-1/ http://www.openoffice.org/security/cves/CVE-2012-0037.html http://www.libreoffice.org/advisories/CVE-2012-0037/ http://www.mozilla.org/security/announce/2012/mfsa2012-01.html http://www.mozilla.org/security/announce/2012/mfsa2012-07.html http://www.mozilla.org/security/announce/2012/mfsa2012-08.html http://www.oracle.com/technetwork/topics/security/javacpufeb2012-366318.html http://www.oracle.com/technetwork/topics/security/javacpufeb2012-366318.html http://www.oracle.com/technetwork/topics/security/javacpufeb2012-366318.html http://www.oracle.com/technetwork/topics/security/javacpufeb2012-366318.html http://www.oracle.com/technetwork/topics/security/javacpufeb2012-366318.html http://www.oracle.com/technetwork/topics/security/javacpufeb2012-366318.html http://www.oracle.com/technetwork/topics/security/javacpufeb2012-366318.html http://www.adobe.com/support/security/bulletins/apsb12-03.html http://www.adobe.com/support/security/bulletins/apsb12-03.html http://www.adobe.com/support/security/bulletins/apsb12-03.html http://www.adobe.com/support/security/bulletins/apsb12-03.html http://www.adobe.com/support/security/bulletins/apsb12-03.html http://www.adobe.com/support/security/bulletins/apsb12-03.html http://www.adobe.com/support/security/bulletins/apsb12-05.html http://www.adobe.com/support/security/bulletins/apsb12-05.html http://www.adobe.com/support/security/bulletins/apsb12-07.html http://www.adobe.com/support/security/bulletins/apsb12-08.html http://www.adobe.com/support/security/bulletins/apsb12-08.html http://www.adobe.com/support/security/bulletins/apsb12-08.html http://www.adobe.com/support/security/bulletins/apsb12-09.html http://www.sudo.ws/sudo/alerts/sudo_debug.html http://www.samba.org/samba/security/CVE-2012-0870 http://www.openssl.org/news/secadv_20120312.txt http://web.mit.edu/kerberos/advisories/MITKRB5-SA-2012-001.txt http://web.mit.edu/kerberos/advisories/MITKRB5-SA-2012-001.txt http://krbdev.mit.edu/rt/Ticket/Display.html?id=7527 http://web.mit.edu/kerberos/www/krb5-1.10/ https://www.isc.org/software/bind/advisories/cve-2012-1033 http://puppetlabs.com/security/cve/cve-2012-1053/ http://puppetlabs.com/security/cve/cve-2012-1054/ http://www.samba.org/samba/history/samba-3.6.4.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.adobe.com/support/security/bulletins/apsb12-18.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.isc.org/software/bind/advisories/cve-2012-1667 http://www.oracle.com/technetwork/topics/security/alert-cve-2012-4681-1835715.html http://www.phpmyadmin.net/home_page/security/PMASA-2012-2.php http://www.mozilla.org/security/announce/2012/mfsa2012-59.html http://puppetlabs.com/security/cve/cve-2012-1986/ http://puppetlabs.com/security/cve/cve-2012-1987/ http://puppetlabs.com/security/cve/cve-2012-1988/ http://puppetlabs.com/security/cve/cve-2012-1989/ http://www.adobe.com/support/security/bulletins/apsb12-14.html http://www.adobe.com/support/security/bulletins/apsb12-14.html http://www.adobe.com/support/security/bulletins/apsb12-14.html http://www.adobe.com/support/security/bulletins/apsb12-14.html http://www.adobe.com/support/security/bulletins/apsb12-14.html http://www.adobe.com/support/security/bulletins/apsb12-14.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.openssl.org/news/secadv_20120419.txt http://www.php.net/archive/2012.php#id2012-05-08-1 http://openssl.org/news/secadv_20120510.txt http://cxf.apache.org/cve-2012-2378.html http://cxf.apache.org/cve-2012-2379.html http://blog.restlet.com/2012/05/23/restlet-framework-2-1-rc5-and-2-0-14-released/ http://www.libreoffice.org/advisories/CVE-2012-2665/ http://www.openssl.org/news/secadv_20130205.txt http://www.oracle.com/technetwork/topics/security/alert-cve-2012-4681-1835715.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://puppetlabs.com/security/cve/cve-2012-3408/ https://kb.isc.org/article/AA-00729 http://puppetlabs.com/security/cve/cve-2012-3864/ http://puppetlabs.com/security/cve/cve-2012-3865/ http://puppetlabs.com/security/cve/cve-2012-3866/ http://puppetlabs.com/security/cve/cve-2012-3867/ https://kb.isc.org/article/AA-00730 https://www.mozilla.org/security/advisories/mfsa2012-65/ http://www.mozilla.org/security/announce/2012/mfsa2012-74.html http://www.mozilla.org/security/announce/2012/mfsa2012-75.html http://www.mozilla.org/security/announce/2012/mfsa2012-77.html http://www.mozilla.org/security/announce/2012/mfsa2012-79.html http://www.mozilla.org/security/announce/2012/mfsa2012-87.html http://www.mozilla.org/security/announce/2012/mfsa2012-81.html http://www.mozilla.org/security/announce/2012/mfsa2012-84.html http://www.mozilla.org/security/announce/2012/mfsa2012-83.html http://www.mozilla.org/security/announce/2012/mfsa2012-82.html http://www.mozilla.org/security/announce/2012/mfsa2012-85.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-16.html http://www.adobe.com/support/security/bulletins/apsb12-19.html http://www.adobe.com/support/security/bulletins/apsb12-19.html http://www.adobe.com/support/security/bulletins/apsb12-19.html http://www.adobe.com/support/security/bulletins/apsb12-19.html http://www.adobe.com/support/security/bulletins/apsb12-19.html http://www.adobe.com/support/security/bulletins/apsb12-19.html http://www.mozilla.org/security/announce/2012/mfsa2012-85.html http://www.mozilla.org/security/announce/2012/mfsa2012-85.html http://www.mozilla.org/security/announce/2012/mfsa2012-85.html http://www.mozilla.org/security/announce/2012/mfsa2012-85.html http://www.mozilla.org/security/announce/2012/mfsa2012-85.html http://www.mozilla.org/security/announce/2012/mfsa2012-83.html http://www.mozilla.org/security/announce/2012/mfsa2012-86.html http://www.mozilla.org/security/announce/2012/mfsa2012-86.html http://www.mozilla.org/security/announce/2012/mfsa2012-86.html http://www.mozilla.org/security/announce/2012/mfsa2012-86.html http://www.mozilla.org/security/announce/2012/mfsa2012-88.html http://www.mozilla.org/security/announce/2012/mfsa2012-89.html http://www.mozilla.org/security/announce/2012/mfsa2012-89.html http://www.mozilla.org/security/announce/2012/mfsa2012-90.html http://www.mozilla.org/security/announce/2012/mfsa2012-90.html http://www.mozilla.org/security/announce/2012/mfsa2012-90.html http://www.mozilla.org/security/announce/2012/mfsa2012-93.html http://www.mozilla.org/security/announce/2012/mfsa2012-92.html http://www.mozilla.org/security/announce/2012/mfsa2012-95.html http://www.mozilla.org/security/announce/2012/mfsa2012-96.html http://www.mozilla.org/security/announce/2012/mfsa2012-97.html http://www.mozilla.org/security/announce/2012/mfsa2012-101.html http://www.mozilla.org/security/announce/2012/mfsa2012-99.html http://www.mozilla.org/security/announce/2012/mfsa2012-103.html http://www.mozilla.org/security/announce/2012/mfsa2012-104.html http://www.mozilla.org/security/announce/2012/mfsa2012-105.html http://www.mozilla.org/security/announce/2012/mfsa2012-105.html http://www.mozilla.org/security/announce/2012/mfsa2012-105.html http://www.mozilla.org/security/announce/2012/mfsa2012-105.html http://www.mozilla.org/security/announce/2012/mfsa2012-105.html http://www.mozilla.org/security/announce/2012/mfsa2012-105.html http://www.mozilla.org/security/announce/2012/mfsa2012-105.html http://www.phpmyadmin.net/home_page/security/PMASA-2012-3.php http://www.phpmyadmin.net/home_page/security/PMASA-2012-4.php http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.36 http://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.32 https://issues.apache.org/jira/browse/QPID-4631 https://issues.apache.org/jira/browse/QPID-4629 https://issues.apache.org/jira/browse/QPID-4629 https://issues.apache.org/jira/browse/QPID-4629 https://access.redhat.com/knowledge/solutions/295843 http://www.freeipa.org/page/CVE-2012-4546 http://www.gwtproject.org/release-notes.html#Release_Notes_2_4_0 http://www.phpmyadmin.net/home_page/security/PMASA-2012-4.php http://www.oracle.com/technetwork/topics/security/alert-cve-2012-4681-1835715.html http://xforce.iss.net/xforce/xfdb/78764 http://xforce.iss.net/xforce/xfdb/78765 http://xforce.iss.net/xforce/xfdb/78766 http://xforce.iss.net/xforce/xfdb/78767 http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://www.oracle.com/technetwork/topics/security/javacpuoct2012-1515924.html http://googlechromereleases.blogspot.com/2012/11/stable-update-for-chrome-os_30.html https://code.google.com/p/chromium/issues/detail?id=145525 https://kb.isc.org/article/AA-00801 http://www.adobe.com/support/security/bulletins/apsb12-24.html http://www.adobe.com/support/security/bulletins/apsb12-24.html http://www.adobe.com/support/security/bulletins/apsb12-24.html http://www.adobe.com/support/security/bulletins/apsb12-24.html http://www.adobe.com/support/security/bulletins/apsb12-24.html http://www.adobe.com/support/security/bulletins/apsb12-24.html http://www.adobe.com/support/security/bulletins/apsb12-24.html http://www.mozilla.org/security/announce/2012/mfsa2012-75.html http://research.cs.wisc.edu/htcondor/security/vulnerabilities/CONDOR-2012-0003.html http://www.freeipa.org/page/CVE-2012-5484 https://bugs.launchpad.net/keystone/+bug/1064914 http://www.nds.ruhr-uni-bochum.de/research/publications/backwards-compatibility/ http://cxf.apache.org/cve-2012-5575.html https://mariadb.atlassian.net/browse/MDEV-3908 http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://lists.openstack.org/pipermail/openstack-announce/2012-December/000059.html http://framework.zend.com/security/advisory/ZF2012-05 http://phenoelit.org/blog/archives/2012/12/21/let_me_github_that_for_you/index.html http://seclists.org/oss-sec/2012/q4/511 http://seclists.org/oss-sec/2012/q4/511 http://seclists.org/oss-sec/2012/q4/511 http://www.adobe.com/support/security/bulletins/apsb12-27.html http://www.adobe.com/support/security/bulletins/apsb12-27.html http://www.adobe.com/support/security/bulletins/apsb12-27.html https://kb.isc.org/article/AA-00828 https://kb.isc.org/article/AA-00855 http://www.mozilla.org/security/announce/2012/mfsa2012-105.html http://www.mozilla.org/security/announce/2012/mfsa2012-106.html http://www.mozilla.org/security/announce/2012/mfsa2012-106.html http://www.mozilla.org/security/announce/2012/mfsa2012-106.html http://www.mozilla.org/security/announce/2012/mfsa2012-94.html http://www.mozilla.org/security/announce/2012/mfsa2012-102.html http://www.mozilla.org/security/announce/2012/mfsa2012-106.html http://www.mozilla.org/security/announce/2012/mfsa2012-105.html http://www.mozilla.org/security/announce/2012/mfsa2012-105.html http://www.mozilla.org/security/announce/2012/mfsa2012-100.html http://www.mozilla.org/security/announce/2012/mfsa2012-91.html http://www.mozilla.org/security/announce/2012/mfsa2012-91.html https://developers.google.com/web-toolkit/release-notes#Release_Notes_Current http://www.kb.cert.org/vuls/id/922681 http://www.kb.cert.org/vuls/id/922681 http://www.kb.cert.org/vuls/id/922681 http://www.kb.cert.org/vuls/id/922681 http://www.kb.cert.org/vuls/id/922681 http://www.kb.cert.org/vuls/id/922681 http://www.kb.cert.org/vuls/id/922681 http://www.kb.cert.org/vuls/id/922681 https://bugs.launchpad.net/hplip/+bug/1016507/comments/1 http://pidgin.im/news/security/?id=70 http://phenoelit.org/blog/archives/2012/12/21/let_me_github_that_for_you/index.html https://snyk.io/vuln/npm:jquery:20120206 http://www.openssl.org/news/secadv_20130205.txt http://www.isg.rhul.ac.uk/tls/ http://www.openssl.org/news/secadv_20130205.txt https://polarssl.org/tech-updates/releases/polarssl-1.2.5-released http://www.freeipa.org/page/CVE-2013-0199 http://www.samba.org/samba/security/CVE-2013-0213 http://www.samba.org/samba/security/CVE-2013-0214 http://curl.haxx.se/docs/adv_20130206.html https://maven.apache.org/security.html http://www.ruby-lang.org/en/news/2013/02/06/rdoc-xss-cve-2013-0256/ http://www.ruby-lang.org/en/news/2013/02/22/json-dos-cve-2013-0269/ http://www.pidgin.im/news/security/?id=65 http://www.pidgin.im/news/security/?id=66 http://www.pidgin.im/news/security/?id=67 http://www.pidgin.im/news/security/?id=68 http://lists.openstack.org/pipermail/openstack-announce/2013-February/000079.html https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/1h2DR63ViGo http://bundler.io/blog/2014/08/14/bundler-may-install-gems-from-a-different-source-than-expected-cve-2013-0334.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html https://www.samba.org/samba/security/CVE-2013-0454 http://www.adobe.com/support/security/bulletins/apsb13-08.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-01.html http://www.adobe.com/support/security/bulletins/apsb13-04.html http://www.adobe.com/support/security/bulletins/apsb13-04.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-07.html http://www.adobe.com/support/security/bulletins/apsb13-07.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-08.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-09.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-08.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-09.html https://blog.mozilla.org/security/2013/01/03/revoking-trust-in-two-turktrust-certficates/ http://googleonlinesecurity.blogspot.in/2013/01/enhancing-digital-certificate-security.html http://www.mozilla.org/security/announce/2013/mfsa2013-20.html http://www.mozilla.org/security/announce/2013/mfsa2013-05.html http://www.mozilla.org/security/announce/2013/mfsa2013-08.html http://www.mozilla.org/security/announce/2013/mfsa2013-09.html http://www.mozilla.org/security/announce/2013/mfsa2013-10.html http://www.mozilla.org/security/announce/2013/mfsa2013-11.html http://www.mozilla.org/security/announce/2013/mfsa2013-01.html http://www.mozilla.org/security/announce/2013/mfsa2013-12.html http://www.mozilla.org/security/announce/2013/mfsa2013-13.html http://www.mozilla.org/security/announce/2013/mfsa2013-16.html http://www.mozilla.org/security/announce/2013/mfsa2013-17.html http://www.mozilla.org/security/announce/2013/mfsa2013-18.html http://www.mozilla.org/security/announce/2013/mfsa2013-19.html http://www.mozilla.org/security/announce/2013/mfsa2013-14.html http://www.mozilla.org/security/announce/2013/mfsa2013-15.html http://www.mozilla.org/security/announce/2013/mfsa2013-04.html http://www.mozilla.org/security/announce/2013/mfsa2013-02.html http://www.mozilla.org/security/announce/2013/mfsa2013-02.html http://www.mozilla.org/security/announce/2013/mfsa2013-02.html http://www.mozilla.org/security/announce/2013/mfsa2013-02.html http://www.mozilla.org/security/announce/2013/mfsa2013-07.html http://www.mozilla.org/security/announce/2013/mfsa2013-23.html http://www.mozilla.org/security/announce/2013/mfsa2013-02.html http://www.mozilla.org/security/announce/2013/mfsa2013-02.html http://www.mozilla.org/security/announce/2013/mfsa2013-03.html http://www.mozilla.org/security/announce/2013/mfsa2013-01.html http://www.mozilla.org/security/announce/2013/mfsa2013-01.html http://www.mozilla.org/security/announce/2013/mfsa2013-02.html http://www.mozilla.org/security/announce/2013/mfsa2013-22.html http://www.mozilla.org/security/announce/2013/mfsa2013-24.html http://www.mozilla.org/security/announce/2013/mfsa2013-25.html http://www.mozilla.org/security/announce/2013/mfsa2013-26.html http://www.mozilla.org/security/announce/2013/mfsa2013-27.html http://www.mozilla.org/security/announce/2013/mfsa2013-28.html http://www.mozilla.org/security/announce/2013/mfsa2013-28.html http://www.mozilla.org/security/announce/2013/mfsa2013-28.html http://www.mozilla.org/security/announce/2013/mfsa2013-28.html http://www.mozilla.org/security/announce/2013/mfsa2013-28.html http://www.mozilla.org/security/announce/2013/mfsa2013-28.html http://www.mozilla.org/security/announce/2013/mfsa2013-21.html http://www.mozilla.org/security/announce/2013/mfsa2013-21.html http://www.bugzilla.org/security/3.6.12/ http://www.bugzilla.org/security/3.6.12/ http://www.mozilla.org/security/announce/2013/mfsa2013-29.html http://www.mozilla.org/security/announce/2013/mfsa2013-30.html http://www.mozilla.org/security/announce/2013/mfsa2013-30.html http://www.mozilla.org/security/announce/2013/mfsa2013-40.html http://www.mozilla.org/security/announce/2013/mfsa2013-39.html http://www.mozilla.org/security/announce/2013/mfsa2013-38.html http://www.mozilla.org/security/announce/2013/mfsa2013-36.html http://www.mozilla.org/security/announce/2013/mfsa2013-35.html http://www.mozilla.org/security/announce/2013/mfsa2013-31.html http://www.mozilla.org/security/announce/2013/mfsa2013-41.html http://www.oracle.com/technetwork/topics/security/alert-cve-2013-1493-1915081.html http://seclists.org/bugtraq/2013/Feb/119 http://www.occamsec.com/vulnerabilities.html#nagios_metacharacter_vulnerability http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-09.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-05.html http://www.adobe.com/support/security/bulletins/apsb13-09.html http://www.adobe.com/support/security/bulletins/apsb13-02.html http://www.adobe.com/support/security/bulletins/apsb13-11.html http://www.adobe.com/support/security/bulletins/apsb13-11.html http://www.adobe.com/support/security/bulletins/apsb13-11.html http://krbdev.mit.edu/rt/Ticket/Display.html?id=7570 http://web.mit.edu/kerberos/krb5-1.11/ http://xenbits.xen.org/xsa/advisory-62.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013update-1905892.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013update-1905892.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013update-1905892.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013update-1905892.html http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html http://www.oracle.com/technetwork/topics/security/alert-cve-2013-1493-1915081.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.kb.cert.org/vuls/id/225657 http://www.isg.rhul.ac.uk/tls/ http://www.gnutls.org/security.html#GNUTLS-SA-2013-1 http://www.isg.rhul.ac.uk/tls/ http://www.isg.rhul.ac.uk/tls/ http://www.isg.rhul.ac.uk/tls/TLStiming.pdf http://www.isg.rhul.ac.uk/tls/ http://www.isg.rhul.ac.uk/tls/TLStiming.pdf http://www.mozilla.org/security/announce/2013/mfsa2013-41.html http://www.mozilla.org/security/announce/2013/mfsa2013-42.html http://www.mozilla.org/security/announce/2013/mfsa2013-43.html http://www.mozilla.org/security/announce/2013/mfsa2013-46.html http://www.mozilla.org/security/announce/2013/mfsa2013-47.html http://www.mozilla.org/security/announce/2013/mfsa2013-48.html http://www.mozilla.org/security/announce/2013/mfsa2013-48.html http://www.mozilla.org/security/announce/2013/mfsa2013-48.html http://www.mozilla.org/security/announce/2013/mfsa2013-48.html http://www.mozilla.org/security/announce/2013/mfsa2013-48.html http://www.mozilla.org/security/announce/2013/mfsa2013-48.html http://www.mozilla.org/security/announce/2013/mfsa2013-49.html http://www.mozilla.org/security/announce/2013/mfsa2013-49.html http://www.mozilla.org/security/announce/2013/mfsa2013-50.html http://www.mozilla.org/security/announce/2013/mfsa2013-50.html http://www.mozilla.org/security/announce/2013/mfsa2013-50.html http://www.mozilla.org/security/announce/2013/mfsa2013-51.html http://www.mozilla.org/security/announce/2013/mfsa2013-52.html http://www.mozilla.org/security/announce/2013/mfsa2013-53.html http://www.mozilla.org/security/announce/2013/mfsa2013-54.html http://www.mozilla.org/security/announce/2013/mfsa2013-55.html http://www.mozilla.org/security/announce/2013/mfsa2013-56.html http://www.mozilla.org/security/announce/2013/mfsa2013-57.html http://www.mozilla.org/security/announce/2013/mfsa2013-58.html http://www.mozilla.org/security/announce/2013/mfsa2013-59.html http://www.mozilla.org/security/announce/2013/mfsa2013-60.html http://www.mozilla.org/security/announce/2013/mfsa2013-61.html http://www.mozilla.org/security/announce/2013/mfsa2013-63.html http://www.mozilla.org/security/announce/2013/mfsa2013-63.html http://www.mozilla.org/security/announce/2013/mfsa2013-64.html http://www.mozilla.org/security/announce/2013/mfsa2013-65.html http://www.mozilla.org/security/announce/2013/mfsa2013-67.html http://www.mozilla.org/security/announce/2013/mfsa2013-68.html http://www.mozilla.org/security/announce/2013/mfsa2013-69.html http://www.mozilla.org/security/announce/2013/mfsa2013-70.html http://www.mozilla.org/security/announce/2013/mfsa2013-72.html http://www.mozilla.org/security/announce/2013/mfsa2013-73.html http://www.mozilla.org/security/announce/2013/mfsa2013-75.html http://www.mozilla.org/security/announce/2013/mfsa2013-76.html http://www.mozilla.org/security/announce/2013/mfsa2013-76.html http://www.mozilla.org/security/announce/2013/mfsa2013-77.html http://www.mozilla.org/security/announce/2013/mfsa2013-78.html http://www.mozilla.org/security/announce/2013/mfsa2013-79.html http://www.mozilla.org/security/announce/2013/mfsa2013-80.html http://www.mozilla.org/security/announce/2013/mfsa2013-81.html http://www.mozilla.org/security/announce/2013/mfsa2013-82.html http://www.mozilla.org/security/announce/2013/mfsa2013-85.html http://www.mozilla.org/security/announce/2013/mfsa2013-86.html http://www.mozilla.org/security/announce/2013/mfsa2013-88.html http://www.mozilla.org/security/announce/2013/mfsa2013-89.html http://www.mozilla.org/security/announce/2013/mfsa2013-90.html http://www.mozilla.org/security/announce/2013/mfsa2013-90.html http://www.mozilla.org/security/announce/2013/mfsa2013-91.html http://www.mozilla.org/security/announce/2013/mfsa2013-92.html http://www.mozilla.org/security/announce/2013/mfsa2013-103.html https://www.stunnel.org/CVE-2013-1762.html https://bugs.freedesktop.org/show_bug.cgi?id=61433 http://lists.freedesktop.org/archives/telepathy-bugs/2013-February/021155.html http://xmpp.org/extensions/xep-0115.html http://www.sudo.ws/sudo/alerts/epoch_ticket.html http://www.sudo.ws/sudo/alerts/tty_tickets.html https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-05-02 http://www.ruby-lang.org/en/news/2013/02/22/rexml-dos-2013-02-22/ http://subversion.apache.org/security/CVE-2013-1845-advisory.txt http://subversion.apache.org/security/CVE-2013-1846-advisory.txt http://subversion.apache.org/security/CVE-2013-1847-advisory.txt http://subversion.apache.org/security/CVE-2013-1849-advisory.txt http://qpid.apache.org/release_notes_0.22.html https://issues.apache.org/jira/browse/QPID-4918 http://www.phpmyadmin.net/home_page/security/PMASA-2013-1.php https://cwiki.apache.org/confluence/display/WW/S2-012 https://cwiki.apache.org/confluence/display/WW/S2-013 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-05-02 https://issues.jenkins-ci.org/browse/SECURITY-67 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-05-02 https://issues.jenkins-ci.org/browse/SECURITY-63 https://issues.jenkins-ci.org/browse/SECURITY-69 http://code.google.com/p/httplib2/issues/detail?id=282 https://bugs.launchpad.net/httplib2/+bug/1175272 http://blog.phusion.nl/2013/01/04/securing-the-rails-session-secret/ http://blog.mhartl.com/2008/08/15/a-security-issue-with-rails-secret-session-keys/ https://lists.libreswan.org/pipermail/swan-announce/2013/000003.html http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://www.ruby-lang.org/en/news/2013/05/14/taint-bypass-dl-fiddle-cve-2013-2065/ http://www.x.org/wiki/Development/Security/Advisory-2013-05-23 http://lists.openstack.org/pipermail/openstack-announce/2013-May/000102.html https://cwiki.apache.org/confluence/display/WW/S2-013 http://cxf.apache.org/security-advisories.data/CVE-2013-2160.txt.asc http://santuario.apache.org/secadv.data/CVE-2013-2172.txt.asc http://codex.wordpress.org/Version_3.5.2 http://codex.wordpress.org/Version_3.5.2 http://codex.wordpress.org/Version_3.5.2 http://codex.wordpress.org/Version_3.5.2 http://codex.wordpress.org/Version_3.5.2 http://codex.wordpress.org/Version_3.5.2 http://codex.wordpress.org/Version_3.5.2 http://codex.wordpress.org/Version_3.5.2 https://kb.isc.org/article/AA-00871 https://kb.isc.org/article/AA-00879 https://puppetlabs.com/security/cve/cve-2013-2275/ http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/cpuapr2013-1899555.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://downloads.asterisk.org/pub/security/AST-2013-001.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-14.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://www.phpmyadmin.net/home_page/security/PMASA-2013-2.php http://www.phpmyadmin.net/home_page/security/PMASA-2013-3.php http://www.adobe.com/support/security/bulletins/apsb13-14.html http://www.adobe.com/support/security/bulletins/apsb13-14.html http://www.adobe.com/support/security/bulletins/apsb13-14.html http://www.adobe.com/support/security/bulletins/apsb13-14.html http://www.adobe.com/support/security/bulletins/apsb13-14.html http://www.adobe.com/support/security/bulletins/apsb13-14.html http://www.adobe.com/support/security/bulletins/apsb13-14.html http://www.adobe.com/support/security/bulletins/apsb13-14.html http://www.adobe.com/support/security/bulletins/apsb13-14.html http://www.adobe.com/support/security/bulletins/apsb13-14.html http://www.adobe.com/support/security/bulletins/apsb13-14.html http://www.adobe.com/support/security/bulletins/apsb13-14.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-16.html http://www.adobe.com/support/security/bulletins/apsb13-17.html http://www.adobe.com/support/security/bulletins/apsb13-17.html http://www.adobe.com/support/security/bulletins/apsb13-15.html http://www.adobe.com/support/security/bulletins/apsb13-17.html http://www.adobe.com/support/security/bulletins/apsb13-21.html http://www.adobe.com/support/security/bulletins/apsb13-21.html http://www.adobe.com/support/security/bulletins/apsb13-21.html http://puppetlabs.com/security/cve/cve-2013-3567/ http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujuly2013-1899826.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.ruby-lang.org/en/news/2013/06/27/hostname-check-bypassing-vulnerability-in-openssl-client-cve-2013-4073/ http://www.wireshark.org/security/wnpa-sec-2013-32.html http://www.wireshark.org/security/wnpa-sec-2013-33.html http://www.wireshark.org/security/wnpa-sec-2013-34.html http://www.wireshark.org/security/wnpa-sec-2013-35.html http://www.wireshark.org/security/wnpa-sec-2013-36.html http://www.wireshark.org/security/wnpa-sec-2013-37.html http://www.wireshark.org/security/wnpa-sec-2013-38.html http://www.wireshark.org/security/wnpa-sec-2013-39.html http://www.wireshark.org/security/wnpa-sec-2013-40.html http://www.wireshark.org/security/wnpa-sec-2013-41.html http://www.squid-cache.org/Advisories/SQUID-2013_2.txt http://www.squid-cache.org/Advisories/SQUID-2013_3.txt http://www.samba.org/samba/security/ http://subversion.apache.org/security/CVE-2013-4131-advisory.txt http://www.gopivotal.com/security/cve-2013-4152 https://github.com/SpringSource/spring-framework/pull/317 https://jira.springsource.org/browse/SPR-10806 http://blog.diniscruz.com/2013/08/using-xmldecoder-to-execute-server-side.html http://restlet.org/learn/2.1/changes http://eprint.iacr.org/2013/448 http://subversion.apache.org/security/CVE-2013-4246-advisory.txt https://www.djangoproject.com/weblog/2013/aug/13/security-releases-issued/ http://subversion.apache.org/security/CVE-2013-4262-advisory.txt http://restlet.org/learn/2.1/changes http://subversion.apache.org/security/CVE-2013-4277-advisory.txt http://blog.rubygems.org/2013/09/09/CVE-2013-4287.html https://issues.apache.org/jira/browse/WW-4200 https://www.djangoproject.com/weblog/2013/sep/10/security-releases-issued/ https://issues.apache.org/jira/browse/WW-4201 http://camel.apache.org/security-advisories.data/CVE-2013-4330.txt.asc http://wordpress.org/news/2013/09/wordpress-3-6-1/ http://wordpress.org/news/2013/09/wordpress-3-6-1/ http://wordpress.org/news/2013/09/wordpress-3-6-1/ http://httpd.apache.org/security/vulnerabilities_24.html http://blog.rubygems.org/2013/09/24/CVE-2013-4363.html http://xenbits.xen.org/xsa/advisory-67.html http://xenbits.xen.org/xsa/advisory-68.html http://xenbits.xen.org/xsa/advisory-69.html http://xenbits.xen.org/xsa/advisory-70.html http://xenbits.xen.org/xsa/advisory-71.html http://xenbits.xen.org/xsa/advisory-72.html https://bugs.launchpad.net/glance/+bug/1235378 http://docs.saltstack.com/topics/releases/0.17.1.html http://docs.saltstack.com/topics/releases/0.17.1.html http://docs.saltstack.com/topics/releases/0.17.1.html http://docs.saltstack.com/topics/releases/0.17.1.html http://docs.saltstack.com/topics/releases/0.17.1.html http://www.samba.org/samba/security/CVE-2013-4475 http://www.samba.org/samba/security/CVE-2013-4476 https://launchpad.net/bugs/1073306 https://launchpad.net/bugs/1202266 http://subversion.apache.org/security/CVE-2013-4505-advisory.txt https://rhn.redhat.com/errata/RHSA-2012-1265.html http://curl.haxx.se/docs/adv_20131115.html http://www.openssh.com/txt/gcmrekey.adv http://subversion.apache.org/security/CVE-2013-4558-advisory.txt https://libreswan.org/security/CVE-2013-4564/CVE-2013-4564.txt.asc http://lists.gnupg.org/pipermail/gnupg-announce/2013q4/000337.html http://www.cs.tau.ac.il/~tromer/acoustic/ https://polarssl.org/tech-updates/security-advisories/polarssl-security-advisory-2013-03 https://jira.mongodb.org/browse/SERVER-9983 http://puppetlabs.com/security/cve/cve-2013-4761/ https://www.eucalyptus.com/resources/security/advisories/esa-15 http://fish2.com/ipmi/remote-pw-cracking.html https://community.rapid7.com/community/metasploit/blog/2013/07/02/a-penetration-testers-guide-to-ipmi https://access.redhat.com/site/articles/545183 https://kb.isc.org/article/AA-01015/74/CVE-2013-4854%3A-A-specially-crafted-query-can-cause-BIND-to-terminate-abnormally.html https://kb.isc.org/article/AA-01016 http://puppetlabs.com/security/cve/cve-2013-4956/ http://strongswan.org/blog/2013/08/01/strongswan-denial-of-service-vulnerability-(cve-2013-5018).html https://www.us-cert.gov/ncas/alerts/TA14-013A http://www.adobe.com/support/security/bulletins/apsb13-21.html http://www.adobe.com/support/security/bulletins/apsb13-26.html http://www.adobe.com/support/security/bulletins/apsb13-26.html http://helpx.adobe.com/security/products/flash-player/apsb13-28.html http://helpx.adobe.com/security/products/flash-player/apsb13-28.html http://www.mozilla.org/security/announce/2013/mfsa2013-93.html http://www.mozilla.org/security/announce/2013/mfsa2013-93.html http://www.mozilla.org/security/announce/2013/mfsa2013-94.html http://www.mozilla.org/security/announce/2013/mfsa2013-96.html http://www.mozilla.org/security/announce/2013/mfsa2013-97.html http://www.mozilla.org/security/announce/2013/mfsa2013-98.html http://www.mozilla.org/security/announce/2013/mfsa2013-99.html http://www.mozilla.org/security/announce/2013/mfsa2013-100.html http://www.mozilla.org/security/announce/2013/mfsa2013-100.html http://www.mozilla.org/security/announce/2013/mfsa2013-100.html http://www.mozilla.org/security/announce/2013/mfsa2013-101.html http://www.mozilla.org/security/announce/2013/mfsa2013-102.html http://www.mozilla.org/security/announce/2013/mfsa2013-95.html http://www.mozilla.org/security/announce/2013/mfsa2013-103.html http://www.mozilla.org/security/announce/2013/mfsa2013-103.html http://www.mozilla.org/security/announce/2013/mfsa2013-104.html http://www.mozilla.org/security/announce/2013/mfsa2013-104.html http://www.mozilla.org/security/announce/2013/mfsa2013-105.html http://www.mozilla.org/security/announce/2013/mfsa2013-106.html http://www.mozilla.org/security/announce/2013/mfsa2013-114.html http://www.mozilla.org/security/announce/2013/mfsa2013-107.html http://www.mozilla.org/security/announce/2013/mfsa2013-115.html http://www.mozilla.org/security/announce/2013/mfsa2013-108.html http://www.mozilla.org/security/announce/2013/mfsa2013-109.html http://www.mozilla.org/security/announce/2013/mfsa2013-110.html http://downloads.asterisk.org/pub/security/AST-2013-004.html http://downloads.asterisk.org/pub/security/AST-2013-005.html http://downloads.asterisk.org/pub/security/AST-2013-004.html http://downloads.asterisk.org/pub/security/AST-2013-005.html http://wordpress.org/news/2013/09/wordpress-3-6-1/ http://wordpress.org/news/2013/09/wordpress-3-6-1/ https://support.zabbix.com/browse/ZBX-7091 http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://seclists.org/fulldisclosure/2013/Oct/116 http://www.security-explorations.com/materials/SE-2012-01-ORACLE-13.pdf http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://www.oracle.com/technetwork/topics/security/cpuoct2013-1899837.html http://h30499.www3.hp.com/t5/HP-Security-Research-Blog/JSF-outputText-tag-the-good-the-bad-and-the-ugly/bc-p/6370209 http://www.oracle.com/technetwork/topics/security/cpujan2014verbose-1972951.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html http://www.oracle.com/technetwork/topics/security/cpujan2014verbose-1972951.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujan2014verbose-1972951.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html http://strongswan.org/blog/2013/11/01/strongswan-denial-of-service-vulnerability-(cve-2013-6075).html http://strongswan.org/blog/2013/11/01/strongswan-denial-of-service-vulnerability-(cve-2013-6076).html https://kb.isc.org/article/AA-01062 http://www.wireshark.org/security/wnpa-sec-2013-61.html http://www.wireshark.org/security/wnpa-sec-2013-62.html http://www.wireshark.org/security/wnpa-sec-2013-63.html http://www.wireshark.org/security/wnpa-sec-2013-64.html http://www.wireshark.org/security/wnpa-sec-2013-65.html https://drupal.org/SA-CORE-2013-003 https://drupal.org/SA-CORE-2013-003 https://drupal.org/SA-CORE-2013-003 https://drupal.org/SA-CORE-2013-003 https://drupal.org/SA-CORE-2013-003 http://www.agarri.fr/kom/archives/2013/11/27/compromising_an_unreachable_solr_server_with_cve-2013-6397/index.html http://curl.haxx.se/docs/adv_20131217.html http://www.gopivotal.com/security/cve-2013-6429 http://www.gopivotal.com/security/cve-2013-6430 http://blog.sendsafely.com/post/69590974866/web-based-single-sign-on-and-the-dangers-of-saml-xml http://lists.x.org/archives/xorg-announce/2014-January/002389.html https://libreswan.org/security/CVE-2013-6467/CVE-2013-6467.txt https://libreswan.org/security/CVE-2013-6467/CVE-2013-6467.txt http://pidgin.im/news/security/?id=71 http://pidgin.im/news/security/?id=72 http://pidgin.im/news/security/?id=73 http://pidgin.im/news/security/?id=74 http://pidgin.im/news/security/?id=77 http://pidgin.im/news/security/?id=76 http://pidgin.im/news/security/?id=75 http://pidgin.im/news/security/?id=78 http://pidgin.im/news/security/?id=79 http://pidgin.im/news/security/?id=80 http://pidgin.im/news/security/?id=82 http://pidgin.im/news/security/?id=83 http://pidgin.im/news/security/?id=84 http://docs.saltstack.com/topics/releases/0.17.1.html http://www.mozilla.org/security/announce/2013/mfsa2013-111.html http://www.mozilla.org/security/announce/2013/mfsa2013-112.html http://www.mozilla.org/security/announce/2013/mfsa2013-113.html http://www.mozilla.org/security/announce/2014/mfsa2014-14.html http://xenbits.xenproject.org/xsa/advisory-82.html http://www.wireshark.org/security/wnpa-sec-2013-66.html http://www.wireshark.org/security/wnpa-sec-2013-67.html http://www.wireshark.org/security/wnpa-sec-2013-68.html http://www.php.net/ChangeLog-5.php#5.5.9 http://blog.diniscruz.com/2013/12/xstream-remote-code-execution-exploit.html https://securityblog.redhat.com/2014/01/23/java-deserialization-flaws-part-2-xml-deserialization/ http://xstream.codehaus.org/security.html http://www.php.net/ChangeLog-5.php#5.5.9 http://www.php.net/ChangeLog-5.php#5.5.9 http://subversion.apache.org/security/CVE-2013-4262-advisory.txt http://camel.apache.org/security-advisories.data/CVE-2014-0002.txt.asc http://camel.apache.org/security-advisories.data/CVE-2014-0003.txt.asc http://curl.haxx.se/docs/security.html#20140129 http://www.pidgin.im/news/security/?id=85 http://subversion.apache.org/security/CVE-2014-0032-advisory.txt https://access.redhat.com/site/solutions/88203 http://www.gopivotal.com/security/cve-2014-0054 https://cwiki.apache.org/confluence/display/WW/S2-020 http://www.gopivotal.com/security/cve-2014-0097 http://www.sudo.ws/sudo/alerts/env_add.html http://www.ocert.org/advisories/ocert-2014-002.html https://cwiki.apache.org/confluence/display/WW/S2-021 https://cwiki.apache.org/confluence/display/WW/S2-021 https://cwiki.apache.org/confluence/display/WW/S2-022 http://httpd.apache.org/security/vulnerabilities_24.html http://httpd.apache.org/security/vulnerabilities_24.html http://www.squid-cache.org/Advisories/SQUID-2014_1.txt http://curl.haxx.se/docs/adv_20140326A.html http://curl.haxx.se/docs/adv_20140326B.html http://www.openssl.org/news/secadv_20140407.txt http://www.samba.org/samba/security/CVE-2014-0178 http://security.libvirt.org/2014/0003.html https://www.openssl.org/news/secadv_20140605.txt https://www.openssl.org/news/secadv_20140605.txt http://lists.x.org/archives/xorg-announce/2014-May/002431.html http://lists.x.org/archives/xorg-announce/2014-May/002431.html http://lists.x.org/archives/xorg-announce/2014-May/002431.html https://www.openssl.org/news/secadv_20140605.txt https://www.openssl.org/news/secadv_20140605.txt https://access.redhat.com/site/articles/904433 https://access.redhat.com/site/solutions/905793 http://httpd.apache.org/security/vulnerabilities_24.html https://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.43 https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.55 http://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.44 http://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.55 http://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.9 http://httpd.apache.org/security/vulnerabilities_24.html http://www.samba.org/samba/security/CVE-2014-0239 http://www.samba.org/samba/security/CVE-2014-0244 http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA https://www.djangoproject.com/weblog/2014/aug/20/security/ https://www.djangoproject.com/weblog/2014/aug/20/security/ https://www.djangoproject.com/weblog/2014/aug/20/security/ https://www.djangoproject.com/weblog/2014/aug/20/security/ http://helpx.adobe.com/security/products/flash-player/apsb14-02.html http://helpx.adobe.com/security/products/flash-player/apsb14-02.html http://helpx.adobe.com/security/products/flash-player/apsb14-04.html http://helpx.adobe.com/security/products/flash-player/apsb14-07.html http://helpx.adobe.com/security/products/flash-player/apsb14-07.html http://helpx.adobe.com/security/products/flash-player/apsb14-07.html http://helpx.adobe.com/security/products/flash-player/apsb14-08.html http://helpx.adobe.com/security/products/flash-player/apsb14-08.html http://helpx.adobe.com/security/products/flash-player/apsb14-09.html http://helpx.adobe.com/security/products/flash-player/apsb14-09.html http://helpx.adobe.com/security/products/flash-player/apsb14-09.html http://helpx.adobe.com/security/products/flash-player/apsb14-09.html http://helpx.adobe.com/security/products/flash-player/apsb14-14.html http://helpx.adobe.com/security/products/flash-player/apsb14-13.html http://helpx.adobe.com/security/products/flash-player/apsb14-14.html http://helpx.adobe.com/security/products/flash-player/apsb14-14.html http://helpx.adobe.com/security/products/flash-player/apsb14-14.html http://helpx.adobe.com/security/products/flash-player/apsb14-14.html http://helpx.adobe.com/security/products/flash-player/apsb14-14.html http://helpx.adobe.com/security/products/flash-player/apsb14-16.html http://helpx.adobe.com/security/products/flash-player/apsb14-16.html http://helpx.adobe.com/security/products/flash-player/apsb14-16.html http://helpx.adobe.com/security/products/flash-player/apsb14-16.html http://helpx.adobe.com/security/products/flash-player/apsb14-16.html http://helpx.adobe.com/security/products/flash-player/apsb14-16.html http://helpx.adobe.com/security/products/flash-player/apsb14-17.html http://helpx.adobe.com/security/products/flash-player/apsb14-18.html http://helpx.adobe.com/security/products/flash-player/apsb14-17.html http://helpx.adobe.com/security/products/flash-player/apsb14-18.html http://helpx.adobe.com/security/products/flash-player/apsb14-18.html http://helpx.adobe.com/security/products/flash-player/apsb14-18.html http://helpx.adobe.com/security/products/flash-player/apsb14-18.html http://helpx.adobe.com/security/products/flash-player/apsb14-18.html http://helpx.adobe.com/security/products/flash-player/apsb14-18.html http://helpx.adobe.com/security/products/flash-player/apsb14-21.html http://helpx.adobe.com/security/products/flash-player/apsb14-21.html http://helpx.adobe.com/security/products/flash-player/apsb14-21.html http://helpx.adobe.com/security/products/flash-player/apsb14-21.html http://helpx.adobe.com/security/products/flash-player/apsb14-21.html http://helpx.adobe.com/security/products/flash-player/apsb14-21.html http://helpx.adobe.com/security/products/flash-player/apsb14-21.html http://helpx.adobe.com/security/products/flash-player/apsb14-21.html http://helpx.adobe.com/security/products/flash-player/apsb14-21.html http://helpx.adobe.com/security/products/flash-player/apsb14-21.html http://helpx.adobe.com/security/products/flash-player/apsb14-21.html http://helpx.adobe.com/security/products/flash-player/apsb14-22.html http://helpx.adobe.com/security/products/flash-player/apsb14-21.html http://helpx.adobe.com/security/products/flash-player/apsb14-22.html http://helpx.adobe.com/security/products/flash-player/apsb14-22.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb14-27.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html https://helpx.adobe.com/security/products/flash-player/apsb14-27.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html https://kb.isc.org/article/AA-01078/0 https://kb.isc.org/article/AA-01085 http://cve.mitre.org/cve/identifiers/syntaxchange.html http://baraktawily.blogspot.com/2014/01/soapui-code-execution-vulnerability-cve.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html https://www.djangoproject.com/weblog/2014/may/14/security-releases-issued/ http://www.mozilla.org/security/announce/2014/mfsa2014-01.html http://www.mozilla.org/security/announce/2014/mfsa2014-01.html http://www.mozilla.org/security/announce/2014/mfsa2014-02.html http://www.mozilla.org/security/announce/2014/mfsa2014-03.html http://www.mozilla.org/security/announce/2014/mfsa2014-13.html http://www.mozilla.org/security/announce/2014/mfsa2014-04.html http://www.mozilla.org/security/announce/2014/mfsa2014-05.html http://www.mozilla.org/security/announce/2014/mfsa2014-07.html http://www.mozilla.org/security/announce/2014/mfsa2014-08.html http://www.mozilla.org/security/announce/2014/mfsa2014-09.html http://www.mozilla.org/security/announce/2014/mfsa2014-11.html http://www.mozilla.org/security/announce/2014/mfsa2014-10.html http://www.mozilla.org/security/announce/2014/mfsa2014-12.html http://www.mozilla.org/security/announce/2014/mfsa2014-12.html http://www.mozilla.org/security/announce/2014/mfsa2014-15.html http://www.mozilla.org/security/announce/2014/mfsa2014-15.html http://www.mozilla.org/security/announce/2014/mfsa2014-16.html http://www.mozilla.org/security/announce/2014/mfsa2014-17.html http://www.mozilla.org/security/announce/2014/mfsa2014-18.html http://www.mozilla.org/security/announce/2014/mfsa2014-19.html http://www.mozilla.org/security/announce/2014/mfsa2014-20.html http://www.mozilla.org/security/announce/2014/mfsa2014-22.html http://www.mozilla.org/security/announce/2014/mfsa2014-23.html http://www.mozilla.org/security/announce/2014/mfsa2014-28.html http://www.mozilla.org/security/announce/2014/mfsa2014-26.html http://www.mozilla.org/security/announce/2014/mfsa2014-27.html http://www.mozilla.org/security/announce/2014/mfsa2014-29.html http://www.mozilla.org/security/announce/2014/mfsa2014-29.html http://www.mozilla.org/security/announce/2014/mfsa2014-30.html http://www.mozilla.org/security/announce/2014/mfsa2014-31.html http://www.mozilla.org/security/announce/2014/mfsa2014-32.html http://www.mozilla.org/security/announce/2014/mfsa2014-34.html http://www.mozilla.org/security/announce/2014/mfsa2014-36.html http://www.mozilla.org/security/announce/2014/mfsa2014-37.html http://www.mozilla.org/security/announce/2014/mfsa2014-38.html http://www.mozilla.org/security/announce/2014/mfsa2014-39.html http://www.mozilla.org/security/announce/2014/mfsa2014-47.html http://www.mozilla.org/security/announce/2014/mfsa2014-41.html http://www.mozilla.org/security/announce/2014/mfsa2014-42.html http://www.mozilla.org/security/announce/2014/mfsa2014-43.html http://www.mozilla.org/security/announce/2014/mfsa2014-44.html http://www.mozilla.org/security/announce/2014/mfsa2014-46.html http://www.mozilla.org/security/announce/2014/mfsa2014-48.html http://www.mozilla.org/security/announce/2014/mfsa2014-48.html http://www.mozilla.org/security/announce/2014/mfsa2014-49.html http://www.mozilla.org/security/announce/2014/mfsa2014-49.html http://www.mozilla.org/security/announce/2014/mfsa2014-49.html http://www.mozilla.org/security/announce/2014/mfsa2014-51.html http://www.mozilla.org/security/announce/2014/mfsa2014-52.html http://www.mozilla.org/security/announce/2014/mfsa2014-53.html http://www.mozilla.org/security/announce/2014/mfsa2014-54.html http://www.mozilla.org/security/announce/2014/mfsa2014-63.html http://www.mozilla.org/security/announce/2014/mfsa2014-55.html http://www.mozilla.org/security/announce/2014/mfsa2014-56.html http://www.mozilla.org/security/announce/2014/mfsa2014-56.html http://www.mozilla.org/security/announce/2014/mfsa2014-57.html http://www.mozilla.org/security/announce/2014/mfsa2014-58.html http://www.mozilla.org/security/announce/2014/mfsa2014-66.html http://www.mozilla.org/security/announce/2014/mfsa2014-67.html http://www.mozilla.org/security/announce/2014/mfsa2014-67.html http://www.mozilla.org/security/announce/2014/mfsa2014-61.html http://www.mozilla.org/security/announce/2014/mfsa2014-62.html http://www.mozilla.org/security/announce/2014/mfsa2014-64.html http://www.mozilla.org/security/announce/2014/mfsa2014-65.html http://www.mozilla.org/security/announce/2014/mfsa2014-65.html http://www.mozilla.org/security/announce/2014/mfsa2014-65.html http://www.mozilla.org/security/announce/2014/mfsa2014-60.html http://www.mozilla.org/security/announce/2014/mfsa2014-67.html http://www.mozilla.org/security/announce/2014/mfsa2014-68.html http://www.mozilla.org/security/announce/2014/mfsa2014-69.html http://www.mozilla.org/security/announce/2014/mfsa2014-70.html http://www.mozilla.org/security/announce/2014/mfsa2014-72.html http://www.mozilla.org/security/announce/2014/mfsa2014-73.html http://www.mozilla.org/security/announce/2014/mfsa2014-74.html http://www.mozilla.org/security/announce/2014/mfsa2014-74.html http://www.mozilla.org/security/announce/2014/mfsa2014-75.html http://www.mozilla.org/security/announce/2014/mfsa2014-76.html http://www.mozilla.org/security/announce/2014/mfsa2014-77.html http://www.mozilla.org/security/announce/2014/mfsa2014-78.html http://www.mozilla.org/security/announce/2014/mfsa2014-79.html http://www.mozilla.org/security/announce/2014/mfsa2014-80.html http://www.mozilla.org/security/announce/2014/mfsa2014-82.html http://www.mozilla.org/security/announce/2014/mfsa2014-80.html http://www.mozilla.org/security/announce/2014/mfsa2014-81.html http://www.mozilla.org/security/announce/2014/mfsa2014-81.html http://www.mozilla.org/security/announce/2014/mfsa2014-83.html http://www.mozilla.org/security/announce/2014/mfsa2014-83.html http://www.mozilla.org/security/announce/2014/mfsa2014-84.html http://www.mozilla.org/security/announce/2014/mfsa2014-85.html http://www.mozilla.org/security/announce/2014/mfsa2014-86.html http://www.mozilla.org/security/announce/2014/mfsa2014-87.html http://www.mozilla.org/security/announce/2014/mfsa2014-88.html http://www.mozilla.org/security/announce/2014/mfsa2014-89.html http://webkitgtk.org/security/WSA-2015-0001.html http://webkitgtk.org/security/WSA-2015-0001.html https://github.com/restlet/restlet-framework-java/wiki/XEE-security-enhancements http://restlet.org/learn/2.1/changes http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://seclists.org/oss-sec/2014/q1/266 http://seclists.org/oss-sec/2014/q1/266 http://seclists.org/oss-sec/2014/q1/266 http://seclists.org/oss-sec/2014/q1/266 http://seclists.org/oss-sec/2014/q1/263 http://seclists.org/oss-sec/2014/q1/264 http://www.gopivotal.com/security/cve-2014-1904 http://www.mozilla.org/security/announce/2014/mfsa2014-14.html http://www.php.net/ChangeLog-5.php#5.5.9 http://www.wireshark.org/security/wnpa-sec-2014-01.html http://www.wireshark.org/security/wnpa-sec-2014-02.html http://www.wireshark.org/security/wnpa-sec-2014-03.html http://www.wireshark.org/security/wnpa-sec-2014-04.html http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixMSQL http://framework.zend.com/security/advisory/ZF2014-01 http://framework.zend.com/security/advisory/ZF2014-01 http://framework.zend.com/security/advisory/ZF2014-01 http://framework.zend.com/security/advisory/ZF2014-02 http://framework.zend.com/security/advisory/ZF2014-02 https://www.ruby-lang.org/en/news/2014/05/09/dispute-of-vulnerability-cve-2014-2734/ http://www.wireshark.org/security/wnpa-sec-2014-06.html https://drupal.org/SA-CORE-2014-002 http://www.ibm.com/developerworks/java/jdk/alerts/#IBM_Security_Update_July_2014 http://www-01.ibm.com/support/docview.wss?uid=swg21680334 http://xforce.iss.net/xforce/xfdb/93756 https://www.ibm.com/developerworks/java/jdk/alerts/#IBM_Security_Update_July_2014 https://access.redhat.com/solutions/1191453 http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html https://kb.isc.org/article/AA-01161/ http://puppetlabs.com/security/cve/cve-2014-3248 http://puppetlabs.com/security/cve/CVE-2014-3250 https://www.openssl.org/news/secadv_20140605.txt http://theforeman.org/security.html#2014-3491 http://theforeman.org/security.html#2014-3492 http://www.samba.org/samba/security/CVE-2014-3493 https://www.openssl.org/news/secadv_20140806.txt https://www.openssl.org/news/secadv_20140806.txt https://www.openssl.org/news/secadv_20140806.txt https://www.openssl.org/news/secadv_20140806.txt https://www.openssl.org/news/secadv_20140806.txt https://www.openssl.org/news/secadv_20140806.txt https://www.openssl.org/news/secadv_20140806.txt https://www.openssl.org/news/secadv_20140806.txt https://www.openssl.org/news/secadv_20141015.txt https://access.redhat.com/solutions/1120423 http://subversion.apache.org/security/CVE-2014-3522-advisory.txt http://httpd.apache.org/security/vulnerabilities_24.html http://subversion.apache.org/security/CVE-2014-3528-advisory.txt http://openwall.com/lists/oss-security/2014/07/08/1 https://www.samba.org/samba/security/CVE-2014-3560 http://docs.saltstack.com/en/latest/topics/releases/2014.1.10.html https://github.com/saltstack/salt/releases/tag/v2014.1.10 http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=commit;h=2cbd76f7911fc215845e89b50d6af5ff4a83dd77 https://www.openssl.org/news/secadv_20141015.txt https://www.openssl.org/news/secadv_20141015.txt https://www.openssl.org/news/secadv_20150108.txt https://www.openssl.org/news/secadv_20150108.txt https://www.openssl.org/news/secadv_20150108.txt https://www.openssl.org/news/secadv_20150108.txt http://www.pivotal.io/security/cve-2014-3578 https://jvn.jp/en/jp/JVN49154900/ http://subversion.apache.org/security/CVE-2014-3580-advisory.txt http://httpd.apache.org/security/vulnerabilities_24.html http://curl.haxx.se/docs/adv_20140910A.html http://bh.ht.vc/vhost_confusion.pdf http://curl.haxx.se/docs/adv_20140910B.html http://www.rsyslog.com/remote-syslog-pri-vulnerability/ http://www.rsyslog.com/remote-syslog-pri-vulnerability-cve-2014-3683/ http://www.libreoffice.org/about-us/security/advisories/cve-2014-3693 http://curl.haxx.se/docs/adv_20141105.html https://www.djangoproject.com/weblog/2014/may/14/security-releases-issued/ https://nodesecurity.io/advisories/marked_multiple_content_injection_vulnerabilities http://www.securityfocus.com/bid/67356 http://permalink.gmane.org/gmane.comp.security.oss.general/12787 https://kb.isc.org/article/AA-01166 http://www.openwall.com/lists/oss-security/2014/06/03/9 http://www.openwall.com/lists/oss-security/2014/06/03/9 http://www.openwall.com/lists/oss-security/2014/06/05/16 http://www.securityfocus.com/bid/67903 http://www.wireshark.org/security/wnpa-sec-2014-07.html https://sourceware.org/bugzilla/show_bug.cgi?id=17048 https://issues.asterisk.org/jira/browse/ASTERISK-23609 http://downloads.digium.com/pub/security/AST-2014-006.html https://www.mail-archive.com/cas-user@lists.jasig.org/msg17338.html http://www.wireshark.org/security/wnpa-sec-2014-05.html http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://web.mit.edu/Kerberos/advisories/MITKRB5-SA-2014-001.txt http://helpx.adobe.com/security/products/flash-player/apsb14-17.html https://polarssl.org/tech-updates/security-advisories/polarssl-security-advisory-2014-02 https://www.openssl.org/news/secadv_20140806.txt http://www.wireshark.org/security/wnpa-sec-2014-08.html http://www.wireshark.org/security/wnpa-sec-2014-08.html http://www.wireshark.org/security/wnpa-sec-2014-09.html http://www.wireshark.org/security/wnpa-sec-2014-10.html http://www.wireshark.org/security/wnpa-sec-2014-11.html http://security.libvirt.org/2014/0003.html http://helpx.adobe.com/security/products/flash-player/apsb14-18.html http://web.mit.edu/Kerberos/advisories/MITKRB5-SA-2015-001.txt http://www.squid-cache.org/Advisories/SQUID-2014_3.txt https://access.redhat.com/articles/1200223 https://securityblog.redhat.com/2014/09/24/bash-specially-crafted-environment-variables-code-injection-attack http://www.roundup-tracker.org/docs/upgrading.html#user-data-visibility https://nodesecurity.io/advisories/express-no-charset-in-content-type-header https://www.wireshark.org/security/wnpa-sec-2014-12.html https://www.wireshark.org/security/wnpa-sec-2014-12.html https://www.wireshark.org/security/wnpa-sec-2014-13.html https://www.wireshark.org/security/wnpa-sec-2014-14.html https://www.wireshark.org/security/wnpa-sec-2014-15.html https://www.wireshark.org/security/wnpa-sec-2014-16.html https://www.wireshark.org/security/wnpa-sec-2014-17.html https://www.wireshark.org/security/wnpa-sec-2014-18.html https://www.wireshark.org/security/wnpa-sec-2014-19.html https://www.wireshark.org/security/wnpa-sec-2014-19.html https://www.wireshark.org/security/wnpa-sec-2014-19.html https://www.wireshark.org/security/wnpa-sec-2014-19.html https://www.ruby-lang.org/en/news/2014/08/19/ruby-1-9-2-p330-released/ http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.squid-cache.org/Advisories/SQUID-2014_4.txt http://www.squid-cache.org/Advisories/SQUID-2014_4.txt http://gparted.org/news.php?item=184 https://cwiki.apache.org/confluence/display/WW/S2-023 http://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.44 http://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.59 http://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.17 https://groups.google.com/forum/#!topic/rubyonrails-security/dCp7duBiQgo https://groups.google.com/forum/#!topic/rubyonrails-security/doAVp0YaTqY http://googlechromereleases.blogspot.com/2014/11/stable-channel-update_18.html http://googlechromereleases.blogspot.com/2014/11/stable-channel-update_18.html http://googlechromereleases.blogspot.com/2014/11/stable-channel-update_18.html http://googlechromereleases.blogspot.com/2014/11/stable-channel-update_18.html http://googlechromereleases.blogspot.com/2014/11/stable-channel-update_18.html http://googlechromereleases.blogspot.com/2014/11/stable-channel-update_18.html http://googlechromereleases.blogspot.com/2014/11/stable-channel-update_18.html http://googlechromereleases.blogspot.com/2014/11/stable-channel-update_18.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html http://googlechromereleases.blogspot.com/2015/01/stable-update.html https://www.ruby-lang.org/en/news/2014/10/27/rexml-dos-cve-2014-8080/ https://www.ruby-lang.org/en/news/2014/11/13/rexml-dos-cve-2014-8090/ http://www.x.org/wiki/Development/Security/Advisory-2014-12-09/ http://www.x.org/wiki/Development/Security/Advisory-2014-12-09/ http://www.x.org/wiki/Development/Security/Advisory-2014-12-09/ http://www.x.org/wiki/Development/Security/Advisory-2014-12-09/ http://www.x.org/wiki/Development/Security/Advisory-2014-12-09/ http://www.x.org/wiki/Development/Security/Advisory-2014-12-09/ http://www.x.org/wiki/Development/Security/Advisory-2014-12-09/ http://www.x.org/wiki/Development/Security/Advisory-2014-12-09/ http://www.x.org/wiki/Development/Security/Advisory-2014-12-09/ http://www.x.org/wiki/Development/Security/Advisory-2014-12-09/ http://www.x.org/wiki/Development/Security/Advisory-2014-12-09/ http://www.x.org/wiki/Development/Security/Advisory-2014-12-09/ http://www.x.org/wiki/Development/Security/Advisory-2014-12-09/ http://community.openvpn.net/openvpn/wiki/SecurityAnnouncement-97597e732b http://subversion.apache.org/security/CVE-2014-8108-advisory.txt http://icedtea.classpath.org/pipermail/thermostat-announce/2014-December/000013.html http://www.libssh.org/2014/12/19/libssh-0-6-4-security-and-bugfix-release/ http://www.ocert.org/advisories/ocert-2014-012.html http://www.ocert.org/advisories/ocert-2014-012.html http://www.ocert.org/advisories/ocert-2014-011.html http://www.ocert.org/advisories/ocert-2014-011.html http://www.ocert.org/advisories/ocert-2014-011.html https://www.samba.org/samba/security/CVE-2014-8143 http://www.ocert.org/advisories/ocert-2014-010.html http://curl.haxx.se/docs/adv_20150108B.html http://curl.haxx.se/docs/adv_20150108A.html http://santuario.apache.org/secadv.data/CVE-2014-8152.txt http://www.ocert.org/advisories/ocert-2015-001.html http://www.ocert.org/advisories/ocert-2015-001.html http://www.postgresql.org/about/news/1569/ https://www.openssl.org/news/secadv_20150108.txt http://helpx.adobe.com/security/products/flash-player/apsb14-24.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html http://helpx.adobe.com/security/products/flash-player/apsb14-26.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html http://helpx.adobe.com/security/products/flash-player/apsb14-24.html https://helpx.adobe.com/security/products/flash-player/apsb14-27.html https://kb.isc.org/article/AA-01216/74/CVE-2014-8500%3A-A-Defect-in-Delegation-Handling-Can-Be-Exploited-to-Crash-BIND.html http://xenbits.xen.org/xsa/advisory-109.html http://xenbits.xen.org/xsa/advisory-110.html https://www.kde.org/info/security/advisory-20141113-1.txt http://www.mozilla.org/security/announce/2014/mfsa2014-91.html http://www.mozilla.org/security/announce/2014/mfsa2014-91.html http://www.mozilla.org/security/announce/2015/mfsa2015-01.html http://www.mozilla.org/security/announce/2015/mfsa2015-01.html http://www.mozilla.org/security/announce/2015/mfsa2015-09.html http://www.mozilla.org/security/announce/2015/mfsa2015-02.html http://www.mozilla.org/security/announce/2015/mfsa2015-03.html http://www.mozilla.org/security/announce/2015/mfsa2015-04.html http://www.mozilla.org/security/announce/2015/mfsa2015-05.html http://www.mozilla.org/security/announce/2015/mfsa2015-06.html http://www.mozilla.org/security/announce/2015/mfsa2015-08.html https://kb.isc.org/article/AA-01217/74/CVE-2014-8680%3A-Defects-in-GeoIP-features-can-cause-BIND-to-crash.html https://www.wireshark.org/security/wnpa-sec-2014-20.html https://www.wireshark.org/security/wnpa-sec-2014-21.html https://www.wireshark.org/security/wnpa-sec-2014-22.html https://www.wireshark.org/security/wnpa-sec-2014-22.html https://www.wireshark.org/security/wnpa-sec-2014-23.html http://xenbits.xen.org/xsa/advisory-112.html http://www.ocert.org/advisories/ocert-2014-009.html http://xenbits.xen.org/xsa/advisory-113.html https://helpx.adobe.com/security/products/flash-player/apsb14-27.html https://helpx.adobe.com/security/products/flash-player/apsb14-27.html https://helpx.adobe.com/security/products/flash-player/apsb14-27.html https://www.strongswan.org/blog/2015/01/05/strongswan-denial-of-service-vulnerability-(cve-2014-9221).html https://access.redhat.com/articles/1305723 http://support.ntp.org/bin/view/Main/SecurityNotice#Weak_default_key_in_config_auth https://access.redhat.com/articles/1305723 http://support.ntp.org/bin/view/Main/SecurityNotice#non_cryptographic_random_number https://access.redhat.com/articles/1305723 http://support.ntp.org/bin/view/Main/SecurityNotice#Buffer_overflow_in_crypto_recv https://access.redhat.com/articles/1305723 http://support.ntp.org/bin/view/Main/SecurityNotice#receive_missing_return_on_error http://support.ntp.org/bin/view/Main/SecurityNotice#vallen_is_not_validated_in_sever http://support.ntp.org/bin/view/Main/SecurityNotice#1_can_be_spoofed_on_some_OSes_so https://groups.google.com/forum/#!topic/docker-user/nFAz-B-n4Bw https://groups.google.com/forum/#!topic/docker-user/nFAz-B-n4Bw https://groups.google.com/forum/#!topic/docker-user/nFAz-B-n4Bw http://web.mit.edu/Kerberos/advisories/MITKRB5-SA-2015-001.txt http://web.mit.edu/Kerberos/advisories/MITKRB5-SA-2015-001.txt http://web.mit.edu/Kerberos/advisories/MITKRB5-SA-2015-001.txt https://blog.fuzzing-project.org/3-less-out-of-bounds-read-access-TFPA-0022014.html http://www.sudo.ws/alerts/tz.html http://support.ntp.org/bin/view/Main/SecurityNotice#vallen_is_not_validated_in_sever http://support.ntp.org/bin/view/Main/SecurityNotice#1_can_be_spoofed_on_some_OSes_so http://lists.freedesktop.org/archives/pixman/2014-April/003244.html http://pivotal.io/security/cve-2015-0201 https://subversion.apache.org/security/CVE-2015-0202-advisory.txt https://www.openssl.org/news/secadv_20150108.txt https://securityblog.redhat.com/2015/03/04/factoring-rsa-export-keys-freak-cve-2015-0204/ https://www.openssl.org/news/secadv_20150108.txt https://www.openssl.org/news/secadv_20150108.txt https://openssl.org/news/secadv_20150319.txt https://access.redhat.com/articles/1384453 https://openssl.org/news/secadv_20150319.txt https://access.redhat.com/articles/1384453 https://openssl.org/news/secadv_20150319.txt https://access.redhat.com/articles/1384453 https://www.djangoproject.com/weblog/2015/jan/13/security/ https://www.djangoproject.com/weblog/2015/jan/13/security/ https://www.djangoproject.com/weblog/2015/jan/13/security/ https://www.djangoproject.com/weblog/2015/jan/13/security/ http://httpd.apache.org/security/vulnerabilities_24.html#2.4.16 http://www.openwall.com/lists/oss-security/2015/01/27/9 https://community.qualys.com/blogs/laws-of-vulnerabilities/2015/01/27/the-ghost-vulnerability https://access.redhat.com/articles/1332213 http://security.libvirt.org/2015/0001.html https://www.samba.org/samba/security/CVE-2015-0240 https://access.redhat.com/articles/1346913 https://securityblog.redhat.com/2015/02/23/samba-vulnerability-cve-2015-0240/ http://www.postgresql.org/about/news/1569/ http://www.postgresql.org/about/news/1569/ http://www.postgresql.org/about/news/1569/ http://www.postgresql.org/about/news/1569/ http://www.ocert.org/advisories/ocert-2015-002.html https://subversion.apache.org/security/CVE-2015-0248-advisory.txt http://xmlgraphics.apache.org/security.html https://subversion.apache.org/security/CVE-2015-0251-advisory.txt http://xerces.apache.org/xerces-c/secadv/CVE-2015-0252.txt http://httpd.apache.org/security/vulnerabilities_24.html#2.4.16 http://www.x.org/wiki/Development/Security/Advisory-2015-02-10/ https://camel.apache.org/security-advisories.data/CVE-2015-0263.txt.asc https://camel.apache.org/security-advisories.data/CVE-2015-0264.txt.asc https://openssl.org/news/secadv_20150319.txt https://access.redhat.com/articles/1384453 https://openssl.org/news/secadv_20150319.txt https://access.redhat.com/articles/1384453 https://openssl.org/news/secadv_20150319.txt https://access.redhat.com/articles/1384453 https://openssl.org/news/secadv_20150319.txt https://access.redhat.com/articles/1384453 https://openssl.org/news/secadv_20150319.txt https://access.redhat.com/articles/1384453 https://openssl.org/news/secadv_20150319.txt https://access.redhat.com/articles/1384453 https://openssl.org/news/secadv_20150319.txt https://access.redhat.com/articles/1384453 https://openssl.org/news/secadv_20150319.txt https://access.redhat.com/articles/1384453 https://openssl.org/news/secadv_20150319.txt https://access.redhat.com/articles/1384453 http://helpx.adobe.com/security/products/flash-player/apsb15-01.html http://helpx.adobe.com/security/products/flash-player/apsb15-01.html http://helpx.adobe.com/security/products/flash-player/apsb15-01.html http://helpx.adobe.com/security/products/flash-player/apsb15-01.html http://helpx.adobe.com/security/products/flash-player/apsb15-01.html http://helpx.adobe.com/security/products/flash-player/apsb15-01.html http://helpx.adobe.com/security/products/flash-player/apsb15-01.html http://helpx.adobe.com/security/products/flash-player/apsb15-01.html http://helpx.adobe.com/security/products/flash-player/apsb15-01.html http://helpx.adobe.com/security/products/flash-player/apsb15-02.html https://helpx.adobe.com/security/products/flash-player/apsa15-01.html https://helpx.adobe.com/security/products/flash-player/apsb15-03.html https://helpx.adobe.com/security/products/flash-player/apsa15-01.html https://helpx.adobe.com/security/products/flash-player/apsb15-03.html https://helpx.adobe.com/security/products/flash-player/apsa15-02.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-05.html https://helpx.adobe.com/security/products/flash-player/apsb15-05.html https://helpx.adobe.com/security/products/flash-player/apsb15-05.html https://helpx.adobe.com/security/products/flash-player/apsb15-05.html https://helpx.adobe.com/security/products/flash-player/apsb15-05.html https://helpx.adobe.com/security/products/flash-player/apsb15-05.html https://helpx.adobe.com/security/products/flash-player/apsb15-05.html https://helpx.adobe.com/security/products/flash-player/apsb15-05.html https://helpx.adobe.com/security/products/flash-player/apsb15-05.html https://helpx.adobe.com/security/products/flash-player/apsb15-05.html https://helpx.adobe.com/security/products/flash-player/apsb15-05.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html http://xenbits.xen.org/xsa/advisory-116.html http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixJAVA https://securityblog.redhat.com/2015/09/02/factoring-rsa-keys-with-tls-perfect-forward-secrecy/ https://people.redhat.com/~fweimer/rsa-crt-leaks.pdf http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL https://www.wireshark.org/security/wnpa-sec-2015-01.html https://www.wireshark.org/security/wnpa-sec-2015-01.html https://www.wireshark.org/security/wnpa-sec-2015-02.html https://www.wireshark.org/security/wnpa-sec-2015-03.html https://www.wireshark.org/security/wnpa-sec-2015-04.html https://www.wireshark.org/security/wnpa-sec-2015-05.html http://www.mozilla.org/security/announce/2015/mfsa2015-47.html http://www.mozilla.org/security/announce/2015/mfsa2015-44.html http://www.mozilla.org/security/announce/2015/mfsa2015-40.html http://www.mozilla.org/security/announce/2015/mfsa2015-42.html http://www.mozilla.org/security/announce/2015/mfsa2015-39.html http://www.mozilla.org/security/announce/2015/mfsa2015-39.html http://www.mozilla.org/security/announce/2015/mfsa2015-38.html http://www.mozilla.org/security/announce/2015/mfsa2015-38.html http://www.mozilla.org/security/announce/2015/mfsa2015-37.html http://www.mozilla.org/security/announce/2015/mfsa2015-36.html http://www.mozilla.org/security/announce/2015/mfsa2015-34.html http://www.mozilla.org/security/announce/2015/mfsa2015-32.html http://www.mozilla.org/security/announce/2015/mfsa2015-31.html http://www.mozilla.org/security/announce/2015/mfsa2015-30.html http://www.mozilla.org/security/announce/2014/mfsa2015-30.html http://www.mozilla.org/security/announce/2015/mfsa2015-33.html https://www.mozilla.org/en-US/security/advisories/mfsa2015-29 https://www.mozilla.org/en-US/security/advisories/mfsa2015-28 https://www.mozilla.org/en-US/security/advisories/mfa2015-26 https://www.mozilla.org/en-US/security/advisories/mfsa2015-25 https://www.mozilla.org/en-US/security/advisories/mfsa2015-24 https://www.mozilla.org/en-US/security/advisories/mfsa2015-23 https://www.mozilla.org/en-US/security/advisories/mfsa2015-22 https://www.mozilla.org/en-US/security/advisories/mfsa2015-21 https://www.mozilla.org/en-US/security/advisories/mfsa2015-20 https://www.mozilla.org/en-US/security/advisories/mfsa2015-19 https://www.mozilla.org/en-US/security/advisories/mfsa2015-18 https://www.mozilla.org/en-US/security/advisories/mfsa2015-17 https://www.mozilla.org/en-US/security/advisories/mfsa2015-14 https://www.mozilla.org/en-US/security/advisories/mfsa2015-16 https://www.mozilla.org/en-US/security/advisories/mfsa2015-13 https://www.mozilla.org/en-US/security/advisories/mfsa2015-15 https://www.mozilla.org/en-US/security/advisories/mfsa2015-11 https://www.mozilla.org/en-US/security/advisories/mfsa2015-11 http://seclists.org/oss-sec/2015/q4/574 http://seclists.org/oss-sec/2014/q4/1133 https://polarssl.org/tech-updates/security-advisories/polarssl-security-advisory-2014-04 http://googlechromereleases.blogspot.com/2015/02/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/02/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/02/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/02/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_28.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.html http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_28.html http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html https://googlechromereleases.blogspot.com/2015/06/chrome-stable-update.html https://googlechromereleases.blogspot.com/2015/06/chrome-stable-update.html https://googlechromereleases.blogspot.com/2015/06/chrome-stable-update.html https://googlechromereleases.blogspot.com/2015/06/chrome-stable-update.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/07/stable-channel-update_21.html http://googlechromereleases.blogspot.com/2015/09/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/09/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/09/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/09/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/09/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/09/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/09/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/09/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/09/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/09/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/09/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/11/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/09/stable-channel-update_24.html http://googlechromereleases.blogspot.com/2015/09/stable-channel-update_24.html http://www.halfdog.net/Security/2015/MandbSymlinkLocalRootPrivilegeEscalation/ https://kb.isc.org/article/AA-01235/0/CVE-2015-1349%3A-A-Problem-with-Trust-Anchor-Management-Can-Cause-named-to-Crash.html http://puppetlabs.com/security/cve/cve-2015-1426 https://mail-archives.apache.org/mod_mbox/www-announce/201505.mbox/%3CCAOpgucy52yzNN1FaRcxwhZmx8ZtNRjmK6V0Bxk4svAD-R1q70Q@mail.gmail.com%3E http://www.openoffice.org/security/cves/CVE-2015-1774.html http://www.libreoffice.org/about-us/security/advisories/cve-2015-1774 https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities http://seclists.org/oss-sec/2016/q1/344 http://www.libssh2.org/adv_20150311.html https://openssl.org/news/secadv_20150319.txt https://access.redhat.com/articles/1384453 http://openssl.org/news/secadv_20150709.txt http://shibboleth.net/community/advisories/secadv_20150225.txt http://www.x.org/wiki/Development/Security/Advisory-2015-03-17/ http://www.x.org/wiki/Development/Security/Advisory-2015-03-17/ http://www.x.org/wiki/Development/Security/Advisory-2015-03-17/ https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-02-27 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-02-27 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-02-27 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-02-27 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-02-27 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-02-27 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-03-23 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-03-23 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-03-23 http://struts.apache.org/docs/s2-024.html https://mail-archives.apache.org/mod_mbox/www-announce/201505.mbox/%3CCA+RK=_CFiTfQ2d0V+kuJx_y5izmYccaKjXaJ3V72KK7tbOhbkg@mail.gmail.com%3E http://docs.saltstack.com/en/latest/topics/releases/2014.7.4.html http://docs.saltstack.com/en/latest/topics/releases/2014.7.4.html http://w1.fi/security/2015-1/ https://doc.powerdns.com/md/security/powerdns-advisory-2015-01/ http://xenbits.xen.org/xsa/advisory-121.html http://xenbits.xen.org/xsa/advisory-122.html http://dev.eclipse.org/mhonarc/lists/jetty-announce/msg00074.html http://xenbits.xen.org/xsa/advisory-120.html http://xenbits.xen.org/xsa/advisory-123.html http://xenbits.xen.org/xsa/advisory-119.html https://www.playframework.com/security/vulnerability/CVE-2015-2156-HttpOnlyBypass http://engineering.linkedin.com/security/look-netty%E2%80%99s-recent-security-update-cve%C2%AD-2015%C2%AD-2156 https://codex.wordpress.org/Version_4.2.4 https://www.djangoproject.com/weblog/2015/mar/09/security-releases/ https://www.djangoproject.com/weblog/2015/mar/18/security-releases/ https://www.djangoproject.com/weblog/2015/mar/18/security-releases/ http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA https://www.mozilla.org/en-US/security/advisories/mfsa2015-45/ http://www.mozilla.org/security/announce/2015/mfsa2015-46.html http://www.mozilla.org/security/announce/2015/mfsa2015-46.html http://www.mozilla.org/security/announce/2015/mfsa2015-48.html http://www.mozilla.org/security/announce/2015/mfsa2015-49.html http://www.mozilla.org/security/announce/2015/mfsa2015-50.html http://www.mozilla.org/security/announce/2015/mfsa2015-51.html http://www.mozilla.org/security/announce/2015/mfsa2015-53.html http://www.mozilla.org/security/announce/2015/mfsa2015-54.html http://www.mozilla.org/security/announce/2015/mfsa2015-55.html http://www.mozilla.org/security/announce/2015/mfsa2015-56.html http://www.mozilla.org/security/announce/2015/mfsa2015-71.html http://www.mozilla.org/security/announce/2015/mfsa2015-65.html http://www.mozilla.org/security/announce/2015/mfsa2015-59.html http://www.mozilla.org/security/announce/2015/mfsa2015-59.html http://www.mozilla.org/security/announce/2015/mfsa2015-59.html http://www.mozilla.org/security/announce/2015/mfsa2015-60.html http://www.mozilla.org/security/announce/2015/mfsa2015-61.html http://www.mozilla.org/security/announce/2015/mfsa2015-62.html http://www.mozilla.org/security/announce/2015/mfsa2015-64.html http://www.mozilla.org/security/announce/2015/mfsa2015-63.html http://www.mozilla.org/security/announce/2015/mfsa2015-65.html http://www.mozilla.org/security/announce/2015/mfsa2015-66.html http://www.mozilla.org/security/announce/2015/mfsa2015-66.html http://www.mozilla.org/security/announce/2015/mfsa2015-66.html http://www.mozilla.org/security/announce/2015/mfsa2015-66.html http://www.mozilla.org/security/announce/2015/mfsa2015-66.html http://www.mozilla.org/security/announce/2015/mfsa2015-66.html http://www.mozilla.org/security/announce/2015/mfsa2015-66.html http://www.mozilla.org/security/announce/2015/mfsa2015-67.html http://www.mozilla.org/security/announce/2015/mfsa2015-69.html http://www.imperva.com/docs/HII_Attacking_SSL_when_using_RC4.pdf http://www.antoniobarresi.com/files/cain_advisory.txt https://struts.apache.org/docs/s2-025.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-06.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-09.html https://helpx.adobe.com/security/products/flash-player/apsb15-11.html https://helpx.adobe.com/security/products/flash-player/apsb15-11.html https://helpx.adobe.com/security/products/flash-player/apsb15-11.html https://helpx.adobe.com/security/products/flash-player/apsb15-11.html https://helpx.adobe.com/security/products/flash-player/apsb15-11.html https://helpx.adobe.com/security/products/flash-player/apsb15-11.html https://helpx.adobe.com/security/products/flash-player/apsb15-11.html https://helpx.adobe.com/security/products/flash-player/apsb15-11.html https://helpx.adobe.com/security/products/flash-player/apsb15-11.html https://helpx.adobe.com/security/products/flash-player/apsb15-11.html https://helpx.adobe.com/security/products/flash-player/apsb15-11.html https://helpx.adobe.com/security/products/flash-player/apsb15-14.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html http://curl.haxx.se/docs/adv_20150422A.html http://curl.haxx.se/docs/adv_20150422D.html http://curl.haxx.se/docs/adv_20150422C.html https://www.libssh.org/2015/04/30/libssh-0-6-5-security-and-bugfix-release/ http://curl.haxx.se/docs/adv_20150422B.html http://www.ocert.org/advisories/ocert-2015-003.html http://curl.haxx.se/docs/adv_20150429.html http://httpd.apache.org/security/vulnerabilities_24.html#2.4.16 http://httpd.apache.org/security/vulnerabilities_22.html#2.2.31 http://subversion.apache.org/security/CVE-2015-3184-advisory.txt http://httpd.apache.org/security/vulnerabilities_24.html#2.4.16 https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities http://subversion.apache.org/security/CVE-2015-3187-advisory.txt http://pivotal.io/security/cve-2015-3192 https://openssl.org/news/secadv/20151203.txt https://openssl.org/news/secadv/20151203.txt https://openssl.org/news/secadv/20151203.txt https://openssl.org/news/secadv/20151203.txt https://www.openssl.org/news/secadv/20160128.txt http://jaanuskp.blogspot.com/2015/05/cve-2015-3200.html https://libreswan.org/security/CVE-2015-3204/CVE-2015-3204.txt https://libreswan.org/security/CVE-2015-3204/CVE-2015-3204-libreswan.patch https://www.samba.org/samba/security/CVE-2015-3223.html https://www.drupal.org/SA-CORE-2015-002 https://www.drupal.org/SA-CORE-2015-002 https://www.drupal.org/SA-CORE-2015-002 https://www.drupal.org/SA-CORE-2015-002 https://libreswan.org/security/CVE-2015-3240/ https://access.redhat.com/articles/1537873 https://access.redhat.com/articles/1537873 http://mail-archives.us.apache.org/mod_mbox/www-announce/201507.mbox/%3CCABF6JR37mWzDmXDqRQwRUXiojBZrhidndnsY1ZgmcZv-o7-a+g@mail.gmail.com%3E http://directory.apache.org/api/#news http://seclists.org/oss-sec/2015/q3/121 http://xenbits.xen.org/xsa/advisory-137.html https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities https://www.obrela.com/home/security-labs/advisories/osi-advisory-osi-1502/ http://www.openwall.com/lists/oss-security/2015/04/14/4 http://xenbits.xen.org/xsa/advisory-132.html https://www.drupal.org/node/2424103 https://www.drupal.org/node/2424103 http://www.squid-cache.org/Advisories/SQUID-2015_1.txt https://access.redhat.com/articles/1444903 https://securityblog.redhat.com/2015/05/13/venom-dont-get-bitten/ http://venom.crowdstrike.com/ http://xenbits.xen.org/xsa/advisory-133.html https://www.wireshark.org/security/wnpa-sec-2015-12 https://www.wireshark.org/security/wnpa-sec-2015-12 https://www.wireshark.org/security/wnpa-sec-2015-13.html https://www.wireshark.org/security/wnpa-sec-2015-14.html https://www.wireshark.org/security/wnpa-sec-2015-15.html https://www.wireshark.org/security/wnpa-sec-2015-16.html https://www.wireshark.org/security/wnpa-sec-2015-17.html https://www.wireshark.org/security/wnpa-sec-2015-18.html http://www.ocert.org/advisories/ocert-2015-006.html http://blog.rubygems.org/2015/05/14/CVE-2015-3900.html http://www.phpmyadmin.net/home_page/security/PMASA-2015-2.php http://www.phpmyadmin.net/home_page/security/PMASA-2015-3.php http://www.ansible.com/security https://www.djangoproject.com/weblog/2015/may/20/security-release/ https://weakdh.org/ https://access.redhat.com/articles/1456263 https://www.altsci.com/ipsec/ipsec-tools-sa.html http://symfony.com/blog/cve-2015-4050-esi-unauthorized-access https://discuss.elastic.co/t/kibana-cross-site-scripting-vulnerability-cve-2015-4093/2258/1 http://xenbits.xen.org/xsa/advisory-128.html http://xenbits.xen.org/xsa/advisory-129.html http://xenbits.xen.org/xsa/advisory-130.html http://xenbits.xen.org/xsa/advisory-131.html http://w1.fi/security/2015-2/wps-upnp-http-chunked-transfer-encoding.txt http://w1.fi/security/2015-3/integer-underflow-in-ap-mode-wmm-action-frame.txt http://w1.fi/security/2015-4/eap-pwd-missing-payload-length-validation.txt http://w1.fi/security/2015-4/eap-pwd-missing-payload-length-validation.txt http://w1.fi/security/2015-4/eap-pwd-missing-payload-length-validation.txt http://w1.fi/security/2015-4/eap-pwd-missing-payload-length-validation.txt http://xenbits.xen.org/xsa/advisory-136.html https://www.elastic.co/community/security/ https://www.drupal.org/node/2454063 https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://www.mozilla.org/security/announce/2015/mfsa2015-79.html https://www.mozilla.org/security/announce/2015/mfsa2015-79.html https://www.mozilla.org/security/announce/2015/mfsa2015-80.html https://www.mozilla.org/en-US/security/advisories/mfsa2015-99/ https://www.mozilla.org/security/announce/2015/mfsa2015-81.html https://www.mozilla.org/security/announce/2015/mfsa2015-82.html https://www.mozilla.org/security/announce/2015/mfsa2015-83.html https://www.mozilla.org/security/announce/2015/mfsa2015-83.html https://www.mozilla.org/security/announce/2015/mfsa2015-86.html https://www.mozilla.org/security/announce/2015/mfsa2015-87.html https://www.mozilla.org/security/announce/2015/mfsa2015-89.html https://www.mozilla.org/security/announce/2015/mfsa2015-89.html https://www.mozilla.org/security/announce/2015/mfsa2015-90.html https://www.mozilla.org/security/announce/2015/mfsa2015-90.html https://www.mozilla.org/security/announce/2015/mfsa2015-90.html https://www.mozilla.org/security/announce/2015/mfsa2015-91.html https://www.mozilla.org/security/announce/2015/mfsa2015-88.html https://www.mozilla.org/security/announce/2015/mfsa2015-92.html https://www.mozilla.org/security/announce/2015/mfsa2015-83.html https://www.mozilla.org/security/announce/2015/mfsa2015-78.html https://access.redhat.com/articles/1563163 https://blog.mozilla.org/security/2015/08/06/firefox-exploit-found-in-the-wild/ https://www.mozilla.org/security/announce/2015/mfsa2015-93.html https://www.mozilla.org/security/announce/2015/mfsa2015-94.html https://www.mozilla.org/security/announce/2015/mfsa2015-95.html https://www.mozilla.org/en-US/security/advisories/mfsa2015-96/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-96/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-108/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-97/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-98/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-100/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-101/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-102/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-103/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-106/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-104/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-105/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-107/ https://www.mozilla.org/security/announce/2015/mfsa2015-116.html https://www.mozilla.org/security/announce/2015/mfsa2015-116.html https://www.mozilla.org/security/announce/2015/mfsa2015-117.html https://www.mozilla.org/en-US/security/advisories/mfsa2015-109/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-112/ https://www.mozilla.org/security/announce/2015/mfsa2015-118.html https://www.mozilla.org/en-US/security/advisories/mfsa2015-110/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-111/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-112/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-112/ http://www.libreoffice.org/about-us/security/advisories/cve-2015-4551/ http://www.openoffice.org/security/cves/CVE-2015-4551.html https://kb.isc.org/article/AA-01267/ https://www.wireshark.org/security/wnpa-sec-2015-19.html https://www.wireshark.org/security/wnpa-sec-2015-20.html http://freeradius.org/security.html http://www.ocert.org/advisories/ocert-2015-008.html https://owncloud.org/security/advisory/?id=oc-sa-2015-006 https://owncloud.org/security/advisory/?id=oc-sa-2015-007 https://owncloud.org/security/advisory/?id=oc-sa-2015-008 http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpujul2015verbose-2367947.html#MSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsa15-03.html https://helpx.adobe.com/security/products/flash-player/apsb15-18.html https://helpx.adobe.com/security/products/flash-player/apsa15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-18.html https://helpx.adobe.com/security/products/flash-player/apsa15-04.html https://helpx.adobe.com/security/products/flash-player/apsb15-16.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html http://support.ntp.org/bin/view/Main/SecurityNotice#June_2015_NTP_Security_Vulnerabi http://projects.theforeman.org/issues/11119 http://xenbits.xen.org/xsa/advisory-140.html http://xenbits.xen.org/xsa/advisory-139.html https://struts.apache.org/docs/s2-025.html http://seclists.org/bugtraq/2016/Feb/149 http://lists.x.org/archives/xorg-announce/2015-August/002630.html http://lists.x.org/archives/xorg-announce/2015-August/002630.html http://lists.x.org/archives/xorg-announce/2015-August/002630.html https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities https://pivotal.io/security/cve-2015-5211 http://www.libreoffice.org/about-us/security/advisories/cve-2015-5212/ http://www.openoffice.org/security/cves/CVE-2015-5212.html http://www.libreoffice.org/about-us/security/advisories/cve-2015-5213/ http://www.openoffice.org/security/cves/CVE-2015-5213.html http://www.libreoffice.org/about-us/security/advisories/cve-2015-5214/ http://www.openoffice.org/security/cves/CVE-2015-5214.html http://juddi.apache.org/security.html#cveidcve-2015-5241 https://www.samba.org/samba/security/CVE-2015-5252.html http://cxf.apache.org/security-advisories.data/CVE-2015-5253.txt.asc?version=1&modificationDate=1447433340000&api=v2 http://activemq.apache.org/security-advisories.data/CVE-2015-5254-announcement.txt https://blog.srcclr.com/spring-social-core-vulnerability-disclosure/ https://subversion.apache.org/security/CVE-2015-5259-advisory.txt https://issues.apache.org/jira/browse/HTTPCLIENT-1478 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65142 https://sourceware.org/bugzilla/show_bug.cgi?id=17079 http://www.postgresql.org/about/news/1615/ http://www.postgresql.org/about/news/1615/ http://elemental-ircd.com/security/e50b0d59-f3c5-4472-a3cd-e2e07731417c/ https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2015-01 https://www.samba.org/samba/security/CVE-2015-5296.html https://www.samba.org/samba/security/CVE-2015-5299.html https://www.cs.bu.edu/~goldbe/NTPattack.html http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/vuln-ech-overflow.html http://w1.fi/security/2015-6/ https://doc.powerdns.com/md/security/powerdns-advisory-2015-03/ http://w1.fi/security/2015-7/ http://w1.fi/security/2015-7/ http://w1.fi/security/2015-8/ https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11 https://www.samba.org/samba/security/CVE-2015-5330.html https://moodle.org/mod/forum/discuss.php?d=322852 https://moodle.org/mod/forum/discuss.php?d=322852 https://moodle.org/mod/forum/discuss.php?d=322852 https://moodle.org/mod/forum/discuss.php?d=322852 https://moodle.org/mod/forum/discuss.php?d=322852 https://moodle.org/mod/forum/discuss.php?d=322852 https://moodle.org/mod/forum/discuss.php?d=322852 https://moodle.org/mod/forum/discuss.php?d=322852 https://moodle.org/mod/forum/discuss.php?d=322852 https://moodle.org/mod/forum/discuss.php?d=322852 https://subversion.apache.org/security/CVE-2015-5343-advisory.txt https://camel.apache.org/security-advisories.data/CVE-2015-5344.txt.asc?version=1&modificationDate=1454056803000&api=v2 http://seclists.org/bugtraq/2016/Feb/146 http://seclists.org/bugtraq/2016/Feb/143 https://camel.apache.org/security-advisories.data/CVE-2015-5348.txt http://seclists.org/bugtraq/2016/Feb/148 https://thejh.net/written-stuff/openssh-6.8-xsecurity https://access.redhat.com/articles/2243351 https://roundcube.net/news/2015/06/05/updates-1.1.2-and-1.0.6-released/ https://roundcube.net/news/2015/06/05/updates-1.1.2-and-1.0.6-released/ https://roundcube.net/news/2015/06/05/updates-1.1.2-and-1.0.6-released/ http://www.squid-cache.org/Advisories/SQUID-2015_2.txt http://blog.bestpractical.com/2015/08/security-vulnerabilities-in-rt.html https://kb.isc.org/article/AA-01272 https://access.redhat.com/solutions/1548963 https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-19.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://kingcope.wordpress.com/2015/07/16/openssh-keyboard-interactive-authentication-brute-force-vulnerability-maxauthtries-bypass/ https://wordpress.org/news/2015/07/wordpress-4-2-3/ https://wordpress.org/news/2015/07/wordpress-4-2-3/ http://lists.openstack.org/pipermail/openstack/2015-July/013548.html http://lists.openstack.org/pipermail/openstack/2015-July/013548.html https://wordpress.org/news/2015/09/wordpress-4-3-1/ https://wordpress.org/news/2015/09/wordpress-4-3-1/ https://kb.isc.org/article/AA-01287/0 http://framework.zend.com/security/advisory/ZF2015-07 http://botan.randombit.net/security.html http://botan.randombit.net/security.html https://codex.wordpress.org/Version_4.2.4 https://codex.wordpress.org/Version_4.2.4 https://codex.wordpress.org/Version_4.2.4 https://codex.wordpress.org/Version_4.2.4 https://codex.wordpress.org/Version_4.2.4 https://owncloud.org/security/advisory/?id=oc-sa-2015-010 https://owncloud.org/security/advisory/?id=oc-sa-2015-011 https://kb.isc.org/article/AA-01291/0 http://www.ansible.com/security https://www.wireshark.org/security/wnpa-sec-2015-21 https://www.wireshark.org/security/wnpa-sec-2015-22 https://www.wireshark.org/security/wnpa-sec-2015-23 https://www.wireshark.org/security/wnpa-sec-2015-24 https://www.wireshark.org/security/wnpa-sec-2015-25 https://www.wireshark.org/security/wnpa-sec-2015-26 https://www.wireshark.org/security/wnpa-sec-2015-27 https://www.wireshark.org/security/wnpa-sec-2015-28 https://www.wireshark.org/security/wnpa-sec-2015-29 http://www.gnutls.org/security.html#GNUTLS-SA-2015-3 https://owncloud.org/security/advisory/?id=oc-sa-2015-014 http://blog.bestpractical.com/2015/08/security-vulnerabilities-in-rt.html http://www.openssh.com/txt/release-7.0 http://www.openssh.com/txt/release-7.0 http://www.openssh.com/txt/release-7.0 https://www.drupal.org/SA-CORE-2015-003 https://www.drupal.org/SA-CORE-2015-003 https://www.drupal.org/SA-CORE-2015-003 https://www.drupal.org/SA-CORE-2015-003 https://www.drupal.org/SA-CORE-2015-003 https://owncloud.org/security/advisory/?id=oc-sa-2015-015 https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html https://helpx.adobe.com/security/products/flash-player/apsb15-23.html http://googlechromereleases.blogspot.com/2015/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/10/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/10/stable-channel-update.html https://nodejs.org/en/blog/vulnerability/cve-2015-8027_cve-2015-6764/ http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update_8.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update_8.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update_8.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update_8.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update_15.html https://pgbouncer.github.io/2015/09/pgbouncer-1-6-1/ https://docs.saltstack.com/en/latest/topics/releases/2015.8.1.html https://docs.saltstack.com/en/latest/topics/releases/2015.5.6.html http://zerodayinitiative.com/advisories/ZDI-15-570/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-112/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-112/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-112/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-112/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-113/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-113/ https://www.mozilla.org/en-US/security/advisories/mfsa2015-112/ https://www.mozilla.org/security/announce/2015/mfsa2015-133.html https://access.redhat.com/articles/2043623 https://www.mozilla.org/security/announce/2015/mfsa2015-133.html https://access.redhat.com/articles/2043623 https://www.mozilla.org/security/announce/2015/mfsa2015-133.html https://access.redhat.com/articles/2043623 https://www.mozilla.org/en-US/security/advisories/mfsa2015-115/ https://www.mozilla.org/security/announce/2015/mfsa2015-121.html https://www.mozilla.org/security/announce/2015/mfsa2015-122.html https://www.mozilla.org/security/announce/2015/mfsa2015-123.html https://www.mozilla.org/security/announce/2015/mfsa2015-127.html https://www.mozilla.org/security/announce/2015/mfsa2015-128.html https://www.mozilla.org/security/announce/2015/mfsa2015-129.html https://www.mozilla.org/security/announce/2015/mfsa2015-130.html https://www.mozilla.org/security/announce/2015/mfsa2015-132.html https://www.mozilla.org/security/announce/2015/mfsa2015-131.html https://www.mozilla.org/security/announce/2015/mfsa2015-131.html https://www.mozilla.org/security/announce/2015/mfsa2015-131.html https://www.mozilla.org/security/announce/2015/mfsa2015-134.html https://www.mozilla.org/security/announce/2015/mfsa2015-134.html https://www.mozilla.org/security/announce/2015/mfsa2015-144.html https://www.mozilla.org/security/announce/2015/mfsa2015-135.html https://www.mozilla.org/security/announce/2015/mfsa2015-145.html https://www.mozilla.org/security/announce/2015/mfsa2015-136.html https://www.mozilla.org/security/announce/2015/mfsa2015-137.html https://www.mozilla.org/security/announce/2015/mfsa2015-138.html https://www.mozilla.org/security/announce/2015/mfsa2015-141.html https://www.mozilla.org/security/announce/2015/mfsa2015-139.html https://www.mozilla.org/security/announce/2015/mfsa2015-146.html https://www.mozilla.org/security/announce/2015/mfsa2015-149.html https://www.mozilla.org/security/announce/2015/mfsa2015-140.html https://www.mozilla.org/security/announce/2015/mfsa2015-143.html https://www.mozilla.org/security/announce/2015/mfsa2015-143.html https://www.mozilla.org/security/announce/2015/mfsa2015-142.html https://www.mozilla.org/security/announce/2015/mfsa2015-142.html https://www.mozilla.org/security/announce/2015/mfsa2015-144.html https://www.mozilla.org/security/announce/2015/mfsa2015-144.html https://www.mozilla.org/security/announce/2015/mfsa2015-147.html https://www.mozilla.org/security/announce/2015/mfsa2015-148.html http://xenbits.xen.org/xsa/advisory-142.html https://www.mozilla.org/en-US/security/advisories/mfsa2015-114/ https://puppet.com/security/cve/cve-2015-7331 https://github.com/nodejs/node/issues/3138 http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/ https://access.redhat.com/solutions/2045023 http://seclists.org/bugtraq/2015/Dec/87 http://seclists.org/bugtraq/2015/Dec/87 http://www.cs.tau.ac.il/~tromer/ecdh/ https://blog.phusion.nl/2015/12/07/cve-2015-7519/ http://seclists.org/bugtraq/2016/Jan/157 https://github.com/openshift/origin/pull/6113 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-12-09 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-12-09 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-12-09 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-12-09 https://www.samba.org/samba/security/CVE-2015-7540.html https://access.redhat.com/articles/2161461 https://www.samba.org/samba/security/CVE-2015-7560.html https://access.redhat.com/articles/2112261 http://www.mitls.org/pages/attacks/SLOTH https://www.mozilla.org/en-US/security/advisories/mfsa2015-150/ https://groups.google.com/forum/#!msg/rubyonrails-security/ANv0HDHEC3k/mt7wNGxbFQAJ http://weblog.rubyonrails.org/2016/1/25/Rails-5-0-0-beta1-1-4-2-5-1-4-1-14-1-3-2-22-1-and-rails-html-sanitizer-1-0-3-have-been-released/ https://groups.google.com/forum/#!msg/rubyonrails-security/cawsWcQ6c8g/tegZtYdbFQAJ http://weblog.rubyonrails.org/2016/1/25/Rails-5-0-0-beta1-1-4-2-5-1-4-1-14-1-3-2-22-1-and-rails-html-sanitizer-1-0-3-have-been-released/ http://weblog.rubyonrails.org/2016/1/25/Rails-5-0-0-beta1-1-4-2-5-1-4-1-14-1-3-2-22-1-and-rails-html-sanitizer-1-0-3-have-been-released/ https://groups.google.com/forum/#!msg/rubyonrails-security/OU9ugTZcbjc/PjEP46pbFQAJ http://weblog.rubyonrails.org/2016/1/25/Rails-5-0-0-beta1-1-4-2-5-1-4-1-14-1-3-2-22-1-and-rails-html-sanitizer-1-0-3-have-been-released/ https://groups.google.com/forum/#!msg/rubyonrails-security/uh--W4TDwmI/m_CVZtdbFQAJ http://weblog.rubyonrails.org/2016/1/25/Rails-5-0-0-beta1-1-4-2-5-1-4-1-14-1-3-2-22-1-and-rails-html-sanitizer-1-0-3-have-been-released/ https://groups.google.com/forum/#!msg/rubyonrails-security/dthJ5wL69JE/YzPnFelbFQAJ http://weblog.rubyonrails.org/2016/1/25/Rails-5-0-0-beta1-1-4-2-5-1-4-1-14-1-3-2-22-1-and-rails-html-sanitizer-1-0-3-have-been-released/ https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-25.html https://helpx.adobe.com/security/products/flash-player/apsb15-27.html https://helpx.adobe.com/security/products/flash-player/apsa15-05.html https://helpx.adobe.com/security/products/flash-player/apsb15-27.html https://helpx.adobe.com/security/products/flash-player/apsa15-05.html https://helpx.adobe.com/security/products/flash-player/apsb15-27.html https://helpx.adobe.com/security/products/flash-player/apsa15-05.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://www.opensmtpd.org/announces/release-5.7.2.txt http://seclists.org/oss-sec/2015/q4/17 https://github.com/ntp-project/ntp/blob/stable/NEWS#L11 http://support.ntp.org/bin/view/Main/SecurityNotice#October_2015_NTP_Security_Vulner https://github.com/ntp-project/ntp/blob/stable/NEWS#L11 http://support.ntp.org/bin/view/Main/SecurityNotice#October_2015_NTP_Security_Vulner http://framework.zend.com/security/advisory/ZF2015-08 https://owncloud.org/security/advisory/?id=oc-sa-2015-018 https://github.com/ntp-project/ntp/blob/stable/NEWS#L91 http://support.ntp.org/bin/view/Main/SecurityNotice#October_2015_NTP_Security_Vulner https://github.com/ntp-project/ntp/blob/stable/NEWS#L11 http://support.ntp.org/bin/view/Main/SecurityNotice#October_2015_NTP_Security_Vulner https://www.cs.bu.edu/~goldbe/NTPattack.html https://www.cs.bu.edu/~goldbe/NTPattack.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://xenbits.xen.org/xsa/advisory-145.html http://xenbits.xen.org/xsa/advisory-146.html http://xenbits.xen.org/xsa/advisory-147.html http://botan.randombit.net/security.html http://botan.randombit.net/security.html http://botan.randombit.net/security.html http://botan.randombit.net/security.html https://www.wireshark.org/security/wnpa-sec-2015-30.html http://xenbits.xen.org/xsa/advisory-148.html http://talosintel.com/reports/TALOS-2015-0052/ http://support.ntp.org/bin/view/Main/SecurityNotice#October_2015_NTP_Security_Vulner http://talosintel.com/reports/TALOS-2015-0054/ http://support.ntp.org/bin/view/Main/SecurityNotice#October_2015_NTP_Security_Vulner http://talosintel.com/reports/TALOS-2015-0055/ http://support.ntp.org/bin/view/Main/SecurityNotice#October_2015_NTP_Security_Vulner http://talosintel.com/reports/TALOS-2015-0062/ http://support.ntp.org/bin/view/Main/SecurityNotice#October_2015_NTP_Security_Vulner http://talosintel.com/reports/TALOS-2015-0063/ http://support.ntp.org/bin/view/Main/NtpBug2919 http://talosintel.com/reports/TALOS-2015-0064/ http://support.ntp.org/bin/view/Main/SecurityNotice#October_2015_NTP_Security_Vulner http://talosintel.com/reports/TALOS-2015-0065/ http://support.ntp.org/bin/view/Main/SecurityNotice#October_2015_NTP_Security_Vulner https://github.com/ntp-project/ntp/blob/stable/NEWS#L295 http://support.ntp.org/bin/view/Main/SecurityNotice#October_2015_NTP_Security_Vulner http://talosintel.com/reports/TALOS-2015-0069/ http://support.ntp.org/bin/view/Main/SecurityNotice#October_2015_NTP_Security_Vulner https://www.drupal.org/SA-CORE-2015-004 http://xenbits.xen.org/xsa/advisory-149.html http://xenbits.xen.org/xsa/advisory-151.html http://xenbits.xen.org/xsa/advisory-150.html http://xenbits.xen.org/xsa/advisory-152.html http://xenbits.xen.org/xsa/advisory-153.html http://support.ntp.org/bin/view/Main/SecurityNotice#January_2016_NTP_4_2_8p6_Securit http://www.talosintel.com/reports/TALOS-2016-0070/ http://support.ntp.org/bin/view/Main/NtpBug2936 http://www.talosintel.com/reports/TALOS-2016-0071/ http://support.ntp.org/bin/view/Main/SecurityNotice#January_2016_NTP_4_2_8p6_Securit http://www.talosintel.com/reports/TALOS-2016-0072/ http://support.ntp.org/bin/view/Main/SecurityNotice#January_2016_NTP_4_2_8p6_Securit http://www.talosintel.com/reports/TALOS-2016-0073/ http://support.ntp.org/bin/view/Main/SecurityNotice#January_2016_NTP_4_2_8p6_Securit http://www.talosintel.com/reports/TALOS-2016-0074/ http://support.ntp.org/bin/view/Main/SecurityNotice#January_2016_NTP_4_2_8p6_Securit http://www.talosintel.com/reports/TALOS-2016-0075/ http://support.ntp.org/bin/view/Main/SecurityNotice#January_2016_NTP_4_2_8p6_Securit http://www.talosintel.com/reports/TALOS-2016-0076/ https://wordpress.org/news/2015/09/wordpress-4-3-1/ https://kb.isc.org/article/AA-01317 https://www.strongswan.org/blog/2015/11/16/strongswan-vulnerability-%28cve-2015-8023%29.html https://nodejs.org/en/blog/vulnerability/cve-2015-8027_cve-2015-6764/ https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2015-01 http://w1.fi/security/2015-5/incomplete-wps-and-p2p-nfc-ndef-record-payload-length-validation.txt https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-28.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11 http://symfony.com/blog/cve-2015-8124-session-fixation-in-the-remember-me-login-feature http://symfony.com/blog/cve-2015-8125-potential-remote-timing-attack-vulnerability-in-security-remember-me-service http://symfony.com/blog/cve-2015-8124-session-fixation-in-the-remember-me-login-feature http://symfony.com/blog/cve-2015-8125-potential-remote-timing-attack-vulnerability-in-security-remember-me-service http://support.ntp.org/bin/view/Main/SecurityNotice#January_2016_NTP_4_2_8p6_Securit http://www.talosintel.com/reports/TALOS-2016-0077/ http://support.ntp.org/bin/view/Main/SecurityNotice#January_2016_p6_NTP_Security_Vul http://www.talosintel.com/reports/TALOS-2016-0078/ http://support.ntp.org/bin/view/Main/SecurityNotice#January_2016_NTP_4_2_8p6_Securit http://www.talosintel.com/reports/TALOS-2016-0079/ http://support.ntp.org/bin/view/Main/SecurityNotice#January_2016_NTP_4_2_8p6_Securit http://www.talosintel.com/reports/TALOS-2016-0080/ https://www.djangoproject.com/weblog/2015/nov/24/security-releases-issued/ https://nodesecurity.io/advisories/46 https://lists.debian.org/debian-printing/2015/11/msg00020.html http://xenbits.xen.org/xsa/advisory-158.html http://xenbits.xen.org/xsa/advisory-159.html http://xenbits.xen.org/xsa/advisory-159.html http://xenbits.xen.org/xsa/advisory-160.html http://hmarco.org/bugs/CVE-2015-8370-Grub2-authentication-bypass.html https://kb.isc.org/article/AA-01318 http://census-labs.com/news/2016/01/11/gdcm-buffer-overflow-imageregionreaderreadintobuffer/ http://census-labs.com/news/2016/01/11/gdcm-out-bounds-read-jpeglscodec-decodeextent/ https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://kb.isc.org/article/AA-01319 https://www.samba.org/samba/security/CVE-2015-8467.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html http://googlechromereleases.blogspot.com/2015/12/stable-channel-update.html https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=096fe9eaea40a17e125569f9e657e34cdb6d73bd http://googlechromereleases.blogspot.com/2015/12/stable-channel-update_8.html http://xenbits.xen.org/xsa/advisory-155.html http://xenbits.xen.org/xsa/advisory-157.html http://xenbits.xen.org/xsa/advisory-157.html http://xenbits.xen.org/xsa/advisory-120.html http://xenbits.xen.org/xsa/advisory-164.html http://xenbits.xen.org/xsa/advisory-165.html https://kb.isc.org/article/AA-01334 https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://nghttp2.org/blog/2015/12/23/nghttp2-v1-6-0/ https://www.phpmyadmin.net/security/PMASA-2015-6/ http://gultsch.de/gajim_roster_push_and_message_interception.html https://kb.isc.org/article/AA-01335 https://kb.isc.org/article/AA-01336 https://www.wireshark.org/security/wnpa-sec-2015-31 https://www.wireshark.org/security/wnpa-sec-2015-32 https://www.wireshark.org/security/wnpa-sec-2015-32 https://www.wireshark.org/security/wnpa-sec-2015-33 https://www.wireshark.org/security/wnpa-sec-2015-34 https://www.wireshark.org/security/wnpa-sec-2015-35 https://www.wireshark.org/security/wnpa-sec-2015-36 https://www.wireshark.org/security/wnpa-sec-2015-37 https://www.wireshark.org/security/wnpa-sec-2015-38 https://www.wireshark.org/security/wnpa-sec-2015-39 https://www.wireshark.org/security/wnpa-sec-2015-40 https://www.wireshark.org/security/wnpa-sec-2015-41 https://www.wireshark.org/security/wnpa-sec-2015-42 https://www.wireshark.org/security/wnpa-sec-2015-42 https://www.wireshark.org/security/wnpa-sec-2015-43 https://www.wireshark.org/security/wnpa-sec-2015-44 https://www.wireshark.org/security/wnpa-sec-2015-45 https://www.wireshark.org/security/wnpa-sec-2015-46 https://www.wireshark.org/security/wnpa-sec-2015-47 https://www.wireshark.org/security/wnpa-sec-2015-48 https://www.wireshark.org/security/wnpa-sec-2015-49 https://www.wireshark.org/security/wnpa-sec-2015-50 https://www.wireshark.org/security/wnpa-sec-2015-51 https://www.wireshark.org/security/wnpa-sec-2015-52 https://www.wireshark.org/security/wnpa-sec-2015-53 https://www.wireshark.org/security/wnpa-sec-2015-54 https://www.wireshark.org/security/wnpa-sec-2015-55 https://www.wireshark.org/security/wnpa-sec-2015-56 https://www.wireshark.org/security/wnpa-sec-2015-57 https://www.wireshark.org/security/wnpa-sec-2015-58 https://www.wireshark.org/security/wnpa-sec-2015-59 https://www.wireshark.org/security/wnpa-sec-2015-60 http://freeradius.org/security.html#eap-pwd-2015 http://freeradius.org/security.html#eap-pwd-2015 http://freeradius.org/security.html#eap-pwd-2015 http://www.scip.ch/en/?vuldb.80728 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8790 http://www.scip.ch/en/?vuldb.80729 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8791 http://www.scip.ch/en/?vuldb.80731 http://www.scip.ch/en/?vuldb.80732 https://lists.lysator.liu.se/pipermail/nettle-bugs/2015/003028.html https://lists.lysator.liu.se/pipermail/nettle-bugs/2015/003024.html http://www.spinics.net/lists/linux-usb/msg132311.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html https://helpx.adobe.com/security/products/flash-player/apsb15-32.html http://seclists.org/oss-sec/2016/q2/479 https://bugs.chromium.org/p/project-zero/issues/detail?id=735 https://blog.fuzzing-project.org/39-Heap-use-after-free-in-Pidgin-OTR-plugin.html http://seclists.org/oss-sec/2016/q1/572 https://wordpress.org/news/2015/05/wordpress-4-2-2/ https://nodesecurity.io/advisories/93 https://rt.perl.org/Public/Bug/Display.html?id=123562 https://nodesecurity.io/advisories/23 https://github.com/chjj/marked/issues/497 https://nodesecurity.io/advisories/semver_redos https://nodesecurity.io/advisories/serve-static-xss https://nodesecurity.io/advisories/48 https://nodesecurity.io/advisories/57 https://blog.srcclr.com/handlebars_vulnerability_research_findings/ https://blog.srcclr.com/handlebars_vulnerability_research_findings/ https://github.com/stedolan/jq/issues/995 https://github.com/uclouvain/openjpeg/issues/563 https://github.com/dosfstools/dosfstools/issues/12 https://blog.fuzzing-project.org/44-dosfstools-fsck.vfat-Several-invalid-memory-accesses.html http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=28466 http://seclists.org/oss-sec/2016/q2/459 https://github.com/ImageMagick/ImageMagick/pull/34 http://seclists.org/oss-sec/2016/q2/459 http://www.squidguard.org/Downloads/Patches/1.4/Readme.Patch-20150201 https://github.com/qpdf/qpdf/issues/51 http://www.ibm.com/developerworks/java/jdk/alerts/#IBM_Security_Update_April_2016 http://www.ibm.com/developerworks/java/jdk/alerts/#IBM_Security_Update_April_2016 http://www.ibm.com/developerworks/java/jdk/alerts/#IBM_Security_Update_April_2016 http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpujan2016verbose-2367956.html http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2016verbose-2881709.html http://www.oracle.com/technetwork/topics/security/cpuapr2016verbose-2881709.html http://www.oracle.com/technetwork/topics/security/cpuapr2016verbose-2881709.html http://www.oracle.com/technetwork/topics/security/cpuapr2016verbose-2881709.html http://www.oracle.com/technetwork/topics/security/cpuapr2016verbose-2881709.html http://www.oracle.com/technetwork/topics/security/cpuapr2016verbose-2881709.html http://www.oracle.com/technetwork/topics/security/cpuapr2016verbose-2881709.html http://www.oracle.com/technetwork/topics/security/cpuapr2016verbose-2881709.html http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2016verbose-2881709.html http://www.oracle.com/technetwork/topics/security/cpuapr2016verbose-2881709.html http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2016verbose-2881709.html http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2016verbose-2881709.html http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html#AppendixMSQL http://www.oracle.com/technetwork/topics/security/cpuapr2016verbose-2881709.html http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixJAVA https://www.openssl.org/news/secadv/20160128.txt http://cachebleed.info/ https://www.openssl.org/news/secadv/20160301.txt https://www.openssl.org/news/secadv/20160301.txt https://www.openssl.org/news/secadv/20160301.txt http://seclists.org/bugtraq/2016/Feb/144 http://seclists.org/bugtraq/2016/Feb/145 http://www.halfdog.net/Security/2015/NtpCronjobUserNtpToRootPrivilegeEscalation/ https://access.redhat.com/node/2131021 http://xerces.apache.org/xerces-c/secadv/CVE-2016-0729.txt http://activemq.apache.org/security-advisories.data/CVE-2016-0734-announcement.txt https://httpd.apache.org/security/vulnerabilities_24.html#2.4.25 https://www.redteam-pentesting.de/advisories/rt-sa-2016-001.txt https://www.libssh.org/security/advisories/CVE-2016-0739.txt http://mailman.nginx.org/pipermail/nginx-announce/2016/000169.html http://mailman.nginx.org/pipermail/nginx-announce/2016/000169.html http://mailman.nginx.org/pipermail/nginx-announce/2016/000169.html https://groups.google.com/forum/#!msg/rubyonrails-security/9oLY_FCzvoc/w9oI9XxbFQAJ http://weblog.rubyonrails.org/2016/1/25/Rails-5-0-0-beta1-1-4-2-5-1-4-1-14-1-3-2-22-1-and-rails-html-sanitizer-1-0-3-have-been-released/ https://groups.google.com/forum/#!msg/rubyonrails-security/335P1DcLG00/OfB9_LhbFQAJ https://nvisium.com/blog/2016/01/26/rails-dynamic-render-to-rce-cve-2016-0752/ https://groups.google.com/forum/#!msg/rubyonrails-security/6jQVC1geukQ/8oYETcxbFQAJ http://weblog.rubyonrails.org/2016/1/25/Rails-5-0-0-beta1-1-4-2-5-1-4-1-14-1-3-2-22-1-and-rails-html-sanitizer-1-0-3-have-been-released/ https://prosody.im/security/advisory_20160127/ https://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.47 https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.72 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.5_and_8.0.37 http://seclists.org/bugtraq/2016/Feb/147 https://mail.gnome.org/archives/networkmanager-list/2016-April/msg00000.html https://www.samba.org/samba/security/CVE-2016-0771.html https://access.redhat.com/articles/2123781 https://www.qualys.com/2016/01/14/cve-2016-0777-cve-2016-0778/openssh-cve-2016-0777-cve-2016-0778.txt http://www.openssh.com/txt/release-7.1p2 http://www.openssh.com/txt/release-7.1p2 https://www.qualys.com/2016/01/14/cve-2016-0777-cve-2016-0778/openssh-cve-2016-0777-cve-2016-0778.txt http://activemq.apache.org/security-advisories.data/CVE-2016-0782-announcement.txt http://struts.apache.org/docs/s2-029.html http://www.libssh2.org/adv_20160223.html https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24 https://www.openssl.org/news/secadv/20160301.txt https://access.redhat.com/articles/2176731 https://www.openssl.org/news/secadv/20160301.txt https://www.drownattack.com/ https://googleprojectzero.blogspot.cz/2015/03/exploiting-dram-rowhammer-bug-to-gain.html https://helpx.adobe.com/security/products/flash-player/apsb16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-04.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://nodesecurity.io/advisories/101 https://nodesecurity.io/advisories/95 https://nodesecurity.io/advisories/106 https://nodesecurity.io/advisories/118 https://nodesecurity.io/advisories/120 https://www.tenable.com/security/research/tra-2016-20 http://www.pidgin.im/news/security/?id=91 http://www.tenable.com/security/research/tra-2016-12 http://www.squid-cache.org/Advisories/SQUID-2016_11.txt https://www.elastic.co/community/security https://www.elastic.co/community/security https://nodesecurity.io/advisories/126 https://nodesecurity.io/advisories/130 https://nodesecurity.io/advisories/134 http://www.squid-cache.org/Advisories/SQUID-2016_10.txt https://www.openssh.com/txt/release-7.4 https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://www.openssh.com/txt/release-7.4 https://www.openssh.com/txt/release-7.4 https://www.openssh.com/txt/release-7.4 http://xenbits.xen.org/xsa/advisory-204.html https://helpx.adobe.com/security/products/flash-player/apsb16-08.html http://xenbits.xen.org/xsa/advisory-202.html http://xenbits.xen.org/xsa/advisory-203.html http://seclists.org/oss-sec/2016/q4/745 https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html http://www.openwall.com/lists/oss-security/2016/12/30/5 https://helpx.adobe.com/security/products/flash-player/apsb16-08.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://github.com/lxc/lxc/commit/e986ea3dfa4a2957f71ae9bfaed406dd6e1ffff6 https://github.com/libgit2/libgit2/releases/tag/v0.25.1 https://github.com/libgit2/libgit2/releases/tag/v0.24.6 https://github.com/libgit2/libgit2/releases/tag/v0.25.1 https://github.com/libgit2/libgit2/releases/tag/v0.24.6 https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://github.com/libgit2/libgit2/releases/tag/v0.25.1 https://github.com/libgit2/libgit2/releases/tag/v0.24.6 https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://tools.ietf.org/html/rfc8021 https://bugzilla.novell.com/show_bug.cgi?id=1020078 https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://www.foxmole.com/advisories/foxmole-2016-07-05.txt https://www.foxmole.com/advisories/foxmole-2016-07-05.txt https://www.foxmole.com/advisories/foxmole-2016-07-05.txt https://www.foxmole.com/advisories/foxmole-2016-07-05.txt https://www.foxmole.com/advisories/foxmole-2016-07-05.txt https://www.foxmole.com/advisories/foxmole-2016-07-05.txt https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://access.redhat.com/solutions/3001781 https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://helpx.adobe.com/security/products/flash-player/apsb16-10.html https://helpx.adobe.com/security/products/flash-player/apsa16-01.html https://blog.phusion.nl/2017/01/10/passenger-5-1-1/ https://www.elastic.co/community/security https://nodesecurity.io/advisories/108 https://nodesecurity.io/advisories/117 https://nodesecurity.io/advisories/87 https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/ https://nodesecurity.io/advisories/161 https://nodesecurity.io/advisories/217 https://nodesecurity.io/advisories/222 https://nodesecurity.io/advisories/288 https://savannah.gnu.org/bugs/index.php?45990 https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://jvn.jp/en/jp/JVN03188560/ https://jvn.jp/en/jp/JVN65044642/ http://legalhackers.com/advisories/Tomcat-DebPkgs-Root-Privilege-Escalation-Exploit-CVE-2016-1240.txt http://www.tryton.org/posts/security-release-for-issue5795-and-issue5808.html https://lists.torproject.org/pipermail/tor-announce/2016-December/000122.html https://kb.isc.org/article/AA-01352 https://kb.isc.org/article/AA-01353 https://foxglovesecurity.com/2016/06/13/finding-pearls-fuzzing-clamav/ https://foxglovesecurity.com/2016/06/13/finding-pearls-fuzzing-clamav/ https://blog.filippo.io/bleichenbacher-06-signature-forgery-in-python-rsa/ https://owncloud.org/security/advisory/?id=oc-sa-2016-001 https://owncloud.org/security/advisory/?id=oc-sa-2016-003 https://owncloud.org/security/advisory/?id=oc-sa-2016-004 https://arxiv.org/pdf/1701.04739.pdf https://arxiv.org/pdf/1701.04739.pdf http://www.talosintel.com/reports/TALOS-2016-0058/ http://www.talosintel.com/reports/TALOS-2016-0060/ http://www.talosintel.com/reports/TALOS-2016-0057/ http://www.talosintel.com/reports/TALOS-2016-0059/ http://www.talosintel.com/reports/TALOS-2016-0061/ http://exim.org/static/doc/CVE-2016-1531.txt http://www.kb.cert.org/vuls/id/862384 http://httpd.apache.org/security/vulnerabilities_24.html http://support.ntp.org/bin/view/Main/SecurityNotice#April_2016_NTP_4_2_8p7_Security http://www.talosintel.com/reports/TALOS-2016-0081/ http://support.ntp.org/bin/view/Main/SecurityNotice#April_2016_NTP_4_2_8p7_Security http://www.talosintel.com/reports/TALOS-2016-0082/ http://support.ntp.org/bin/view/Main/SecurityNotice#April_2016_NTP_4_2_8p7_Security http://www.talosintel.com/reports/TALOS-2016-0083/ http://support.ntp.org/bin/view/Main/SecurityNotice#April_2016_NTP_4_2_8p7_Security http://www.talosintel.com/reports/TALOS-2016-0084/ http://support.ntp.org/bin/view/Main/SecurityNotice#April_2016_NTP_4_2_8p7_Security http://www.talosintel.com/reports/TALOS-2016-0132/ https://wordpress.org/news/2016/01/wordpress-4-4-1-security-and-maintenance-release/ https://sourceforge.net/p/guacamole/news/2016/02/security-advisory---stored-xss-cve-2016-1566--guac-1465/ http://chrony.tuxfamily.org/news.html#_20_jan_2016_chrony_2_2_1_and_chrony_1_31_2_released http://www.talosintel.com/reports/TALOS-2016-0071/ http://googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.html http://googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.html http://googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.html http://googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.html http://googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.html http://googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.html http://googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.html http://googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.html http://googlechromereleases.blogspot.fr/2016/01/stable-channel-update_20.html http://googlechromereleases.blogspot.com/2016/02/stable-channel-update_9.html http://googlechromereleases.blogspot.com/2016/02/stable-channel-update_9.html http://googlechromereleases.blogspot.com/2016/02/stable-channel-update_9.html http://googlechromereleases.blogspot.com/2016/02/stable-channel-update_9.html http://googlechromereleases.blogspot.com/2016/02/stable-channel-update_9.html http://googlechromereleases.blogspot.com/2016/02/stable-channel-update_9.html http://googlechromereleases.blogspot.com/2016/02/stable-channel-update_9.html http://googlechromereleases.blogspot.com/2016/02/stable-channel-update_18.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update_8.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update_8.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update_8.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update_24.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update_24.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update_24.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update_24.html http://googlechromereleases.blogspot.com/2016/03/stable-channel-update_24.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_13.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_13.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_13.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_13.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_13.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_13.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_13.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_13.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_13.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_28.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_28.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_28.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_28.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_28.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_28.html http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_28.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html http://googlechromereleases.blogspot.com/2016/06/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/06/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/06/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/06/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/06/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/06/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/06/stable-channel-update.html http://googlechromereleases.blogspot.com/2016/06/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/06/stable-channel-update_16.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://docs.saltstack.com/en/latest/topics/releases/2015.8.4.html https://symfony.com/blog/cve-2016-1902-securerandom-s-fallback-not-secure-when-openssl-fails http://www.openvas.org/OVSA20160113.html https://www.mozilla.org/security/announce/2016/mfsa2016-01.html https://www.mozilla.org/security/announce/2016/mfsa2016-01.html https://www.mozilla.org/security/announce/2016/mfsa2016-02.html https://www.mozilla.org/security/announce/2016/mfsa2016-03.html https://www.mozilla.org/security/announce/2016/mfsa2016-06.html https://www.mozilla.org/security/announce/2016/mfsa2016-04.html https://www.mozilla.org/security/announce/2016/mfsa2016-09.html https://www.mozilla.org/security/announce/2016/mfsa2016-10.html https://www.mozilla.org/security/announce/2016/mfsa2016-10.html https://www.mozilla.org/security/announce/2016/mfsa2016-10.html https://www.mozilla.org/security/announce/2016/mfsa2016-11.html https://www.mozilla.org/en-US/security/advisories/mfsa2016-13/ https://www.mozilla.org/en-US/security/advisories/mfsa2016-35 https://groups.google.com/forum/#!topic/mozilla.dev.tech.nspr/dV4MyMsg6jw https://www.mozilla.org/security/announce/2016/mfsa2016-16.html https://www.mozilla.org/security/announce/2016/mfsa2016-16.html https://www.mozilla.org/security/announce/2016/mfsa2016-17.html https://www.mozilla.org/security/announce/2016/mfsa2016-18.html https://www.mozilla.org/security/announce/2016/mfsa2016-19.html https://www.mozilla.org/security/announce/2016/mfsa2016-20.html https://www.mozilla.org/security/announce/2016/mfsa2016-21.html https://www.mozilla.org/security/announce/2016/mfsa2016-22.html https://www.mozilla.org/security/announce/2016/mfsa2016-23.html https://www.mozilla.org/security/announce/2016/mfsa2016-24.html https://www.mozilla.org/security/announce/2016/mfsa2016-25.html https://www.mozilla.org/security/announce/2016/mfsa2016-26.html https://www.mozilla.org/security/announce/2016/mfsa2016-27.html https://www.mozilla.org/security/announce/2016/mfsa2016-28.html https://www.mozilla.org/security/announce/2016/mfsa2016-31.html https://www.mozilla.org/security/announce/2016/mfsa2016-29.html https://www.mozilla.org/security/announce/2016/mfsa2016-30.html https://www.mozilla.org/en-US/security/advisories/mfsa2016-38/ https://www.mozilla.org/security/announce/2016/mfsa2016-32.html https://www.mozilla.org/security/announce/2016/mfsa2016-32.html https://www.mozilla.org/security/announce/2016/mfsa2016-32.html https://www.mozilla.org/security/announce/2016/mfsa2016-33.html https://www.mozilla.org/security/announce/2016/mfsa2016-34.html https://www.mozilla.org/security/announce/2016/mfsa2016-32.html https://www.mozilla.org/security/announce/2016/mfsa2016-32.html https://www.mozilla.org/security/announce/2016/mfsa2016-37.html https://www.mozilla.org/security/announce/2016/mfsa2016-15.html https://www.mozilla.org/en-US/security/advisories/mfsa2016-36 http://seclists.org/oss-sec/2016/q1/173 http://seclists.org/oss-sec/2016/q1/173 http://www.openwall.com/lists/oss-security/2016/01/26/3 https://www.djangoproject.com/weblog/2016/feb/01/releases-192-and-189/ http://seclists.org/oss-sec/2016/q1/194 https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/ https://kb.isc.org/article/AA-01351 https://blog.fuzzing-project.org/36-Heap-buffer-overflow-in-fgetwln-function-of-libbsd.html https://groups.google.com/forum/#!msg/rubyonrails-security/ddY6HgqB2z4/we0RasMZIAAJ https://groups.google.com/forum/#!msg/rubyonrails-security/ly-IH-fxr_Q/WLoOhcMZIAAJ https://openssl.org/news/secadv/20160503.txt https://openssl.org/news/secadv/20160503.txt https://openssl.org/news/secadv/20160503.txt https://openssl.org/news/secadv/20160503.txt https://openssl.org/news/secadv/20160503.txt https://access.redhat.com/articles/2243351 https://access.redhat.com/articles/2243351 https://access.redhat.com/articles/2243351 https://access.redhat.com/articles/2243351 https://access.redhat.com/articles/2243351 https://access.redhat.com/articles/2243351 https://access.redhat.com/articles/2243351 https://access.redhat.com/articles/2253041 http://badlock.org/ https://www.samba.org/samba/security/CVE-2016-2123.html https://www.samba.org/samba/security/CVE-2016-2125.html https://www.samba.org/samba/security/CVE-2016-2126.html http://seclists.org/oss-sec/2016/q1/563 https://moodle.org/mod/forum/discuss.php?d=329783 https://moodle.org/mod/forum/discuss.php?d=329783 https://moodle.org/mod/forum/discuss.php?d=329783 https://moodle.org/mod/forum/discuss.php?d=329783 https://moodle.org/mod/forum/discuss.php?d=329783 https://moodle.org/mod/forum/discuss.php?d=329783 https://moodle.org/mod/forum/discuss.php?d=329783 https://moodle.org/mod/forum/discuss.php?d=329783 https://moodle.org/mod/forum/discuss.php?d=329783 https://httpd.apache.org/security/vulnerabilities_24.html#2.4.25 http://struts.apache.org/docs/s2-030.html https://subversion.apache.org/security/CVE-2016-2167-advisory.txt https://subversion.apache.org/security/CVE-2016-2168-advisory.txt https://jira.spring.io/browse/AMQP-590 http://pivotal.io/security/cve-2016-2173 https://openssl.org/news/secadv/20160503.txt https://www.openssl.org/news/secadv/20160922.txt https://www.openssl.org/news/secadv/20160922.txt http://eprint.iacr.org/2016/594 https://www.openssl.org/news/secadv/20160922.txt https://www.openssl.org/news/secadv/20160922.txt https://www.openssl.org/news/secadv/20160922.txt https://www.openssl.org/news/secadv/20160922.txt https://sweet32.info/ https://access.redhat.com/articles/2548661 https://access.redhat.com/errata/RHSA-2016:1940 https://moodle.org/mod/forum/discuss.php?d=329783 http://www.postgresql.org/about/news/1656/ http://botan.randombit.net/security.html#id1 http://botan.randombit.net/security.html#id1 http://botan.randombit.net/security.html#id1 https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/ http://www.dest-unreach.org/socat/contrib/socat-secadv7.html https://wordpress.org/news/2016/02/wordpress-4-4-2-security-and-maintenance-release/ https://wordpress.org/news/2016/02/wordpress-4-4-2-security-and-maintenance-release/ https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69687 http://downloads.asterisk.org/pub/security/AST-2016-003.html http://xenbits.xen.org/xsa/advisory-154.html http://xenbits.xen.org/xsa/advisory-170.html https://www.kde.org/info/security/advisory-20160209-1.txt http://downloads.asterisk.org/pub/security/AST-2016-002.html http://seclists.org/bugtraq/2016/Feb/28 http://mirror.easyname.at/nongnu//quagga/quagga-1.0.20160309.changelog.txt http://www.talosintel.com/reports/TALOS-2016-0133/ http://www.pidgin.im/news/security/?id=98 http://www.talosintel.com/reports/TALOS-2016-0134/ http://www.pidgin.im/news/security/?id=99 http://www.talosintel.com/reports/TALOS-2016-0135/ http://www.pidgin.im/news/security/?id=100 http://www.talosintel.com/reports/TALOS-2016-0136/ http://www.pidgin.im/news/security/?id=101 http://www.talosintel.com/reports/TALOS-2016-0137/ http://www.pidgin.im/news/security/?id=102 http://www.talosintel.com/reports/TALOS-2016-0138/ http://www.pidgin.im/news/security/?id=103 http://www.talosintel.com/reports/TALOS-2016-0139/ http://www.pidgin.im/news/security/?id=104 http://www.talosintel.com/reports/TALOS-2016-0140/ http://www.pidgin.im/news/security/?id=105 http://www.talosintel.com/reports/TALOS-2016-0141/ http://www.pidgin.im/news/security/?id=106 http://www.talosintel.com/reports/TALOS-2016-0142/ http://www.pidgin.im/news/security/?id=107 http://www.talosintel.com/reports/TALOS-2016-0143/ http://www.pidgin.im/news/security/?id=108 http://www.talosintel.com/reports/TALOS-2016-0118/ http://www.pidgin.im/news/security/?id=92 http://www.talosintel.com/reports/TALOS-2016-0119/ http://www.pidgin.im/news/security/?id=93 http://www.talosintel.com/reports/TALOS-2016-0120/ http://www.pidgin.im/news/security/?id=94 https://www.pidgin.im/news/security/?id=95 http://www.talosintelligence.com/reports/TALOS-2016-0122/ http://www.talosintel.com/reports/TALOS-2016-0123/ http://www.pidgin.im/news/security/?id=96 http://seclists.org/oss-sec/2016/q1/330 https://lkml.org/lkml/2016/2/13/11 http://seclists.org/oss-sec/2016/q1/331 https://publicobject.com/2016/02/11/okhttp-certificate-pinning-vulnerability/ https://github.com/beanshell/beanshell/releases/tag/2.0b6 http://seclists.org/fulldisclosure/2016/Feb/99 https://www.djangoproject.com/weblog/2016/mar/01/security-releases/ https://www.djangoproject.com/weblog/2016/mar/01/security-releases/ http://support.ntp.org/bin/view/Main/SecurityNotice#April_2016_NTP_4_2_8p7_Security http://support.ntp.org/bin/view/Main/SecurityNotice#April_2016_NTP_4_2_8p7_Security http://support.ntp.org/bin/view/Main/SecurityNotice#April_2016_NTP_4_2_8p7_Security http://support.ntp.org/bin/view/Main/SecurityNotice#April_2016_NTP_4_2_8p7_Security https://www.wireshark.org/security/wnpa-sec-2016-01.html https://www.wireshark.org/security/wnpa-sec-2016-02.html https://www.wireshark.org/security/wnpa-sec-2016-03.html https://www.wireshark.org/security/wnpa-sec-2016-04.html https://www.wireshark.org/security/wnpa-sec-2016-05.html https://www.wireshark.org/security/wnpa-sec-2016-06.html https://www.wireshark.org/security/wnpa-sec-2016-07.html https://www.wireshark.org/security/wnpa-sec-2016-08.html https://www.wireshark.org/security/wnpa-sec-2016-09.html https://www.wireshark.org/security/wnpa-sec-2016-10.html https://www.wireshark.org/security/wnpa-sec-2016-10.html https://www.wireshark.org/security/wnpa-sec-2016-11.html https://lkml.org/lkml/2016/1/12/215 http://www.spinics.net/lists/alsa-devel/msg45102.html https://lkml.org/lkml/2016/1/12/465 http://marc.info/?l=linux-kernel&m=145269654327048 https://gist.githubusercontent.com/dvyukov/e833610757b098956b50/raw/d819cd13b466e4adbe3dd825ee481e4512e77633/gistfile1.txt http://seclists.org/oss-sec/2016/q1/133 https://www.phpmyadmin.net/security/PMASA-2016-10/ https://www.phpmyadmin.net/security/PMASA-2016-11/ https://www.phpmyadmin.net/security/PMASA-2016-12/ https://www.phpmyadmin.net/security/PMASA-2016-13/ http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/vuln-pscp-sink-sscanf.html http://seclists.org/fulldisclosure/2016/Mar/22 http://www.squid-cache.org/Advisories/SQUID-2016_2.txt http://www.squid-cache.org/Advisories/SQUID-2016_2.txt http://www.squid-cache.org/Advisories/SQUID-2016_2.txt http://www.squid-cache.org/Advisories/SQUID-2016_2.txt https://kb.isc.org/article/AA-01354 https://kb.isc.org/article/AA-01393/ https://kb.isc.org/article/AA-01419/0 https://puppet.com/security/cve/cve-2016-2785 https://puppet.com/security/cve/cve-2016-2788 https://www.mozilla.org/security/announce/2016/mfsa2016-37.html https://www.mozilla.org/security/announce/2016/mfsa2016-37.html https://www.mozilla.org/security/announce/2016/mfsa2016-37.html https://www.mozilla.org/security/announce/2016/mfsa2016-37.html https://www.mozilla.org/security/announce/2016/mfsa2016-37.html https://www.mozilla.org/security/announce/2016/mfsa2016-37.html https://www.mozilla.org/security/announce/2016/mfsa2016-37.html https://www.mozilla.org/security/announce/2016/mfsa2016-37.html https://www.mozilla.org/security/announce/2016/mfsa2016-37.html https://www.mozilla.org/security/announce/2016/mfsa2016-37.html https://www.mozilla.org/security/announce/2016/mfsa2016-37.html https://www.mozilla.org/security/announce/2016/mfsa2016-37.html https://www.mozilla.org/security/announce/2016/mfsa2016-37.html https://bugzilla.mozilla.org/show_bug.cgi?id=1253263 https://www.mozilla.org/security/announce/2016/mfsa2016-39.html https://www.mozilla.org/security/announce/2016/mfsa2016-39.html https://www.mozilla.org/security/announce/2016/mfsa2016-39.html https://www.mozilla.org/security/announce/2016/mfsa2016-39.html https://www.mozilla.org/security/announce/2016/mfsa2016-47.html https://www.mozilla.org/security/announce/2016/mfsa2016-40.html https://www.mozilla.org/security/announce/2016/mfsa2016-41.html https://www.mozilla.org/security/announce/2016/mfsa2016-42.html https://www.mozilla.org/security/announce/2016/mfsa2016-42.html https://www.mozilla.org/security/announce/2016/mfsa2016-43.html https://www.mozilla.org/security/announce/2016/mfsa2016-44.html https://www.mozilla.org/security/announce/2016/mfsa2016-49.html https://www.mozilla.org/security/announce/2016/mfsa2016-45.html https://www.mozilla.org/security/announce/2016/mfsa2016-46.html https://www.mozilla.org/security/announce/2016/mfsa2016-49.html https://www.mozilla.org/security/announce/2016/mfsa2016-50.html https://www.mozilla.org/security/announce/2016/mfsa2016-48.html https://www.mozilla.org/security/announce/2016/mfsa2016-51.html https://www.mozilla.org/security/announce/2016/mfsa2016-52.html https://www.mozilla.org/security/announce/2016/mfsa2016-54.html https://www.mozilla.org/security/announce/2016/mfsa2016-85.html https://www.mozilla.org/security/announce/2016/mfsa2016-56.html https://www.mozilla.org/security/announce/2016/mfsa2016-57.html https://www.mozilla.org/security/announce/2016/mfsa2016-63.html https://www.mozilla.org/security/announce/2016/mfsa2016-58.html https://www.mozilla.org/security/announce/2016/mfsa2016-60.html https://www.mozilla.org/security/announce/2016/mfsa2016-60.html https://www.mozilla.org/security/announce/2016/mfsa2016-61.html https://www.mozilla.org/security/announce/2016/mfsa2016-62.html https://www.mozilla.org/security/announce/2016/mfsa2016-62.html https://www.mozilla.org/security/announce/2016/mfsa2016-77.html https://www.mozilla.org/security/announce/2016/mfsa2016-64.html https://www.mozilla.org/security/announce/2016/mfsa2016-65.html http://googlechromereleases.blogspot.cz/2016/03/stable-channel-update.html https://codereview.chromium.org/1423573002 https://codereview.chromium.org/1454003003/ https://kb.isc.org/article/AA-01433 http://seclists.org/oss-sec/2016/q1/568 http://www.postgresql.org/about/news/1656/ https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_3.7.3_.282016-3-29.29 https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_3.7.3_.282016-3-29.29 https://lists.libreswan.org/pipermail/swan-announce/2016/000019.html https://struts.apache.org/docs/s2-032.html https://struts.apache.org/docs/s2-031.html http://mail-archives.apache.org/mod_mbox/hadoop-general/201701.mbox/%3C0ed32746-5a53-9051-5877-2b1abd88beb6%40apache.org%3E https://struts.apache.org/docs/s2-033.html http://activemq.apache.org/security-advisories.data/CVE-2016-3088-announcement.txt http://tomcat.apache.org/security-8.html http://tomcat.apache.org/security-7.html https://struts.apache.org/docs/s2-034.html https://www.kde.org/info/security/advisory-20160621-1.txt https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-04-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-04-11 https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_3.8_.2F_3.8.1_.282016-5-1.29 http://www.openssh.com/txt/x11fwd.adv https://matt.ucc.asn.au/dropbear/CHANGES http://proftpd.org/docs/RELEASE_NOTES-1.3.5b https://www.drupal.org/node/2636502 http://xenbits.xen.org/xsa/advisory-172.html http://xenbits.xen.org/xsa/advisory-172.html https://www.drupal.org/SA-CORE-2016-001 https://www.drupal.org/SA-CORE-2016-001 https://www.drupal.org/SA-CORE-2016-001 https://www.drupal.org/SA-CORE-2016-001 https://www.drupal.org/SA-CORE-2016-001 https://www.drupal.org/SA-CORE-2016-001 https://www.drupal.org/SA-CORE-2016-001 https://www.drupal.org/SA-CORE-2016-001 https://www.drupal.org/SA-CORE-2016-001 https://www.drupal.org/SA-CORE-2016-001 https://docs.saltstack.com/en/latest/topics/releases/2015.5.10.html https://docs.saltstack.com/en/latest/topics/releases/2015.8.8.html https://mail.gnome.org/archives/gnome-announce-list/2015-March/msg00047.html http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpuapr2016-2881694.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html#AppendixJAVA http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://bugzilla.maptools.org/show_bug.cgi?id=2565 http://bugzilla.maptools.org/show_bug.cgi?id=2569 http://bugzilla.maptools.org/show_bug.cgi?id=2568 http://bugzilla.maptools.org/show_bug.cgi?id=2566 https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_3.7.3_.282016-3-29.29 http://bugzilla.maptools.org/show_bug.cgi?id=2546 http://bugs.cacti.net/view.php?id=2673 http://hmarco.org/bugs/CVE-2016-3672-Unlimiting-the-stack-not-longer-disables-ASLR.html http://seclists.org/bugtraq/2016/Apr/34 https://github.com/x-stream/xstream/issues/25 http://googlechromereleases.blogspot.com/2016/03/stable-channel-update_24.html http://projects.theforeman.org/issues/14635 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 https://curl.haxx.se/docs/adv_20160518.html http://www.squid-cache.org/Advisories/SQUID-2016_3.txt http://www.squid-cache.org/Advisories/SQUID-2016_4.txt https://www.spinics.net/lists/netdev/msg367669.html https://bugzilla.novell.com/show_bug.cgi?id=974418 https://nodesecurity.io/advisories/98 http://xenbits.xen.org/xsa/advisory-173.html http://xenbits.xen.org/xsa/advisory-174.html https://sourceforge.net/p/giflib/bugs/87/ https://github.com/weidai11/cryptopp/issues/146 http://struts.apache.org/docs/s2-028.html https://www.wireshark.org/security/wnpa-sec-2016-25.html https://github.com/python-pillow/Pillow/pull/1714 https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2016-030.txt https://codex.wordpress.org/Version_4.5#Security http://openwall.com/lists/oss-security/2016/04/27/7 http://www.squid-cache.org/Advisories/SQUID-2016_5.txt http://www.squid-cache.org/Advisories/SQUID-2016_6.txt http://www.squid-cache.org/Advisories/SQUID-2016_6.txt http://www.squid-cache.org/Advisories/SQUID-2016_6.txt https://nodesecurity.io/advisories/55 https://www.wireshark.org/security/wnpa-sec-2016-19.html https://www.wireshark.org/security/wnpa-sec-2016-20.html https://www.wireshark.org/security/wnpa-sec-2016-21.html https://www.wireshark.org/security/wnpa-sec-2016-22.html https://www.wireshark.org/security/wnpa-sec-2016-23.html https://www.wireshark.org/security/wnpa-sec-2016-24.html https://www.wireshark.org/security/wnpa-sec-2016-26.html https://www.wireshark.org/security/wnpa-sec-2016-27.html https://www.wireshark.org/security/wnpa-sec-2016-27.html https://www.wireshark.org/security/wnpa-sec-2016-28.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-15.html https://helpx.adobe.com/security/products/flash-player/apsa16-02.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-18.html https://helpx.adobe.com/security/products/flash-player/apsa16-03.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/xmpcore/apsb16-24.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-32.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-32.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html http://www.talosintel.com/reports/TALOS-2016-0152/ http://www.talosintel.com/reports/TALOS-2016-0153/ http://www.talosintel.com/reports/TALOS-2016-0154/ https://raw.githubusercontent.com/esnet/security/master/cve-2016-4303/esnet-secadv-2016-0001.txt.asc http://www.talosintel.com/reports/TALOS-2016-0128/ http://www.pidgin.im/news/security/?id=97 https://www.libreoffice.org/about-us/security/advisories/cve-2016-4324/ http://blog.talosintel.com/2016/06/vulnerability-spotlight-libreoffice-rtf.html http://www.talosintelligence.com/reports/TALOS-2016-0176/ http://www.talosintelligence.com/reports/TALOS-2016-0177/ http://www.talosintelligence.com/reports/TALOS-2016-0178/ http://www.talosintelligence.com/reports/TALOS-2016-0179/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.wireshark.org/security/wnpa-sec-2016-12.html https://www.wireshark.org/security/wnpa-sec-2016-13.html https://www.wireshark.org/security/wnpa-sec-2016-14.html https://www.wireshark.org/security/wnpa-sec-2016-15.html https://www.wireshark.org/security/wnpa-sec-2016-16.html https://www.wireshark.org/security/wnpa-sec-2016-17.html https://www.wireshark.org/security/wnpa-sec-2016-18.html https://symfony.com/blog/cve-2016-4423-large-username-storage-in-session https://struts.apache.org/docs/s2-038.html https://struts.apache.org/docs/s2-040.html https://issues.apache.org/jira/browse/QPID-7257 https://struts.apache.org/docs/s2-039.html https://struts.apache.org/docs/s2-035.html https://struts.apache.org/docs/s2-037.html http://mailman.nginx.org/pipermail/nginx-announce/2016/000179.html http://gnutls.org/security.html#GNUTLS-SA-2016-1 http://xerces.apache.org/xerces-c/secadv/CVE-2016-4463.txt https://struts.apache.org/docs/s2-041.html http://w1.fi/security/2016-1/ http://xenbits.xen.org/xsa/advisory-176.html http://www.spinics.net/lists/linux-usb/msg140243.html https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70492 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70498 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70909 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70926 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70926 https://github.com/roundcube/roundcubemail/issues/5240 http://www.squid-cache.org/Advisories/SQUID-2016_7.txt http://www.squid-cache.org/Advisories/SQUID-2016_8.txt http://www.squid-cache.org/Advisories/SQUID-2016_9.txt http://www.squid-cache.org/Advisories/SQUID-2016_9.txt https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-4562 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-4563 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-4564 https://wordpress.org/news/2016/05/wordpress-4-5-2/ https://wordpress.org/news/2016/05/wordpress-4-5-2/ http://comments.gmane.org/gmane.linux.kernel/2214250 http://www.ocert.org/advisories/ocert-2016-001.html https://github.com/dosfstools/dosfstools/issues/25 https://github.com/dosfstools/dosfstools/issues/26 https://blog.fuzzing-project.org/44-dosfstools-fsck.vfat-Several-invalid-memory-accesses.html https://framework.zend.com/security/advisory/ZF2016-03 http://support.ntp.org/bin/view/Main/SecurityNotice#June_2016_ntp_4_2_8p8_NTP_Securi http://support.ntp.org/bin/view/Main/SecurityNotice#June_2016_ntp_4_2_8p8_NTP_Securi http://support.ntp.org/bin/view/Main/SecurityNotice#June_2016_ntp_4_2_8p8_NTP_Securi http://support.ntp.org/bin/view/Main/SecurityNotice#June_2016_ntp_4_2_8p8_NTP_Securi http://support.ntp.org/bin/view/Main/SecurityNotice#June_2016_ntp_4_2_8p8_NTP_Securi http://xenbits.xen.org/xsa/advisory-175.html http://xenbits.xen.org/xsa/advisory-178.html https://httpd.apache.org/security/vulnerabilities_22.html#CVE-2016-4975 https://httpd.apache.org/security/vulnerabilities_24.html#CVE-2016-4975 http://httpd.apache.org/security/vulnerabilities_24.html#2.4.23 https://pivotal.io/security/cve-2016-5007 https://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.47 https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.72 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.5_and_8.0.37 https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.prevanders.net/dwarfbug.html https://www.phpmyadmin.net/security/PMASA-2016-16/ https://www.phpmyadmin.net/security/PMASA-2016-15/ https://www.phpmyadmin.net/security/PMASA-2016-14/ https://www.phpmyadmin.net/security/PMASA-2016-16/ https://www.phpmyadmin.net/security/PMASA-2016-15/ https://www.phpmyadmin.net/security/PMASA-2016-14/ https://www.phpmyadmin.net/security/PMASA-2016-16/ https://www.phpmyadmin.net/security/PMASA-2016-15/ https://www.phpmyadmin.net/security/PMASA-2016-14/ https://github.com/libgd/libgd/issues/211 https://bogner.sh/2016/03/mitm-attack-against-keepass-2s-update-check/ https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/08/stable-channel-update-for-desktop_31.html https://googlechromereleases.blogspot.com/2016/09/stable-channel-update-for-desktop_13.html https://googlechromereleases.blogspot.com/2016/09/stable-channel-update-for-desktop_13.html https://googlechromereleases.blogspot.com/2016/09/stable-channel-update-for-desktop_13.html https://googlechromereleases.blogspot.com/2016/09/stable-channel-update-for-desktop_13.html https://googlechromereleases.blogspot.com/2016/09/stable-channel-update-for-desktop_13.html https://googlechromereleases.blogspot.com/2016/09/stable-channel-update-for-desktop_13.html https://googlechromereleases.blogspot.cz/2016/09/stable-channel-update-for-desktop_13.html https://googlechromereleases.blogspot.com/2016/09/stable-channel-update-for-desktop_29.html https://googlechromereleases.blogspot.com/2016/09/stable-channel-update-for-desktop_29.html https://c-ares.haxx.se/adv_20160929.html https://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/11/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/11/stable-channel-update-for-desktop_9.html https://googlechromereleases.blogspot.com/2016/11/stable-channel-update-for-desktop_9.html https://googlechromereleases.blogspot.com/2016/11/stable-channel-update-for-desktop_9.html https://googlechromereleases.blogspot.com/2016/11/stable-channel-update-for-desktop_9.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html http://xenbits.xen.org/xsa/advisory-181.html https://www.mozilla.org/security/advisories/mfsa2016-84/ https://www.mozilla.org/security/advisories/mfsa2016-86/ https://www.mozilla.org/security/announce/2016/mfsa2016-66.html https://www.mozilla.org/security/announce/2016/mfsa2016-67.html https://www.mozilla.org/security/announce/2016/mfsa2016-70.html https://www.mozilla.org/security/announce/2016/mfsa2016-71.html https://www.mozilla.org/security/announce/2016/mfsa2016-85.html https://www.mozilla.org/security/advisories/mfsa2016-85/ https://www.mozilla.org/security/advisories/mfsa2016-86/ https://www.mozilla.org/security/announce/2016/mfsa2016-72.html https://www.mozilla.org/security/announce/2016/mfsa2016-73.html https://www.mozilla.org/security/announce/2016/mfsa2016-74.html https://www.mozilla.org/security/advisories/mfsa2016-75/ https://www.mozilla.org/security/advisories/mfsa2016-86/ https://www.mozilla.org/security/announce/2016/mfsa2016-76.html https://www.mozilla.org/security/announce/2016/mfsa2016-78.html https://www.mozilla.org/security/announce/2016/mfsa2016-79.html https://www.mozilla.org/security/announce/2016/mfsa2016-80.html https://www.mozilla.org/security/announce/2016/mfsa2016-81.html https://www.mozilla.org/security/announce/2016/mfsa2016-83.html https://www.mozilla.org/security/advisories/mfsa2016-85/ https://www.mozilla.org/security/advisories/mfsa2016-86/ https://www.mozilla.org/security/announce/2016/mfsa2016-85.html https://www.mozilla.org/security/advisories/mfsa2016-85/ https://www.mozilla.org/security/advisories/mfsa2016-86/ https://www.mozilla.org/security/announce/2016/mfsa2016-85.html https://www.mozilla.org/security/advisories/mfsa2016-85/ https://www.mozilla.org/security/advisories/mfsa2016-86/ https://www.mozilla.org/security/announce/2016/mfsa2016-85.html https://www.mozilla.org/security/advisories/mfsa2016-85/ https://www.mozilla.org/security/advisories/mfsa2016-86/ https://www.mozilla.org/security/advisories/mfsa2016-85/ https://www.mozilla.org/security/advisories/mfsa2016-86/ https://www.mozilla.org/security/advisories/mfsa2016-85/ https://www.mozilla.org/security/advisories/mfsa2016-86/ https://www.mozilla.org/security/announce/2016/mfsa2016-85.html https://www.mozilla.org/security/advisories/mfsa2016-85/ https://www.mozilla.org/security/advisories/mfsa2016-86/ https://www.mozilla.org/security/advisories/mfsa2016-85/ https://www.mozilla.org/security/advisories/mfsa2016-86/ https://www.mozilla.org/security/announce/2016/mfsa2016-85.html https://www.mozilla.org/security/announce/2016/mfsa2016-85.html https://www.mozilla.org/security/advisories/mfsa2016-85/ https://www.mozilla.org/security/advisories/mfsa2016-86/ https://www.mozilla.org/security/announce/2016/mfsa2016-89.html https://www.mozilla.org/security/announce/2016/mfsa2016-90.html https://www.mozilla.org/security/announce/2016/mfsa2016-89.html https://www.mozilla.org/security/announce/2016/mfsa2016-89.html https://www.mozilla.org/security/announce/2016/mfsa2016-89.html https://www.mozilla.org/security/announce/2016/mfsa2016-89.html https://nodejs.org/en/blog/vulnerability/september-2016-security-releases/ https://www.wireshark.org/security/wnpa-sec-2016-29.html https://www.wireshark.org/security/wnpa-sec-2016-30.html https://www.wireshark.org/security/wnpa-sec-2016-31.html https://www.wireshark.org/security/wnpa-sec-2016-32.html https://www.wireshark.org/security/wnpa-sec-2016-33.html https://www.wireshark.org/security/wnpa-sec-2016-34.html https://www.wireshark.org/security/wnpa-sec-2016-35.html https://www.wireshark.org/security/wnpa-sec-2016-36.html https://www.wireshark.org/security/wnpa-sec-2016-37.html https://www.wireshark.org/security/wnpa-sec-2016-38.html https://access.redhat.com/security/vulnerabilities/httpoxy https://httpoxy.org/ https://www.apache.org/security/asf-httpoxy-response.txt https://libreswan.org/security/CVE-2016-5391/CVE-2016-5391.txt https://lists.x.org/archives/xorg-announce/2016-October/002720.html http://seclists.org/oss-sec/2016/q3/255 https://curl.haxx.se/docs/adv_20160803A.html https://curl.haxx.se/docs/adv_20160803B.html https://curl.haxx.se/docs/adv_20160803C.html http://legalhackers.com/advisories/Tomcat-RedHat-based-Root-Privilege-Escalation-Exploit.txt https://doc.powerdns.com/md/security/powerdns-advisory-2016-01/ https://doc.powerdns.com/md/security/powerdns-advisory-2016-01/ http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html http://www.oracle.com/technetwork/topics/security/cpujul2016-2881720.html https://blog.tarq.io/cve-2016-5483-backdooring-mysqldump-backups/ https://blog.tarq.io/cve-2016-5483-galera-remote-command-execution-via-crafted-database-name/ http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL https://legalhackers.com/advisories/MySQL-Maria-Percona-PrivEscRace-CVE-2016-6663-5616-Exploit.txt https://legalhackers.com/advisories/MySQL-Maria-Percona-RootPrivEsc-CVE-2016-6664-5617-Exploit.txt http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.talosintelligence.com/reports/TALOS-2016-0187/ https://community.rapid7.com/community/infosec/blog/2016/09/02/r7-2016-19-persistent-xss-via-unescaped-parameters-in-swagger-ui http://www.talosintelligence.com/reports/TALOS-2016-0189/ https://blog.fuzzing-project.org/46-Various-invalid-memory-reads-in-ImageMagick-WPG,-DDS,-DCM.html https://blog.fuzzing-project.org/46-Various-invalid-memory-reads-in-ImageMagick-WPG,-DDS,-DCM.html https://blog.fuzzing-project.org/46-Various-invalid-memory-reads-in-ImageMagick-WPG,-DDS,-DCM.html https://blog.fuzzing-project.org/46-Various-invalid-memory-reads-in-ImageMagick-WPG,-DDS,-DCM.html https://blog.fuzzing-project.org/46-Various-invalid-memory-reads-in-ImageMagick-WPG,-DDS,-DCM.html http://lwn.net/Articles/696868/ https://www.phpmyadmin.net/news/2016/6/23/phpmyadmin-401016-44157-and-463-are-released/ https://www.phpmyadmin.net/news/2016/6/23/phpmyadmin-401016-44157-and-463-are-released/ https://www.phpmyadmin.net/news/2016/6/23/phpmyadmin-401016-44157-and-463-are-released/ https://www.phpmyadmin.net/news/2016/6/23/phpmyadmin-401016-44157-and-463-are-released/ https://www.phpmyadmin.net/news/2016/6/23/phpmyadmin-401016-44157-and-463-are-released/ https://www.phpmyadmin.net/news/2016/6/23/phpmyadmin-401016-44157-and-463-are-released/ https://github.com/tintinweb/pub/tree/master/pocs/cve-2016-5725 https://www.phpmyadmin.net/news/2016/6/23/phpmyadmin-401016-44157-and-463-are-released/ https://www.phpmyadmin.net/news/2016/6/23/phpmyadmin-401016-44157-and-463-are-released/ https://www.phpmyadmin.net/news/2016/6/23/phpmyadmin-401016-44157-and-463-are-released/ https://www.phpmyadmin.net/news/2016/6/23/phpmyadmin-401016-44157-and-463-are-released/ https://www.phpmyadmin.net/news/2016/6/23/phpmyadmin-401016-44157-and-463-are-released/ https://www.phpmyadmin.net/news/2016/6/23/phpmyadmin-401016-44157-and-463-are-released/ https://wordpress.org/news/2016/06/wordpress-4-5-3/ https://wordpress.org/news/2016/06/wordpress-4-5-3/ https://wordpress.org/news/2016/06/wordpress-4-5-3/ https://wordpress.org/news/2016/06/wordpress-4-5-3/ https://wordpress.org/news/2016/06/wordpress-4-5-3/ https://wordpress.org/news/2016/06/wordpress-4-5-3/ https://wordpress.org/news/2016/06/wordpress-4-5-3/ https://wordpress.org/news/2016/06/wordpress-4-5-3/ http://www.talosintelligence.com/reports/TALOS-2016-0205 https://www.korelogic.com/Resources/Advisories/KL-001-2016-003.txt https://www.drupal.org/SA-CORE-2016-002 https://www.drupal.org/SA-CORE-2016-002 https://www.percona.com/blog/2017/01/12/cve-2016-6225-percona-xtrabackup-encryption-iv-not-set-properly/ https://www.kde.org/info/security/advisory-20160724-1.txt https://framework.zend.com/security/advisory/ZF2016-02 http://xenbits.xen.org/xsa/advisory-182.html http://xenbits.xen.org/xsa/advisory-183.html https://www.openssl.org/news/secadv/20160922.txt https://www.openssl.org/news/secadv/20160922.txt https://www.openssl.org/news/secadv/20160922.txt https://www.openssl.org/news/secadv/20160922.txt https://www.openssl.org/news/secadv/20160922.txt https://www.openssl.org/news/secadv/20160922.txt https://www.openssl.org/news/secadv/20160926.txt https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000395.html https://groups.google.com/forum/#!msg/rubyonrails-security/I-VWr034ouk/gGu2FrCwDAAJ https://groups.google.com/forum/#!msg/rubyonrails-security/rgO20zYW33s/gmamLa-wDAAJ https://sintonen.fi/advisories/tar-extract-pathname-bypass.txt https://community.openvpn.net/openvpn/wiki/SWEET32 https://sweet32.info/ https://lists.wikimedia.org/pipermail/mediawiki-announce/2016-August/000195.html https://lists.wikimedia.org/pipermail/mediawiki-announce/2016-August/000195.html https://lists.wikimedia.org/pipermail/mediawiki-announce/2016-August/000195.html https://lists.wikimedia.org/pipermail/mediawiki-announce/2016-August/000195.html https://lists.wikimedia.org/pipermail/mediawiki-announce/2016-August/000195.html https://lists.wikimedia.org/pipermail/mediawiki-announce/2016-August/000195.html https://www.wireshark.org/security/wnpa-sec-2016-41.html https://www.wireshark.org/security/wnpa-sec-2016-42.html https://www.wireshark.org/security/wnpa-sec-2016-43.html https://www.wireshark.org/security/wnpa-sec-2016-44.html https://www.wireshark.org/security/wnpa-sec-2016-45.html https://www.wireshark.org/security/wnpa-sec-2016-46.html https://www.wireshark.org/security/wnpa-sec-2016-47.html https://www.wireshark.org/security/wnpa-sec-2016-48.html https://www.wireshark.org/security/wnpa-sec-2016-49.html https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://codex.wordpress.org/Version_4.5#Security https://codex.wordpress.org/Version_4.5#Security https://legalhackers.com/advisories/MySQL-Exploit-Remote-Root-Code-Execution-Privesc-CVE-2016-6662.txt https://legalhackers.com/advisories/MySQL-Maria-Percona-PrivEscRace-CVE-2016-6663-5616-Exploit.txt https://legalhackers.com/advisories/MySQL-Maria-Percona-RootPrivEsc-CVE-2016-6664-5617-Exploit.txt https://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.47 https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.72 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.5_and_8.0.37 https://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.47 https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.72 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.5_and_8.0.37 https://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.47 https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.72 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.5_and_8.0.37 https://tomcat.apache.org/security-jk.html#Fixed_in_Apache_Tomcat_JK_Connector_1.2.42 http://activemq.apache.org/security-advisories.data/CVE-2016-6810-announcement.txt http://cxf.apache.org/security-advisories.data/CVE-2016-6812.txt.asc?version=1&modificationDate=1482164360602&api=v2 https://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.48 https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.73 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.39 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.8 https://access.redhat.com/solutions/2891171 https://access.redhat.com/articles/2991951 https://sumofpwn.nl/advisory/2016/path_traversal_vulnerability_in_wordpress_core_ajax_handlers.html https://sumofpwn.nl/advisory/2016/path_traversal_vulnerability_in_wordpress_core_ajax_handlers.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-29.html https://helpx.adobe.com/security/products/flash-player/apsb16-32.html https://helpx.adobe.com/security/products/flash-player/apsb16-32.html https://helpx.adobe.com/security/products/flash-player/apsb16-32.html https://helpx.adobe.com/security/products/flash-player/apsb16-32.html https://helpx.adobe.com/security/products/flash-player/apsb16-32.html https://helpx.adobe.com/security/products/flash-player/apsb16-32.html https://helpx.adobe.com/security/products/flash-player/apsb16-32.html https://helpx.adobe.com/security/products/flash-player/apsb16-32.html https://helpx.adobe.com/security/products/flash-player/apsb16-32.html https://helpx.adobe.com/security/products/flash-player/apsb16-32.html https://helpx.adobe.com/security/products/flash-player/apsb16-25.html https://www.sudo.ws/alerts/noexec_bypass.html https://irssi.org/security/irssi_sa_2016.txt https://irssi.org/security/irssi_sa_2016.txt https://www.openssl.org/news/secadv/20160926.txt https://www.openssl.org/news/secadv/20161110.txt https://www.openssl.org/news/secadv/20161110.txt https://www.openssl.org/news/secadv/20161110.txt https://www.openssl.org/news/secadv/20170126.txt https://doc.powerdns.com/md/security/powerdns-advisory-2016-02/ https://doc.powerdns.com/md/security/powerdns-advisory-2016-03/ https://doc.powerdns.com/md/security/powerdns-advisory-2016-04/ https://doc.powerdns.com/md/security/powerdns-advisory-2016-04/ https://www.sudo.ws/alerts/noexec_wordexp.html https://xenbits.xen.org/xsa/advisory-185.html https://xenbits.xen.org/xsa/advisory-186.html https://xenbits.xen.org/xsa/advisory-187.html https://nodejs.org/en/blog/vulnerability/september-2016-security-releases/ https://nodesecurity.io/advisories/127 https://plone.org/security/hotfix/20160830/filesystem-information-leak https://plone.org/security/hotfix/20160830/non-persistent-xss-in-plone-forms https://plone.org/security/hotfix/20160830/open-redirection-in-plone https://plone.org/security/hotfix/20160830/non-persistent-xss-in-plone-1 https://plone.org/security/hotfix/20160830/non-persistent-xss-in-plone https://plone.org/security/hotfix/20160830/non-persistent-xss-in-zope2 https://curl.haxx.se/docs/adv_20160907.html https://www.curesec.com/blog/article/blog/MoinMoin-198-XSS-175.html https://www.curesec.com/blog/article/blog/MoinMoin-198-XSS-175.html https://www.blackhat.com/docs/us-16/materials/us-16-VanGoethem-HEIST-HTTP-Encrypted-Information-Can-Be-Stolen-Through-TCP-Windows-wp.pdf https://www.blackhat.com/docs/us-16/materials/us-16-VanGoethem-HEIST-HTTP-Encrypted-Information-Can-Be-Stolen-Through-TCP-Windows-wp.pdf https://xenbits.xen.org/xsa/advisory-188.html https://curl.haxx.se/docs/adv_20160914.html https://wordpress.org/news/2016/09/wordpress-4-6-1-security-and-maintenance-release/ https://wordpress.org/news/2016/09/wordpress-4-6-1-security-and-maintenance-release/ https://www.wireshark.org/security/wnpa-sec-2016-50.html https://www.wireshark.org/security/wnpa-sec-2016-51.html https://www.wireshark.org/security/wnpa-sec-2016-52.html https://www.wireshark.org/security/wnpa-sec-2016-53.html https://www.wireshark.org/security/wnpa-sec-2016-54.html https://www.wireshark.org/security/wnpa-sec-2016-55.html https://owncloud.org/security/advisory/?id=oc-sa-2016-011 http://support.ntp.org/bin/view/Main/NtpBug3071 http://support.ntp.org/bin/view/Main/NtpBug3114 http://support.ntp.org/bin/view/Main/NtpBug3113 http://support.ntp.org/bin/view/Main/NtpBug3072 http://support.ntp.org/bin/view/Main/NtpBug3102 http://support.ntp.org/bin/view/Main/NtpBug3067 http://support.ntp.org/bin/view/Main/NtpBug3102 http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL https://www.gnutls.org/security.html https://lists.gnupg.org/pipermail/gnutls-devel/2016-September/008146.html https://blog.checkpoint.com/wp-content/uploads/2016/12/PHP_Technical_Report.pdf https://blog.checkpoint.com/wp-content/uploads/2016/12/PHP_Technical_Report.pdf http://blog.checkpoint.com/2016/12/27/check-point-discovers-three-zero-day-vulnerabilities-web-programming-language-php-7/ http://downloads.asterisk.org/pub/security/AST-2016-007.html https://irssi.org/2016/09/22/buf.pl-update/ http://xenbits.xen.org/xsa/advisory-190.html https://helpx.adobe.com/security/products/flash-player/apsb16-36.html https://helpx.adobe.com/security/products/flash-player/apsb16-37.html https://helpx.adobe.com/security/products/flash-player/apsb16-37.html https://helpx.adobe.com/security/products/flash-player/apsb16-37.html https://helpx.adobe.com/security/products/flash-player/apsb16-37.html https://helpx.adobe.com/security/products/flash-player/apsb16-37.html https://helpx.adobe.com/security/products/flash-player/apsb16-37.html https://helpx.adobe.com/security/products/flash-player/apsb16-37.html https://helpx.adobe.com/security/products/flash-player/apsb16-37.html https://helpx.adobe.com/security/products/flash-player/apsb16-37.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://helpx.adobe.com/security/products/flash-player/apsb16-39.html https://lists.x.org/archives/xorg-announce/2016-October/002720.html https://lists.x.org/archives/xorg-announce/2016-October/002720.html https://lists.x.org/archives/xorg-announce/2016-October/002720.html https://lists.x.org/archives/xorg-announce/2016-October/002720.html https://lists.x.org/archives/xorg-announce/2016-October/002720.html https://lists.x.org/archives/xorg-announce/2016-October/002720.html https://lists.x.org/archives/xorg-announce/2016-October/002720.html https://lists.x.org/archives/xorg-announce/2016-October/002720.html https://lists.x.org/archives/xorg-announce/2016-October/002720.html https://lists.x.org/archives/xorg-announce/2016-October/002720.html https://lists.x.org/archives/xorg-announce/2016-October/002720.html https://lists.x.org/archives/xorg-announce/2016-October/002720.html https://collectiveidea.com/blog/archives/2016/10/06/bundlers-multiple-source-security-vulnerability https://github.com/bundler/bundler/issues/5051 https://github.com/bundler/bundler/issues/5274 https://www.wireshark.org/security/wnpa-sec-2016-56.html https://www.wireshark.org/security/wnpa-sec-2016-57.html https://www.kde.org/info/security/advisory-20161006-1.txt https://www.kde.org/info/security/advisory-20161006-2.txt https://www.kde.org/info/security/advisory-20161006-3.txt https://github.com/libass/libass/releases/tag/0.13.4 https://github.com/libass/libass/releases/tag/0.13.4 https://github.com/libass/libass/releases/tag/0.13.4 http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881724.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixJAVA http://www.talosintelligence.com/reports/TALOS-2016-0190 http://www.talosintelligence.com/reports/TALOS-2016-0193/ http://www.talosintelligence.com/reports/TALOS-2016-0206/ http://blog.talosintel.com/2016/09/redis-vulnerability.html http://security.360.cn/cve/CVE-2016-8610 https://curl.haxx.se/docs/adv_20161102A.html https://curl.haxx.se/docs/adv_20161102B.html https://curl.haxx.se/docs/adv_20161102C.html https://curl.haxx.se/docs/adv_20161102D.html https://curl.haxx.se/docs/adv_20161102E.html https://curl.haxx.se/docs/adv_20161102F.html https://curl.haxx.se/docs/adv_20161102G.html https://curl.haxx.se/docs/adv_20161102H.html https://curl.haxx.se/docs/adv_20161102I.html https://curl.haxx.se/docs/adv_20161102J.html https://curl.haxx.se/docs/adv_20161102K.html http://www.talosintelligence.com/reports/TALOS-2016-0219/ http://www.talosintelligence.com/reports/TALOS-2016-0220/ http://www.talosintelligence.com/reports/TALOS-2016-0221/ http://www.talosintelligence.com/reports/TALOS-2016-0227/ https://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.48 https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.73 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.39 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.8 http://cxf.apache.org/security-advisories.data/CVE-2016-8739.txt.asc?version=1&modificationDate=1482164360575&api=v2 https://httpd.apache.org/security/vulnerabilities_24.html http://seclists.org/bugtraq/2016/Dec/3 https://httpd.apache.org/security/vulnerabilities_24.html#2.4.25 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.9 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.40 https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.74 https://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.49 http://camel.apache.org/security-advisories.data/CVE-2016-8749.txt.asc https://karaf.apache.org/security/cve-2016-8750.txt https://blog.torproject.org/blog/tor-0289-released-important-fixes https://kb.isc.org/article/AA-01434 https://blogs.gentoo.org/ago/2016/10/18/libwmf-memory-allocation-failure-in-wmf_malloc-api-c/ http://www.talosintelligence.com/reports/TALOS-2016-0260/ https://www.mozilla.org/en-US/security/advisories/mfsa2016-89/#CVE-2016-9063 https://www.mozilla.org/security/announce/2016/mfsa2016-89.html https://www.mozilla.org/security/announce/2016/mfsa2016-89.html https://www.mozilla.org/en-US/security/advisories/mfsa2016-89/#CVE-2016-9067 https://www.mozilla.org/en-US/security/advisories/mfsa2016-89/#CVE-2016-9068 https://www.mozilla.org/en-US/security/advisories/mfsa2016-89/#CVE-2016-9067 https://www.mozilla.org/en-US/security/advisories/mfsa2016-89/#CVE-2016-9070 https://www.mozilla.org/security/announce/2016/mfsa2016-89.html https://www.mozilla.org/en-US/security/advisories/mfsa2016-89/#CVE-2016-9073 https://www.mozilla.org/en-US/security/advisories/mfsa2016-89/#CVE-2016-9074 https://www.mozilla.org/security/announce/2016/mfsa2016-89.html https://www.mozilla.org/en-US/security/advisories/mfsa2016-89/#CVE-2016-9076 https://www.mozilla.org/security/announce/2016/mfsa2016-89.html https://www.mozilla.org/en-US/security/advisories/mfsa2016-92/#CVE-2016-9079 https://kb.isc.org/article/AA-01439 https://kb.isc.org/article/AA-01440 http://seclists.org/fulldisclosure/2016/Nov/13 http://security.samsungmobile.com/smrupdate.html#SMR-NOV-2016 http://security.samsungmobile.com/smrupdate.html#SMR-NOV-2016 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-11-16 http://support.ntp.org/bin/view/Main/NtpBug3118 http://support.ntp.org/bin/view/Main/NtpBug3119 http://support.ntp.org/bin/view/Main/NtpBug3110 https://www.wireshark.org/security/wnpa-sec-2016-58.html https://www.wireshark.org/security/wnpa-sec-2016-61.html https://www.wireshark.org/security/wnpa-sec-2016-59.html https://www.wireshark.org/security/wnpa-sec-2016-62.html https://www.wireshark.org/security/wnpa-sec-2016-60.html http://xenbits.xen.org/xsa/advisory-196.html http://xenbits.xen.org/xsa/advisory-196.html http://xenbits.xen.org/xsa/advisory-198.html http://xenbits.xen.org/xsa/advisory-198.html http://xenbits.xen.org/xsa/advisory-197.html http://xenbits.xen.org/xsa/advisory-192.html http://xenbits.xen.org/xsa/advisory-195.html http://xenbits.xen.org/xsa/advisory-194.html http://xenbits.xen.org/xsa/advisory-193.html http://xenbits.xen.org/xsa/advisory-191.html https://kb.isc.org/article/AA-01441 https://scarybeastsecurity.blogspot.com/2016/11/0day-poc-risky-design-decisions-in.html?m=1 https://scarybeastsecurity.blogspot.sk/2016/11/0day-poc-risky-design-decisions-in.html https://scarybeastsecurity.blogspot.cz/2016/11/0day-exploit-compromising-linux-desktop.html https://www.drupal.org/SA-CORE-2016-005 https://www.drupal.org/SA-CORE-2016-005 https://www.drupal.org/SA-CORE-2016-005 https://www.drupal.org/SA-CORE-2016-005 https://legalhackers.com/advisories/Nagios-Exploit-Command-Injection-CVE-2016-9565-2008-4796.html https://legalhackers.com/advisories/Nagios-Exploit-Root-PrivEsc-CVE-2016-9566.html https://curl.haxx.se/docs/adv_20161221A.html https://curl.haxx.se/docs/adv_20161223.html https://scarybeastsecurity.blogspot.com/2016/11/0day-exploit-advancing-exploitation.html https://scarybeastsecurity.blogspot.com/2016/11/0day-exploit-advancing-exploitation.html https://scarybeastsecurity.blogspot.com/2016/11/0day-exploit-advancing-exploitation.html http://xenbits.xen.org/xsa/advisory-199.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html http://seclists.org/oss-sec/2016/q3/624 https://kb.isc.org/article/AA-01442/0 https://scarybeastsecurity.blogspot.com/2016/11/0day-exploit-advancing-exploitation.html http://xenbits.xen.org/xsa/advisory-201.html http://xenbits.xen.org/xsa/advisory-201.html http://xenbits.xen.org/xsa/advisory-201.html http://xenbits.xen.org/xsa/advisory-201.html https://wiki.mozilla.org/images/0/09/Zlib-report.pdf https://docs.google.com/document/d/10i1KZS5so8xDqH2rplRa2xet0tyTvvJlLbQQmZIUIKE/edit#heading=h.t13tvnx4loq7 https://wiki.mozilla.org/images/0/09/Zlib-report.pdf https://docs.google.com/document/d/10i1KZS5so8xDqH2rplRa2xet0tyTvvJlLbQQmZIUIKE/edit#heading=h.t13tvnx4loq7 https://wiki.mozilla.org/images/0/09/Zlib-report.pdf https://docs.google.com/document/d/10i1KZS5so8xDqH2rplRa2xet0tyTvvJlLbQQmZIUIKE/edit#heading=h.t13tvnx4loq7 https://wiki.mozilla.org/images/0/09/Zlib-report.pdf https://docs.google.com/document/d/10i1KZS5so8xDqH2rplRa2xet0tyTvvJlLbQQmZIUIKE/edit#heading=h.t13tvnx4loq7 https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://www.phpmyadmin.net/news/2016/11/25/phpmyadmin-401018-44159-and-465-are-released/ https://pivotal.io/security/cve-2016-9877 https://pivotal.io/security/cve-2016-9878 https://pivotal.io/security/cve-2016-9879 https://www.mozilla.org/security/announce/2016/mfsa2016-95/#CVE-2016-9893 https://www.mozilla.org/security/announce/2016/mfsa2016-95/#CVE-2016-9895 https://www.mozilla.org/security/announce/2016/mfsa2016-95/#CVE-2016-9897 https://www.mozilla.org/security/announce/2016/mfsa2016-95/#CVE-2016-9898 https://www.mozilla.org/en-US/security/advisories/mfsa2016-95/#CVE-2016-9899 https://www.mozilla.org/security/announce/2016/mfsa2016-95/#CVE-2016-9900 https://www.mozilla.org/security/announce/2016/mfsa2016-95/#CVE-2016-9901 https://www.mozilla.org/security/announce/2016/mfsa2016-95/#CVE-2016-9902 https://www.mozilla.org/security/announce/2016/mfsa2016-95/#CVE-2016-9904 https://www.mozilla.org/security/announce/2016/mfsa2016-95/#CVE-2016-9905 http://xenbits.xen.org/xsa/advisory-200.html http://downloads.asterisk.org/pub/security/AST-2016-008.html http://downloads.asterisk.org/pub/security/AST-2016-009.html https://access.redhat.com/security/vulnerabilities/cve-2016-9962 https://exim.org/static/doc/CVE-2016-9963.txt http://www.tryton.org/ca/posts/security-release-for-issue6361.html https://source.android.com/security/bulletin/2017-05-01#id-in-kernel-uvc-driver https://source.android.com/security/bulletin/2017-05-01#id-in-kernel-trace-subsystem https://blog.trendmicro.com/trendlabs-security-intelligence/vulnerability-f2fs-file-system-leads-memory-corruption-android-linux/ https://source.android.com/security/bulletin/2017-08-01#kernel-components https://www.ruby-lang.org/en/news/2017/09/14/sprintf-buffer-underrun-cve-2017-0898/ http://blog.rubygems.org/2017/08/27/2.6.13-released.html http://blog.rubygems.org/2017/08/27/2.6.13-released.html http://blog.rubygems.org/2017/08/27/2.6.13-released.html http://blog.rubygems.org/2017/08/27/2.6.13-released.html http://blog.rubygems.org/2017/10/09/2.6.14-released.html https://nextcloud.com/security/advisory/?id=nc-sa-2018-001 https://www.phpmyadmin.net/security/PMASA-2017-1/ https://www.phpmyadmin.net/security/PMASA-2017-3/ https://www.phpmyadmin.net/security/PMASA-2017-4/ https://www.phpmyadmin.net/security/PMASA-2017-5/ https://www.phpmyadmin.net/security/PMASA-2017-6/ https://www.phpmyadmin.net/security/PMASA-2017-7/ https://mail.gnome.org/archives/shotwell-list/2017-January/msg00048.html http://doc.akka.io/docs/akka/2.4/security/2017-02-10-java-serialization.html https://snyk.io/vuln/npm:qs:20170213 https://jenkins.io/security/advisory/2017-07-10/ https://jenkins.io/security/advisory/2017-07-10/ https://jenkins.io/security/advisory/2017-07-10/ https://jenkins.io/security/advisory/2017-07-10/ https://jenkins.io/security/advisory/2017-07-10/ https://groups.google.com/forum/#!msg/golang-dev/4NdLzS8sls8/uIz8QlnIBQAJ https://groups.google.com/forum/#!msg/golang-dev/4NdLzS8sls8/uIz8QlnIBQAJ https://curl.haxx.se/docs/adv_20170809C.html https://curl.haxx.se/docs/adv_20170809B.html https://curl.haxx.se/docs/adv_20170809A.html https://jenkins.io/security/advisory/2017-08-07/ https://jenkins.io/security/advisory/2017-08-07/ https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.3_.2F_4.3.1_.282017-08-10.29 https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.3_.2F_4.3.1_.282017-08-10.29 https://lkml.org/lkml/2017/8/10/757 http://blog.recurity-labs.com/2017-08-10/scm-vulns http://python-security.readthedocs.io/vuln/cve-2017-1000158_pystring_decodeescape_integer_overflow.html https://snyk.io/vuln/npm:ejs:20161130 https://snyk.io/vuln/npm:ejs:20161130-1 https://jenkins.io/security/advisory/2017-04-27/ https://jenkins.io/security/advisory/2017-06-06/ https://jenkins.io/security/advisory/2017-06-06/ https://www.armis.com/blueborne/ https://www.armis.com/blueborne/ https://access.redhat.com/security/vulnerabilities/blueborne https://access.redhat.com/solutions/3177231 https://access.redhat.com/blogs/product-security/posts/blueborne https://www.qualys.com/2017/09/26/cve-2017-1000253/cve-2017-1000253.txt https://curl.haxx.se/docs/adv_20171004.html https://curl.haxx.se/docs/adv_20171023.html https://jenkins.io/security/advisory/2017-04-26/ https://jenkins.io/security/advisory/2017-04-26/#cli-login-command-allowed-impersonating-any-jenkins-user https://jenkins.io/security/advisory/2017-04-26/#xstream-java-crash-when-trying-to-instantiate-void-void http://www.openwall.com/lists/oss-security/2017/04/03/4 https://jenkins.io/security/advisory/2017-04-26/ https://aaltodoc.aalto.fi/bitstream/handle/123456789/21584/master_Bidaj_Andi_2016.pdf?sequence=1 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://access.redhat.com/security/vulnerabilities/stackguard https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt https://access.redhat.com/security/vulnerabilities/stackguard https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt https://www.sudo.ws/alerts/linux_tty.html https://access.redhat.com/security/vulnerabilities/3059071 https://www.sudo.ws/alerts/linux_tty.html https://access.redhat.com/security/vulnerabilities/3059071 https://access.redhat.com/security/cve/CVE-2017-1000367 https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt https://c-ares.haxx.se/adv_20170620.html https://jenkins.io/security/advisory/2017-11-08/ https://jenkins.io/security/advisory/2017-11-08/ https://jenkins.io/security/advisory/2017-10-11/ https://jenkins.io/security/advisory/2017-10-11/ https://jenkins.io/security/advisory/2017-10-11/ https://jenkins.io/security/advisory/2017-10-11/ https://jenkins.io/security/advisory/2017-10-11/ https://jenkins.io/security/advisory/2017-10-11/ https://jenkins.io/security/advisory/2017-10-11/ https://jenkins.io/security/advisory/2017-10-11/ https://jenkins.io/security/advisory/2017-10-11/ https://lists.opendaylight.org/pipermail/opendaylight-announce/2018-January/000027.html https://jenkins.io/security/advisory/2017-12-11/ https://github.com/kubernetes/kubernetes/issues/60813 http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL https://puppet.com/security/cve/CVE-2017-10690 https://www.ruby-lang.org/en/news/2017/09/14/webrick-basic-auth-escape-sequence-injection-cve-2017-10784/ https://security-tracker.debian.org/tracker/CVE-2017-10794 http://xenbits.xen.org/xsa/advisory-216.html http://xenbits.xen.org/xsa/advisory-217.html http://xenbits.xen.org/xsa/advisory-218.html http://xenbits.xen.org/xsa/advisory-218.html http://xenbits.xen.org/xsa/advisory-219.html http://xenbits.xen.org/xsa/advisory-220.html http://xenbits.xen.org/xsa/advisory-221.html http://xenbits.xen.org/xsa/advisory-222.html http://xenbits.xen.org/xsa/advisory-223.html http://xenbits.xen.org/xsa/advisory-224.html http://xenbits.xen.org/xsa/advisory-224.html http://xenbits.xen.org/xsa/advisory-224.html http://xenbits.xen.org/xsa/advisory-225.html https://irssi.org/security/irssi_sa_2017_07.txt https://irssi.org/security/irssi_sa_2017_07.txt http://freeradius.org/security/fuzzer-2017.html http://freeradius.org/security/fuzzer-2017.html http://freeradius.org/security/fuzzer-2017.html http://freeradius.org/security/fuzzer-2017.html http://freeradius.org/security/fuzzer-2017.html http://freeradius.org/security/fuzzer-2017.html http://freeradius.org/security/fuzzer-2017.html http://freeradius.org/security/fuzzer-2017.html http://freeradius.org/security/fuzzer-2017.html http://freeradius.org/security/fuzzer-2017.html http://freeradius.org/security/fuzzer-2017.html https://www.orpheus-lyre.info/ https://www.strongswan.org/blog/2017/08/14/strongswan-vulnerability-(cve-2017-11185).html https://helpx.adobe.com/security/products/flash-player/apsb17-33.html https://helpx.adobe.com/security/products/flash-player/apsb17-33.html https://helpx.adobe.com/security/products/flash-player/apsb17-33.html https://helpx.adobe.com/security/products/flash-player/apsb17-28.html https://helpx.adobe.com/security/products/flash-player/apsb17-28.html https://helpx.adobe.com/security/products/flash-player/apsb17-32.html https://helpx.adobe.com/security/products/flash-player/apsb17-42.html https://www.wireshark.org/security/wnpa-sec-2017-36.html https://www.wireshark.org/security/wnpa-sec-2017-35.html https://www.wireshark.org/security/wnpa-sec-2017-34.html https://www.wireshark.org/security/wnpa-sec-2017-37.html https://www.wireshark.org/security/wnpa-sec-2017-13.html https://www.wireshark.org/security/wnpa-sec-2017-28.html http://news.dieweltistgarnichtso.net/posts/gnome-thumbnailer-msi-fail.html https://discuss.elastic.co/t/kibana-6-0-1-and-5-6-5-security-update/110571 https://nodejs.org/en/blog/vulnerability/july-2017-security-releases/ https://www.tenable.com/security/research/tra-2017-36 https://github.com/dotnet/announcements/issues/44 https://github.com/aspnet/announcements/issues/278 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0438 http://xenbits.xen.org/xsa/advisory-229.html http://xenbits.xen.org/xsa/advisory-226.html http://xenbits.xen.org/xsa/advisory-228.html http://xenbits.xen.org/xsa/advisory-227.html https://source.android.com/security/bulletin/2017-09-01 https://www.samba.org/samba/security/CVE-2017-12150.html https://www.samba.org/samba/security/CVE-2017-12151.html https://www.samba.org/samba/security/CVE-2017-12163.html https://community.openvpn.net/openvpn/wiki/CVE-2017-12166 https://www.postgresql.org/about/news/1801/ http://seclists.org/oss-sec/2017/q4/63 https://www.varnish-cache.org/security/VSV00001.html https://wiki.openstack.org/wiki/OSSN/OSSN-0080 https://www.talosintelligence.com/reports/TALOS-2017-0300 https://www.openoffice.org/security/cves/CVE-2017-12607.html https://www.libreoffice.org/about-us/security/advisories/CVE-2017-12607 https://www.talosintelligence.com/reports/TALOS-2017-0301 https://www.openoffice.org/security/cves/CVE-2017-12608.html https://www.libreoffice.org/about-us/security/advisories/CVE-2017-12608 https://lists.apache.org/thread.html/b6157be1a09df332294213bd21e90dcf9fe4c1810193be54620e4210@%3Cusers.kafka.apache.org%3E https://struts.apache.org/docs/s2-053.html http://www.apache.org/dist/apr/Announcement1.x.html https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.81 https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.81 https://tomcat.apache.org/security-7.html https://tomcat.apache.org/security-8.html http://www.apache.org/dist/apr/Announcement1.x.html http://opennlp.apache.org/news/cve-2017-12620.html http://mail-archives.apache.org/mod_mbox/hive-user/201710.mbox/%3C3791103E-80D5-4E75-AF23-6F8ED54DDEBE%40apache.org%3E https://xerces.apache.org/xerces-c/secadv/CVE-2017-12627.txt https://access.redhat.com/security/vulnerabilities/CVE-2017-12629 https://docs.saltstack.com/en/2016.11/topics/releases/2016.11.7.html https://www.djangoproject.com/weblog/2017/sep/05/security-releases/ http://xenbits.xen.org/xsa/advisory-230.html https://simplesamlphp.org/security/201708-01 https://access.redhat.com/security/vulnerabilities/kracks https://w1.fi/security/2017-1/wpa-packet-number-reuse-with-replayed-messages.txt https://www.krackattacks.com/ https://access.redhat.com/security/vulnerabilities/kracks https://w1.fi/security/2017-1/wpa-packet-number-reuse-with-replayed-messages.txt https://www.krackattacks.com/ https://w1.fi/security/2017-1/wpa-packet-number-reuse-with-replayed-messages.txt https://www.krackattacks.com/ https://access.redhat.com/security/vulnerabilities/kracks https://w1.fi/security/2017-1/wpa-packet-number-reuse-with-replayed-messages.txt https://www.krackattacks.com/ https://w1.fi/security/2017-1/wpa-packet-number-reuse-with-replayed-messages.txt https://www.krackattacks.com/ https://access.redhat.com/security/vulnerabilities/kracks https://w1.fi/security/2017-1/wpa-packet-number-reuse-with-replayed-messages.txt https://www.krackattacks.com/ https://w1.fi/security/2017-1/wpa-packet-number-reuse-with-replayed-messages.txt https://www.krackattacks.com/ https://access.redhat.com/security/vulnerabilities/kracks https://w1.fi/security/2017-1/wpa-packet-number-reuse-with-replayed-messages.txt https://www.krackattacks.com/ https://access.redhat.com/security/vulnerabilities/kracks https://w1.fi/security/2017-1/wpa-packet-number-reuse-with-replayed-messages.txt https://www.krackattacks.com/ https://access.redhat.com/security/vulnerabilities/kracks https://w1.fi/security/2017-1/wpa-packet-number-reuse-with-replayed-messages.txt https://www.krackattacks.com/ https://www.viestintavirasto.fi/en/cybersecurity/vulnerabilities/2017/haavoittuvuus-2017-037.html https://www.viestintavirasto.fi/en/cybersecurity/vulnerabilities/2017/haavoittuvuus-2017-037.html https://robotattack.org/ https://www.wireshark.org/security/wnpa-sec-2017-40.html https://www.wireshark.org/security/wnpa-sec-2017-41.html https://www.wireshark.org/security/wnpa-sec-2017-39.html https://www.wireshark.org/security/wnpa-sec-2017-38.html https://www.ruby-lang.org/en/news/2017/09/14/openssl-asn1-buffer-underrun-cve-2017-14033/ https://www.ruby-lang.org/en/news/2017/09/14/json-heap-exposure-cve-2017-14064/ https://rtpbleed.com/ http://xenbits.xen.org/xsa/advisory-231.html http://xenbits.xen.org/xsa/advisory-233.html http://xenbits.xen.org/xsa/advisory-232.html http://xenbits.xen.org/xsa/advisory-234.html http://seclists.org/oss-sec/2017/q3/436 http://xenbits.xen.org/xsa/advisory-207.html https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0510 https://www.dovecot.org/list/dovecot-news/2018-February/000370.html https://access.redhat.com/security/vulnerabilities/3199382 https://security.googleblog.com/2017/10/behind-masq-yet-more-dns-and-dhcp.html https://access.redhat.com/security/vulnerabilities/3199382 https://security.googleblog.com/2017/10/behind-masq-yet-more-dns-and-dhcp.html https://access.redhat.com/security/vulnerabilities/3199382 https://security.googleblog.com/2017/10/behind-masq-yet-more-dns-and-dhcp.html https://access.redhat.com/security/vulnerabilities/3199382 https://security.googleblog.com/2017/10/behind-masq-yet-more-dns-and-dhcp.html https://access.redhat.com/security/vulnerabilities/3199382 https://security.googleblog.com/2017/10/behind-masq-yet-more-dns-and-dhcp.html https://access.redhat.com/security/vulnerabilities/3199382 https://security.googleblog.com/2017/10/behind-masq-yet-more-dns-and-dhcp.html http://downloads.asterisk.org/pub/security/AST-2017-008.html https://www.samba.org/samba/security/CVE-2017-14746.html https://lgtm.com/blog/restlet_CVE-2017-14868 https://nodejs.org/en/blog/vulnerability/oct-2017-dos/ https://github.com/restlet/restlet-framework-java/wiki/XEE-security-enhancements#vulnerability-cve-2017-14949 http://www.sourcebrella.com/blog/double-free-vulnerability-international-components-unicode-icu/ https://mathias-kettner.de/check_mk_werks.php?werk_id=5208 https://nodesecurity.io/advisories/525 https://access.redhat.com/solutions/3442891 https://www.postgresql.org/about/news/1801/ https://www.postgresql.org/about/news/1801/ https://unbound.net/downloads/CVE-2017-15105.txt http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2018q1/011896.html http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=4fe6744a220eddd3f1749b40cac3dfc510787de6 https://moodle.org/mod/forum/discuss.php?d=361784 https://bugs.launchpad.net/tripleo/+bug/1730370 https://www.dovecot.org/list/dovecot-news/2018-February/000370.html https://www.dovecot.org/list/dovecot-news/2018-February/000370.html https://wiki.openstack.org/wiki/OSSN/OSSN-0084 https://www.wireshark.org/security/wnpa-sec-2017-46.html https://www.wireshark.org/security/wnpa-sec-2017-45.html https://www.wireshark.org/security/wnpa-sec-2017-44.html https://www.wireshark.org/security/wnpa-sec-2017-42.html https://www.wireshark.org/security/wnpa-sec-2017-43.html https://irssi.org/security/irssi_sa_2017_10.txt https://irssi.org/security/irssi_sa_2017_10.txt https://www.samba.org/samba/security/CVE-2017-15275.html https://kate.io/blog/git-bomb/ https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop_26.html https://chromereleases.googleblog.com/2017/11/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/11/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop_26.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop_14.html http://xenbits.xen.org/xsa/advisory-241.html http://xenbits.xen.org/xsa/advisory-239.html http://xenbits.xen.org/xsa/advisory-237.html http://xenbits.xen.org/xsa/advisory-238.html http://xenbits.xen.org/xsa/advisory-243.html http://xenbits.xen.org/xsa/advisory-242.html http://xenbits.xen.org/xsa/advisory-244.html http://xenbits.xen.org/xsa/advisory-240.html https://xenbits.xen.org/xsa/advisory-235.html http://xenbits.xen.org/xsa/advisory-236.html https://uima.apache.org/security_report#CVE-2017-15691 https://qpid.apache.org/cves/CVE-2017-15702.html https://mail-archives.apache.org/mod_mbox/spamassassin-announce/201809.mbox/raw/%3Cc57c0f41-742c-3c3e-249c-ae2614bf0d7d%40apache.org%3E/ http://tomcat.apache.org/security-9.html#Fixed_in_Apache_Tomcat_9.0.2 http://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.48 http://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.84 https://cwiki.apache.org/confluence/display/WW/S2-054 https://httpd.apache.org/security/vulnerabilities_24.html https://httpd.apache.org/security/vulnerabilities_24.html https://irssi.org/security/irssi_sa_2017_10.txt https://irssi.org/security/irssi_sa_2017_10.txt https://irssi.org/security/irssi_sa_2017_10.txt https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/ https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/ https://nodesecurity.io/advisories/318 https://nodesecurity.io/advisories/323 https://nodesecurity.io/advisories/531 https://nodesecurity.io/advisories/536 https://nodesecurity.io/advisories/526 https://nodesecurity.io/advisories/535 https://blog.phusion.nl/2017/10/13/passenger-security-advisory-5-1-11/ https://www.mozilla.org/en-US/security/advisories/mfsa2018-21/#CVE-2017-16541 https://www.twistlock.com/2017/11/20/cve-2017-16544-busybox-autocompletion-vulnerability/ http://research.cs.wisc.edu/htcondor/security/vulnerabilities/HTCONDOR-2017-0001.html http://xenbits.xen.org/xsa/advisory-246.html http://xenbits.xen.org/xsa/advisory-247.html http://xenbits.xen.org/xsa/advisory-245.html https://www.wireshark.org/security/wnpa-sec-2017-48.html https://www.wireshark.org/security/wnpa-sec-2017-47.html https://www.wireshark.org/security/wnpa-sec-2017-49.html https://jenkins.io/security/advisory/2017-12-05/ https://www.ruby-lang.org/en/news/2017/12/14/net-ftp-command-injection-cve-2017-17405/ https://bz.mercurial-scm.org/show_bug.cgi?id=5730 https://access.redhat.com/solutions/3442891 http://xenbits.xen.org/xsa/advisory-249.html http://xenbits.xen.org/xsa/advisory-250.html http://xenbits.xen.org/xsa/advisory-251.html http://xenbits.xen.org/xsa/advisory-248.html https://efail.de/ https://efail.de/ https://www.ruby-lang.org/en/news/2018/03/28/http-response-splitting-in-webrick-cve-2017-17742/ https://dumpco.re/blog/openslp-2.0.0-double-free https://simplesamlphp.org/security/201709-01 https://simplesamlphp.org/security/201710-01 https://github.com/qpdf/qpdf/issues/143 https://github.com/qpdf/qpdf/issues/147 https://github.com/qpdf/qpdf/issues/150 https://github.com/qpdf/qpdf/issues/149 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881121 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887640 https://www.kernel.org/doc/Documentation/filesystems/dax.txt https://lwn.net/Articles/618064/ https://security.cucumberlinux.com/security/details.php?id=346 https://www.phpmyadmin.net/security/PMASA-2017-8/ https://puppet.com/security/cve/cve-2017-2292 https://puppet.com/security/cve/cve-2017-2295 https://puppet.com/security/cve/CVE-2017-2299 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2017-02-01 https://www.samba.org/samba/security/CVE-2017-2619.html https://xenbits.xen.org/xsa/advisory-209.html https://www.x41-dsec.de/lab/advisories/x41-2017-001-xorg/ https://curl.haxx.se/docs/adv_20170222.html https://access.redhat.com/security/vulnerabilities/CVE-2017-2636 https://a13xp0p0v.github.io/2017/03/24/CVE-2017-2636.html https://access.redhat.com/solutions/3022771 https://wiki.openstack.org/wiki/OSSN/OSSN-0007 https://jenkins.io/security/advisory/2017-03-20/ https://jenkins.io/security/advisory/2017-03-20/ http://www.talosintelligence.com/reports/TALOS-2017-0274/ https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0303 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0304 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0307 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0311 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0319 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0321 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0336 http://blog.talosintelligence.com/2017/07/vulnerbility-spotlight-freerdp-multiple.html https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0337 http://blog.talosintelligence.com/2017/07/vulnerbility-spotlight-freerdp-multiple.html http://blog.talosintelligence.com/2017/07/vulnerbility-spotlight-freerdp-multiple.html https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0338 http://blog.talosintelligence.com/2017/07/vulnerbility-spotlight-freerdp-multiple.html https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0339 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0340 http://blog.talosintelligence.com/2017/07/vulnerbility-spotlight-freerdp-multiple.html https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0341 http://blog.talosintelligence.com/2017/07/vulnerbility-spotlight-freerdp-multiple.html https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0366 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0392 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0395 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0427 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0430 https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0431 https://helpx.adobe.com/security/products/flash-player/apsb17-02.html https://helpx.adobe.com/security/products/flash-player/apsb17-02.html https://helpx.adobe.com/security/products/flash-player/apsb17-02.html https://helpx.adobe.com/security/products/flash-player/apsb17-02.html https://helpx.adobe.com/security/products/flash-player/apsb17-02.html https://helpx.adobe.com/security/products/flash-player/apsb17-02.html https://helpx.adobe.com/security/products/flash-player/apsb17-02.html https://helpx.adobe.com/security/products/flash-player/apsb17-02.html https://helpx.adobe.com/security/products/flash-player/apsb17-02.html https://helpx.adobe.com/security/products/flash-player/apsb17-02.html https://helpx.adobe.com/security/products/flash-player/apsb17-02.html https://helpx.adobe.com/security/products/flash-player/apsb17-02.html https://helpx.adobe.com/security/products/flash-player/apsb17-02.html https://helpx.adobe.com/security/products/flash-player/apsb17-04.html https://helpx.adobe.com/security/products/flash-player/apsb17-04.html https://helpx.adobe.com/security/products/flash-player/apsb17-04.html https://helpx.adobe.com/security/products/flash-player/apsb17-04.html https://helpx.adobe.com/security/products/flash-player/apsb17-04.html https://helpx.adobe.com/security/products/flash-player/apsb17-04.html https://helpx.adobe.com/security/products/flash-player/apsb17-04.html https://helpx.adobe.com/security/products/flash-player/apsb17-04.html https://helpx.adobe.com/security/products/flash-player/apsb17-04.html https://helpx.adobe.com/security/products/flash-player/apsb17-04.html https://helpx.adobe.com/security/products/flash-player/apsb17-07.html https://helpx.adobe.com/security/products/flash-player/apsb17-04.html https://helpx.adobe.com/security/products/flash-player/apsb17-04.html https://helpx.adobe.com/security/products/flash-player/apsb17-07.html https://helpx.adobe.com/security/products/flash-player/apsb17-07.html https://helpx.adobe.com/security/products/flash-player/apsb17-07.html https://helpx.adobe.com/security/products/flash-player/apsb17-07.html https://helpx.adobe.com/security/products/flash-player/apsb17-07.html https://helpx.adobe.com/security/products/flash-player/apsb17-07.html https://helpx.adobe.com/security/products/flash-player/apsb17-07.html https://helpx.adobe.com/security/products/flash-player/apsb17-10.html https://helpx.adobe.com/security/products/flash-player/apsb17-10.html https://helpx.adobe.com/security/products/flash-player/apsb17-10.html https://helpx.adobe.com/security/products/flash-player/apsb17-10.html https://helpx.adobe.com/security/products/flash-player/apsb17-10.html https://helpx.adobe.com/security/products/flash-player/apsb17-10.html https://helpx.adobe.com/security/products/flash-player/apsb17-10.html https://helpx.adobe.com/security/products/flash-player/apsb17-15.html https://helpx.adobe.com/security/products/flash-player/apsb17-15.html https://helpx.adobe.com/security/products/flash-player/apsb17-15.html https://helpx.adobe.com/security/products/flash-player/apsb17-15.html https://helpx.adobe.com/security/products/flash-player/apsb17-15.html https://helpx.adobe.com/security/products/flash-player/apsb17-15.html https://helpx.adobe.com/security/products/flash-player/apsb17-15.html https://helpx.adobe.com/security/products/flash-player/apsb17-17.html https://helpx.adobe.com/security/products/flash-player/apsb17-17.html https://helpx.adobe.com/security/products/flash-player/apsb17-17.html https://helpx.adobe.com/security/products/flash-player/apsb17-17.html https://helpx.adobe.com/security/products/flash-player/apsb17-17.html https://helpx.adobe.com/security/products/flash-player/apsb17-21.html https://helpx.adobe.com/security/products/flash-player/apsb17-17.html https://helpx.adobe.com/security/products/flash-player/apsb17-17.html https://helpx.adobe.com/security/products/flash-player/apsb17-17.html https://helpx.adobe.com/security/products/flash-player/apsb17-17.html https://helpx.adobe.com/security/products/flash-player/apsb17-23.html https://helpx.adobe.com/security/products/flash-player/apsb17-21.html https://helpx.adobe.com/security/products/flash-player/apsb17-21.html https://helpx.adobe.com/security/products/flash-player/apsb17-23.html https://helpx.adobe.com/security/products/flash-player/apsb17-33.html https://helpx.adobe.com/security/products/flash-player/apsb17-33.html https://kb.isc.org/article/AA-01453 https://kb.isc.org/article/AA-01465 https://kb.isc.org/article/AA-01466 https://kb.isc.org/article/AA-01471 https://kb.isc.org/article/AA-01504 https://kb.isc.org/article/AA-01503 https://kb.isc.org/article/AA-01541 https://kb.isc.org/article/AA-01542 https://cxf.apache.org/security-advisories.data/CVE-2017-3156.txt.asc http://www.libreoffice.org/about-us/security/advisories/cve-2017-3157/ http://camel.apache.org/security-advisories.data/CVE-2017-3159.txt.asc https://httpd.apache.org/security/vulnerabilities_24.html https://httpd.apache.org/security/vulnerabilities_22.html https://httpd.apache.org/security/vulnerabilities_24.html https://httpd.apache.org/security/vulnerabilities_22.html https://www.kb.cert.org/vuls/id/793496 http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL http://riddle.link/ http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixJAVA https://www.computest.nl/advisories/CT-2017-0425_MySQL-Connector-J.txt http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMySQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMySQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMySQL http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL https://www.secforce.com/blog/2017/04/cve-2017-3599-pre-auth-mysql-remote-dos/ https://blog.tarq.io/cve-2016-5483-backdooring-mysqldump-backups/ https://blog.tarq.io/cve-2016-5483-galera-remote-command-execution-via-crafted-database-name/ http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html#AppendixMSQL https://www.openssl.org/news/secadv/20170126.txt https://www.openssl.org/news/secadv/20170126.txt https://www.openssl.org/news/secadv/20170126.txt https://www.openssl.org/news/secadv/20170216.txt https://www.openssl.org/news/secadv/20170828.txt https://www.openssl.org/news/secadv/20171102.txt https://www.openssl.org/news/secadv/20171207.txt https://www.openssl.org/news/secadv/20171207.txt https://github.com/rabbitmq/rabbitmq-server/releases/tag/rabbitmq_v3_6_9 https://github.com/rabbitmq/rabbitmq-server/releases/tag/rabbitmq_v3_6_9 https://github.com/rabbitmq/rabbitmq-server/releases/tag/rabbitmq_v3_6_9 https://pivotal.io/security/cve-2017-4971 https://pivotal.io/security/cve-2017-4995 https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop_29.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop_29.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop_29.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop_29.html https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop_29.html https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/05/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop_15.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop_15.html https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop_15.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/09/stable-channel-update-for-desktop_21.html https://chromereleases.googleblog.com/2017/09/stable-channel-update-for-desktop_21.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html https://irssi.org/security/irssi_sa_2017_01.txt https://irssi.org/security/irssi_sa_2017_01.txt https://irssi.org/security/irssi_sa_2017_01.txt https://irssi.org/security/irssi_sa_2017_01.txt https://gnutls.org/security.html#GNUTLS-SA-2017-1 https://www.mozilla.org/security/announce/2017/mfsa2016-01/#CVE-2017-5373 https://www.mozilla.org/en-US/security/advisories/mfsa2017-02/#CVE-2017-5375 https://www.mozilla.org/en-US/security/advisories/mfsa2017-02/#CVE-2017-5376 https://www.mozilla.org/en-US/security/advisories/mfsa2017-02/#CVE-2017-5378 https://www.mozilla.org/en-US/security/advisories/mfsa2017-02/#CVE-2017-5380 https://www.mozilla.org/en-US/security/advisories/mfsa2017-02/#CVE-2017-5383 https://www.mozilla.org/en-US/security/advisories/mfsa2017-02/#CVE-2017-5386 https://www.mozilla.org/en-US/security/advisories/mfsa2017-02/#CVE-2017-5390 https://www.mozilla.org/en-US/security/advisories/mfsa2017-02/#CVE-2017-5396 https://www.mozilla.org/en-US/security/advisories/mfsa2017-06/#CVE-2017-5398 https://www.mozilla.org/en-US/security/advisories/mfsa2017-06/#CVE-2017-5400 https://www.mozilla.org/en-US/security/advisories/mfsa2017-06/#CVE-2017-5401 https://www.mozilla.org/en-US/security/advisories/mfsa2017-06/#CVE-2017-5402 https://www.mozilla.org/en-US/security/advisories/mfsa2017-06/#CVE-2017-5404 https://www.mozilla.org/en-US/security/advisories/mfsa2017-06/#CVE-2017-5405 https://www.mozilla.org/en-US/security/advisories/mfsa2017-06/#CVE-2017-5407 https://www.mozilla.org/en-US/security/advisories/mfsa2017-06/#CVE-2017-5408 https://www.mozilla.org/en-US/security/advisories/mfsa2017-06/#CVE-2017-5410 https://www.mozilla.org/en-US/security/advisories/mfsa2017-08/#CVE-2017-5428 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5429 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5430 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5432 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5433 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5434 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5435 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5436 https://www.mozilla.org/en-US/security/advisories/mfsa2017-12/#CVE-2016-10196 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5438 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5439 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5440 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5441 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5442 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5443 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5444 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5445 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5446 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5447 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5448 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5449 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5451 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5453 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5454 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5455 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5456 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5458 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5459 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5460 https://www.mozilla.org/en-US/security/advisories/mfsa2017-10/#CVE-2017-5461 https://www.mozilla.org/en-US/security/advisories/mfsa2017-10/#CVE-2017-5462 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5464 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5465 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5466 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5467 https://www.mozilla.org/en-US/security/advisories/mfsa2017-10/#CVE-2017-5468 https://www.mozilla.org/en-US/security/advisories/mfsa2017-11/#CVE-2017-5469 https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-5470 https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-5472 https://lists.quagga.net/pipermail/quagga-dev/2017-January/016586.html https://plone.org/security/hotfix/20170117/sandbox-escape https://www.tibco.com/support/advisories/2017/06/tibco-security-advisory-june-28-2017-tibco-jasperreports-server-2017 https://www.tibco.com/support/advisories/2017/06/tibco-security-advisory-june-28-2017-tibco-jasperreports-server-2017-0 https://www.tibco.com/support/advisories/2017/11/tibco-security-advisory-november-15-2017-tibco-jasperreports-2017-5532 https://www.tibco.com/support/advisories/2017/11/tibco-security-advisory-november-15-2017-tibco-jasperreports-server-2017 https://www.wireshark.org/security/wnpa-sec-2017-01.html https://www.wireshark.org/security/wnpa-sec-2017-02.html https://wordpress.org/news/2017/01/wordpress-4-7-2-security-release/ https://wordpress.org/news/2017/01/wordpress-4-7-2-security-release/ https://wordpress.org/news/2017/01/wordpress-4-7-2-security-release/ https://cwiki.apache.org/confluence/display/WW/S2-045 https://camel.apache.org/security-advisories.data/CVE-2017-5643.txt http://cxf.apache.org/security-advisories.data/CVE-2017-5653.txt.asc https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.5.1 https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.5.1 http://cxf.apache.org/security-advisories.data/CVE-2017-5656.txt.asc https://lists.apache.org/thread.html/22d84783d94c53a5132ec89f002fe5165c87561a9428bcb6713b3c98@%3Cdev.trafficserver.apache.org%3E https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.78 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.44 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.15 https://access.redhat.com/security/vulnerabilities/speculativeexecution https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html https://spectreattack.com/ https://meltdownattack.com https://01.org/security/advisories/intel-oss-10001 https://edk2-docs.gitbooks.io/security-advisory/content/edk-ii-tianocompress-bounds-checking-issues.html https://edk2-docs.gitbooks.io/security-advisory/content/edk-ii-tianocompress-bounds-checking-issues.html https://edk2-docs.gitbooks.io/security-advisory/content/edk-ii-tianocompress-bounds-checking-issues.html https://edk2-docs.gitbooks.io/security-advisory/content/edk-ii-tianocompress-bounds-checking-issues.html https://edk2-docs.gitbooks.io/security-advisory/content/edk-ii-tianocompress-bounds-checking-issues.html https://access.redhat.com/security/vulnerabilities/speculativeexecution https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html https://spectreattack.com/ https://meltdownattack.com https://access.redhat.com/security/vulnerabilities/speculativeexecution https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html https://spectreattack.com/ https://meltdownattack.com https://github.com/jheyens/bash_completion_vuln/blob/master/2017-01-17.bash_completion_report.pdf https://forum.bestpractical.com/t/security-vulnerabilities-in-rt-2017-06-15/32016 http://blogs.gentoo.org/ago/2017/02/09/zziplib-heap-based-buffer-overflow-in-__zzip_get32-fetch-c/ http://blogs.gentoo.org/ago/2017/02/09/zziplib-heap-based-buffer-overflow-in-__zzip_get64-fetch-c/ http://blogs.gentoo.org/ago/2017/02/09/zziplib-heap-based-buffer-overflow-in-zzip_mem_entry_extra_block-memdisk-c/ http://blogs.gentoo.org/ago/2017/02/09/zziplib-invalid-memory-read-in-zzip_mem_entry_extra_block-memdisk-c/ http://blogs.gentoo.org/ago/2017/02/09/zziplib-out-of-bounds-read-in-zzip_mem_entry_new-memdisk-c/ http://blogs.gentoo.org/ago/2017/02/09/zziplib-null-pointer-dereference-in-prescan_entry-fseeko-c/ http://blogs.gentoo.org/ago/2017/02/09/zziplib-null-pointer-dereference-in-zzip_mem_entry_new-memdisk-c/ http://blogs.gentoo.org/ago/2017/02/09/zziplib-assertion-failure-in-seeko-c/ http://tomcat.apache.org/security-7.html https://access.redhat.com/articles/2991951 https://access.redhat.com/node/2934281 https://www.x41-dsec.de/lab/advisories/x41-2017-004-tnef/ https://www.x41-dsec.de/lab/advisories/x41-2017-004-tnef/ https://www.x41-dsec.de/lab/advisories/x41-2017-004-tnef/ https://www.x41-dsec.de/lab/advisories/x41-2017-004-tnef/ https://www.kde.org/info/security/advisory-20170228-1.txt https://github.com/pingidentity/mod_auth_openidc/releases/tag/v2.1.6 https://www.wireshark.org/security/wnpa-sec-2017-11.html https://www.wireshark.org/security/wnpa-sec-2017-08.html https://www.wireshark.org/security/wnpa-sec-2017-03.html https://www.wireshark.org/security/wnpa-sec-2017-10.html https://www.wireshark.org/security/wnpa-sec-2017-05.html https://www.wireshark.org/security/wnpa-sec-2017-04.html https://www.wireshark.org/security/wnpa-sec-2017-09.html https://www.wireshark.org/security/wnpa-sec-2017-07.html https://www.kb.cert.org/vuls/id/550620 https://secuniaresearch.flexerasoftware.com/secunia_research/2017-7/ https://www.drupal.org/SA-CORE-2017-002 https://www.drupal.org/SA-CORE-2017-003 https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html https://wiki.openstack.org/wiki/OSSN/OSSN-0078 https://bugs.launchpad.net/ossn/+bug/1606495 https://bugs.launchpad.net/ossn/+bug/1153614 https://www.foxmole.com/advisories/foxmole-2016-07-05.txt http://xenbits.xen.org/xsa/advisory-212.html https://blogs.gentoo.org/ago/2017/03/20/libpcre-invalid-memory-read-in-_pcre32_xclass-pcre_xclass-c/ https://blogs.gentoo.org/ago/2017/03/20/libpcre-two-stack-based-buffer-overflow-write-in-pcre32_copy_substring-pcre_get-c/ https://blogs.gentoo.org/ago/2017/03/20/libpcre-two-stack-based-buffer-overflow-write-in-pcre32_copy_substring-pcre_get-c/ https://blogs.gentoo.org/ago/2017/03/27/imagemagick-memory-allocation-failure-in-acquiremagickmemory-memory-c-incomplete-fix-for-cve-2016-8862-and-cve-2016-8866/ https://packetstormsecurity.com/files/141930/Linux-3.16.0-28-Integer-Overflow.html https://googleprojectzero.blogspot.com/2017/05/exploiting-linux-kernel-via-packet.html https://packetstormsecurity.com/files/142008/Linux-Kernel-Ubuntu-14.04-LTS-SIGIO-Signal.html https://curl.haxx.se/docs/adv_20170403.html https://curl.haxx.se/docs/adv_20170419.html https://community.openvpn.net/openvpn/wiki/QuarkslabAndCryptographyEngineerAudits https://community.openvpn.net/openvpn/wiki/QuarkslabAndCryptographyEngineerAudits https://www.postgresql.org/about/news/1746/ https://www.postgresql.org/about/news/1746/ https://www.postgresql.org/about/news/1746/ https://www.samba.org/samba/security/CVE-2017-7494.html https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=06bd3c36a733ac27962fea7d6f47168841376824 http://seclists.org/oss-sec/2017/q2/259 https://www.gnutls.org/security.html#GNUTLS-SA-2017-4 https://community.openvpn.net/openvpn/wiki/VulnerabilitiesFixedInOpenVPN243 https://guidovranken.wordpress.com/2017/06/21/the-openvpn-post-audit-bug-bonanza/ http://lists.gnu.org/archive/html/bug-cpio/2017-06/msg00001.html https://community.openvpn.net/openvpn/wiki/VulnerabilitiesFixedInOpenVPN243 https://guidovranken.wordpress.com/2017/06/21/the-openvpn-post-audit-bug-bonanza/ https://community.openvpn.net/openvpn/wiki/VulnerabilitiesFixedInOpenVPN243 https://guidovranken.wordpress.com/2017/06/21/the-openvpn-post-audit-bug-bonanza/ https://community.openvpn.net/openvpn/wiki/VulnerabilitiesFixedInOpenVPN243 https://guidovranken.wordpress.com/2017/06/21/the-openvpn-post-audit-bug-bonanza/ https://lists.gnupg.org/pipermail/gnupg-announce/2017q2/000408.html https://eprint.iacr.org/2017/627 http://mailman.nginx.org/pipermail/nginx-announce/2017/000200.html https://www.postgresql.org/about/news/1772/ https://www.postgresql.org/about/news/1772/ https://www.postgresql.org/about/news/1772/ http://downloads.asterisk.org/pub/security/AST-2017-001.html http://mosquitto.org/2017/05/security-advisory-cve-2017-7650/ https://httpd.apache.org/security/vulnerabilities_24.html https://httpd.apache.org/security/vulnerabilities_24.html https://httpd.apache.org/security/vulnerabilities_22.html https://lists.apache.org/thread.html/203bdcf9bbb718f3dc6f7aaf3e2af632474d51fa9e7bfb7832729905@%3Cdev.trafficserver.apache.org%3E https://tomcat.apache.org/security-7.html https://tomcat.apache.org/security-8.html https://tomcat.apache.org/security-8.html https://httpd.apache.org/security/vulnerabilities_24.html https://httpd.apache.org/security/vulnerabilities_22.html http://www.squirrelmail.org/security/issue/2017-04-24 https://www.wireshark.org/security/wnpa-sec-2017-14.html https://www.wireshark.org/security/wnpa-sec-2017-16.html https://www.wireshark.org/security/wnpa-sec-2017-13.html https://www.wireshark.org/security/wnpa-sec-2017-12.html https://www.wireshark.org/security/wnpa-sec-2017-17.html https://www.wireshark.org/security/wnpa-sec-2017-15.html https://www.wireshark.org/security/wnpa-sec-2017-20.html https://www.wireshark.org/security/wnpa-sec-2017-19.html https://www.wireshark.org/security/wnpa-sec-2017-18.html https://www.wireshark.org/security/wnpa-sec-2017-21.html https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7749 https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7750 https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7751 https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7752 https://www.mozilla.org/en-US/security/advisories/mfsa2017-19/#CVE-2017-7753 https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7754 https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7756 https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7757 https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7758 https://www.mozilla.org/en-US/security/advisories/mfsa2017-15/ https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7764 https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7778 https://sourceforge.net/p/silgraphite/mailman/message/35824024/ https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7778 https://sourceforge.net/p/silgraphite/mailman/message/35824024/ https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7778 https://sourceforge.net/p/silgraphite/mailman/message/35824024/ https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7778 https://sourceforge.net/p/silgraphite/mailman/message/35824024/ https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7778 https://sourceforge.net/p/silgraphite/mailman/message/35824024/ https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7778 https://sourceforge.net/p/silgraphite/mailman/message/35824024/ https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7778 https://sourceforge.net/p/silgraphite/mailman/message/35824024/ https://www.mozilla.org/en-US/security/advisories/mfsa2017-16/#CVE-2017-7778 https://www.mozilla.org/en-US/security/advisories/mfsa2017-19/#CVE-2017-7779 https://www.mozilla.org/en-US/security/advisories/mfsa2017-18/#CVE-2017-7780 https://www.mozilla.org/en-US/security/advisories/mfsa2017-18/#CVE-2017-7781 https://www.mozilla.org/en-US/security/advisories/mfsa2017-18/#CVE-2017-7783 https://www.mozilla.org/en-US/security/advisories/mfsa2017-19/#CVE-2017-7784 https://www.mozilla.org/en-US/security/advisories/mfsa2017-19/#CVE-2017-7785 https://www.mozilla.org/en-US/security/advisories/mfsa2017-19/#CVE-2017-7786 https://www.mozilla.org/en-US/security/advisories/mfsa2017-19/#CVE-2017-7787 https://www.mozilla.org/en-US/security/advisories/mfsa2017-18/#CVE-2017-7788 https://www.mozilla.org/en-US/security/advisories/mfsa2017-18/#CVE-2017-7789 https://www.mozilla.org/en-US/security/advisories/mfsa2017-19/#CVE-2017-7791 https://www.mozilla.org/en-US/security/advisories/mfsa2017-19/#CVE-2017-7792 https://www.mozilla.org/en-US/security/advisories/mfsa2017-22/#CVE-2017-7793 https://www.mozilla.org/en-US/security/advisories/mfsa2017-18/#CVE-2017-7794 https://www.mozilla.org/en-US/security/advisories/mfsa2017-18/#CVE-2017-7797 https://www.mozilla.org/en-US/security/advisories/mfsa2017-19/#CVE-2017-7798 https://www.mozilla.org/en-US/security/advisories/mfsa2017-18/#CVE-2017-7799 https://www.mozilla.org/en-US/security/advisories/mfsa2017-19/#CVE-2017-7800 https://www.mozilla.org/en-US/security/advisories/mfsa2017-19/#CVE-2017-7801 https://www.mozilla.org/en-US/security/advisories/mfsa2017-19/#CVE-2017-7802 https://www.mozilla.org/en-US/security/advisories/mfsa2017-19/#CVE-2017-7803 https://www.mozilla.org/en-US/security/advisories/mfsa2017-18/#CVE-2017-7806 https://www.mozilla.org/en-US/security/advisories/mfsa2017-19/#CVE-2017-7807 https://www.mozilla.org/en-US/security/advisories/mfsa2017-18/#CVE-2017-7808 https://www.mozilla.org/en-US/security/advisories/mfsa2017-19/#CVE-2017-7809 https://www.mozilla.org/en-US/security/advisories/mfsa2017-22/#CVE-2017-7810 https://www.mozilla.org/en-US/security/advisories/mfsa2017-22/#CVE-2017-7814 https://www.mozilla.org/en-US/security/advisories/mfsa2017-22/#CVE-2017-7818 https://www.mozilla.org/en-US/security/advisories/mfsa2017-22/#CVE-2017-7819 https://www.mozilla.org/en-US/security/advisories/mfsa2017-22/#CVE-2017-7823 https://www.mozilla.org/en-US/security/advisories/mfsa2017-22/#CVE-2017-7824 https://www.mozilla.org/en-US/security/advisories/mfsa2017-22/#CVE-2017-7825 https://www.mozilla.org/en-US/security/advisories/mfsa2017-25/#CVE-2017-7826 https://www.mozilla.org/en-US/security/advisories/mfsa2017-25/#CVE-2017-7828 https://www.mozilla.org/en-US/security/advisories/mfsa2017-30/#CVE-2017-7829 https://www.mozilla.org/en-US/security/advisories/mfsa2017-25/#CVE-2017-7830 https://www.mozilla.org/en-US/security/advisories/mfsa2017-27/#CVE-2017-7843 https://www.mozilla.org/en-US/security/advisories/mfsa2017-30/#CVE-2017-7829 https://www.mozilla.org/en-US/security/advisories/mfsa2017-30/#CVE-2017-7847 https://www.mozilla.org/en-US/security/advisories/mfsa2017-30/#CVE-2017-7848 https://www.gnutls.org/security.html#GNUTLS-SA-2017-3 https://github.com/sandstorm-io/capnproto/blob/master/security-advisories/2017-04-17-0-apple-clang-elides-bounds-check.md http://x-stream.github.io/CVE-2017-7957.html https://pivotal.io/security/cve-2017-8039 https://weechat.org/download/security/ https://cisofy.com/security/cve/cve-2017-8108/ https://roundcube.net/news/2017/04/28/security-updates-1.2.5-1.1.9-and-1.0.11 https://source.android.com/security/bulletin/2017-09-01 https://www.kde.org/info/security/advisory-20170510-1.txt http://seclists.org/oss-sec/2017/q2/240 https://github.com/dotnet/announcements/issues/34 https://www.sidertia.com/Home/Community/Blog/2017/07/14/Microsoft-fixes-the-CVE-2017-8585-security-vulnerability-discovered-by-Sidertia-Team https://github.com/aspnet/Announcements/issues/279 https://access.redhat.com/solutions/3025811/ https://varnish-cache.org/security/VSV00002.html https://curl.haxx.se/docs/adv_2017-12e7.html https://curl.haxx.se/docs/adv_2017-ae72.html https://curl.haxx.se/docs/adv_2017-af0a.html https://blog.torproject.org/new-stable-tor-releases-security-fixes-0319-03013-02914-02817-02516 https://blog.torproject.org/new-stable-tor-releases-security-fixes-0319-03013-02914-02817-02516 https://blog.torproject.org/new-stable-tor-releases-security-fixes-0319-03013-02914-02817-02516 https://blog.torproject.org/new-stable-tor-releases-security-fixes-0319-03013-02914-02817-02516 https://blog.torproject.org/new-stable-tor-releases-security-fixes-0319-03013-02914-02817-02516 https://www.kde.org/info/security/advisory-20170510-2.txt http://xenbits.xen.org/xsa/advisory-213.html http://xenbits.xen.org/xsa/advisory-214.html http://xenbits.xen.org/xsa/advisory-215.html http://seclists.org/oss-sec/2017/q2/260 http://seclists.org/oss-sec/2017/q2/261 https://www.strongswan.org/blog/2017/05/30/strongswan-vulnerability-(cve-2017-9022).html https://www.strongswan.org/blog/2017/05/30/strongswan-vulnerability-(cve-2017-9023).html http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/2017q2/001985.html http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/2017q2/001985.html https://www.compass-security.com/fileadmin/Datein/Research/Advisories/CSNC-2017-017_itext_xml_external_entity_attack.txt https://scarybeastsecurity.blogspot.com/2017/05/bleed-continues-18-byte-file-14k-bounty.html https://packetstormsecurity.com/files/142630/GS20170523000807.txt https://libexpat.github.io/doc/cve-2017-9233/ http://www.openldap.org/its/?findid=8655 https://www.wireshark.org/security/wnpa-sec-2017-30.html https://www.wireshark.org/security/wnpa-sec-2017-29.html https://www.wireshark.org/security/wnpa-sec-2017-26.html https://www.wireshark.org/security/wnpa-sec-2017-25.html https://www.wireshark.org/security/wnpa-sec-2017-31.html https://www.wireshark.org/security/wnpa-sec-2017-23.html https://www.wireshark.org/security/wnpa-sec-2017-27.html https://www.wireshark.org/security/wnpa-sec-2017-28.html https://www.wireshark.org/security/wnpa-sec-2017-24.html https://www.wireshark.org/security/wnpa-sec-2017-22.html https://www.wireshark.org/security/wnpa-sec-2017-33.html https://www.wireshark.org/security/wnpa-sec-2017-32.html https://irssi.org/security/irssi_sa_2017_06.txt https://irssi.org/security/irssi_sa_2017_06.txt https://curl.haxx.se/docs/adv_20170614.html https://www.kde.org/info/security/advisory-20170615-1.txt https://source.android.com/security/bulletin/2017-09-01 https://sympa.inria.fr/sympa/arc/caml-list/2017-06/msg00094.html https://httpd.apache.org/security/vulnerabilities_22.html#2.2.34 https://httpd.apache.org/security/vulnerabilities_24.html#2.4.27 https://httpd.apache.org/security/vulnerabilities_24.html#2.4.27 http://struts.apache.org/docs/s2-048.html https://struts.apache.org/docs/s2-051.html https://blog.fuzzing-project.org/60-Optionsbleed-HTTP-OPTIONS-method-can-leak-Apaches-server-memory.html https://subversion.apache.org/security/CVE-2017-9800-advisory.txt https://struts.apache.org/docs/s2-050.html https://struts.apache.org/docs/s2-052.html https://www.talosintelligence.com/reports/TALOS-2017-0295 https://www.openoffice.org/security/cves/CVE-2017-9806.html https://www.libreoffice.org/about-us/security/advisories/CVE-2017-9806 http://somevulnsofadlab.blogspot.com.br/2017/06/libtiffmemory-leak-in-tiffmalloc.html https://www.eyrie.org/~eagle/software/remctl/security/2018-04-01.html https://www.nccgroup.trust/us/our-research/technical-advisory-return-of-the-hidden-number-problem/ https://curl.haxx.se/docs/adv_2018-70a2.html https://www.openssl.org/news/secadv/20180612.txt https://www.openssl.org/news/secadv/20180327.txt https://www.openssl.org/news/secadv/20180416.txt http://www.openwall.com/lists/oss-security/2018/04/16/3 https://www.openssl.org/news/secadv/20180327.txt https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0765 https://github.com/dotnet/announcements/issues/67 https://www.knot-resolver.cz/2018-01-22-knot-resolver-1.5.2.html https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2018-01.html https://curl.haxx.se/docs/adv_2018-824a.html https://curl.haxx.se/docs/adv_2018-b3bf.html https://jenkins.io/security/advisory/2018-01-22/ https://jenkins.io/security/advisory/2018-01-22/ https://gerrit.ovirt.org/#/c/86635/ https://gerrit.ovirt.org/#/c/62679/ http://www.batterystapl.es/2018/01/security-implications-of-ansi-escape.html https://www.sec-consult.com/en/blog/advisories/multiple-vulnerabilities-in-infozip-unzip/index.html https://www.sec-consult.com/en/blog/advisories/multiple-vulnerabilities-in-infozip-unzip/index.html https://www.sec-consult.com/en/blog/advisories/multiple-vulnerabilities-in-infozip-unzip/index.html https://www.sec-consult.com/en/blog/advisories/multiple-vulnerabilities-in-infozip-unzip/index.html https://www.sec-consult.com/en/blog/advisories/multiple-vulnerabilities-in-infozip-unzip/index.html https://sensuapp.org/docs/1.2/overview/changelog.html#core-v1-2-1-changes https://www.ruby-lang.org/en/news/2018/02/17/multiple-vulnerabilities-in-rubygems/ https://www.ruby-lang.org/en/news/2018/02/17/multiple-vulnerabilities-in-rubygems/ https://www.ruby-lang.org/en/news/2018/02/17/multiple-vulnerabilities-in-rubygems/ https://www.ruby-lang.org/en/news/2018/02/17/multiple-vulnerabilities-in-rubygems/ https://www.ruby-lang.org/en/news/2018/02/17/multiple-vulnerabilities-in-rubygems/ https://www.ruby-lang.org/en/news/2018/02/17/multiple-vulnerabilities-in-rubygems/ https://www.ruby-lang.org/en/news/2018/02/17/multiple-vulnerabilities-in-rubygems/ https://gerrit.ovirt.org/#/c/87265 https://jenkins.io/security/advisory/2018-02-26/ https://jenkins.io/security/advisory/2018-02-26/ https://jenkins.io/security/advisory/2018-02-26/ https://jenkins.io/security/advisory/2018-02-26/ https://sourceforge.net/p/net-snmp/bugs/2821/ https://curl.haxx.se/docs/adv_2018-9cd6.html https://curl.haxx.se/docs/adv_2018-97a2.html https://curl.haxx.se/docs/adv_2018-b047.html https://jolokia.org/#Security_fixes_with_1.5.0 https://jolokia.org/#Security_fixes_with_1.5.0 https://nawilson.com/2018/03/19/cve-2018-1000134-and-the-unboundid-ldap-sdk-for-java/ https://www.rsyslog.com/cve-2018-1000140/ http://seclists.org/oss-sec/2018/q2/99 https://epadillas.github.io/2018/04/02/http-header-splitting-in-gunicorn-19.4.5 https://jenkins.io/security/advisory/2018-04-11/ https://jenkins.io/security/advisory/2018-04-11/ https://jenkins.io/security/advisory/2018-06-04/ https://jenkins.io/security/advisory/2018-06-04/ https://jenkins.io/security/advisory/2018-06-04/ https://jenkins.io/security/advisory/2018-06-04/ https://jenkins.io/security/advisory/2018-06-04/ https://jenkins.io/security/advisory/2018-05-09/ https://jenkins.io/security/advisory/2018-05-09/ https://jenkins.io/security/advisory/2018-05-09/ https://jenkins.io/security/advisory/2018-05-09/ https://curl.haxx.se/docs/adv_2018-82c2.html https://curl.haxx.se/docs/adv_2018-b138.html https://jenkins.io/security/advisory/2018-06-25/ https://jenkins.io/security/advisory/2018-06-25/ https://groups.google.com/forum/#!topic/rustlang-security-announcements/4ybxYLTtXuM https://snyk.io/research/zip-slip-vulnerability https://www.libreoffice.org/about-us/security/advisories/cve-2018-10119/ https://www.libreoffice.org/about-us/security/advisories/cve-2018-10120/ https://github.com/google/guava/wiki/CVE-2018-10237 https://groups.google.com/forum/#!topic/guava-announce/xqWALw4W1vs/discussion https://www.kde.org/info/security/advisory-20180503-1.txt https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-1039 https://xenbits.xen.org/xsa/advisory-259.html https://xenbits.xen.org/xsa/advisory-258.html https://www.samba.org/samba/security/CVE-2018-1050.html https://www.postgresql.org/about/news/1829/ https://www.postgresql.org/about/news/1829/ https://pagure.io/389-ds-base/issue/49545 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889270 https://www.samba.org/samba/security/CVE-2018-1057.html https://www.postgresql.org/about/news/1834/ https://access.redhat.com/security/cve/CVE-2018-1059 https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-5-final https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-5-final https://gerrit.ovirt.org/#/c/84875 https://gerrit.ovirt.org/#/c/84861 https://security.libvirt.org/2018/0004.html https://matrix.org/blog/2018/05/01/security-update-synapse-0-28-1/ https://bugzilla.redhat.com/show_bug.cgi?id=1540622 https://www.strongswan.org/blog/2018/05/28/strongswan-vulnerability-(cve-2018-10811).html https://eprint.iacr.org/2018/747 https://eprint.iacr.org/2018/747 https://eprint.iacr.org/2018/747 https://prosody.im/security/advisory_20180531/ https://blog.prosody.im/prosody-0-10-2-security-release/ https://pagure.io/389-ds-base/issue/49768 https://pagure.io/SSSD/sssd/issue/3766 https://github.com/ansible/ansible/pull/41414 https://www.samba.org/samba/security/CVE-2018-10858.html https://snyk.io/research/zip-slip-vulnerability https://access.redhat.com/security/vulnerabilities/pop_ss https://pagure.io/389-ds-base/issue/49789 https://access.redhat.com/articles/3414511 https://github.com/libgit2/libgit2/releases/tag/v0.27.3 https://github.com/libgit2/libgit2/releases/tag/v0.27.3 http://www.openwall.com/lists/oss-security/2018/07/11/7 https://pulp.plan.io/issues/3521 https://gerrit.ovirt.org/#/c/93195/ https://www.postgresql.org/about/news/1878/ https://www.samba.org/samba/security/CVE-2018-10918.html https://www.samba.org/samba/security/CVE-2018-10919.html https://www.postgresql.org/about/news/1878/ https://www.libssh.org/security/advisories/CVE-2018-10933.txt https://www.postgresql.org/about/news/1883/ http://xenbits.xen.org/xsa/advisory-262.html http://xenbits.xen.org/xsa/advisory-261.html https://lists.schedmd.com/pipermail/slurm-announce/2018/000008.html https://access.redhat.com/security/vulnerabilities/3422241 http://www.openwall.com/lists/oss-security/2018/04/23/3 https://snyk.io/vuln/npm:is-my-json-valid:20180214 https://snyk.io/vuln/npm:braces:20180219 http://seclists.org/fulldisclosure/2018/May/43 https://access.redhat.com/security/vulnerabilities/3442151 https://access.redhat.com/articles/3422521 http://seclists.org/fulldisclosure/2018/May/43 http://seclists.org/fulldisclosure/2018/May/43 https://issues.jboss.org/browse/UNDERTOW-1338 https://bugs.openjdk.java.net/browse/JDK-6956385 http://seclists.org/oss-sec/2018/q2/122 https://www.qualys.com/2018/05/17/procps-ng-audit-report-advisory.txt http://antirez.com/news/119 http://antirez.com/news/119 https://www.qualys.com/2018/05/17/procps-ng-audit-report-advisory.txt https://www.qualys.com/2018/05/17/procps-ng-audit-report-advisory.txt https://www.edwardthomson.com/blog/upgrading_git_for_cve2018_11235.html https://www.qualys.com/2018/05/17/procps-ng-audit-report-advisory.txt https://www.qualys.com/2018/05/17/procps-ng-audit-report-advisory.txt https://www.qualys.com/2018/05/17/procps-ng-audit-report-advisory.txt https://jira.opendaylight.org/browse/SDNINTRFAC-14 https://www.samba.org/samba/security/CVE-2018-1139.html https://www.samba.org/samba/security/CVE-2018-1140.html https://bugzilla.samba.org/show_bug.cgi?id=13374 https://www.tenable.com/security/research/tra-2018-17 http://www.squid-cache.org/Advisories/SQUID-2018_3.txt https://spark.apache.org/security.html#CVE-2018-11770 https://lists.apache.org/thread.html/b8da751fc0ca949534cdf2744111da6bb0349d2798fac94b0a50f330@%3Cannounce.apache.org%3E https://cwiki.apache.org/confluence/display/WW/S2-057 https://mail-archives.apache.org/mod_mbox/spamassassin-announce/201809.mbox/raw/%3Cc57c0f41-742c-3c3e-249c-ae2614bf0d7d%40apache.org%3E/ https://mail-archives.apache.org/mod_mbox/spamassassin-announce/201809.mbox/raw/%3Cc57c0f41-742c-3c3e-249c-ae2614bf0d7d%40apache.org%3E/ http://tomcat.apache.org/security-9.html#Fixed_in_Apache_Tomcat_9.0.12 http://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.34 http://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.91 http://karaf.apache.org/security/cve-2018-11786.txt http://karaf.apache.org/security/cve-2018-11787.txt https://lists.apache.org/thread.html/88de8350cda9b184888ec294c813c5bd8a2081de8fd3666f8904bc05@%3Cdev.tika.apache.org%3E https://lists.apache.org/thread.html/a9760973a873522f4d4c0a99916ceb74f361d91006b663a0a418d34a@%3Cannounce.apache.org%3E https://pivotal.io/security/cve-2018-1196 https://pivotal.io/security/cve-2018-1199 https://neopg.io/blog/enigmail-signature-spoof/ http://seclists.org/oss-sec/2018/q2/187 https://lists.gnupg.org/pipermail/gnupg-announce/2018q2/000425.html https://blog.phusion.nl/passenger-5-3-2 https://blog.phusion.nl/passenger-5-3-2 https://blog.phusion.nl/passenger-5-3-2 https://blog.phusion.nl/2018/06/12/passenger-5-3-2-various-security-fixes/ https://pulsesecurity.co.nz/advisories/phusion-passenger-priv-esc https://www.wireshark.org/security/wnpa-sec-2018-50 http://downloads.asterisk.org/pub/security/AST-2018-008.html http://downloads.asterisk.org/pub/security/AST-2018-007.html https://matrix.org/blog/2018/06/08/synapse-0-31-1-released/ https://neopg.io/blog/pass-signature-spoof/ https://lists.zx2c4.com/pipermail/password-store/2018-June/003308.html https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-12358 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-12359 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-12360 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-12361 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-12362 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-12363 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-12364 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-12365 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-12366 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-12367 https://www.mozilla.org/en-US/security/advisories/mfsa2018-15/#CVE-2018-12368 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-12369 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-12370 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-12371 https://www.mozilla.org/en-US/security/advisories/mfsa2018-20/#CVE-2018-12375 https://www.mozilla.org/en-US/security/advisories/mfsa2018-21/#CVE-2018-12376 https://www.mozilla.org/en-US/security/advisories/mfsa2018-21/#CVE-2018-12377 https://www.mozilla.org/en-US/security/advisories/mfsa2018-21/#CVE-2018-12378 https://www.mozilla.org/en-US/security/advisories/mfsa2018-21/#CVE-2018-12379 https://www.mozilla.org/en-US/security/advisories/mfsa2018-20/#CVE-2018-12381 https://www.mozilla.org/en-US/security/advisories/mfsa2018-20/#CVE-2018-12382 https://www.mozilla.org/en-US/security/advisories/mfsa2018-20/#CVE-2018-12383 https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.39_release_notes https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.36.5_release_notes https://www.mozilla.org/en-US/security/advisories/mfsa2018-23/#CVE-2018-12385 https://www.mozilla.org/en-US/security/advisories/mfsa2018-24/#CVE-2018-12386 https://www.mozilla.org/en-US/security/advisories/mfsa2018-24/#CVE-2018-12387 https://www.mozilla.org/en-US/security/advisories/mfsa2018-27/#CVE-2018-12389 https://www.mozilla.org/en-US/security/advisories/mfsa2018-27/#CVE-2018-12390 https://www.mozilla.org/en-US/security/advisories/mfsa2018-27/#CVE-2018-12391 https://www.mozilla.org/en-US/security/advisories/mfsa2018-27/#CVE-2018-12392 https://www.mozilla.org/en-US/security/advisories/mfsa2018-27/#CVE-2018-12393 https://www.mozilla.org/en-US/security/advisories/mfsa2018-27/#CVE-2018-12395 https://www.mozilla.org/en-US/security/advisories/mfsa2018-27/#CVE-2018-12396 https://www.mozilla.org/en-US/security/advisories/mfsa2018-27/#CVE-2018-12397 https://codewhitesec.blogspot.com/2018/05/poor-richfaces.html https://codewhitesec.blogspot.com/2018/05/poor-richfaces.html https://www.compass-security.com/fileadmin/Datein/Research/Advisories/CSNC-2018-021_vertx.txt https://pivotal.io/security/cve-2018-1270 https://pivotal.io/security/cve-2018-1271 https://pivotal.io/security/cve-2018-1272 https://pivotal.io/security/cve-2018-1273 https://pivotal.io/security/cve-2018-1274 https://lists.apache.org/thread.html/74bd2bff1827febb348dfb323986fa340d3bb97a315ab93c3ccc8299@%3Cdev.hive.apache.org%3E https://helpx.adobe.com/security/products/flash-player/apsb18-25.html https://helpx.adobe.com/security/products/flash-player/apsb18-25.html https://helpx.adobe.com/security/products/flash-player/apsb18-25.html https://helpx.adobe.com/security/products/flash-player/apsb18-25.html https://helpx.adobe.com/security/products/flash-player/apsb18-25.html https://lists.apache.org/thread.html/29184dbce4a37be2af36e539ecb479b1d27868f73ccfdff46c7174b4@%3Cdev.hive.apache.org%3E https://lists.apache.org/thread.html/29f61337323f48c47d4b41d74b9e452bd60e65d0e5103af9a6bb2fef@%3Cusers.kafka.apache.org%3E https://lists.apache.org/thread.html/45e7d5e2c6face85aab693f5ae0616563132ff757e5a558da80d0209@%3Cdev.ignite.apache.org%3E https://tools.ietf.org/html/rfc4616 https://httpd.apache.org/security/vulnerabilities_24.html https://httpd.apache.org/security/vulnerabilities_24.html https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.85 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.50 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.28 https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.85 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.50 https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.28 http://www.openwall.com/lists/oss-security/2018/04/08/3 https://httpd.apache.org/security/vulnerabilities_24.html https://lists.apache.org/thread.html/d5da94ef60312c01a8d2348466680d1b5fb70702c71a3e84e94f7933@%3Cdev.hive.apache.org%3E http://tomcat.apache.org/security-jk.html#Fixed_in_Apache_Tomcat_JK_Connector_1.2.43 https://commons.apache.org/proper/commons-compress/security-reports.html http://www.zsh.org/mla/zsh-announce/136 https://cwiki.apache.org/confluence/display/WW/S2-056 https://httpd.apache.org/security/vulnerabilities_24.html#CVE-2018-1333 https://lists.apache.org/thread.html/b3ed4432380af767effd4c6f27665cc7b2686acccbefeb9f55851dca@%3Cdev.tika.apache.org%3E https://lists.apache.org/thread.html/4d20c5748fb9f836653bc78a1bad991ba8485d82a1e821f70b641932@%3Cdev.tika.apache.org%3E https://lists.apache.org/thread.html/4d2cb5c819401bb075e2a1130e0d14f0404a136541a6f91da0225828@%3Cdev.tika.apache.org%3E https://exchange.xforce.ibmcloud.com/vulnerabilities/138823 http://www.openwall.com/lists/oss-security/2018/07/16/1 http://www.openwall.com/lists/oss-security/2018/07/16/1 https://www.wireshark.org/security/wnpa-sec-2018-38.html https://www.wireshark.org/security/wnpa-sec-2018-36.html https://www.wireshark.org/security/wnpa-sec-2018-39.html https://www.wireshark.org/security/wnpa-sec-2018-34.html https://www.wireshark.org/security/wnpa-sec-2018-37.html https://www.wireshark.org/security/wnpa-sec-2018-35.html https://www.wireshark.org/security/wnpa-sec-2018-42.html https://www.wireshark.org/security/wnpa-sec-2018-40.html https://www.wireshark.org/security/wnpa-sec-2018-41.html https://www.wireshark.org/security/wnpa-sec-2018-43.html https://www.djangoproject.com/weblog/2018/aug/01/security-releases/ https://curl.haxx.se/docs/CVE-2018-14618.html https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b32a7dc8aef1882fbf983eb354837488cc9d54dc https://access.redhat.com/security/vulnerabilities/mutagen-astronomy https://www.openwall.com/lists/oss-security/2018/09/25/4 https://www.mail-archive.com/haproxy@formilux.org/msg31253.html https://bugs.python.org/issue34623 https://pagure.io/389-ds-base/issue/49969 https://access.redhat.com/articles/3623521 https://bugs.chromium.org/p/project-zero/issues/detail?id=1650 https://lists.x.org/archives/xorg-announce/2018-October/002927.html https://symfony.com/blog/cve-2018-14773-remove-support-for-legacy-and-risky-http-headers https://www.yubico.com/support/security-advisories/ysa-2018-03/ https://www.yubico.com/support/security-advisories/ysa-2018-03/ https://pivotal.io/security/cve-2018-15756 https://pivotal.io/security/cve-2018-15758 http://seclists.org/oss-sec/2018/q3/142 http://seclists.org/oss-sec/2018/q3/142 https://www.kb.cert.org/vuls/id/332928 https://helpx.adobe.com/security/products/flash-player/apsb18-31.html https://www.wireshark.org/security/wnpa-sec-2018-45.html https://www.wireshark.org/security/wnpa-sec-2018-46.html https://www.wireshark.org/security/wnpa-sec-2018-44.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html https://www.x41-dsec.de/lab/advisories/x41-2018-002-OpenSC/ https://www.x41-dsec.de/lab/advisories/x41-2018-002-OpenSC/ https://www.x41-dsec.de/lab/advisories/x41-2018-002-OpenSC/ https://www.ruby-lang.org/en/news/2018/10/17/openssl-x509-name-equality-check-does-not-work-correctly-cve-2018-16395/ https://www.ruby-lang.org/en/news/2018/10/17/not-propagated-taint-flag-in-some-formats-of-pack-cve-2018-16396/ https://www.x41-dsec.de/lab/advisories/x41-2018-002-OpenSC/ https://www.x41-dsec.de/lab/advisories/x41-2018-002-OpenSC/ https://www.x41-dsec.de/lab/advisories/x41-2018-002-OpenSC/ https://www.x41-dsec.de/lab/advisories/x41-2018-002-OpenSC/ https://www.x41-dsec.de/lab/advisories/x41-2018-002-OpenSC/ https://www.x41-dsec.de/lab/advisories/x41-2018-002-OpenSC/ https://www.x41-dsec.de/lab/advisories/x41-2018-002-OpenSC/ https://www.x41-dsec.de/lab/advisories/x41-2018-002-OpenSC/ https://www.x41-dsec.de/lab/advisories/x41-2018-002-OpenSC/ https://www.x41-dsec.de/lab/advisories/x41-2018-002-OpenSC/ http://seclists.org/oss-sec/2018/q3/142 https://www.kb.cert.org/vuls/id/332928 http://seclists.org/oss-sec/2018/q3/142 https://www.kb.cert.org/vuls/id/332928 https://www.artifex.com/news/ghostscript-security-resolved/ https://www.kb.cert.org/vuls/id/332928 https://www.artifex.com/news/ghostscript-security-resolved/ https://www.kb.cert.org/vuls/id/332928 https://www.artifex.com/news/ghostscript-security-resolved/ https://www.kb.cert.org/vuls/id/332928 https://www.artifex.com/news/ghostscript-security-resolved/ https://github.com/ansible/ansible/pull/47436 https://curl.haxx.se/docs/CVE-2018-16839.html https://curl.haxx.se/docs/CVE-2018-16840.html https://curl.haxx.se/docs/CVE-2018-16842.html https://www.openwall.com/lists/oss-security/2018/11/02/1 https://www.djangoproject.com/weblog/2018/oct/01/security-release/ https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop_11.html https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop_11.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://www.wireshark.org/security/wnpa-sec-2018-49 https://www.wireshark.org/security/wnpa-sec-2018-48 https://www.wireshark.org/security/wnpa-sec-2018-47 https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg02396.html https://blogs.securiteam.com/index.php/archives/3731 https://jenkins.io/security/advisory/2018-07-18/#SECURITY-897 https://jenkins.io/security/advisory/2018-07-18/#SECURITY-914 https://jenkins.io/security/advisory/2018-07-18/#SECURITY-891 https://jenkins.io/security/advisory/2018-07-18/#SECURITY-892 https://jenkins.io/security/advisory/2018-07-18/#SECURITY-944 https://jenkins.io/security/advisory/2018-07-18/#SECURITY-925 https://jenkins.io/security/advisory/2018-07-18/#SECURITY-390 https://blog.bentkowski.info/2018/06/xss-in-google-colaboratory-csp-bypass.html https://jenkins.io/security/advisory/2018-08-15/#SECURITY-637 https://jenkins.io/security/advisory/2018-08-15/#SECURITY-672 https://jenkins.io/security/advisory/2018-08-15/#SECURITY-790 https://jenkins.io/security/advisory/2018-08-15/#SECURITY-996 https://jenkins.io/security/advisory/2018-08-15/#SECURITY-1071 https://jenkins.io/security/advisory/2018-08-15/#SECURITY-1076 http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html https://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html#AppendixJAVA https://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html#AppendixJAVA http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html https://edk2-docs.gitbooks.io/security-advisory/content/edk-ii-authenticated-variable-bypass.html https://access.redhat.com/security/vulnerabilities/L1TF https://www.redhat.com/en/blog/understanding-l1-terminal-fault-aka-foreshadow-what-you-need-know https://www.redhat.com/en/blog/deeper-look-l1-terminal-fault-aka-foreshadow https://foreshadowattack.eu/ https://software.intel.com/security-software-guidance/software-guidance/l1-terminal-fault https://access.redhat.com/articles/3562741 https://access.redhat.com/security/vulnerabilities/ssbd https://bugs.chromium.org/p/project-zero/issues/detail?id=1528 https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00115.html https://software.intel.com/sites/default/files/managed/b9/f9/336983-Intel-Analysis-of-Speculative-Execution-Side-Channels-White-Paper.pdf https://software.intel.com/sites/default/files/managed/c5/63/336996-Speculative-Execution-Side-Channel-Mitigations.pdf https://access.redhat.com/solutions/3452311 https://access.redhat.com/security/vulnerabilities/L1TF https://www.redhat.com/en/blog/understanding-l1-terminal-fault-aka-foreshadow-what-you-need-know https://www.redhat.com/en/blog/deeper-look-l1-terminal-fault-aka-foreshadow https://foreshadowattack.eu/ https://software.intel.com/security-software-guidance/software-guidance/l1-terminal-fault https://access.redhat.com/articles/3562741 https://access.redhat.com/solutions/3485131 http://www.openwall.com/lists/oss-security/2018/06/15/5 https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00145.html https://access.redhat.com/solutions/3523601 https://people.csail.mit.edu/vlk/spectre11.pdf https://01.org/security/advisories/intel-oss-10002 https://software.intel.com/sites/default/files/managed/4e/a1/337879-analyzing-potential-bounds-Check-bypass-vulnerabilities.pdf https://nodesecurity.io/advisories/578 https://hackerone.com/reports/311236 https://nodesecurity.io/advisories/593 https://hackerone.com/reports/319532 https://github.com/rgrove/sanitize/issues/176 http://seclists.org/oss-sec/2018/q1/254 https://nodesecurity.io/advisories/612 https://hackerone.com/reports/311333 http://www.openwall.com/lists/oss-security/2018/06/19/2 https://blog.heroku.com/rails-asset-pipeline-vulnerability https://nextcloud.com/security/advisory/?id=NC-SA-2018-007 https://hackerone.com/reports/248656 https://nextcloud.com/security/advisory/?id=NC-SA-2018-006 https://hackerone.com/reports/232347 https://nextcloud.com/security/advisory/?id=NC-SA-2018-008 https://hackerone.com/reports/383117 https://www.talosintelligence.com/vulnerability_reports/TALOS-2018-0516 https://heasarc.gsfc.nasa.gov/FTP/software/fitsio/c/docs/changes2.txt https://www.talosintelligence.com/vulnerability_reports/TALOS-2018-0531 https://heasarc.gsfc.nasa.gov/FTP/software/fitsio/c/docs/changes2.txt https://www.talosintelligence.com/vulnerability_reports/TALOS-2018-0531 https://heasarc.gsfc.nasa.gov/FTP/software/fitsio/c/docs/changes2.txt https://talosintelligence.com/vulnerability_reports/TALOS-2018-0694 https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://helpx.adobe.com/security/products/flash-player/apsb18-01.html https://helpx.adobe.com/security/products/flash-player/apsb18-03.html https://helpx.adobe.com/security/products/flash-player/apsb18-03.html https://helpx.adobe.com/security/products/flash-player/apsb18-05.html https://helpx.adobe.com/security/products/flash-player/apsb18-05.html https://helpx.adobe.com/security/products/flash-player/apsb18-08.html https://helpx.adobe.com/security/products/flash-player/apsb18-08.html https://helpx.adobe.com/security/products/flash-player/apsb18-08.html https://helpx.adobe.com/security/products/flash-player/apsb18-08.html https://helpx.adobe.com/security/products/flash-player/apsb18-08.html https://helpx.adobe.com/security/products/flash-player/apsb18-08.html https://helpx.adobe.com/security/products/flash-player/apsb18-16.html https://helpx.adobe.com/security/products/flash-player/apsb18-19.html https://helpx.adobe.com/security/products/flash-player/apsb18-19.html https://helpx.adobe.com/security/products/flash-player/apsb18-19.html https://helpx.adobe.com/security/products/flash-player/apsb18-19.html https://helpx.adobe.com/security/products/flash-player/apsb18-24.html https://helpx.adobe.com/security/products/flash-player/apsb18-24.html https://www.mozilla.org/en-US/security/advisories/mfsa2018-03/#CVE-2018-5089 https://www.mozilla.org/en-US/security/advisories/mfsa2018-03/#CVE-2018-5091 https://www.mozilla.org/en-US/security/advisories/mfsa2018-03/#CVE-2018-5095 https://www.mozilla.org/en-US/security/advisories/mfsa2018-03/#CVE-2018-5096 https://www.mozilla.org/en-US/security/advisories/mfsa2018-03/#CVE-2018-5097 https://www.mozilla.org/en-US/security/advisories/mfsa2018-03/#CVE-2018-5098 https://www.mozilla.org/en-US/security/advisories/mfsa2018-03/#CVE-2018-5099 https://www.mozilla.org/en-US/security/advisories/mfsa2018-03/#CVE-2018-5102 https://www.mozilla.org/en-US/security/advisories/mfsa2018-03/#CVE-2018-5103 https://www.mozilla.org/en-US/security/advisories/mfsa2018-03/#CVE-2018-5104 https://www.mozilla.org/en-US/security/advisories/mfsa2018-03/#CVE-2018-5117 https://www.mozilla.org/en-US/security/advisories/mfsa2018-07/#CVE-2018-5125 https://www.mozilla.org/en-US/security/advisories/mfsa2018-07/#CVE-2018-5127 https://www.mozilla.org/en-US/security/advisories/mfsa2018-07/#CVE-2018-5129 https://www.mozilla.org/en-US/security/advisories/mfsa2018-07/#CVE-2018-5130 https://www.mozilla.org/en-US/security/advisories/mfsa2018-07/#CVE-2018-5131 https://www.mozilla.org/en-US/security/advisories/mfsa2018-07/#CVE-2018-5144 https://www.mozilla.org/en-US/security/advisories/mfsa2018-07/#CVE-2018-5145 https://www.mozilla.org/en-US/security/advisories/mfsa2018-08 https://www.mozilla.org/en-US/security/advisories/mfsa2018-10/ https://www.mozilla.org/en-US/security/advisories/mfsa2018-12/#CVE-2018-5150 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5151 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5152 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5153 https://www.mozilla.org/en-US/security/advisories/mfsa2018-12/#CVE-2018-5154 https://www.mozilla.org/en-US/security/advisories/mfsa2018-12/#CVE-2018-5155 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-5156 https://www.mozilla.org/en-US/security/advisories/mfsa2018-12/#CVE-2018-5157 https://www.mozilla.org/en-US/security/advisories/mfsa2018-12/#CVE-2018-5158 https://www.mozilla.org/en-US/security/advisories/mfsa2018-12/#CVE-2018-5159 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5160 https://www.mozilla.org/en-US/security/advisories/mfsa2018-13/#CVE-2018-5161 https://www.mozilla.org/en-US/security/advisories/mfsa2018-13/#CVE-2018-5162 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5163 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5164 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5165 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5166 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5167 https://www.mozilla.org/en-US/security/advisories/mfsa2018-12/#CVE-2018-5168 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5169 https://www.mozilla.org/en-US/security/advisories/mfsa2018-13/#CVE-2018-5170 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5172 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5173 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5174 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5175 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5176 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5177 https://www.mozilla.org/en-US/security/advisories/mfsa2018-12/#CVE-2018-5178 https://chromereleases.googleblog.com/2018/10/stable-channel-update-for-desktop.html https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5180 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5181 https://www.mozilla.org/en-US/security/advisories/mfsa2018-11/#CVE-2018-5182 https://www.mozilla.org/en-US/security/advisories/mfsa2018-12/#CVE-2018-5183 https://www.mozilla.org/en-US/security/advisories/mfsa2018-13/#CVE-2018-5184 https://www.mozilla.org/en-US/security/advisories/mfsa2018-13/#CVE-2018-5185 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-5186 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-5187 https://www.mozilla.org/en-US/security/advisories/mfsa2018-16/#CVE-2018-5188 https://irssi.org/security/irssi_sa_2018_01.txt https://irssi.org/security/irssi_sa_2018_01.txt https://irssi.org/security/irssi_sa_2018_01.txt https://irssi.org/security/irssi_sa_2018_01.txt https://www.quagga.net/security/Quagga-2018-0543.txt https://www.quagga.net/security/Quagga-2018-1114.txt https://www.quagga.net/security/Quagga-2018-1550.txt https://www.quagga.net/security/Quagga-2018-1975.txt https://www.kb.cert.org/vuls/id/304725 https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00128.html https://www.bluetooth.com/news/unknown/2018/07/bluetooth-sig-security-update https://www.kb.cert.org/vuls/id/857035 https://access.redhat.com/articles/3553061 https://www.kb.cert.org/vuls/id/962459 https://www.spinics.net/lists/netdev/msg514742.html https://access.redhat.com/articles/3553061 https://www.kb.cert.org/vuls/id/641765 https://github.com/bbbrumley/portsmash https://kb.isc.org/article/AA-01565 https://kb.isc.org/article/AA-01567 https://kb.isc.org/article/AA-01562/ https://kb.isc.org/article/AA-01602/74/CVE-2018-5736 https://kb.isc.org/article/AA-01606/74/CVE-2018-5737 https://kb.isc.org/article/AA-01616/0/CVE-2018-5738 https://kb.isc.org/article/AA-01639/74/CVE-2018-5740 https://kb.isc.org/docs/cve-2018-5741 https://packetstormsecurity.com/files/146172/secunia-libraw.txt https://packetstormsecurity.com/files/146172/secunia-libraw.txt https://packetstormsecurity.com/files/146172/secunia-libraw.txt https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop_24.html https://chromereleases.googleblog.com/2018/02/stable-channel-update-for-desktop_13.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop_26.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html https://chromereleases.googleblog.com/2018/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/06/stable-channel-update-for-desktop_12.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html https://www.djangoproject.com/weblog/2018/feb/01/security-releases/ https://www.strongswan.org/blog/2018/02/19/strongswan-vulnerability-%28cve-2018-6459%29.html https://puppet.com/security/cve/CVE-2018-6514 https://puppet.com/security/cve/CVE-2018-6515 https://github.com/TElgamal/attack-on-pycrypto-elgamal https://github.com/Legrandin/pycryptodome/issues/90 http://lists.unbit.it/pipermail/uwsgi/2018-February/008835.html https://exim.org/static/doc/security/CVE-2018-6789.txt https://devco.re/blog/2018/03/06/exim-off-by-one-RCE-exploiting-CVE-2018-6789-en/ https://www.kde.org/info/security/advisory-20180208-1.txt https://www.kde.org/info/security/advisory-20180208-2.txt https://rt.perl.org/Public/Bug/Display.html?id=132227 https://rt.perl.org/Public/Bug/Display.html?id=132063 https://github.com/jollheef/libreoffice-remote-arbitrary-file-disclosure https://www.libreoffice.org/about-us/security/advisories/cve-2018-1055/ https://rt.perl.org/Public/Bug/Display.html?id=131844 https://www.ruby-lang.org/en/news/2018/03/28/unintentional-file-and-directory-creation-with-directory-traversal-cve-2018-6914/ https://www.vmware.com/security/advisories/VMSA-2018-0017.html https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14398 https://www.wireshark.org/security/wnpa-sec-2018-10.html https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14339 https://www.wireshark.org/security/wnpa-sec-2018-07.html https://www.wireshark.org/security/wnpa-sec-2018-05.html https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14442 https://www.wireshark.org/security/wnpa-sec-2018-09.html https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14374 https://www.wireshark.org/security/wnpa-sec-2018-08.html https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14446 https://www.wireshark.org/security/wnpa-sec-2018-12.html https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14409 https://www.wireshark.org/security/wnpa-sec-2018-13.html https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14410 https://www.wireshark.org/security/wnpa-sec-2018-14.html https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14443 https://www.wireshark.org/security/wnpa-sec-2018-11.html https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14403 https://access.redhat.com/solutions/3442891 https://www.djangoproject.com/weblog/2018/mar/06/security-releases/ https://www.djangoproject.com/weblog/2018/mar/06/security-releases/ http://xenbits.xen.org/xsa/advisory-252.html http://xenbits.xen.org/xsa/advisory-255.html http://xenbits.xen.org/xsa/advisory-256.html https://www.drupal.org/sa-core-2018-002 https://groups.drupal.org/security/faq-2018-002 https://www.drupal.org/sa-core-2018-004 https://www.trustwave.com/Resources/Security-Advisories/Advisories/TWSL2018-008/?fid=11632 http://www.openwall.com/lists/oss-security/2018/05/21/4 https://httpd.apache.org/security/vulnerabilities_24.html#CVE-2018-8011 http://openwall.com/lists/oss-security/2018/05/21/6 https://cwiki.apache.org/confluence/display/ZOOKEEPER/Server-Server+mutual+authentication https://issues.apache.org/jira/browse/ZOOKEEPER-1045 https://xmlgraphics.apache.org/security.html http://seclists.org/oss-sec/2018/q2/135 http://tomcat.apache.org/security-9.html#Fixed_in_Apache_Tomcat_9.0.9 http://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.32 http://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.53 http://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.89 https://lists.apache.org/thread.html/e0fdf53114a321142ecfa5cfa17658090f0b4e1677de431e329b37ab@%3Cdev.ignite.apache.org%3E http://mail-archives.apache.org/mod_mbox/www-announce/201807.mbox/%3C20180721095943.GA24320%40minotaur.apache.org%3E http://tomcat.apache.org/security-native.html#Fixed_in_Apache_Tomcat_Native_Connector_1.2.17 http://mail-archives.apache.org/mod_mbox/www-announce/201807.mbox/%3C20180721095943.GA24320%40minotaur.apache.org%3E http://tomcat.apache.org/security-native.html#Fixed_in_Apache_Tomcat_Native_Connector_1.2.17 https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201807.mbox/%3C0cdc01d413b7%24f97ba580%24ec72f080%24%40apache.org%3E http://www.openwall.com/lists/oss-security/2018/06/29/1 http://cxf.apache.org/security-advisories.data/CVE-2018-8039.txt.asc?version=1&modificationDate=1530184663000&api=v2 https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8409 https://insinuator.net/2018/03/squirrelmail-full-disclosure-troopers18/ http://www.openwall.com/lists/oss-security/2018/03/17/2 http://www.openwall.com/lists/oss-security/2018/03/15/2 https://www.ruby-lang.org/en/news/2018/03/28/large-request-dos-in-webrick-cve-2018-8777/ https://www.ruby-lang.org/en/news/2018/03/28/buffer-under-read-unpack-cve-2018-8778/ https://www.ruby-lang.org/en/news/2018/03/28/poisoned-nul-byte-unixsocket-cve-2018-8779/ https://www.ruby-lang.org/en/news/2018/03/28/poisoned-nul-byte-dir-cve-2018-8780/ https://access.redhat.com/security/vulnerabilities/pop_ss http://www.cs.ucr.edu/~nael/pubs/asplos18.pdf https://arstechnica.com/gadgets/2018/03/its-not-just-spectre-researchers-reveal-more-branch-prediction-attacks/ https://www.drupal.org/sa-core-2018-003 An unaligned memory access bug was found in the way ZZIPlib handled ZIP files. This flaw could potentially be used to crash the application using ZZIPlib by tricking the application into processing specially crafted ZIP files. It was found that mailman stored private email messages in a world-readable directory. A local user could use this flaw to read private mailing list archives. A directory traversal flaw was found in the way the jar tool extracted JAR archive files. A specially crafted JAR archive could cause jar to overwrite arbitrary files writable by the user running jar when the archive was extracted. It was found that when transparent interception mode was enabled in squid a remote attacker could bypass access controls implemented for certain web elements like Flash and Java and communicate with restricted intranet sites via crafted Host headers. It was found that ftpd, a Kerberos-aware FTP server, did not properly drop privileges. On Red Hat Enterprise Linux 5, the ftpd daemon did not check for the potential failure of the krb5_setegid() function call. On systems where the set real, set effective, or set saved group ID system calls might fail, a remote FTP user could use this flaw to gain unauthorized read or write access to files that were owned by the root group. A heap-based buffer overflow flaw was found in the way JasPer decoded JPEG 2000 compressed image files. An attacker could create a malicious JPEG 2000 compressed image file that, when opened, would cause applications that use JasPer (such as Nautilus) to crash or, potentially, execute arbitrary code. A heap-based buffer overflow flaw was found in the way JasPer decoded JPEG 2000 compressed image files. An attacker could create a malicious JPEG 2000 compressed image file that, when opened, would cause applications that use JasPer (such as Nautilus) to crash or, potentially, execute arbitrary code. It was found that the parameters passed to operation invocations on the JMX console were not properly sanitized. Remote attackers could use this flaw to inject arbitrary web script or HTML into the JMX console. It was found that the Xen hypervisor implementation as shipped with Red Hat Enterprise Linux 5 did not properly restrict the syscall return addresses in the sysret return path to canonical addresses. An unprivileged user in a 64-bit para-virtualized guest, that is running on a 64-bit host that has an Intel CPU, could use this flaw to crash the host or, potentially, escalate their privileges, allowing them to execute arbitrary code at the hypervisor level. A flaw was found in the way tcsd, the daemon that manages Trusted Computing resources, processed incoming TCP packets. A remote attacker could send a specially crafted TCP packet that, when processed by tcsd, could cause the daemon to crash. Note that by default tcsd accepts requests on localhost only. A denial of service flaw was found in the implementation of hash arrays in Expat. An attacker could use this flaw to make an application using Expat consume an excessive amount of CPU time by providing a specially crafted XML file that triggers multiple hash function collisions. To mitigate this issue, randomization has been added to the hash function to reduce the chance of an attacker successfully causing intentional collisions. A memory leak flaw was found in Expat. If an XML file processed by an application linked against Expat triggered a memory re-allocation failure, Expat failed to free the previously allocated memory. This could cause the application to exit unexpectedly or crash when all available memory is exhausted. A denial of service flaw was found in the way the File Information (fileinfo) extension parsed certain Composite Document Format (CDF) files. A remote attacker could use this flaw to crash a PHP application using fileinfo via a specially crafted CDF file. It was discovered that the xfs_metadump tool of the xfsprogs suite did not fully adhere to the standards of obfuscation described in its man page. In case a user with the necessary privileges used xfs_metadump and relied on the advertised obfuscation, the generated data could contain unexpected traces of potentially sensitive information. Multiple cross-site scripting flaws were discovered in the Red Hat Certificate System Agent and End Entity pages. An attacker could use these flaws to perform a cross-site scripting (XSS) attack against victims using the Certificate System's web interface. It was found that if Cumin were asked to display a link name containing non-ASCII characters, the request would terminate with an error. If data containing non-ASCII characters were added to the database (such as via Cumin or Wallaby), requests to load said data would terminate and the requested page would not be displayed until an administrator cleans the database. It was discovered that luci stored usernames and passwords in session cookies. This issue prevented the session inactivity timeout feature from working correctly, and allowed attackers able to get access to a session cookie to obtain the victim's authentication credentials. It was found that the distcheck rule in Automake-generated Makefiles made a directory world-writable when preparing source archives. If a malicious, local user could access this directory, they could execute arbitrary code with the privileges of the user running "make distcheck". A flaw was found in the way the dhcpd daemon handled the expiration time of IPv6 leases. If dhcpd's configuration was changed to reduce the default IPv6 lease time, lease renewal requests for previously assigned leases could cause dhcpd to crash. It was found that the Apache Qpid daemon (qpidd) treated AMQP connections with the federation_tag attribute set as a broker-to-broker connection, rather than a client-to-server connection. This resulted in the source user ID of messages not being checked. A client that can establish an AMQP connection with the broker could use this flaw to bypass intended authentication. For Condor users, if condor-aviary is installed, this flaw could be used to submit jobs that would run as any user (except root, as Condor does not run jobs as root). It was discovered that dracut created initramfs images as world readable. A local user could possibly use this flaw to obtain sensitive information from these files, such as iSCSI authentication passwords, encrypted root file system crypttab passwords, or other information. A flaw was found in the way the cupsGetFile() and cupsPutFile() functions of cups-pk-helper checked user IDs. If a local attacker performed a symbolic link attack, and was able to trick a CUPS administrator into approving the file transmission, the attacker could possibly use this flaw to access or modify certain system files, potentially leading to privilege escalation. It was discovered that Plone, included as a part of luci, did not properly protect the administrator interface (control panel). A remote attacker could use this flaw to inject a specially crafted Python statement or script into Plone's restricted Python sandbox that, when the administrator interface was accessed, would be executed with the privileges of that administrator user. It was discovered that Plone, included as a part of luci, did not properly sanitize HTTP headers provided within certain URL requests. A remote attacker could use a specially crafted URL that, when processed, would cause the injected HTTP headers to be returned as a part of the Plone HTTP response, potentially allowing the attacker to perform other more advanced attacks. It was discovered that Plone, included as a part of luci, did not properly protect the privilege of running RestrictedPython scripts. A remote attacker could use a specially crafted URL that, when processed, would allow the attacker to submit and perform expensive computations or, in conjunction with other attacks, be able to access or alter privileged information. It was discovered that Plone, included as a part of luci, did not properly enforce permissions checks on the membership database. A remote attacker could use a specially crafted URL that, when processed, could allow the attacker to enumerate user account names. It was discovered that Plone, included as a part of luci, did not properly handle the processing of requests for certain collections. A remote attacker could use a specially crafted URL that, when processed, would lead to excessive I/O and/or cache resource consumption. It was discovered that Plone, included as a part of luci, did not properly handle the processing of very large values passed to an internal utility function. A remote attacker could use a specially crafted URL that, when processed, would lead to excessive memory consumption. It was discovered that Plone, included as a part of luci, allowed a remote anonymous user to change titles of content items due to improper permissions checks. Multiple insecure temporary file creation flaws were found in Red Hat Storage. A local user on the Red Hat Storage server could use these flaws to cause arbitrary files to be overwritten as the root user via a symbolic link attack. An integer overflow flaw, leading to a heap-based buffer overflow, was found in the way grep parsed large lines of data. An attacker able to trick a user into running grep on a specially crafted data file could use this flaw to crash grep or, potentially, execute arbitrary code with the privileges of the user running grep. It was found that Apache Commons HttpClient 3.x, as used in Amazon Flexible Payments Service (FPS) merchant Java SDK and other products, does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate. Apache Axis did not verify that the server host name matched the domain name in the subject's Common Name (CN) or subjectAltName field in X.509 certificates. This could allow a man-in-the-middle attacker to spoof an SSL server if they had a certificate that was valid for any domain name. A flaw was found in the regular expression matching routines that process multibyte character input. If an application utilized the glibc regular expression matching mechanism, an attacker could provide specially-crafted input that, when processed, would cause the application to crash. It was discovered that bouncycastle leaked timing information when decrypting TLS/SSL protocol encrypted records when CBC-mode cipher suites were used. A remote attacker could possibly use this flaw to retrieve plain text from the encrypted packets by using a TLS/SSL server as a padding oracle. A flaw was found in the way Ruby on Rails handled hashes in certain queries. A remote attacker could use this flaw to perform a denial of service (resource consumption) attack by sending specially crafted queries that would result in the creation of Ruby symbols, which were never garbage collected. A cross-site scripting (XSS) flaw was found in Action Pack. A remote attacker could use this flaw to conduct XSS attacks against users of an application using Action Pack. A cross-site scripting (XSS) flaw was found in Action Pack. A remote attacker could use this flaw to conduct XSS attacks against users of an application using Action Pack. It was found that getaddrinfo() did not limit the amount of stack memory used during name resolution. An attacker able to make an application resolve an attacker-controlled hostname or IP address could possibly cause the application to exhaust all stack memory and crash. A buffer overflow flaw was found in the way the XListInputDevices() function of X.Org X11's libXi runtime library handled signed numbers. A malicious X11 server could possibly use this flaw to execute arbitrary code with the privileges of the user running an X11 client. Two stack-based buffer overflow flaws were found in the way libX11, the Core X11 protocol client library, processed certain user-specified files. A malicious X11 server could possibly use this flaw to crash an X11 client via a specially crafted file. A flaw was found in the way the X.Org X11 libXt runtime library used uninitialized pointers. A malicious X11 server could possibly use this flaw to execute arbitrary code with the privileges of the user running an X11 client. The HawtJNI Library class wrote native libraries to a predictable file name in /tmp when the native libraries were bundled in a JAR file, and no custom library path was specified. A local attacker could overwrite these native libraries with malicious versions during the window between when HawtJNI writes them and when they are executed. It was discovered that when used to create images, livecd-tools gave the root user an empty password rather than leaving the password locked in situations where no 'rootpw' directive was used or when the 'rootpw --lock' directive was used within the Kickstart file, which could allow local users to gain access to the root account. A denial of service flaw was found in the way Python's SSL module implementation performed matching of certain certificate names. A remote attacker able to obtain a valid certificate that contained multiple wildcard characters could use this flaw to issue a request to validate such a certificate, resulting in excessive consumption of CPU. An unaligned memory access bug was found in the way ZZIPlib handled ZIP files. This flaw could potentially be used to crash the application using ZZIPlib by tricking the application into processing specially crafted ZIP files. The implementation of big key management in security/keys/big_key.c in the Linux kernel before 4.8.7 mishandles unsuccessful crypto registration in conjunction with successful key-type registration, which allows local users to cause a denial of service (NULL pointer dereference and panic) or possibly have unspecified other impact via a crafted application that uses the big_key data type. A vulnerability was found in the patch for CVE-2013-6045 for OpenJPEG. A specially crafted JPEG2000 image, when read by an application using OpenJPEG, could cause heap-based buffer overflows leading to a crash or possible code execution. A double-free flaw was found in the way GnuTLS parsed certain X.509 certificates with Proxy Certificate Information extension. An attacker could create a specially-crafted certificate which, when processed by an application compiled against GnuTLS, could cause that application to crash. A denial of service flaw was discovered in bind versions that include the "deny-answer-aliases" feature. This flaw may allow a remote attacker to trigger an INSIST assert in named leading to termination of the process and a denial of service condition. A flaw was found in katello-debug where certain scripts and log files used insecure temporary files. A local user could exploit this flaw to conduct a symbolic-link attack, allowing them to overwrite the contents of arbitrary files. It was found that the fix for CVE-2016-9576 was incomplete: the Linux kernel's sg implementation did not properly restrict write operations in situations where the KERNEL_DS option is set. A local attacker to read or write to arbitrary kernel memory locations or cause a denial of service (use-after-free) by leveraging write access to a /dev/sg device. A flaw was found in the way method-level authorization for JAX-WS Service endpoints was performed by the EJB invocation handler implementation. Any restrictions declared on EJB methods were ignored when executing the JAX-WS handlers, and only class-level restrictions were applied. A remote attacker who is authorized to access the EJB class, could invoke a JAX-WS handler which they were not authorized to invoke. A flaw was found in GMR (Geo-Mobile Radio) 1 BCCH protocol dissector of wireshark which an attacker can trigger a denial of service attack and crash wireshark by sending a specially crafted packet onto the wire or by convincing wireshark user to read malformed packet trace file. It was possible for an attacker, using complex and limited conditions, to upload a malicious JSP to a Tomcat server and then trigger the execution of that JSP. A stack-based buffer overflow flaw was found in the way the Quagga OSPFD daemon handled LSA (link-state advertisement) packets. A remote attacker could use this flaw to crash the ospfd daemon resulting in denial of service. A buffer overflow flaw was found in Squid's DNS lookup module. A remote attacker able to send HTTP requests to the Squid proxy could use this flaw to crash Squid. A TOCTOU race condition was discovered in shadow-utils. A local attacker with write privileges in a directory removed or copied by usermod/userdel could potentially exploit this flaw, when the administrator invokes usermod/userdel, to delete or modify other files on the system. An out-of-bounds write flaw was found in the way the glibc's readdir_r() function handled file system entries longer than the NAME_MAX character constant. A remote attacker could provide a specially crafted NTFS or CIFS file system that, when processed by an application using readdir_r(), would cause that application to crash or, potentially, allow the attacker to execute arbitrary code with the privileges of the user running the application. A flaw was found in the way Apache Santuario XML Security for Java validated XML signatures. Santuario allowed a signature to specify an arbitrary canonicalization algorithm, which would be applied to the SignedInfo XML fragment. A remote attacker could exploit this to spoof an XML signature via a specially crafted XML signature block. A flaw was found in the ext4 subsystem. This vulnerability is a use after free vulnerability was found in __ext4_journal_stop(). Attackers could abuse this to allow any code which attempts to deal with the journal failure to be mishandled or not fail at all. This could lead to data corruption or crashes. It was found that ResourceServlet in Spring Framework does not sanitize the paths that have been provided properly. An attacker can utilize this flaw to conduct a directory traversal attacks. Multiple integer overflow flaws, leading to heap-based buffer overflows, were found in glibc's memory allocator functions (pvalloc, valloc, and memalign). If an application used such a function, it could cause the application to crash or, potentially, execute arbitrary code with the privileges of the user running the application. It was found that python-oauth2 did not properly verify the nonce of a signed URL. An attacker able to capture network traffic of a website using OAuth2 authentication could use this flaw to conduct replay attacks against that website. It was found that python-oauth2 did not properly generate random values for use in nonces. An attacker able to capture network traffic of a website using OAuth2 authentication could use this flaw to conduct replay attacks against that website. A flaw was found in the Linux kernel in that the aoedisk_debugfs_show() function in drivers/block/aoe/aoeblk.c allows local users to obtain some kernel address information by reading a debugfs file. This address is not useful to commit a further attack. A resource consumption issue was found in the way Xerces-J handled XML declarations. A remote attacker could use an XML document with a specially crafted declaration using a long pseudo-attribute name that, when parsed by an application using Xerces-J, would cause that application to use an excessive amount of CPU. It was found that getaddrinfo() did not limit the amount of stack memory used during name resolution. An attacker able to make an application resolve an attacker-controlled hostname or IP address could possibly cause the application to exhaust all stack memory and crash. A flaw was found in the way luci generated its configuration file. The file was created as world readable for a short period of time, allowing a local user to gain access to the authentication secrets stored in the configuration file. A flaw was found in the way the luci service was initialized. If a system administrator started the luci service from a directory that was writable to by a local user, that user could use this flaw to execute arbitrary code as the root or luci user. A flaw was found in the way the ipc_rcu_putref() function in the Linux kernel's IPC implementation handled reference counter decrementing. A local, unprivileged user could use this flaw to trigger an Out of Memory (OOM) condition and, potentially, crash the system. It was found that if a KDC served multiple realms, certain requests could cause the setup_server_realm() function to dereference a NULL pointer. A remote, unauthenticated attacker could use this flaw to crash the KDC using a specially crafted request. A flaw was found in the way the get_dumpable() function return value was interpreted in the ptrace subsystem of the Linux kernel. When 'fs.suid_dumpable' was set to 2, a local, unprivileged local user could use this flaw to bypass intended ptrace restrictions and obtain potentially sensitive information. It was found that if a KDC served multiple realms, certain requests could cause the setup_server_realm() function to dereference a NULL pointer. A remote, unauthenticated attacker could use this flaw to crash the KDC using a specially crafted request. An integer overflow flaw was found in the way the Linux kernel's Frame Buffer device implementation mapped kernel memory to user space via the mmap syscall. A local user able to access a frame buffer device file (/dev/fb*) could possibly use this flaw to escalate their privileges on the system. A buffer over-read flaw was found in the way the DateInterval class parsed interval specifications. An attacker able to make a PHP application parse a specially crafted specification using DateInterval could possibly cause the PHP interpreter to crash. A denial of service flaw was found in the header handling component of Action View. A remote attacker could send strings in specially crafted headers that would be cached indefinitely, which would result in all available system memory eventually being consumed. It was found that the number_to_currency Action View helper did not properly escape the unit parameter. An attacker could use this flaw to perform a cross-site scripting (XSS) attack on an application that uses data submitted by a user in the unit parameter. It was discovered that the internationalization component of Ruby on Rails could, under certain circumstances, return a fallback HTML string that contained user input. A remote attacker could possibly use this flaw to perform a reflective cross-site scripting (XSS) attack by providing a specially crafted input to an application using the aforementioned component. It was found that RPM wrote file contents to the target installation directory under a temporary name, and verified its cryptographic signature only after the temporary file has been written completely. Under certain conditions, the system interprets the unverified temporary file contents and extracts commands from it. This could allow an attacker to modify signed RPM files in such a way that they would execute code chosen by the attacker during package installation. It was found that the ParserPool and Decrypter classes in the OpenSAML Java implementation resolved external entities, permitting XML External Entity (XXE) attacks. A remote attacker could use this flaw to read files accessible to the user running the application server, and potentially perform other more advanced XXE attacks. It was discovered that the Apache Santuario XML Security for Java project allowed Document Type Definitions (DTDs) to be processed when applying Transforms even when secure validation was enabled. A remote attacker could use this flaw to exhaust all available memory on the system, causing a denial of service. It was discovered that the Python xmlrpclib did not restrict the size of a gzip compressed HTTP responses. A malicious XMLRPC server could cause an XMLRPC client using xmlrpclib to consume an excessive amount of memory. It was discovered that multiple Python standard library modules implementing network protocols (such as httplib or smtplib) failed to restrict sizes of server responses. A malicious server could cause a client using one of the affected modules to consume an excessive amount of memory. It was found that ruby will_paginate is vulnerable to a XSS via malformed input that cause pagination to occur on an improper boundary. This could allow an attacker with the ability to pass data to the will_paginate gem to display arbitrary HTML including scripting code within the web interface. It was identified that PicketBox/JBossSX allowed any deployed application to alter or read the underlying application server configuration and state without any authorization checks. An attacker able to deploy applications could use this flaw to circumvent security constraints applied to other applications deployed on the same system, disclose privileged information, and in certain cases allow arbitrary code execution. It was found that XStream could deserialize arbitrary user-supplied XML content, representing objects of any type. A remote attacker able to pass XML to XStream could use this flaw to perform a variety of attacks, including remote code execution in the context of the server running the XStream application. A denial of service flaw was found in the way BIND handled queries for NSEC3-signed zones. A remote attacker could use this flaw against an authoritative name server that served NCES3-signed zones by sending a specially crafted query, which, when processed, would cause named to crash. In Red Hat JBoss Enterprise Application Platform, when running under a security manager, it was possible for deployed code to get access to the Modular Service Container (MSC) service registry without any permission checks. This could allow malicious deployments to modify the internal state of the server in various ways. A flaw was found in the way TLS False Start was implemented in NSS. An attacker could use this flaw to potentially return unencrypted information from the server. It was discovered that yum-updatesd did not properly perform RPM package signature checks. When yum-updatesd was configured to automatically install updates, a remote attacker could use this flaw to install a malicious update on the target system using an unsigned RPM or an RPM signed with an untrusted key. A race condition was found in the way NSS implemented session ticket handling as specified by RFC 5077. An attacker could use this flaw to crash an application using NSS or, in rare cases, execute arbitrary code with the privileges of the user running that application. It was found that NSS accepted weak Diffie-Hellman Key exchange (DHKE) parameters. This could possibly lead to weak encryption being used in communication between the client and the server. A denial of service flaw was found in the way Apache Commons FileUpload, which is embedded in Tomcat and JBoss Web, handled small-sized buffers used by MultipartStream. A remote attacker could use this flaw to create a malformed Content-Type header for a multipart request, causing Tomcat to enter an infinite loop when processing such an incoming request. It was found that the security audit functionality logged request parameters in plain text. This may have caused passwords to be included in the audit log files when using BASIC or FORM-based authentication. A local attacker with access to audit log files could possibly use this flaw to obtain application or server authentication credentials. It was found that the security auditing functionality provided by PicketBox and JBossSX, both security frameworks for Java applications, used a world-readable audit.log file to record sensitive information. A local user could possibly use this flaw to gain access to the sensitive information in the audit.log file. It was discovered that the socket.recvfrom_into() function failed to check the size of the supplied buffer. This could lead to a buffer overflow when the function was called with an insufficiently sized buffer. It was found that Mojarra JavaServer Faces did not properly escape user-supplied content in certain circumstances. Contents of outputText tags and raw EL expressions that immediately follow script or style elements were not escaped. A remote attacker could use a specially crafted URL to execute arbitrary web script in the user's browser. A denial of service flaw was found in the way the File Information (fileinfo) extension handled indirect rules. A remote attacker could use this flaw to cause a PHP application using fileinfo to crash or consume an excessive amount of CPU. A stack-based buffer overflow was found in the way the FreeRADIUS rlm_pap module handled long password hashes. An attacker able to make radiusd process a malformed password hash could cause the daemon to crash. JBoss Fuse did not enable encrypted passwords by default in its usage of Apache Zookeeper. This permitted sensitive information disclosure via logging to local users. This issue is a vulnerability in JBoss Fuse's usage of Apache Zookeeper, not in Zookeeper itself as was previously stated. It was found that certain malformed requests caused RichFaces to leak memory. A remote, unauthenticated attacker could use this flaw to send a large number of malformed requests to a RichFaces application that uses the Atmosphere framework, leading to a denial of service (excessive memory consumption) on the application server. It was discovered that the fix for CVE-2012-3544 did not properly resolve a denial of service flaw in the way Tomcat and JBoss Web processed chunk extensions and trailing headers in chunked requests. A remote attacker could use this flaw to send an excessively long request that, when processed by Tomcat, could consume network bandwidth, CPU, and memory on the Tomcat server. Note that chunked transfer encoding is enabled by default. It was found that several application-provided XML files, such as web.xml, content.xml, *.tld, *.tagx, and *.jspx, resolved external entities, permitting XML External Entity (XXE) attacks. An attacker able to deploy malicious applications to Tomcat could use this flaw to circumvent security restrictions set by the JSM, and gain access to sensitive information on the system. Note that this flaw only affected deployments in which Tomcat is running applications from untrusted sources, such as in a shared hosting environment. It was found that previous fixes in Tomcat 6 to path parameter handling introduced a regression that caused Tomcat to not properly disable URL rewriting to track session IDs when the disableURLRewriting option was enabled. A man-in-the-middle attacker could potentially use this flaw to hijack a user's session. It was found that when Tomcat / JBoss Web processed a series of HTTP requests in which at least one request contained either multiple content-length headers, or one content-length header with a chunked transfer-encoding header, Tomcat / JBoss Web would incorrectly handle the request. A remote attacker could use this flaw to poison a web cache, perform cross-site scripting (XSS) attacks, or obtain sensitive information from other requests. It was found that Java Security Manager permissions configured via a policy file were not properly applied, causing all deployed applications to be granted the java.security.AllPermission permission. In certain cases, an attacker could use this flaw to circumvent expected security measures to perform actions which would otherwise be restricted. A flaw was found in the way the Linux kernel processed an authenticated COOKIE_ECHO chunk during the initialization of an SCTP connection. A remote attacker could use this flaw to crash the system by initiating a specially crafted SCTP handshake in order to trigger a NULL pointer dereference on the system. It was discovered that Apache Shiro authenticated users without specifying a user name or a password when used in conjunction with an LDAP back end that allowed unauthenticated binds. It was discovered that JBoss Web / Apache Tomcat did not limit the length of chunk sizes when using chunked transfer encoding. A remote attacker could use this flaw to perform a denial of service attack against JBoss Web / Apache Tomcat by streaming an unlimited quantity of data, leading to excessive consumption of server resources. A denial of service flaw was found in the way the File Information (fileinfo) extension handled search rules. A remote attacker could use this flaw to cause a PHP application using fileinfo to crash or consume an excessive amount of CPU. It was found that the get and log methods of the AgentController wrote log messages without sanitizing user input. A remote attacker could use this flaw to insert arbitrary content into the log files written to by AgentController. A NULL pointer dereference flaw was found in the gdImageCreateFromXpm() function of PHP's gd extension. A remote attacker could use this flaw to crash a PHP application using gd via a specially crafted X PixMap (XPM) file. It was found that Red Hat CloudForms exposed default routes that were reachable via HTTP(S) requests. An authenticated user could use this flaw to access potentially sensitive controllers and actions that would allow for privilege escalation. It was found that OpenSSH did not properly handle certain AcceptEnv parameter values with wildcard characters. A remote attacker could use this flaw to bypass intended environment variable restrictions. A NULL pointer dereference flaw was found in the rds_ib_laddr_check() function in the Linux kernel's implementation of Reliable Datagram Sockets (RDS). A local, unprivileged user could use this flaw to crash the system. A denial of service flaw was found in the File Information (fileinfo) extension rules for detecting AWK files. A remote attacker could use this flaw to cause a PHP application using fileinfo to consume an excessive amount of CPU. It was found that the implementation of Internationalizing Domain Names in Applications (IDNA) hostname matching in NSS did not follow the RFC 6125 recommendations. This could lead to certain invalid certificates with international characters to be accepted as valid. It was found that the secure processing feature of Xalan-Java had insufficient restrictions defined for certain properties and features. A remote attacker able to provide Extensible Stylesheet Language Transformations (XSLT) content to be processed by an application using Xalan-Java could use this flaw to bypass the intended constraints of the secure processing feature. Depending on the components available in the classpath, this could lead to arbitrary remote code execution in the context of the application server running the application that uses Xalan-Java. A denial of service flaw was found in the nova VMware driver. An authenticated user could exceed their quota by placing an image into rescue and then deleting it, causing the rescue image to be left behind. Note that only setups using the nova VMware driver were affected. It was discovered that OpenSSH clients did not correctly verify DNS SSHFP records. A malicious server could use this flaw to force a connecting client to skip the DNS SSHFP record check and require the user to perform manual host verification of the DNS SSHFP record. A Cross-Site Request Forgery (CSRF) flaw was found in the oVirt REST API. A remote attacker could provide a specially crafted web page that, when visited by a user with a valid REST API session, would allow the attacker to trigger calls to the oVirt REST API. It was found that the oVirt web admin interface did not include the HttpOnly flag when setting session IDs with the Set-Cookie header. This flaw could make it is easier for a remote attacker to hijack an oVirt web admin session by leveraging a cross-site scripting (XSS) vulnerability. It was discovered that luci stored usernames and passwords in session cookies. This issue prevented the session inactivity timeout feature from working correctly, and allowed attackers able to get access to a session cookie to obtain the victim's authentication credentials. A flaw was found in the way httpd handled HTTP Trailer headers when processing requests using chunked encoding. A malicious client could use Trailer headers to set additional HTTP headers after header processing was performed by other modules. This could, for example, lead to a bypass of header restrictions defined with mod_headers. A flaw was found in the way the Linux kernel performed forking inside of a transaction. A local, unprivileged user on a PowerPC system that supports transactional memory could use this flaw to crash the system. It was found that a remote attacker could use a race condition flaw in the ath_tx_aggr_sleep() function to crash the system by creating large network traffic on the system's Atheros 9k wireless network adapter. A NULL pointer dereference flaw was found in the rds_iw_laddr_check() function in the Linux kernel's implementation of Reliable Datagram Sockets (RDS). A local, unprivileged user could use this flaw to crash the system. A race condition flaw was found in the way the Linux kernel's mac80211 subsystem implementation handled synchronization between TX and STA wake-up code paths. A remote attacker could use this flaw to crash the system. It was found that Jolokia was vulnerable to Cross-Site Request Forgery (CSRF) attacks. A remote attacker could provide a specially crafted web page that, when visited by a user logged in to Jolokia, could allow the attacker to execute arbitrary methods on MBeans exposed via JMX. It was found that RBAC policies were not enforced in certain methods of the OpenStack Compute EC2 (Amazon Elastic Compute Cloud) API. A remote attacker could use this flaw to escalate their privileges beyond the user group they were originally restricted to. Note that only certain setups using non-default RBAC rules for OpenStack Compute were affected. An information disclosure flaw was found in the way OpenSSL handled TLS and DTLS Heartbeat Extension packets. A malicious TLS or DTLS client or server could send a specially crafted TLS or DTLS Heartbeat packet to disclose a limited portion of memory per request from a connected client or server. Note that the disclosed portions of memory could potentially include sensitive information such as private keys. It was found that Teiid SQL/XML permitted XML eXternal Entity (XXE) attacks. If a REST endpoint was deployed, a remote attacker could submit a request containing an external XML entity that, when resolved, allowed that attacker to read files on the application server in the context of the user running that server. It was found that Odata4j permitted XML eXternal Entity (XXE) attacks. If a REST endpoint was deployed, a remote attacker could submit a request containing an external XML entity that, when resolved, allowed that attacker to read files on the application server in the context of the user running that server. It was found that Cumin did not set the HttpOnly flag on session cookies. This could allow a malicious script to access the session cookie. A flaw was found in the keystone V3 API. An attacker could send a single request with the same authentication method multiple times, possibly leading to a denial of service due to generating excessive load with minimal requests. Only keystone setups with the V3 API enabled were affected by this issue. A use-after-free flaw was found in the way the ping_init_sock() function of the Linux kernel handled the group_info reference counter. A local, unprivileged user could use this flaw to crash the system or, potentially, escalate their privileges on the system. A cross-site scripting (XSS) flaw was found in the CUPS web interface. An attacker could use this flaw to perform a cross-site scripting attack against users of the CUPS web interface. It was found that libvirt passes the XML_PARSE_NOENT flag when parsing XML documents using the libxml2 library, in which case all XML entities in the parsed documents are expanded. A user able to force libvirtd to parse an XML document with an entity pointing to a file could use this flaw to read the contents of that file (limited to libvirt as shipped with Red Hat Enterprise Linux 7); parsing an XML document with an entity pointing to a special file that blocks on read access could cause libvirtd to hang indefinitely, resulting in a denial of service on the system. It was found that the org.apache.catalina.servlets.DefaultServlet implementation in JBoss Web / Apache Tomcat allowed the definition of XML External Entities (XXEs) in provided XSLTs. A malicious application could use this to circumvent intended security restrictions to disclose sensitive information. It was discovered that the /etc/sysconfig/virt-who configuration file, which may contain hypervisor authentication credentials, was world-readable. A local user could use this flaw to obtain authentication credentials from this file. It was discovered that libxml2 loaded external parameter entities even when entity substitution was disabled. A remote attacker able to provide a specially crafted XML file to an application linked against libxml2 could use this flaw to conduct XML External Entity (XXE) attacks, possibly resulting in a denial of service or an information leak on the system. A flaw was found in the WebSocket08FrameDecoder implementation that could allow a remote attacker to trigger an Out Of Memory Exception by issuing a series of TextWebSocketFrame and ContinuationWebSocketFrames. Depending on the server configuration, this could lead to a denial of service. It was found that the ServerTrustManager in the Smack XMPP API did not verify basicConstraints and nameConstraints in X.509 certificate chains. A man-in-the-middle attacker could use this flaw to spoof servers and obtain sensitive information. It was found that the ParseRoster component in the Smack XMPP API did not verify the From attribute of a roster-query IQ stanza. A remote attacker could use this flaw to spoof IQ responses. It was found that the try_to_unmap_cluster() function in the Linux kernel's Memory Managment subsystem did not properly handle page locking in certain cases, which could potentially trigger the BUG_ON() macro in the mlock_vma_page() function. A local, unprivileged user could use this flaw to crash the system. A denial of service flaw was found in the way Apache CXF created error messages for certain POST requests. A remote attacker could send a specially crafted request which, when processed by an application using Apache CXF, could consume an excessive amount of memory on the system, possibly triggering an Out Of Memory (OOM) error. It was found that when a large invalid SOAP message was processed by Apache CXF, it could be saved to a temporary file in the /tmp directory. A remote attacker could send a specially crafted SOAP message that, when processed by an application using Apache CXF, would use an excessive amount of disk space, possibly causing a denial of service. It was found that the SecurityTokenService (STS), provided as a part of Apache CXF, could under certain circumstances accept invalid SAML tokens as valid. A remote attacker could use a specially crafted SAML token to gain access to an application that uses STS for validation of SAML tokens. It was discovered that UsernameTokens were sent in plain text by an Apache CXF client that used a Symmetric EncryptBeforeSigning password policy. A man-in-the-middle attacker could use this flaw to obtain the user name and password used by the client application using Apache CXF. It was found that the permission checks performed by the Linux kernel when a netlink message was received were not sufficient. A local, unprivileged user could potentially bypass these restrictions by passing a netlink socket as stdout or stderr to a more privileged process and altering the output of this process. A flaw was found in the way the Linux kernel's floppy driver handled user space provided data in certain error code paths while processing FDRAWCMD IOCTL commands. A local user with write access to /dev/fdX could use this flaw to free (using the kfree() function) arbitrary kernel memory. (CVE-2014-1737, Important) It was found that the Linux kernel's floppy driver leaked internal kernel memory addresses to user space during the processing of the FDRAWCMD IOCTL command. A local user with write access to /dev/fdX could use this flaw to obtain information about the kernel heap arrangement. (CVE-2014-1738, Low) Note: A local user with write access to /dev/fdX could use these two flaws (CVE-2014-1737 in combination with CVE-2014-1738) to escalate their privileges on the system. A flaw was found in the way the Linux kernel's floppy driver handled user space provided data in certain error code paths while processing FDRAWCMD IOCTL commands. A local user with write access to /dev/fdX could use this flaw to free (using the kfree() function) arbitrary kernel memory. (CVE-2014-1737, Important) It was found that the Linux kernel's floppy driver leaked internal kernel memory addresses to user space during the processing of the FDRAWCMD IOCTL command. A local user with write access to /dev/fdX could use this flaw to obtain information about the kernel heap arrangement. (CVE-2014-1738, Low) Note: A local user with write access to /dev/fdX could use these two flaws (CVE-2014-1737 in combination with CVE-2014-1738) to escalate their privileges on the system. A flaw was found in the way the Linux kernel's futex subsystem handled reference counting when requeuing futexes during futex_wait(). A local, unprivileged user could use this flaw to zero out the reference counter of an inode or an mm struct that backs up the memory area of the futex, which could lead to a use-after-free flaw, resulting in a system crash or, potentially, privilege escalation. A directory traversal flaw was found in the way Ruby on Rails handled wildcard segments in routes with implicit rendering. A remote attacker could use this flaw to retrieve arbitrary local files accessible to a Ruby on Rails application using the aforementioned routes via a specially crafted request. A denial of service flaw was found in the way the File Information (fileinfo) extension parsed certain Composite Document Format (CDF) files. A remote attacker could use this flaw to crash a PHP application using fileinfo via a specially crafted CDF file. A flaw was found in the way seunshare, a utility for running executables under a different security context, used the capng_lock functionality of the libcap-ng library. The subsequent invocation of suid root binaries that relied on the fact that the setuid() system call, among others, also sets the saved set-user-ID when dropping the binaries' process privileges, could allow a local, unprivileged user to potentially escalate their privileges on the system. Note: the fix for this issue is the kernel part of the overall fix, and introduces the PR_SET_NO_NEW_PRIVS functionality and the related SELinux exec transitions support. A use-after-free flaw was found in the way libXfont processed certain font files when attempting to add a new directory to the font path. A malicious, local user could exploit this issue to potentially execute arbitrary code with the privileges of the X.Org server. Multiple out-of-bounds write flaws were found in the way libXfont parsed replies received from an X.org font server. A malicious X.org server could cause an X client to crash or, possibly, execute arbitrary code with the privileges of the X.Org server. Multiple out-of-bounds write flaws were found in the way libXfont parsed replies received from an X.org font server. A malicious X.org server could cause an X client to crash or, possibly, execute arbitrary code with the privileges of the X.Org server. An integer overflow flaw was found in the QEMU block driver for QCOW version 1 disk images. A user able to alter the QEMU disk image files loaded by a guest could use this flaw to corrupt QEMU process memory on the host, which could potentially result in arbitrary code execution on the host with the privileges of the QEMU process. An integer overflow flaw was found in the QEMU block driver for QCOW version 1 disk images. A user able to alter the QEMU disk image files loaded by a guest could use this flaw to corrupt QEMU process memory on the host, which could potentially result in arbitrary code execution on the host with the privileges of the QEMU process. A NULL pointer dereference flaw was found in the way the futex_wait_requeue_pi() function of the Linux kernel's futex subsystem handled the requeuing of certain Priority Inheritance (PI) futexes. A local, unprivileged user could use this flaw to crash the system. A denial of service flaw was found in the way the File Information (fileinfo) extension parsed certain Composite Document Format (CDF) files. A remote attacker could use this flaw to crash a PHP application using fileinfo via a specially crafted CDF file. A denial of service flaw was found in the way the File Information (fileinfo) extension parsed certain Composite Document Format (CDF) files. A remote attacker could use this flaw to crash a PHP application using fileinfo via a specially crafted CDF file. It was discovered that a user could temporarily be able to see the URL of a provider template used in another tenant. If the template itself could be accessed, then additional information could be leaked that would otherwise not be visible. A denial of service flaw was found in the way the sys_recvfile() function of nmbd, the NetBIOS message block daemon, processed non-blocking sockets. An attacker could send a specially crafted packet that, when processed, would cause nmbd to enter an infinite loop and consume an excessive amount of CPU time. A use-after-free vulnerability in sys_ioprio_get() was found due to get_task_ioprio() accessing the task->io_context without holding the task lock and could potentially race with exit_io_context(), leading to a use-after-free. It was found that the implementation of the GTNSubjectCreatingInterceptor class in gatein-wsrp was not thread safe. For a specific WSRP endpoint, under high-concurrency scenarios or scenarios where SOAP messages take long to execute, it was possible for an unauthenticated remote attacker to gain privileged information if WS-Security is enabled for the WSRP Consumer, and the endpoint in question is being used by a privileged user. It was found that the org.jboss.seam.web.AuthenticationFilter class implementation did not properly use Seam logging. A remote attacker could send specially crafted authentication headers to an application, which could result in arbitrary code execution with the privileges of the user running that application. It was found that mod_wsgi did not properly drop privileges if the call to setuid() failed. If mod_wsgi was set up to allow unprivileged users to run WSGI applications, a local user able to run a WSGI application could possibly use this flaw to escalate their privileges on the system. Note: mod_wsgi is not intended to provide privilege separation for WSGI applications. Systems relying on mod_wsgi to limit or sandbox the privileges of mod_wsgi applications should migrate to a different solution with proper privilege separation. A flaw was found in the way Samba created responses for certain authenticated client requests when a shadow-copy VFS module was enabled. An attacker able to send an authenticated request could use this flaw to disclose limited portions of memory per each request. It was found that JBoss Web / Apache Tomcat did not check for overflowing values when parsing request content length headers. A remote attacker could use this flaw to perform an HTTP request smuggling attack on a JBoss Web / Apache Tomcat server located behind a reverse proxy that processed the content length header correctly. It was found that, in certain circumstances, it was possible for a malicious web application to replace the XML parsers used by JBoss Web / Apache Tomcat to process XSLTs for the default servlet, JSP documents, tag library descriptors (TLDs), and tag plug-in configuration files. The injected XML parser(s) could then bypass the limits imposed on XML external entities and/or gain access to the XML files processed for other web applications deployed on the same JBoss Web / Apache Tomcat instance. It was found that the fix for CVE-2013-2133 was incomplete: the JAX-WS handlers were being executed for outbound messages even when authorization had failed. A remote attacker who is authorized to access the EJB class, could invoke a JAX-WS handler which they were not authorized to invoke. A directory traveral flaw was found in the way glibc loaded locale files. An attacker able to make an application use a specially crafted locale name value (for example, specified in an LC_* environment variable) could possibly use this flaw to execute arbitrary code with the privileges of that application. An out-of-bounds memory access flaw was found in the Linux kernel's system call auditing implementation. On a system with existing audit rules defined, a local, unprivileged user could use this flaw to leak kernel memory to user space or, potentially, crash the system. A flaw was found in the way GnuTLS parsed session IDs from ServerHello messages of the TLS/SSL handshake. A malicious server could use this flaw to send an excessively long session ID value, which would trigger a buffer overflow in a connecting TLS/SSL client application using GnuTLS, causing the client application to crash or, possibly, execute arbitrary code. It was found that OpenSSL clients and servers could be forced, via a specially crafted handshake packet, to use weak keying material for communication. A man-in-the-middle attacker could use this flaw to decrypt and modify traffic between a client and a server. A denial of service flaw was found in the way OpenSSL handled certain DTLS ServerHello requests. A specially crafted DTLS handshake packet could cause a DTLS client using OpenSSL to crash. A flaw was found in the way the Linux kernel's futex subsystem handled the requeuing of certain Priority Inheritance (PI) futexes. A local, unprivileged user could use this flaw to escalate their privileges on the system. It was found that the isCallerInRole() method of the SimpleSecurityManager did not correctly check caller roles. A remote, authenticated attacker could use this flaw to circumvent the caller check in applications that use black list access control based on caller roles. A flaw was found in the way Linux kernel's Transparent Huge Pages (THP) implementation handled non-huge page migration. A local, unprivileged user could use this flaw to crash the kernel by migrating transparent hugepages. A flaw was found in keystone's chained delegation. A trustee able to create a delegation from a trust or an OAuth token could misuse identity impersonation to bypass the enforced scope, possibly allowing them to obtain elevated privileges to the trustor's projects and roles. A denial of service flaw was found in the way the File Information (fileinfo) extension parsed certain Composite Document Format (CDF) files. A remote attacker could use this flaw to crash a PHP application using fileinfo via a specially crafted CDF file. A denial of service flaw was found in the way the File Information (fileinfo) extension parsed certain Composite Document Format (CDF) files. A remote attacker could use this flaw to crash a PHP application using fileinfo via a specially crafted CDF file. A buffer overflow flaw was found in the way the File Information (fileinfo) extension processed certain Pascal strings. A remote attacker able to make a PHP application using fileinfo convert a specially crafted Pascal string provided by an image file could cause that application to crash. It was found that the default context parameters as provided to RESTEasy deployments by JBoss EAP did not explicitly disable external entity expansion for RESTEasy. A remote attacker could use this flaw to perform XML External Entity (XXE) attacks on RESTEasy applications accepting XML input. An out-of-bounds write flaw was found in NSPR. A remote attacker could potentially use this flaw to crash an application using NSPR or, possibly, execute arbitrary code with the privileges of the user running that application. This NSPR flaw was not exposed to web content in any shipped version of Firefox. A denial of service flaw was found in the way the File Information (fileinfo) extension parsed certain Composite Document Format (CDF) files. A remote attacker could use this flaw to crash a PHP application using fileinfo via a specially crafted CDF file. It was found that the fix for CVE-2012-0818 was incomplete: external parameter entities were not disabled when the resteasy.document.expand.entity.references parameter was set to false. A remote attacker able to send XML requests to a RESTEasy endpoint could use this flaw to read files accessible to the user running the application server, and potentially perform other more advanced XXE attacks. An information leak flaw was found in the RAM Disks Memory Copy (rd_mcp) backend driver of the iSCSI Target subsystem of the Linux kernel. A privileged user could use this flaw to leak the contents of kernel memory to an iSCSI initiator remote client. It was discovered that smbd, the Samba file server daemon, did not properly handle certain files that were stored on the disk and used a valid Unicode character in the file name. An attacker able to send an authenticated non-Unicode request that attempted to read such a file could cause smbd to crash. A heap-based buffer overflow flaw was found in the way PHP parsed DNS TXT records. A malicious DNS server or a man-in-the-middle attacker could possibly use this flaw to execute arbitrary code as the PHP interpreter if a PHP application used the dns_get_record() function to perform a DNS query. It was discovered that the ChunkedInputFilter in Tomcat did not fail subsequent attempts to read input after malformed chunked encoding was detected. A remote attacker could possibly use this flaw to make Tomcat process part of the request body as new request, or cause a denial of service. An information leak flaw was found in the way the Linux kernel handled media device enumerate entities IOCTL requests. A local user able to access the /dev/media0 device file could use this flaw to leak kernel memory bytes. It was found that the Spring Framework did not, by default, disable the resolution of URI references in a DTD declaration when processing user-provided XML documents. By observing differences in response times, an attacker could identify valid IP addresses on the internal network with functioning web servers. It was found that the Xen hypervisor implementation did not properly clean memory pages previously allocated by the hypervisor. A privileged guest user could potentially use this flaw to read data relating to other guests or the hypervisor itself. Multiple insecure temporary file use flaws were found in the way the ppc64-diag utility created certain temporary files. A local attacker could possibly use either of these flaws to perform a symbolic link attack and overwrite arbitrary files with the privileges of the user running ppc64-diag, or obtain sensitive information from the temporary files. Multiple insecure temporary file use flaws were found in the way the ppc64-diag utility created certain temporary files. A local attacker could possibly use either of these flaws to perform a symbolic link attack and overwrite arbitrary files with the privileges of the user running ppc64-diag, or obtain sensitive information from the temporary files. A flaw was found in the way the snap utility of powerpc-utils generated an archive containing a configuration snapshot of a service. A local attacker could obtain sensitive information from the generated archive such as plain text passwords. It was found that Swift did not escape all HTTP header values, allowing data to be injected into the responses sent from the Swift server. This could lead to cross-site scripting attacks (and possibly other impacts) if a user were tricked into clicking on a malicious URL. It was found that LibreOffice documents executed macros unconditionally, without user approval, when these documents were opened using LibreOffice. An attacker could use this flaw to execute arbitrary code as the user running LibreOffice by embedding malicious VBA scripts in the document as macros. A race condition flaw was found in the way the Linux kernel's mmap(2), madvise(2), and fallocate(2) system calls interacted with each other while operating on virtual memory file system files. A local user could use this flaw to cause a denial of service. A flaw was found in the way the cups-browsed daemon interpreted the "BrowseAllow" directive in the cups-browsed.conf file. An attacker able to add a malformed "BrowseAllow" directive to the cups-browsed.conf file could use this flaw to bypass intended access restrictions. An out-of-bounds read flaw was found in the way the process_browse_data() function of cups-browsed handled certain browse packets. A remote attacker could send a specially crafted browse packet that, when processed by cups-browsed, would crash the cups-browsed daemon. A type confusion issue was found in the SPL ArrayObject and SPLObjectStorage classes' unserialize() method. A remote attacker able to submit specially crafted input to a PHP application, which would then unserialize this input using one of the aforementioned methods, could use this flaw to execute arbitrary code with the privileges of the user running that PHP application. An integer overflow flaw was found in the way the lzo library decompressed certain archives compressed with the LZO algorithm. An attacker could create a specially crafted LZO-compressed input that, when decompressed by an application using the lzo library, would cause that application to crash or, potentially, execute arbitrary code. A side-channel timing attack flaw was found in Nova. An attacker could possibly use this flaw to guess valid instance ID signatures, giving them access to details of another instance, by analyzing the response times of requests for instance metadata. This issue only affected configurations that proxy metadata requests via Neutron. JBoss Application Server 5 and supported Red Hat JBoss 5.x products contain JBoss Remoting, which includes a partial implementation of the JMX remoting specification JSR 160. This implementation is provided in jmx-remoting.sar, which is deployed by default in unsupported community releases of JBoss Application Server 5.x. This implementation does not implement security as defined in JSR 160, and therefore does not apply any authentication or authorization constraints. A remote attacker could use this flaw to potentially execute arbitrary code on a vulnerable server. All of the supported Red Hat JBoss 5.x products are not affected by this issue in their default configuration. These products are only vulnerable if JMX remoting is enabled by manually deploying jmx-remoting.sar from the jboss-as/docs/examples directory. Unsupported community releases of JBoss Application Server 5.x are affected. All users of the standalone JBoss Remoting project are also affected. For more information, see https://access.redhat.com/solutions/1120423 A flaw was found in the way keystone handled trusts. A trustee could use an out-of-scope project ID to gain unauthorized access to a project if the trustor had the required roles for that requested project. A flaw was found in the way the json module handled negative index argument passed to certain functions (such as raw_decode()). An attacker able to control index value passed to one of the affected functions could possibly use this flaw to disclose portions of the application memory. Multiple information leak flaws were found in the way conga processed luci site extension-related URL requests. A remote, unauthenticated attacker could issue a specially crafted HTTP request that, when processed, would result in unauthorized information disclosure. It was discovered that various components in the luci site extension-related URLs were not properly restricted to administrative users. A remote, authenticated attacker could escalate their privileges to perform certain actions that should be restricted to administrative users, such as adding users and systems, and viewing log data. It was found that authentication tokens were not properly sanitized from the message queue by the notifier middleware. An attacker with read access to the message queue could possibly use this flaw to intercept an authentication token and gain elevated privileges. Note that all services using the notifier middleware configured after the auth_token middleware pipeline were affected. It was found that the implementation of the org.picketlink.common.util.DocumentUtil.getDocumentBuilderFactory() method provided a DocumentBuilderFactory that would expand entity references. A remote, unauthenticated attacker could use this flaw to read files accessible to the user running the application server, and potentially perform other more advanced XXE attacks. An information leak flaw was found in the way the Linux kernel's Advanced Linux Sound Architecture (ALSA) implementation handled access of the user control's state. A local, privileged user could use this flaw to leak kernel memory to user space. A use-after-free flaw was found in the way the Linux kernel's Advanced Linux Sound Architecture (ALSA) implementation handled user controls. A local, privileged user could use this flaw to crash the system. A use-after-free flaw was found in the way the Linux kernel's Advanced Linux Sound Architecture (ALSA) implementation handled user controls. A local, privileged user could use this flaw to crash the system. A use-after-free flaw was found in the way the Linux kernel's Advanced Linux Sound Architecture (ALSA) implementation handled user controls. A local, privileged user could use this flaw to crash the system. An integer overflow flaw was found in the way the Linux kernel's Advanced Linux Sound Architecture (ALSA) implementation handled user controls. A local, privileged user could use this flaw to crash the system. It was discovered that the CGIHTTPServer module incorrectly handled URL encoded paths. A remote attacker could use this flaw to execute scripts outside of the cgi-bin directory, or disclose source of scripts in the cgi-bin directory. An integer overflow flaw was found in the way the lzo1x_decompress_safe() function of the Linux kernel's LZO implementation processed Literal Runs. A local attacker could, in extremely rare cases, use this flaw to crash the system or, potentially, escalate their privileges on the system. It was found that Linux kernel's ptrace subsystem did not properly sanitize the address-space-control bits when the program-status word (PSW) was being set. On IBM S/390 systems, a local, unprivileged user could use this flaw to set address-space-control bits to the kernel space, and thus gain read and write access to kernel memory. An integer underflow flaw was found in the way the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation processed certain COOKIE_ECHO packets. By sending a specially crafted SCTP packet, a remote attacker could use this flaw to prevent legitimate connections to a particular SCTP server socket to be made. It was discovered that Active Record did not properly quote values of the bitstring type attributes when using the PostgreSQL database adapter. A remote attacker could possibly use this flaw to conduct an SQL injection attack against applications using Active Record. It was discovered that Active Record did not properly quote values of the range type attributes when using the PostgreSQL database adapter. A remote attacker could possibly use this flaw to conduct an SQL injection attack against applications using Active Record. A NULL pointer dereference flaw was found in the way the Linux kernel's networking implementation handled logging while processing certain invalid packets coming in via a VxLAN interface. A remote attacker could use this flaw to crash the system by sending a specially crafted packet to such an interface. It was discovered that CUPS allowed certain users to create symbolic links in certain directories under /var/cache/cups/. A local user with the 'lp' group privileges could use this flaw to read the contents of arbitrary files on the system or, potentially, escalate their privileges on the system. It was found that the JClouds scriptbuilder Statements class wrote a temporary file to a predictable location. An attacker could use this flaw to access sensitive data, cause a denial of service, or perform other attacks. Multiple flaws were found in the File Information (fileinfo) extension regular expression rules for detecting various files. A remote attacker could use either of these flaws to cause a PHP application using fileinfo to consume an excessive amount of CPU. It was found that the Linux kernel's ptrace subsystem allowed a traced process' instruction pointer to be set to a non-canonical memory address without forcing the non-sysret code path when returning to user space. A local, unprivileged user could use this flaw to crash the system or, potentially, escalate their privileges on the system. Note: The CVE-2014-4699 issue only affected systems using an Intel CPU. A buffer over-read flaw was found in the way MIT Kerberos handled certain requests. A remote, unauthenticated attacker who is able to inject packets into a client or server application's GSSAPI session could use this flaw to crash the application. A race condition was found in the way NSS verified certain certificates. A remote attacker could use this flaw to crash an application using NSS or, possibly, execute arbitrary code with the privileges of the user running that application. A type confusion issue was found in PHP's phpinfo() function. A malicious script author could possibly use this flaw to disclose certain portions of server memory. A flaw was found that would lead to Cross-Site Request Forgery (CSRF) attacks. A flaw was found in the Linux kernel's implementation of seq_file where a local attacker could manipulate memory in the put() function pointer. This could lead to memory corruption and possible privileged escalation. A denial of service flaw was found in neutron's handling of allowed address pairs. As there was no enforced quota on the amount of allowed address pairs, a sufficiently authorized user could possibly create a large number of firewall rules, impacting performance or potentially rendering a compute node unusable. A race condition issue leading to a use-after-free flaw was found in the way the raw packet sockets implementation in the Linux kernel networking subsystem handled synchronization while creating the TPACKET_V3 ring buffer. A local user able to open a raw packet socket (requires the CAP_NET_RAW capability) could use this flaw to elevate their privileges on the system. A flaw was found in the way the pppol2tp_setsockopt() and pppol2tp_getsockopt() functions in the Linux kernel's PPP over L2TP implementation handled requests with a non-SOL_PPPOL2TP socket option level. A local, unprivileged user could use this flaw to escalate their privileges on the system. A use-after-free flaw was found in the way PHP handled certain ArrayIterators. A malicious script author could possibly use this flaw to disclose certain portions of server memory. A use-after-free flaw was found in the way PHP handled certain Standard PHP Library (SPL) Iterators. A malicious script author could possibly use this flaw to disclose certain portions of server memory. It was discovered that the implementation of org.hibernate.validator.util.ReflectionHelper together with the permissions required to run Hibernate Validator under the Java Security Manager could allow a malicious application deployed in the same application container to execute several actions with escalated privileges, which might otherwise not be possible. This flaw could be used to perform various attacks, including but not restricted to, arbitrary code execution in systems that are otherwise secured by the Java Security Manager. A buffer over-read flaw was found in the way MIT Kerberos handled certain requests. A remote, unauthenticated attacker who is able to inject packets into a client or server application's GSSAPI session could use this flaw to crash the application. A denial of service flaw was found in the way httpd's mod_cgid module executed CGI scripts that did not read data from the standard input. A remote attacker could submit a specially crafted request that would cause the httpd child process to hang indefinitely. A denial of service flaw was found in the mod_proxy httpd module. A remote attacker could send a specially crafted request to a server configured as a reverse proxy using a threaded Multi-Processing Modules (MPM) that would cause the httpd child process to crash. A denial of service flaw was found in the way httpd's mod_deflate module handled request body decompression (configured via the "DEFLATE" input filter). A remote attacker able to send a request whose body would be decompressed could use this flaw to consume an excessive amount of system memory and CPU on the target system. A race condition flaw, leading to heap-based buffer overflows, was found in the mod_status httpd module. A remote attacker able to access a status page served by mod_status on a server using a threaded Multi-Processing Module (MPM) could send a specially crafted request that would cause the httpd child process to crash or, possibly, allow the attacker to execute arbitrary code with the privileges of the "apache" user. A NULL pointer dereference flaw was found in the mod_cache httpd module. A malicious HTTP server could cause the httpd child process to crash when the Apache HTTP Server was used as a forward proxy with caching. Various command-execution flaws were found in the Snoopy library included with Nagios. These flaws allowed remote attackers to execute arbitrary commands by manipulating Nagios HTTP headers. Various command-execution flaws were found in the Snoopy library included with Nagios. These flaws allowed remote attackers to execute arbitrary commands by manipulating Nagios HTTP headers. Various command-execution flaws were found in the Snoopy library included with Nagios. These flaws allowed remote attackers to execute arbitrary commands by manipulating Nagios HTTP headers. A double-free flaw was found in the MIT Kerberos SPNEGO initiators. An attacker able to spoof packets to appear as though they are from an GSSAPI acceptor could use this flaw to crash a client application that uses MIT Kerberos. A NULL pointer dereference flaw was found in the MIT Kerberos SPNEGO acceptor for continuation tokens. A remote, unauthenticated attacker could use this flaw to crash a GSSAPI-enabled server application. It was found that the oVirt storage back end did not wipe memory snapshots when VMs were deleted, even if wipe-after-delete (WAD) was enabled for the VM's disks. A remote attacker with credentials to create a new VM could use this flaw to potentially access the contents of memory snapshots in an uninitialized storage volume, possibly leading to the disclosure of sensitive information. It was found that polkit-qt handled authorization requests with PolicyKit via a D-Bus API that is vulnerable to a race condition. A local user could use this flaw to bypass intended PolicyKit authorizations. It was discovered that CUPS allowed certain users to create symbolic links in certain directories under /var/cache/cups/. A local user with the 'lp' group privileges could use this flaw to read the contents of arbitrary files on the system or, potentially, escalate their privileges on the system. It was found that rhevm-log-collector called sosreport with the PostgreSQL database password passed as a command line parameter. A local attacker could read this password by monitoring a process listing. The password would also be written to a log file, which could potentially be read by a local attacker. A flaw was found in the way the Linux kernel's VFS subsystem handled reference counting when performing unmount operations on symbolic links. A local, unprivileged user could use this flaw to exhaust all available memory on the system or, potentially, trigger a use-after-free error, resulting in a system crash or privilege escalation. It was found that when replication was enabled for each attribute in Red Hat Directory Server / 389 Directory Server, which is the default configuration, the server returned replicated metadata when the directory was searched while debugging was enabled. A remote attacker could use this flaw to disclose potentially sensitive information. A flaw was found in the Linux kernel's implementation of XFS file attributes. Two memory leaks were detected in xfs_attr_shortform_list and xfs_attr3_leaf_list_int when running a docker container backed by xfs/overlay2. A dedicated attacker could possible exhaust all memory and create a denial of service situation. A NULL pointer dereference flaw was found in the way the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation handled simultaneous connections between the same hosts. A remote attacker could use this flaw to crash the system. It was discovered that the default configuration of Elasticsearch enabled dynamic scripting, allowing a remote attacker to execute arbitrary MVEL expressions and Java code via the source parameter passed to _search. A denial of service flaw was found in the way snmptrapd handled certain SNMP traps when started with the "-OQ" option. If an attacker sent an SNMP trap containing a variable with a NULL type where an integer variable type was expected, it would cause snmptrapd to crash. It was discovered that, when loading XML/RSDL documents, the oVirt Engine back end module used an insecure DocumentBuilderFactory. A remote, authenticated attacker could use this flaw to read files accessible to the user running the ovirt-engine server, and potentially perform other more advanced XML External Entity (XXE) attacks. It was found that the redhat-upgrade-tool did not check GPG signatures on downloaded and installed packages during the upgrade process. A heap-based buffer overflow flaw was found in Samba's NetBIOS message block daemon (nmbd). An attacker on the local network could use this flaw to send specially crafted packets that, when processed by nmbd, could possibly lead to arbitrary code execution with root privileges. It was discovered that Subversion clients retrieved cached authentication credentials using the MD5 hash of the server realm string without also checking the server's URL. A malicious server able to provide a realm that triggers an MD5 collision could possibly use this flaw to obtain the credentials for a different realm. It was found that libvirt passes the XML_PARSE_NOENT flag when parsing XML documents using the libxml2 library, in which case all XML entities in the parsed documents are expanded. A user able to force libvirtd to parse an XML document with an entity pointing to a file could use this flaw to read the contents of that file (limited to libvirt as shipped with Red Hat Enterprise Linux 7); parsing an XML document with an entity pointing to a special file that blocks on read access could cause libvirtd to hang indefinitely, resulting in a denial of service on the system. It was found that the Command Line Interface, as provided by Red Hat Enterprise Application Platform, created a history file named .jboss-cli-history in the user's home directory with insecure default file permissions. This could allow a malicious local user to gain information otherwise not accessible to them. It was found that SSLSocket in Smack did not perform hostname verification. An attacker could redirect traffic between an application and an XMPP server by providing a valid certificate for a domain under the attacker's control. It was discovered that the OBJ_obj2txt() function could fail to properly NUL-terminate its output. This could possibly cause an application using OpenSSL functions to format fields of X.509 certificates to disclose portions of its memory. A race condition was found in the way OpenSSL handled ServerHello messages with an included Supported EC Point Format extension. A malicious server could possibly use this flaw to cause a multi-threaded TLS/SSL client using OpenSSL to write into freed memory, causing the client to crash or execute arbitrary code. A flaw was discovered in the way OpenSSL handled DTLS packets. A remote attacker could use this flaw to cause a DTLS server or client using OpenSSL to crash or use excessive amounts of memory. A flaw was discovered in the way OpenSSL handled DTLS packets. A remote attacker could use this flaw to cause a DTLS server or client using OpenSSL to crash or use excessive amounts of memory. A flaw was discovered in the way OpenSSL handled DTLS packets. A remote attacker could use this flaw to cause a DTLS server or client using OpenSSL to crash or use excessive amounts of memory. A NULL pointer dereference flaw was found in the way OpenSSL performed a handshake when using the anonymous Diffie-Hellman (DH) key exchange. A malicious server could cause a DTLS client using OpenSSL to crash if that client had anonymous DH cipher suites enabled. A flaw was found in the way OpenSSL handled fragmented handshake packets. A man-in-the-middle attacker could use this flaw to force a TLS/SSL server using OpenSSL to use TLS 1.0, even if both the client and the server supported newer protocol versions. A buffer overflow was found in the KADM5 administration server (kadmind) when it was used with an LDAP back end for the KDC database. A remote, authenticated attacker could potentially use this flaw to execute arbitrary code on the system running kadmind. It was found that the fix for CVE-2012-1571 was incomplete; the File Information (fileinfo) extension did not correctly parse certain Composite Document Format (CDF) files. A remote attacker could use this flaw to crash a PHP application using fileinfo via a specially crafted CDF file. It was discovered that CUPS allowed certain users to create symbolic links in certain directories under /var/cache/cups/. A local user with the 'lp' group privileges could use this flaw to read the contents of arbitrary files on the system or, potentially, escalate their privileges on the system. It was discovered that CUPS allowed certain users to create symbolic links in certain directories under /var/cache/cups/. A local user with the 'lp' group privileges could use this flaw to read the contents of arbitrary files on the system or, potentially, escalate their privileges on the system. It was found that the fix for CVE-2012-6153 was incomplete: the code added to check that the server hostname matches the domain name in a subject's Common Name (CN) field in X.509 certificates was flawed. A man-in-the-middle attacker could use this flaw to spoof an SSL server using a specially crafted X.509 certificate. It was discovered that luci used eval() on inputs containing strings from the cluster configuration file when generating its web pages. An attacker with privileges to create or edit the cluster configuration could use this flaw to execute arbitrary code as the luci user on a host running luci. A persistent cross-site scripting (XSS) flaw was found in the horizon host aggregate interface. A user with sufficient privileges to add a host aggregate could potentially use this flaw to capture the credentials of another user. A stored cross-site scripting (XSS) flaw was found in the way spacewalk-java displayed log files. By sending a specially crafted request to Satellite, a remote attacker could embed HTML content into the log file, allowing them to inject malicious content into the web page that is used to view that log file. It was found that the fix for CVE-2012-5783 was incomplete: the code added to check that the server host name matches the domain name in a subject's Common Name (CN) field in X.509 certificates was flawed. A man-in-the-middle attacker could use this flaw to spoof an SSL server using a specially crafted X.509 certificate. It was discovered that Axis incorrectly extracted the host name from an X.509 certificate subject's Common Name (CN) field. A man-in-the-middle attacker could use this flaw to spoof an SSL server using a specially crafted X.509 certificate. An off-by-one heap-based buffer overflow flaw was found in glibc's internal __gconv_translit_find() function. An attacker able to make an application call the iconv_open() function with a specially crafted argument could possibly use this flaw to execute arbitrary code with the privileges of that application. It was discovered that HornetQ REST did not set the resteasy.document.expand.entity.references context parameter to false by default. A HornetQ REST application, which does not explicitly set the required context parameter to false, may be vulnerable to XML External Entity (XXE) attacks. A remote attacker able to send XML requests to a HornetQ REST endpoint could use this flaw to read files accessible to the user running the application server, and potentially perform other more advanced XXE attacks. It was found that the MySQL token driver did not correctly store token expiration times, which prevented manual token revocation. Only OpenStack Identity setups configured to make use of revocation events were affected. A flaw was found in keystone revocation events that resulted in the "issued_at" time being updated when a token created by the V2 API was processed by the V3 API. This could allow a user to evade token revocation. Only OpenStack Identity setups configured to make use of revocation events and UUID tokens were affected. It was discovered that domain-scoped tokens were not revoked when a domain was disabled. Only OpenStack Identity setups configured to make use of revocation events were affected. It was discovered that Active Record's create_with method failed to properly check attributes passed to it. A remote attacker could possibly use this flaw to bypass the strong parameter protection and modify arbitrary model attributes via mass assignment if an application using Active Record called create_with with untrusted values. When using Spring Security's CAS Proxy ticket authentication, a malicious CAS Service could trick another CAS Service into authenticating a proxy ticket that was not associated. A remote attacker could use this flaw to bypass any access control restrictions on which CAS services can authenticate to one another. It was found that OpenShift Enterprise did not restrict access to the /proc/net/tcp file in gears, which allowed local users to view all listening connections and connected sockets. This could result in remote system's IP or port numbers in use to be exposed, which may be useful for further targeted attacks. It was discovered that the image_size_cap configuration option in glance was not honored. An authenticated user could use this flaw to upload an image to glance and consume all available storage space, resulting in a denial of service. A directory traversal flaw was found in the Spring Framework. A remote attacker could use this flaw to access arbitrary files on a server, and bypassing security restrictions that are otherwise in place. A flaw was found in the way the Linux kernel's kvm_iommu_map_pages() function handled IOMMU mapping failures. A privileged user in a guest with an assigned host device could use this flaw to crash the host. Multiple buffer over-read flaws were found in the php_parserr() function of PHP. A malicious DNS server or a man-in-the-middle attacker could possibly use this flaw to crash a PHP application that used the dns_get_record() function to perform a DNS query. It was discovered that the implementation used by the Not Yet Commons SSL project to check that the server hostname matches the domain name in the subject's CN field was flawed. This could be exploited by a man-in-the-middle attacker by spoofing a valid certificate using a specially crafted subject. It was found that PHP's gd extension did not properly handle file names with a null character. A remote attacker could possibly use this flaw to make a PHP application access unexpected files and bypass intended file system access restrictions. It was discovered that Apache ActiveMQ performed XML External Entity (XXE) expansion when evaluating XPath expressions. A remote, attacker-controlled consumer able to specify an XPath-based selector to dequeue XML messages from an Apache ActiveMQ broker could use this flaw to read files accessible to the user running the broker, and potentially perform other more advanced XXE attacks. It was found that async-http-client would disable SSL/TLS certificate verification under certain conditions, for example if HTTPS communication also used client certificates. A man-in-the-middle (MITM) attacker could use this flaw to spoof a valid certificate. It was found that async-http-client did not verify that the server hostname matched the domain name in the subject's Common Name (CN) or subjectAltName field in X.509 certificates. This could allow a man-in-the-middle attacker to spoof an SSL server if they had a certificate that was valid for any domain name. A flaw was found in the way Squid handled malformed HTTP Range headers. A remote attacker able to send HTTP requests to the Squid proxy could use this flaw to crash Squid. It was found that the parse_rock_ridge_inode_internal() function of the Linux kernel's ISOFS implementation did not correctly check relocated directories when processing Rock Ridge child link (CL) tags. An attacker with physical access to the system could use a specially crafted ISO image to crash the system or, potentially, escalate their privileges on the system. It was found that the parse_rock_ridge_inode_internal() function of the Linux kernel's ISOFS implementation did not correctly check relocated directories when processing Rock Ridge child link (CL) tags. An attacker with physical access to the system could use a specially crafted ISO image to crash the system or, potentially, escalate their privileges on the system. It was discovered that Apache ActiveMQ Apollo performed XML External Entity (XXE) expansion when evaluating XPath expressions. A remote, attacker-controlled consumer able to specify an XPath-based selector to dequeue XML messages from an Apache ActiveMQ Apollo broker could use this flaw to read files accessible to the user running the broker, and potentially perform other more advanced XXE attacks. An out-of-bounds read flaw was found in the way glibc's iconv() function converted certain encoded data to UTF-8. An attacker able to make an application call the iconv() function with a specially crafted argument could use this flaw to crash that application. It was found that if a configured LDAP server supported the unauthenticated authentication mechanism (as described by RFC 4513), the LDAPLoginModule implementation, provided by ActiveMQ Java Authentication and Authorization Service (JAAS), would consider an authentication attempt to be successful for a valid user that provided an empty password. A remote attacker could use this flaw to bypass the authentication mechanism of an application using LDAPLoginModule, and assume a role of any valid user within that application. It was found that the libcurl library did not correctly handle partial literal IP addresses when parsing received HTTP cookies. An attacker able to trick a user into connecting to a malicious server could use this flaw to set the user's cookie to a crafted domain, making other cookie-related issues easier to exploit. A heap-based buffer overflow flaw was found in procmail's formail utility. A remote attacker could send an email with specially crafted headers that, when processed by formail, could cause procmail to crash or, possibly, execute arbitrary code as the user running formail. It was found that Apache POI would resolve entities in OOXML documents. A remote attacker able to supply OOXML documents that are parsed by Apache POI could use this flaw to read files accessible to the user running the application server, and potentially perform more advanced XML External Entity (XXE) attacks. It was found that Apache POI would expand an unlimited number of entities in OOXML documents. A remote attacker able to supply OOXML documents that are parsed by Apache POI could use this flaw to trigger a denial of service attack via excessive CPU and memory consumption. A denial of service flaw was found in the way the __socket_proto_state_machine() function of glusterfs processed certain fragment headers. A remote attacker could send a specially crafted fragment header that, when processed, would cause the glusterfs process to enter an infinite loop. It was discovered that V8 did not properly check the stack size limit in certain cases. A remote attacker able to send a request that caused a script executed by V8 to use deep recursion could trigger a stack overflow, leading to a crash of an application using V8. A flaw was found in the OLE (Object Linking and Embedding) generation in LibreOffice. An attacker could use this flaw to embed malicious OLE code in a LibreOffice document, allowing for arbitrary code execution. An information leak flaw was found in the way QEMU's VGA emulator accessed frame buffer memory for high resolution displays. A privileged guest user could use this flaw to leak memory contents of the host to the guest by setting the display to use a high resolution in the guest. A buffer overflow flaw was discovered in the way HAProxy handled, under very specific conditions, data uploaded from a client. A remote attacker could possibly use this flaw to crash HAProxy. A flaw was found in the keystone catalog URL replacement. A user with permissions to register an endpoint could use this flaw to leak configuration data, including the master admin_token. Only keystone setups that allow non-cloud-admin users to create endpoints were affected by this issue. A flaw was found in the way the Linux kernel's keys subsystem handled the termination condition in the associative array garbage collection functionality. A local, unprivileged user could use this flaw to crash the system. It was discovered that the openstack-neutron package in Red Hat Enterprise Linux Open Stack Platform 5.0 for Red Hat Enterprise Linux 6 was released with a sudoers file containing a configuration error. This error caused OpenStack Networking to be vulnerable to the CVE-2013-6433 issue. An out-of-bounds read flaw was found in the way libvirt's qemuDomainGetBlockIoTune() function looked up the disk index in a non-persistent (live) disk configuration while a persistent disk configuration was being indexed. A remote attacker able to establish a read-only connection to libvirtd could use this flaw to crash libvirtd or, potentially, leak memory from the libvirtd process. An out-of-bounds write flaw was found in the way the Apple Magic Mouse/Trackpad multi-touch driver handled Human Interface Device (HID) reports with an invalid size. An attacker with physical access to the system could use this flaw to crash the system or, potentially, escalate their privileges on the system. An out-of-bounds read flaw was found in the way the Logitech Unifying receiver driver handled HID reports with an invalid device_index value. An attacker with physical access to the system could use this flaw to crash the system or, potentially, escalate their privileges on the system. Multiple out-of-bounds write flaws were found in the way the Cherry Cymotion keyboard driver, KYE/Genius device drivers, Logitech device drivers, Monterey Genius KB29E keyboard driver, Petalynx Maxter remote control driver, and Sunplus wireless desktop driver handled HID reports with an invalid report descriptor size. An attacker with physical access to the system could use either of these flaws to write data past an allocated memory buffer. A memory corruption flaw was found in the way the USB ConnectTech WhiteHEAT serial driver processed completion commands sent via USB Request Blocks buffers. An attacker with physical access to the system could use this flaw to crash the system or, potentially, escalate their privileges on the system. A buffer overflow flaw was found in the way the Minibox PicoLCD driver handled Human Interface Device (HID) reports with an invalid size. An attacker with physical access to the system could use this flaw to crash the system or, potentially, escalate their privileges on the system. A flaw was found in the way Bash evaluated certain specially crafted environment variables. An attacker could use this flaw to override or bypass environment restrictions to execute shell commands. Certain services and applications allow remote unauthenticated attackers to provide environment variables, allowing them to exploit this issue. It was discovered that unprivileged users could in some cases reset admin-only network attributes to their default values. This could lead to unexpected behavior or in some cases result in a denial of service. It was found that the Linux kernel's networking implementation did not correctly handle the setting of the keepalive socket option on raw sockets. A local user able to create a raw socket could use this flaw to crash the system. A stack overflow flaw caused by infinite recursion was found in the way the Linux kernel's Universal Disk Format (UDF) file system implementation processed indirect Information Control Blocks (ICBs). An attacker with physical access to the system could use a specially crafted UDF image to crash the system. A flaw was found in the way rsyslog handled invalid log message priority values. In certain configurations, a local attacker, or a remote attacker able to connect to the rsyslog port, could use this flaw to crash the rsyslog daemon or, potentially in rsyslog 7.x, execute arbitrary code as the user running the rsyslog daemon. It was found that Red Hat CloudForms contained an insecure send method that accepted user-supplied arguments. An authenticated user could use this flaw to modify the program flow in a way that could result in privilege escalation. Multiple persistent cross-site scripting (XSS) flaws were found in the way Aerogear handled certain user-supplied content. A remote attacker could use these flaws to compromise the application with specially crafted input. It was discovered that by requesting a large enough image size for a generated QR code in JBoss KeyCloak, a remote attacker could cause uncontrolled resource consumption leading to denial of service for legitimate users. It was identified that the login redirect implementation provided by JBoss KeyCloak did not validate the redirect URL. This flaw could be used by a remote attacker to conduct phishing attacks by redirecting users to arbitary websites. An integer overflow flaw, leading to a heap-based buffer overflow, was found in the way screen sizes were handled by LibVNCServer. A malicious VNC server could use this flaw to cause a client to crash or, potentially, execute arbitrary code in the client. A NULL pointer dereference flaw was found in LibVNCServer's framebuffer setup. A malicious VNC server could use this flaw to cause a VNC client to crash. A NULL pointer dereference flaw was found in the way LibVNCServer handled certain ClientCutText message. A remote attacker could use this flaw to crash the VNC server by sending a specially crafted ClientCutText message from a VNC client. A divide-by-zero flaw was found in the way LibVNCServer handled the scaling factor when it was set to "0". A remote attacker could use this flaw to crash the VNC server using a malicious VNC client. Two stack-based buffer overflow flaws were found in the way LibVNCServer handled file transfers. A remote attacker could use this flaw to crash the VNC server using a malicious VNC client. Stored and reflected cross-site scripting (XSS) flaws were found in the way spacewalk-java displayed certain information. By sending a specially crafted request to Satellite, a remote, authenticated attacker could embed HTML content into the stored data, allowing them to inject malicious content into the web page that is used to view that data. It was discovered that JBoss KeyCloak's soft token removal endpoint was vulnerable to Cross-Site Request Forgery (CSRF) attacks. A remote attacker could provide a specially crafted web page that, when visited by a user authenticated by KeyCloak, could allow the attacker to remove a soft token registerd to the user. A NULL pointer dereference flaw was found in the way QEMU handled UDP packets with a source port and address of 0 when QEMU's user networking was in use. A local guest user could use this flaw to crash the guest. It was found that the Linux kernel's KVM subsystem did not handle the VM exits gracefully for the invvpid (Invalidate Translations Based on VPID) instructions. On hosts with an Intel processor and invppid VM exit support, an unprivileged guest user could use these instructions to crash the guest. It was found that the Linux kernel's KVM subsystem did not handle the VM exits gracefully for the invept (Invalidate Translations Derived from EPT) instructions. On hosts with an Intel processor and invept VM exit support, an unprivileged guest user could use these instructions to crash the guest. A race condition flaw was found in the way the Linux kernel's KVM subsystem handled PIT (Programmable Interval Timer) emulation. A guest user who has access to the PIT I/O ports could use this flaw to crash the host. It was found that KVM's Write to Model Specific Register (WRMSR) instruction emulation would write non-canonical values passed in by the guest to certain MSRs in the host's context. A privileged guest user could use this flaw to crash the host. A flaw was found in the way the Linux kernel's KVM subsystem handled non-canonical addresses when emulating instructions that change the RIP (for example, branches or calls). A guest user with access to an I/O or MMIO region could use this flaw to crash the guest. If a JBoss Keycloak application was configured to use '*' as a permitted web origin in the Keycloak administrative console, crafted requests to the login-status-iframe.html endpoint could inject arbitrary Javascript into the generated HTML code via the "origin" query parameter, leading to a cross-site scripting (XSS) vulnerability. A cross-site scripting (XSS) flaw was found in Foreman's template preview screen. A remote attacker could use this flaw to perform cross-site scripting attacks by tricking a user into viewing a malicious template. Note that templates are commonly shared among users. A flaw was found in the way NSS parsed ASN.1 (Abstract Syntax Notation One) input from certain RSA signatures. A remote attacker could use this flaw to forge RSA certificates by providing a specially crafted signature to an application using NSS. A denial of service flaw was found in the way libvirt's virConnectListAllDomains() function computed the number of used domains. A remote attacker able to establish a read-only connection to libvirtd could use this flaw to make any domain operations within libvirt unresponsive. It was found that the fix for CVE-2014-6271 was incomplete, and Bash still allowed certain characters to be injected into other environments via specially crafted environment variables. An attacker could potentially use this flaw to override or bypass environment restrictions to execute shell commands. Certain services and applications allow remote unauthenticated attackers to provide environment variables, allowing them to exploit this issue. A flaw was found in the way Bundler handled gems available from multiple sources. An attacker with access to one of the sources could create a malicious gem with the same name, which they could then use to trick a user into installing, potentially resulting in execution of code from the attacker-supplied malicious gem. It was found that python-keystoneclient treated all settings in paste.ini files as string types. If the "insecure" option were set to any value in a paste.ini configuration file, it would be evaluated as true, resulting in TLS connections being vulnerable to man-in-the-middle attacks. An integer overflow flaw was found in the way the buffer() function handled its offset and size arguments. An attacker able to control those arguments could use this flaw to disclose portions of the application memory or cause it to crash. It was discovered that the fixed-sized redir_stack could be forced to overflow in the Bash parser, resulting in memory corruption, and possibly leading to arbitrary code execution when evaluating untrusted input that would not otherwise be run as code. An off-by-one error was discovered in the way Bash was handling deeply nested flow control constructs. Depending on the layout of the .bss segment, this could allow arbitrary execution of code that would not otherwise be executed by Bash. A NULL pointer dereference flaw was found in the way the Linux kernel's Common Internet File System (CIFS) implementation handled mounting of file system shares. A remote attacker could use this flaw to crash a client system that would mount a file system share from a malicious server. A flaw was found in the way the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation handled malformed Address Configuration Change Chunks (ASCONF). A remote attacker could use either of these flaws to crash the system. The nodejs-qs module has the ability to create sparse arrays during parsing. By specifying a high index in a querystring parameter it is possible to create a large array that will eventually take up all the allocated memory of the running process, resulting in a crash. It was found that OpenShift Enterprise 2.1 did not properly restrict access to services running on different gears. This could allow an attacker to access unprotected network resources running in another user's gear. An out-of-bounds memory read flaw was found in the way shim parsed certain IPv6 packets. A specially crafted DHCPv6 packet could possibly cause shim to crash, preventing the system from booting if IPv6 booting was enabled. A heap-based buffer overflow flaw was found the way shim parsed certain IPv6 addresses. If IPv6 network booting was enabled, a malicious server could supply a crafted IPv6 address that would cause shim to crash or, potentially, execute arbitrary code. An out-of-bounds memory write flaw was found in the way shim processed certain Machine Owner Keys (MOKs). A local attacker could potentially use this flaw to execute arbitrary code on the system. An XML External Entity (XXE) flaw was found in the jbpm-designer BPMN2 import function. A remote attacker could use this flaw to read files accessible to the user running the application server, and potentially perform other more advanced XXE attacks. A denial of service flaw was found in the way the Linux kernel's XFS file system implementation ordered directory hashes under certain conditions. A local attacker could use this flaw to corrupt the file system by creating directories with colliding hash values, potentially resulting in a system crash. A denial of service flaw was found in libxml2, a library providing support to read, modify and write XML and HTML files. A remote attacker could provide a specially crafted XML file that, when processed by an application using libxml2, would lead to excessive CPU consumption (denial of service) based on excessive entity substitutions, even if entity substitution was disabled, which is the parser default behavior. It was found that the Gnome shell did not disable the Print Screen key when the screen was locked. This could allow an attacker with physical access to a system with a locked screen to crash the screen-locking application by creating a large amount of screenshots. A NULL pointer dereference flaw was found in the way the mod_cache httpd module handled Content-Type headers. A malicious HTTP server could cause the httpd child process to crash when the Apache HTTP server was configured to proxy to a server with caching enabled. It was discovered that the DatagramSocket implementation in OpenJDK failed to perform source address checks for packets received on a connected socket. A remote attacker could use this flaw to have their packets processed as if they were received from the expected source. A flaw was found in the metadata constraints in OpenStack Object Storage (swift). By adding metadata in several separate calls, a malicious user could bypass the max_meta_count constraint, and store more metadata than allowed by the configuration. It was discovered that foreman-proxy, when running in SSL-secured mode, did not correctly verify SSL client certificates. This could permit any client with access to the API to make requests and perform actions otherwise restricted. It was discovered that the CipherInputStream class implementation in OpenJDK did not properly handle certain exceptions. This could possibly allow an attacker to affect the integrity of an encrypted stream handled by this class. A command injection flaw was found in the way the wpa_cli utility executed action scripts. If wpa_cli was run in daemon mode to execute an action script (specified using the -a command line option), and wpa_supplicant was configured to connect to a P2P group, malicious P2P group parameters could cause wpa_cli to execute arbitrary code. It was found that the CloudForms Management Engine customization template used a default root password for newly created images if no root password was specified. A race condition flaw was found in the Linux kernel's ext4 file system implementation that allowed a local, unprivileged user to crash the system by simultaneously writing to a file and toggling the O_DIRECT flag using fcntl(F_SETFL) on that file. It was discovered that the StAX XML parser in the JAXP component in OpenJDK performed expansion of external parameter entities even when external entity substitution was disabled. A remote attacker could use this flaw to perform XML eXternal Entity (XXE) attack against applications using the StAX parser to parse untrusted XML documents. A flaw was found in the way Wget handled symbolic links. A malicious FTP server could allow Wget running in the mirror mode (using the '-m' command line option) to write an arbitrary file to a location writable to by the user running Wget, possibly leading to code execution. It was discovered that the TLS/SSL implementation in the JSSE component in OpenJDK failed to properly verify the server identity during the renegotiation following session resumption, making it possible for malicious TLS/SSL servers to perform a Triple Handshake attack against clients using JSSE and client certificate authentication. An integer overflow flaw, leading to a heap-based buffer overflow, was found in the way TigerVNC handled screen sizes. A malicious VNC server could use this flaw to cause a client to crash or, potentially, execute arbitrary code on the client. A NULL pointer dereference flaw was found in TigerVNC's XRegion. A malicious VNC server could use this flaw to cause a client to crash. It was discovered that the Hotspot component in OpenJDK failed to properly handle malformed Shared Archive files. A local attacker able to modify a Shared Archive file used by a virtual machine of a different user could possibly use this flaw to escalate their privileges. A race condition flaw was found in the way the nova VMware driver handled VNC port allocation. An authenticated user could use this flaw to gain unauthorized console access to instances belonging to other tenants by repeatedly spawning new instances. Note that only nova setups using the VMware driver and the VNC proxy service were affected. It was discovered that the nova.conf configuration generated by PackStack did not correctly set the libvirt_vif_driver configuration option if the Open vSwitch (OVS) monolithic plug-in was not used. This could result in deployments defaulting to having the firewall disabled unless the nova configuration was manually modified after PackStack was started. A flaw was found in the way SSL 3.0 handled padding bytes when decrypting messages encrypted using block ciphers in cipher block chaining (CBC) mode. This flaw allows a man-in-the-middle (MITM) attacker to decrypt a selected byte of a cipher text in as few as 256 tries if they are able to force a victim application to repeatedly send the same data over newly created SSL 3.0 connections. A memory leak flaw was found in the way OpenSSL parsed the DTLS Secure Real-time Transport Protocol (SRTP) extension data. A remote attacker could send multiple specially crafted handshake messages to exhaust all available memory of an SSL/TLS or DTLS server. A memory leak flaw was found in the way an OpenSSL handled failed session ticket integrity checks. A remote attacker could exhaust all available memory of an SSL/TLS or DTLS server by sending a large number of invalid session tickets to that server. It was found that the Linux kernel's KVM implementation did not ensure that the host CR4 control register value remained unchanged across VM entries on the same virtual CPU. A local, unprivileged user could use this flaw to cause a denial of service on the system. An integer overflow flaw was found in the way custom objects were unserialized. Specially crafted input processed by the unserialize() function could cause a PHP application to crash. A buffer overflow flaw was found in the Exif extension. A specially crafted JPEG or TIFF file could cause a PHP application using the exif_thumbnail() function to crash or, possibly, execute arbitrary code with the privileges of the user running that PHP application. An out of bounds read flaw was found in the way the xmlrpc extension parsed dates in the ISO 8601 format. A specially crafted XML-RPC request or response could possibly cause a PHP application to crash. It was found that Pidgin's SSL/TLS plug-ins had a flaw in the certificate validation functionality. An attacker could use this flaw to create a fake certificate, that Pidgin would trust, which could be used to conduct man-in-the-middle attacks against Pidgin. A denial of service flaw was found in the way Pidgin's Mxit plug-in handled emoticons. A malicious remote server or a man-in-the-middle attacker could potentially use this flaw to crash Pidgin by sending a specially crafted emoticon. A denial of service flaw was found in the way Pidgin parsed Groupwise server messages. A malicious remote server or a man-in-the-middle attacker could potentially use this flaw to cause Pidgin to consume an excessive amount of memory, possibly leading to a crash, by sending a specially crafted message. An information disclosure flaw was discovered in the way Pidgin parsed XMPP messages. A malicious remote server or a man-in-the-middle attacker could potentially use this flaw to disclose a portion of memory belonging to the Pidgin process by sending a specially crafted XMPP message. A flaw was found in the way the libcurl library performed the duplication of connection handles. If an application set the CURLOPT_COPYPOSTFIELDS option for a handle, using the handle's duplicate could cause the application to crash or disclose a portion of its memory. A denial of service flaw was found in the way OpenStack Compute (nova) looked up VM instances based on an IP address filter. An attacker with sufficient privileges on an OpenStack installation with a large amount of VMs could use this flaw to cause the main nova process to block for an extended amount of time. It was discovered that the org.keycloak.services.resources.SocialResource.callback(String) method implementation lacked Cross-Site Request Forgery (CSRF) protection. A remote attacker could use this flaw to gain access to KeyCloak managed accounts or perform other attacks. An out-of-bounds read flaw was found in the way the File Information (fileinfo) extension parsed Executable and Linkable Format (ELF) files. A remote attacker could use this flaw to crash a PHP application using fileinfo via a specially crafted ELF file. A flaw was found in the OpenStack Compute (nova) VMWare driver, which could allow an authenticated user to delete an instance while it was in the resize state, causing the instance to remain on the back end. A malicious user could use this flaw to cause a denial of service by exhausting all available resources on the system. A flaw was found in the way the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation handled duplicate Address Configuration Change Chunks (ASCONF). A remote attacker could use either of these flaws to crash the system. A flaw was found in the way the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation handled the association's output queue. A remote attacker could send specially crafted packets that would cause the system to use an excessive amount of memory, leading to a denial of service. It was found that the fix for CVE-2014-3601 was incomplete: the Linux kernel's kvm_iommu_map_pages() function still handled IOMMU mapping failures incorrectly. A privileged user in a guest with an assigned host device could use this flaw to crash the host. It was found that Apache WSS4J (Web Services Security for Java), as used by Apache CXF with the TransportBinding, did not, by default, properly enforce all security requirements associated with SAML SubjectConfirmation methods. A remote attacker could use this flaw to perform various types of spoofing attacks on web service endpoints secured by WSS4J that rely on SAML for authentication. An integer overflow flaw was found in the way the strings utility processed certain files. If a user were tricked into running the strings utility on a specially crafted file, it could cause the strings executable to crash. A buffer overflow flaw was found in the way various binutils utilities processed certain files. If a user were tricked into processing a specially crafted file, it could cause the utility used to process that file to crash or, potentially, execute arbitrary code with the privileges of the user running that utility. It was discovered that Undertow is vulnerable to a directory traversal flaw. A remote attacker could use this flaw to read arbitrary files that are accessible to the user running the Java process. An uninitialized data structure use flaw was found in the way the set_pixel_format() function sanitized the value of bits_per_pixel. An attacker able to access a guest's VNC console could use this flaw to crash the guest. It was found that the wordexp() function would perform command substitution even when the WRDE_NOCMD flag was specified. An attacker able to provide specially crafted input to an application using the wordexp() function, and not sanitizing the input correctly, could potentially use this flaw to execute arbitrary commands with the credentials of the user running that application. It was found that CloudForms 4 exposed SQL filters via the REST API without any input escaping. An authenticated user could use this flaw to perform SQL injection attacks against the CloudForms Management Engine database. A flaw was found in the way the Linux kernel's VFS subsystem handled file system locks. A local, unprivileged user could use this flaw to trigger a deadlock in the kernel, causing a denial of service on the system. It was found that uninitialized data could be accessed when processing a user's logout request. By attempting to log out, a user could possibly cause the Apache HTTP Server to crash. An information disclosure flaw was found in mod_auth_mellon's session handling that could lead to session overlapping in memory. A remote attacker could potentially use this flaw to obtain data from another user's session. It was found that when processing undefined security domains, the org.jboss.security.plugins.mapping.JBossMappingManager implementation would fall back to the default security domain if it was available. A user with valid credentials in the defined default domain, with a role that is valid in the expected application domain, could perform actions that were otherwise not available to them. When using the SAML2 STS Login Module, JBossMappingManager exposed this issue due to the PicketLink Trust SecurityActions implementation using a hardcoded default value when defining the context. It was found that when the VIR_DOMAIN_XML_MIGRATABLE flag was used, the QEMU driver implementation of the virDomainGetXMLDesc() function could bypass the restrictions of the VIR_DOMAIN_XML_SECURE flag. A remote attacker able to establish a read-only connection to libvirtd could use this flaw to leak certain limited information from the domain XML data. A stack-based buffer overflow flaw was found in the way the xmlrpc extension parsed dates in the ISO 8601 format. A specially crafted XML-RPC request or response could possibly cause a PHP application to crash or execute arbitrary code with the privileges of the user running that PHP application. An out-of-bounds memory write flaw was found in the way GnuTLS parsed certain ECC (Elliptic Curve Cryptography) certificates or certificate signing requests (CSR). A malicious user could create a specially crafted ECC certificate or a certificate signing request that, when processed by an application compiled against GnuTLS (for example, certtool), could cause that application to crash or execute arbitrary code with the permissions of the user running the application. An out-of-bounds memory access flaw, CVE-2014-7825, was found in the syscall tracing functionality of the Linux kernel's perf subsystem. A local, unprivileged user could use this flaw to crash the system. Additionally, an out-of-bounds memory access flaw, CVE-2014-7826, was found in the syscall tracing functionality of the Linux kernel's ftrace subsystem. On a system with ftrace syscall tracing enabled, a local, unprivileged user could use this flaw to crash the system, or escalate their privileges. An out-of-bounds memory access flaw, CVE-2014-7825, was found in the syscall tracing functionality of the Linux kernel's perf subsystem. A local, unprivileged user could use this flaw to crash the system. Additionally, an out-of-bounds memory access flaw, CVE-2014-7826, was found in the syscall tracing functionality of the Linux kernel's ftrace subsystem. On a system with ftrace syscall tracing enabled, a local, unprivileged user could use this flaw to crash the system, or escalate their privileges. A stack-based buffer overflow flaw was found in the way various binutils utilities processed certain files. If a user were tricked into processing a specially crafted file, it could cause the utility used to process that file to crash or, potentially, execute arbitrary code with the privileges of the user running that utility. It was found that the fix for the CVE-2014-8485 issue was incomplete: a heap-based buffer overflow in the objdump utility could cause it to crash or, potentially, execute arbitrary code with the privileges of the user running objdump when processing specially crafted files. A stack-based buffer overflow flaw was found in the way objdump processed IHEX files. A specially crafted IHEX file could cause objdump to crash or, potentially, execute arbitrary code with the privileges of the user running objdump. A stack-based buffer overflow flaw was found in the SREC parser of the libbfd library. A specially crafted file could cause an application using the libbfd library to crash or, potentially, execute arbitrary code with the privileges of the user running that application. A flaw was found in the way mailx handled the parsing of email addresses. A syntactically valid email address could allow a local attacker to cause mailx to execute arbitrary shell commands through shell meta-characters (CVE-2004-2771) and the direct command execution functionality (CVE-2014-7844). It was found that certain values that were read when loading RAM during migration were not validated. A user able to alter the savevm data (either on the disk or over the wire during migration) could use either of these flaws to corrupt QEMU process memory on the (destination) host, which could potentially result in arbitrary code execution on the host with the privileges of the QEMU process. A flaw was found in the way the Linux kernel's SCTP implementation validated INIT chunks when performing Address Configuration Change (ASCONF). A remote attacker could use this flaw to crash the system by sending a specially crafted SCTP packet to trigger a NULL pointer dereference on the system. A denial of service flaw was found in the way neutron handled the 'dns_nameservers' parameter. By providing specially crafted 'dns_nameservers' values, an authenticated user could use this flaw to crash the neutron service. A buffer overflow flaw was found in mod_proxy_fcgi's handle_headers() function. A malicious FastCGI server that httpd is configured to connect to could send a carefully crafted response that would cause an httpd child process handling the request to crash. It was found that reporting emulation failures to user space could lead to either a local (CVE-2014-7842) or a L2->L1 (CVE-2010-5313) denial of service. In the case of a local denial of service, an attacker must have access to the MMIO area or be able to access an I/O port. Please note that on certain systems, HPET is mapped to userspace as part of vdso (vvar) and thus an unprivileged user may generate MMIO transactions (and enter the emulator) this way. A flaw was found in the way the Linux kernel's splice() system call validated its parameters. On certain file systems, a local, unprivileged user could use this flaw to write past the maximum file size, and thus crash the system. A directory traversal flaw was found in the strip and objcopy utilities. A specially crafted file could cause strip or objdump to overwrite an arbitrary file writable by the user running either of these utilities. A heap-based buffer overflow flaw was found in the way certain binutils utilities processed archive files. If a user were tricked into processing a specially crafted archive file, it could cause the utility used to process that archive to crash or, potentially, execute arbitrary code with the privileges of the user running that utility. A stack-based buffer overflow flaw was found in the TechnoTrend/Hauppauge DEC USB device driver. A local user with write access to the corresponding device could use this flaw to crash the kernel or, potentially, elevate their privileges on the system. A use-after-free flaw was found in the "Remote Control" capabilities of the LibreOffice Impress application. An attacker could use this flaw to remotely execute code with the permissions of the user running LibreOffice Impress. An insufficient bound checking flaw was found in the Xen hypervisor's implementation of acceleration support for the "REP MOVS" instructions. A privileged HVM guest user could potentially use this flaw to crash the host. It was discovered that the Role Based Access Control (RBAC) implementation did not sufficiently verify all authorization conditions that are required by the Maintainer role to perform certain administrative actions. An authenticated user with the Maintainer role could use this flaw to add, modify, or undefine a limited set of attributes and their values, which otherwise cannot be written to. It was found that oVirt did not correctly terminate sessions when a user logged out from the web interface. Upon logout, only the engine session was invalidated but the restapi session persisted. An attacker able to obtain the session data, and able to log in with their own credentials, could replace their session token with the stolen token and elevate their privileges to those of the victim user. Note that in order for this flaw to be exploited, the attacker must also have a valid login and authenticate successfully. It was found that the RESTEasy DocumentProvider did not set the external-parameter-entities and external-general-entities features appropriately, thus allowing external entity expansion. A remote attacker able to send XML requests to a RESTEasy endpoint could use this flaw to read files accessible to the user running the application server, and potentially perform other more advanced XML eXternal Entity (XXE) attacks. It was discovered that the JBoss Application Server (WildFly) JacORB subsystem incorrectly assigned socket-binding-ref sensitivity classification for the security-domain attribute. An authenticated user with a role that has access to attributes with socket-binding-ref and not security-domain-ref sensitivity classification could use this flaw to access sensitive information present in the security-domain attribute. It was found that RichFaces accepted arbitrary strings included in a URL and returned them unencoded in a CSS file. A remote attacker could use this flaw to perform cross-site scripting (XSS) attacks against a user running a RichFaces application. A directory traversal flaw was found in the way the Spring Framework sanitized certain URLs. A remote attacker could use this flaw to obtain any file on the file system that was also accessible to the process in which the Spring web application was running. A flaw was found in the way PCRE handled certain malformed regular expressions. This issue could cause an application (for example, Konqueror) linked against PCRE to crash while parsing malicious regular expressions. A buffer over-read flaw was found in the way flac processed certain ID3v2 metadata. An attacker could create a specially crafted FLAC audio file that could cause an application using the flac library to crash when the file was read. Multiple off-by-one flaws, leading to heap-based buffer overflows, were found in the way JasPer decoded JPEG 2000 files. A specially crafted file could cause an application using JasPer to crash or, possibly, execute arbitrary code. A buffer overflow flaw was found in the way flac decoded FLAC audio files. An attacker could create a specially crafted FLAC audio file that could cause an application using the flac library to crash or execute arbitrary code when the file was read. An information disclosure flaw was found in the way the 389 Directory Server stored information in the Changelog that is exposed via the 'cn=changelog' LDAP sub-tree. An unauthenticated user could in certain cases use this flaw to read data from the Changelog, which could include sensitive information such as plain-text passwords. A heap-based buffer overflow flaw was found in cpio's list_file() function. An attacker could provide a specially crafted archive that, when processed by cpio, would crash cpio, or potentially lead to arbitrary code execution. It was found that the X.Org server did not properly handle SUN-DES-1 (Secure RPC) authentication credentials. A malicious, unauthenticated client could use this flaw to crash the X.Org server by submitting a specially crafted authentication request. Multiple integer overflow flaws were found in the way the X.Org server calculated memory requirements for certain X11 core protocol requests. A malicious, authenticated client could use either of these flaws to crash the X.Org server or, potentially, execute arbitrary code with root privileges. Multiple integer overflow flaws were found in the way the X.Org server calculated memory requirements for certain GLX extension requests. A malicious, authenticated client could use either of these flaws to crash the X.Org server or, potentially, execute arbitrary code with root privileges. An integer overflow flaw was found in the way the X.Org server calculated memory requirements for certain DRI2 extension requests. A malicious, authenticated client could use this flaw to crash the X.Org server. Multiple out-of-bounds access flaws were found in the way the X.Org server calculated memory requirements for certain requests. A malicious, authenticated client could use either of these flaws to crash the X.Org server. Multiple out-of-bounds access flaws were found in the way the X.Org server calculated memory requirements for certain requests. A malicious, authenticated client could use either of these flaws to crash the X.Org server. Multiple out-of-bounds access flaws were found in the way the X.Org server calculated memory requirements for certain requests. A malicious, authenticated client could use either of these flaws to crash the X.Org server, or leak memory contents to the client. Multiple out-of-bounds write flaws were found in the way the X.Org server calculated memory requirements for certain GLX extension requests. A malicious, authenticated client could use either of these flaws to crash the X.Org server or, potentially, execute arbitrary code with root privileges. Multiple out-of-bounds access flaws were found in the way the X.Org server calculated memory requirements for certain requests. A malicious, authenticated client could use either of these flaws to crash the X.Org server. Multiple out-of-bounds access flaws were found in the way the X.Org server calculated memory requirements for certain requests. A malicious, authenticated client could use either of these flaws to crash the X.Org server. Multiple out-of-bounds access flaws were found in the way the X.Org server calculated memory requirements for certain requests. A malicious, authenticated client could use either of these flaws to crash the X.Org server. Multiple out-of-bounds access flaws were found in the way the X.Org server calculated memory requirements for certain requests. A malicious, authenticated client could use either of these flaws to crash the X.Org server. Multiple out-of-bounds access flaws were found in the way the X.Org server calculated memory requirements for certain requests. A malicious, authenticated client could use either of these flaws to crash the X.Org server. It was discovered that, in certain configurations, the Thermostat agent disclosed JMX management URLs of all local Java virtual machines to any local user. A local, unprivileged user could use this flaw to escalate their privileges on the system. It was found that the files back end of Name Service Switch (NSS) did not isolate iteration over an entire database from key-based look-up API calls. An application performing look-ups on a database while iterating over it could enter an infinite loop, leading to a denial of service. It was discovered that under specific conditions the conversation state information stored in a thread-local variable in JBoss Weld was not sanitized correctly when the conversation ended. This could lead to a race condition that could potentially expose sensitive information from a previous conversation to the current conversation. An assertion failure was found in the way the libyaml library parsed wrapped strings. An attacker able to load specially crafted YAML input into an application using libyaml could cause the application to crash. It was found that the Cirrus blit region checks were insufficient. A privileged guest user could use this flaw to write outside of VRAM-allocated buffer boundaries in the host's QEMU process address space with attacker-provided data. It was discovered that the default implementation of FileUploadServlet and FileDownloadServlet provided by the UberFire Framework did not restrict the paths to which a file could be written or read from. In applications using this framework and exposing these servlets, a remote attacker could gain access to information stored in files accessible to the application container process, or execute arbitrary code by uploading malicious content. It was discovered that the default authorization constrains applied on servelets deployed in the KIE Workbench application were insufficient. A remote, authenticated user without sufficient privileges could use this flaw to upload or download arbitrary files, perform privileged actions that otherwise cannot be accessed, or perform other more complex attacks. It was discovered that the jBPM runtime performed expansion of external parameter entities while executing BPMN2 files. A remote attacker could use this flaw to read files accessible to the user running the application server, and potentially perform other more advanced XML eXternal Entity (XXE) attacks. A denial of service flaw was found in the OpenStack Dashboard (horizon) when using the db or memcached session engine. An attacker could make repeated requests to the login page, which would result in a large number of unwanted backend session entries, possibly leading to a denial of service. It was found that reporting emulation failures to user space could lead to either a local (CVE-2014-7842) or a L2->L1 (CVE-2010-5313) denial of service. In the case of a local denial of service, an attacker must have access to the MMIO area or be able to access an I/O port. Please note that on certain systems, HPET is mapped to userspace as part of vdso (vvar) and thus an unprivileged user may generate MMIO transactions (and enter the emulator) this way. The HTCondor scheduler can optionally notify a user of completed jobs by sending an email. Due to the way the daemon sent the email message, authenticated users able to submit jobs could execute arbitrary code with the privileges of the condor user. It was found that when OpenSSH was used in a Kerberos environment, remote authenticated users were allowed to log in as a different user if they were listed in the ~/.k5users file of that user, potentially bypassing intended authentication restrictions. It was found that hivex attempted to read, and possibly write, beyond its allocated buffer when reading a hive file with a very small size or with a truncated or improperly formatted content. An attacker able to supply a specially crafted hive file to an application using the hivex library could possibly use this flaw to execute arbitrary code with the privileges of the user running that application. Multiple flaws were found in the way the File Information (fileinfo) extension parsed Executable and Linkable Format (ELF) files. A remote attacker could use either of these flaws to cause a PHP application using fileinfo to consume an excessive amount of system resources. A denial of service flaw was found in the way BIND followed DNS delegations. A remote attacker could use a specially crafted zone containing a large number of referrals which, when looked up and processed, would cause named to use excessive amounts of memory or crash. A denial of service flaw was found in unbound that an attacker could use to trick the unbound resolver into following an endless loop of delegations, consuming an excessive amount of resources. A denial of service flaw was found in netcf. A specially crafted interface name could cause an application using netcf (such as the libvirt daemon) to crash. A flaw was found in the way mailx handled the parsing of email addresses. A syntactically valid email address could allow a local attacker to cause mailx to execute arbitrary shell commands through shell meta-characters (CVE-2004-2771) and the direct command execution functionality (CVE-2014-7844). It was found that when the nsslapd-unhashed-pw-switch 389 Directory Server configuration option was set to "off", it did not prevent the writing of unhashed passwords into the Changelog. This could potentially allow an authenticated user able to access the Changelog to read sensitive information. It was found that a malicious container image could overwrite arbitrary portions of the host file system by including absolute symlinks, potentially leading to privilege escalation. It was found that the espfix functionality does not work for 32-bit KVM paravirtualized guests. A local, unprivileged guest user could potentially use this flaw to leak kernel stack addresses. A flaw was found in the way the Docker service unpacked images or builds after a "docker pull". An attacker could use this flaw to provide a malicious image or build that, when unpacked, would escalate their privileges on the system. It was found that the espfix functionality could be bypassed by installing a 16-bit RW data segment into GDT instead of LDT (which espfix checks), and using that segment on the stack. A local, unprivileged user could potentially use this flaw to leak kernel stack addresses. A flaw was found in the way the Linux kernel handled GS segment register base switching when recovering from a #SS (stack segment) fault on an erroneous return to user space. A local, unprivileged user could use this flaw to escalate their privileges on the system. A double free flaw was found in the way JasPer parsed ICC color profiles in JPEG 2000 image files. A specially crafted file could cause an application using JasPer to crash or, possibly, execute arbitrary code. A heap-based buffer overflow flaw was found in the way JasPer decoded JPEG 2000 image files. A specially crafted file could cause an application using JasPer to crash or, possibly, execute arbitrary code. The Python standard library HTTP client modules (such as httplib or urllib) did not perform verification of TLS/SSL certificates when connecting to HTTPS servers. A man-in-the-middle attacker could use this flaw to hijack connections and eavesdrop or modify transferred data. An information leak flaw was found in the Linux kernel's IEEE 802.11 wireless networking implementation. When software encryption was used, a remote attacker could use this flaw to leak up to 8 bytes of plaintext. A NULL pointer dereference flaw was found in the way the mod_dav_svn module handled REPORT requests. A remote, unauthenticated attacker could use a specially crafted REPORT request to crash mod_dav_svn. A NULL pointer dereference flaw was found in the way the mod_dav_svn module handled certain requests for URIs that trigger a lookup of a virtual transaction name. A remote, unauthenticated attacker could send a request for a virtual transaction name that does not exist, causing mod_dav_svn to crash. If kadmind were used with an LDAP back end for the KDC database, a remote, authenticated attacker who has the permissions to set the password policy could crash kadmind by attempting to use a named ticket policy object as a password policy for a principal. A flaw was found in the way the File Information (fileinfo) extension parsed Executable and Linkable Format (ELF) files. A remote attacker could use this flaw to cause a PHP application using fileinfo to consume an excessive amount of system resources. A buffer overflow flaw was found in the way unzip computed the CRC32 checksum of certain extra fields of a file. A specially crafted Zip archive could cause unzip to crash when the archive was tested with unzip's '-t' option. An integer underflow flaw, leading to a buffer overflow, was found in the way unzip uncompressed certain extra fields of a file. A specially crafted Zip archive could cause unzip to crash when the archive was tested with unzip's '-t' option. A buffer overflow flaw was found in the way unzip handled Zip64 files. A specially crafted Zip archive could possibly cause unzip to crash when the archive was uncompressed. A flaws was discovered in the way PHP performed object unserialization. Specially crafted input processed by the unserialize() function could cause a PHP application to crash or, possibly, execute arbitrary code. It was found that ntpd automatically generated weak keys for its internal use if no ntpdc request authentication key was specified in the ntp.conf configuration file. A remote attacker able to match the configured IP restrictions could guess the generated key, and possibly use it to send ntpdc query or configuration requests. It was found that ntp-keygen used a weak method for generating MD5 keys. This could possibly allow an attacker to guess generated MD5 keys that could then be used to spoof an NTP client or server. Note: it is recommended to regenerate any MD5 keys that had explicitly been generated with ntp-keygen; the default installation does not contain such keys. Multiple buffer overflow flaws were discovered in ntpd's crypto_recv(), ctl_putdata(), and configure() functions. A remote attacker could use either of these flaws to send a specially crafted request packet that could crash ntpd or, potentially, execute arbitrary code with the privileges of the ntp user. Note: the crypto_recv() flaw requires non default configurations to be active, while the ctl_putdata() flaw, by default, can only be exploited via local attackers, and the configure() flaw requires additional authentication to exploit. A missing return statement in the receive() function could potentially allow a remote attacker to bypass NTP's authentication mechanism. It was found that QEMU's qemuDomainMigratePerform() and qemuDomainMigrateFinish2() functions did not correctly perform a domain unlock on a failed ACL check. A remote attacker able to establish a connection to libvirtd could use this flaw to lock a domain of a more privileged user, causing a denial of service. It was discovered that SoX did not correctly process NIST Sphere and WAV audio files. By tricking a victim into processing a specially crafted NIST Sphere or WAV audio file, a remote attacker could possibly use this flaw to execute arbitrary code with the privileges of the user running SoX. An information leak flaw was found in the way the Linux kernel changed certain segment registers and thread-local storage (TLS) during a context switch. A local, unprivileged user could use this flaw to leak the user space TLS base address of an arbitrary process. It was found that the Linux kernel's ISO file system implementation did not correctly limit the traversal of Rock Ridge extension Continuation Entries (CE). An attacker with physical access to the system could use this flaw to trigger an infinite loop in the kernel, resulting in a denial of service. A double free flaw was found in zend_ts_hash_graceful_destroy() function in the PHP ZTS module. This flaw could possibly cause a PHP application to crash. A flaw was discovered in the bmp2tiff utility. By tricking a user into processing a specially crafted file, a remote attacker could exploit this flaw to cause a crash or memory corruption and, possibly, execute arbitrary code with the privileges of the user running the libtiff tool. It was discovered that the libcurl library failed to properly handle URLs with embedded end-of-line characters. An attacker able to make an application using libcurl access a specially crafted URL via an HTTP proxy could use this flaw to inject additional headers to the request or construct additional requests. A flaw was found in the way PHP handled malformed source files when running in CGI mode. A specially crafted PHP file could cause PHP CGI to crash. It was discovered that an authenticated user could use a path traversal flaw in glance to download or delete any file on the glance server that is accessible to the glance process user. Note that only setups using the OpenStack Image V2 API were affected by this flaw. A race condition flaw was found in the way the Linux kernel keys management subsystem performed key garbage collection. A local attacker could attempt accessing a key while it was being garbage collected, which would cause the system to crash. A use-after-free flaw was found in the way the MIT Kerberos libgssapi_krb5 library processed valid context deletion tokens. An attacker able to make an application using the GSS-API library (libgssapi) call the gss_process_context_token() function could use this flaw to crash that application. A double-free flaw was found in the way MIT Kerberos handled invalid External Data Representation (XDR) data. An authenticated user could use this flaw to crash the MIT Kerberos administration server (kadmind), or other applications using Kerberos libraries, using specially crafted XDR packets. It was found that the MIT Kerberos administration server (kadmind) incorrectly accepted certain authentication requests for two-component server principal names. A remote attacker able to acquire a key with a particularly named principal (such as "kad/x") could use this flaw to impersonate any user to kadmind, and perform administrative actions as that user. An information disclosure flaw was found in the way MIT Kerberos RPCSEC_GSS implementation (libgssrpc) handled certain requests. An attacker could send a specially crafted request to an application using libgssrpc to disclose a limited portion of uninitialized memory used by that application. It was discovered that OpenSSL would accept ephemeral RSA keys when using non-export RSA cipher suites. A malicious server could make a TLS/SSL client using OpenSSL use a weaker key exchange method. It was discovered that OpenSSL would perform an ECDH key exchange with a non-ephemeral key even when the ephemeral ECDH cipher suite was selected. A malicious server could make a TLS/SSL client using OpenSSL use a weaker key exchange method than the one requested by the user. Multiple flaws were found in the way OpenSSL parsed X.509 certificates. An attacker could use these flaws to modify an X.509 certificate to produce a certificate with a different fingerprint without invalidating its signature, and possibly bypass fingerprint-based blacklisting in applications. A NULL pointer dereference flaw was found in the DTLS implementation of OpenSSL. A remote attacker could send a specially crafted DTLS message, which would cause an OpenSSL server to crash. A memory leak flaw was found in the way the dtls1_buffer_record() function of OpenSSL parsed certain DTLS messages. A remote attacker could send multiple specially crafted DTLS messages to exhaust all available memory of a DTLS server. It was found that an OpenSSL server would, under certain conditions, accept Diffie-Hellman client certificates without the use of a private key. An attacker could use a user's client certificate to authenticate as that user, without needing the private key. It was found that OpenSSL's BigNumber Squaring implementation could produce incorrect results under certain special conditions. This flaw could possibly affect certain OpenSSL library functionality, such as RSA blinding. Note that this issue occurred rarely and with a low probability, and there is currently no known way of exploiting it. An off-by-one flaw, leading to a heap-based buffer overflow, was found in the way JasPer decoded JPEG 2000 image files. A specially crafted file could cause an application using JasPer to crash or, possibly, execute arbitrary code. An information leak flaw was found in the way the Linux kernel's ISO9660 file system implementation accessed data on an ISO9660 image with RockRidge Extension Reference (ER) records. An attacker with physical access to the system could use this flaw to disclose up to 255 bytes of kernel memory. An unrestricted stack memory use flaw was found in the way JasPer decoded JPEG 2000 image files. A specially crafted file could cause an application using JasPer to crash or, possibly, execute arbitrary code. An information leak flaw was found in the way the Linux kernel's Virtual Dynamic Shared Object (vDSO) implementation performed address randomization. A local, unprivileged user could use this flaw to leak kernel memory addresses to user-space. It was found that the Linux kernel's Infiniband subsystem did not properly sanitize input parameters while registering memory regions from user space via the (u)verbs API. A local user with access to a /dev/infiniband/uverbsX device could use this flaw to crash the system or, potentially, escalate their privileges on the system. A denial of service flaw was found in the way the HSLFSlideShow class implementation in Apache POI handled certain PPT files. A remote attacker could submit a specially crafted PPT file that would cause Apache POI to hang indefinitely. A flaw was found in the way the Qpid daemon (qpidd) processed certain protocol sequences. An unauthenticated attacker able to send a specially crafted protocol sequence set could use this flaw to crash qpidd. A flaw was found in the way the Linux kernel's netfilter subsystem handled generic protocol tracking. As demonstrated in the Stream Control Transmission Protocol (SCTP) case, a remote attacker could use this flaw to bypass intended iptables rule restrictions when the associated connection tracking module was not loaded on the system. An information leak flaw was found in the wathe PostgreSQL database server handled certain error messages. An authenticated database user could possibly obtain the results of a query they did not have privileges to execute by observing the constraint violation error messages produced when the query was executed. It was discovered that a JkUnmount rule for a subtree of a previous JkMount rule could be ignored. This could allow a remote attacker to potentially access a private artifact in a tree that would otherwise not be accessible to them. Multiple insecure temporary file use issues were found in the way the Hotspot component in OpenJDK created performance statistics and error log files. A local attacker could possibly make a victim using OpenJDK overwrite arbitrary files using a symlink attack. A flaw was found in the way the Hotspot component in OpenJDK verified bytecode from the class files. An untrusted Java application or applet could possibly use this flaw to bypass Java sandbox restrictions. An improper permission check issue was discovered in the JAX-WS component in OpenJDK. An untrusted Java application or applet could use these flaws to bypass Java sandbox restrictions. An improper permission check issue was discovered in the RMI component in OpenJDK. An untrusted Java application or applet could use these flaws to bypass Java sandbox restrictions. A flaw was found in the way the Hotspot garbage collector handled phantom references. An untrusted Java application or applet could use this flaw to corrupt the Java Virtual Machine memory and, possibly, execute arbitrary code, bypassing Java sandbox restrictions. An information leak flaw was found in the Swing component in OpenJDK. An untrusted Java application or applet could use this flaw to bypass certain Java sandbox restrictions. A flaw was found in the way the DER (Distinguished Encoding Rules) decoder in the Security component in OpenJDK handled negative length values. A specially crafted, DER-encoded input could cause a Java application to enter an infinite loop when decoded. It was discovered that the SSL/TLS implementation in the JSSE component in OpenJDK failed to properly check whether the ChangeCipherSpec was received during the SSL/TLS connection handshake. An MITM attacker could possibly use this flaw to force a connection to be established without encryption being enabled. A heap-based buffer overflow was found in glibc's __nss_hostname_digits_dots() function, which is used by the gethostbyname() and gethostbyname2() glibc function calls. A remote attacker able to make an application call either of these functions could use this flaw to execute arbitrary code with the permissions of the user running the application. A flaw was found in the way the File Information (fileinfo) extension parsed Executable and Linkable Format (ELF) files. A remote attacker could use this flaw to crash a PHP application using fileinfo via a specially crafted ELF file. It was discovered that the fix for CVE-2014-9493 was incomplete: an authenticated user could use a path traversal flaw in glance to download or delete any file on the glance server that is accessible to the glance process user. Note that only setups using the OpenStack Image V2 API were affected by this flaw. A boundary check flaw was found in the font parsing code in the 2D component in OpenJDK. A specially crafted font file could allow an untrusted Java application or applet to disclose portions of the Java Virtual Machine memory. A boundary check flaw was found in the font parsing code in the 2D component in OpenJDK. A specially crafted font file could allow an untrusted Java application or applet to disclose portions of the Java Virtual Machine memory. A storage quota bypass flaw was found in OpenStack Image (glance). If an image was deleted while it was being uploaded, it would not count towards a user's quota. A malicious user could use this flaw to deliberately fill the backing store, and cause a denial of service. An improper permission check issue was discovered in the Libraries component in OpenJDK. An untrusted Java application or applet could use these flaws to bypass Java sandbox restrictions. A flaw was found in the way the Hotspot component in OpenJDK in the way this component generated code for bytecode. An untrusted Java application or applet could possibly use this flaw to bypass Java sandbox restrictions. A NULL pointer dereference flaw was found in the MulticastSocket implementation in the Libraries component of OpenJDK. An untrusted Java application or applet could possibly use this flaw to bypass certain Java sandbox restrictions. It was discovered that the virDomainSnapshotGetXMLDesc() and virDomainSaveImageGetXMLDesc() functions did not sufficiently limit the usage of the VIR_DOMAIN_XML_SECURE flag when fine-grained ACLs were enabled. A remote attacker able to establish a connection to libvirtd could use this flaw to obtain certain sensitive information from the domain XML file. A buffer overflow was found in the way unzip uncompressed certain extra fields of a file. A specially crafted Zip archive could cause unzip to crash or, possibly, execute arbitrary code when the archive was tested with unzip's '-t' option. A use-after-free flaw was found in the way PHP's unserialize() function processed data. If a remote attacker was able to pass crafted input to PHP's unserialize() function, they could cause the PHP interpreter to crash or, possibly, execute arbitrary code. A heap-based buffer overflow flaw was found in the way grep processed certain pattern and text combinations. An attacker able to trick a user into running grep on specially crafted input could use this flaw to crash grep or, potentially, read from uninitialized memory. An uninitialized pointer use flaw was found in PHP's Exif extension. A specially crafted JPEG or TIFF file could cause a PHP application using the exif_read_data() function to crash or, possibly, execute arbitrary code with the privileges of the user running that PHP application. It was found that a regular user could remove xattr permissions on files by using the chown or write system calls. A local attacker could use this flaw to deny elevated permissions from valid users, services, or applications, potentially resulting in a denial of service. A flaw was found in the way the Linux kernel's Crypto subsystem handled automatic loading of kernel modules. A local user could use this flaw to load any installed kernel module, and thus increase the attack surface of the running kernel. A use-after-free flaw was found in PHP's OPcache extension. This flaw could possibly lead to a disclosure of a portion of the server memory. A NULL pointer dereference flaw was found in PHP's pgsql extension. A specially crafted table name passed to a function such as pg_insert() or pg_select() could cause a PHP application to crash. A flaw was found in the way the Qpid daemon (qpidd) processed certain protocol sequences. An unauthenticated attacker able to send a specially crafted protocol sequence set that could use this flaw to crash qpidd. It was discovered that the Qpid daemon (qpidd) did not restrict access to anonymous users when the ANONYMOUS mechanism was disallowed. It was found that the Linux kernel KVM subsystem's sysenter instruction emulation was not sufficient. An unprivileged guest user could use this flaw to escalate their privileges by tricking the hypervisor to emulate a SYSENTER instruction in 16-bit mode, if the guest OS did not initialize the SYSENTER model-specific registers (MSRs). Note: Certified guest operating systems for Red Hat Enterprise Linux with KVM do initialize the SYSENTER MSRs and are thus not vulnerable to this issue when running on a KVM hypervisor. A cross-site scripting vulnerability was discovered in RabbitMQ, which allowed using api/ path info to inject and receive data. A remote attacker could use this flaw to create an "/api/..." URL, forcing a server error that resulted in the server returning an HTML page with embedded text from the URL (not escaped). A response-splitting vulnerability was discovered in RabbitMQ. An /api/definitions URL could be specified, which then caused an arbitrary additional header to be returned. A remote attacker could use this flaw to inject arbitrary HTTP headers and possibly gain access to secure data. A heap-based buffer overflow flaw was found in e2fsprogs. A specially crafted Ext2/3/4 file system could cause an application using the ext2fs library (for example, fsck) to crash or, possibly, execute arbitrary code. It was discovered that, under certain circumstances, glibc's getaddrinfo() function would send DNS queries to random file descriptors. An attacker could potentially use this flaw to send DNS queries to unintended recipients, resulting in information disclosure or data loss due to the application encountering corrupted data. It was found that the RPC interface in Satellite would resolve external entities, allowing an attacker to conduct XML External Entity (XXE) attacks. A remote attacker could use this flaw to read files accessible to the user running the Satellite server, and potentially perform other more advanced XXE attacks. It was found that an XMLRPC interface exposed by Satellite could allow an attacker to write arbitrary files and directories under the /var/satellite directory on the Satellite server. It was discovered that the permissions to allow or deny snapshot creation were ignored during live storage migration of a VM's disk between storage domains. An attacker able to live migrate a disk between storage domains could use this flaw to cause a denial of service. An invalid free flaw was found in glibc's getaddrinfo() function when used with the AI_IDN flag. A remote attacker able to make an application call this function could use this flaw to execute arbitrary code with the permissions of the user running the application. Note that this flaw only affected applications using glibc compiled with libidn support. A buffer overflow flaw was found in the way PostgreSQL handled certain numeric formatting. An authenticated database user could use a specially crafted timestamp formatting template to cause PostgreSQL to crash or, under certain conditions, execute arbitrary code with the permissions of the user running PostgreSQL. A buffer overflow flaw was found in the PostgreSQL's internal printf() implementation. An authenticated database user could use a specially crafted string in an SQL query to cause PostgreSQL to crash or, potentially, lead to privilege escalation. A stack-buffer overflow flaw was found in PostgreSQL's pgcrypto module. An authenticated database user could use this flaw to cause PostgreSQL to crash or, potentially, execute arbitrary code with the permissions of the user running PostgreSQL. A flaw was found in the way PostgreSQL handled certain errors that were generated during protocol synchronization. An authenticated database user could use this flaw to inject queries into an existing connection. A heap-based buffer overflow flaw was found in glibc's swscanf() function. An attacker able to make an application call the swscanf() function could use this flaw to crash that application or, potentially, execute arbitrary code with the permissions of the user running the application. A buffer overflow flaw was found in the way the X.Org server handled XkbGetGeometry requests. A malicious, authorized client could use this flaw to disclose portions of the X.Org server memory, or cause the X.Org server to crash using a specially crafted XkbGetGeometry request. It was found that the amsvis command of the powerpc-utils-python package did not verify unpickled data before processing it. This could allow an attacker who can connect to an amsvis server process (or cause an amsvis client process to connect to them) to execute arbitrary code as the user running the amsvis process. It was discovered that a directory shared between the ovirt-engine-dwhd service and a plug-in used during the service's startup had incorrect permissions. A local user could use this flaw to access files in this directory, which could potentially contain sensitive information. An out-of-bounds stack buffer read flaw was found in WavPack. This flaw could potentially be used to crash WavPack CLI utilities by tricking them into processing specially crafted WAVE files. An ouf-of-bounds read flaw was found in the way the file utility processed certain Pascal strings. A remote attacker could cause an application using the file utility (for example, PHP using the fileinfo module) to crash if it was used to identify the type of the attacker-supplied file. A flaw was found in the way the File Information (fileinfo) extension parsed Executable and Linkable Format (ELF) files. A remote attacker could use this flaw to cause a PHP application using fileinfo to crash or disclose certain portions of server memory. It was discovered that the OpenStack Compute (nova) console websocket did not correctly verify the origin header. An attacker could use this flaw to conduct a cross-site websocket hijack attack. Note that only Compute setups with VNC or SPICE enabled were affected by this flaw. It was found that the PHP WSDL extension used a file with a predictable name in a world readable directory as a cache. A local attacker could use this flaw to poison the cache using a specially crafted temporary file. A flaw was found in the way the Linux kernel's Crypto subsystem handled automatic loading of kernel modules. A local user could use this flaw to load any installed kernel module, and thus increase the attack surface of the running kernel. A flaw was found in the way the CUPS daemon added shared printers announced through the network. A malicious host or user could send a specially crafted UDP packet to a CUPS server that, when processed, could potentially lead to arbitrary code execution with the privileges of the user running the CUPS daemon. An integer signedness flaw, leading to a heap-based buffer overflow, was found in the way FreeType handled Mac fonts. If a specially crafted font file was loaded by an application linked against FreeType, it could cause the application to crash or, potentially, execute arbitrary code with the privileges of the user running the application. Multiple integer overflow flaws, leading to heap-based buffer overflows, were found in the way FreeType handled Mac fonts. If a specially crafted font file was loaded by an application linked against FreeType, it could cause the application to crash or, potentially, execute arbitrary code with the privileges of the user running the application. It was found that Tomcat would keep connections open after processing requests with a large enough request body. A remote attacker could potentially use this flaw to exhaust the pool of available connections and preventing further, legitimate connections to the Tomcat server to be made. A flaw was found in the way the nft_flush_table() function of the Linux kernel's netfilter tables implementation flushed rules that were referencing deleted chains. A local user who has the CAP_NET_ADMIN capability could use this flaw to crash the system. An uninitialized pointer use flaw was found in the Samba daemon (smbd). A malicious Samba client could send specially crafted netlogon packets that, when processed by smbd, could potentially lead to arbitrary code execution with the privileges of the user running smbd (by default, the root user). It was found that a prior countermeasure in Apache WSS4J for Bleichenbacher's attack on XML Encryption (CVE-2011-2487) threw an exception that permitted an attacker to determine the failure of the attempted attack, thereby leaving WSS4J vulnerable to the attack. The original flaw allowed a remote attacker to recover the entire plain text form of a symmetric key. It was found that Apache WSS4J permitted bypass of the requireSignedEncryptedDataElements configuration property via XML Signature wrapping attacks. A remote attacker could use this flaw to modify the contents of a signed request. It was found that the VDSM SSL certificate validation implementation did not check whether the server host name matched the domain name in a subject's Common Name (CN) field in a X.509 certificate. A man-in-the-middle attacker could use this flaw to spoof a VDSM server using a specially crafted X.509 certificate. It was reported that Elasticsearch versions 1.3.0-1.3.7 and 1.4.0-1.4.2 have vulnerabilities in the Groovy scripting engine. The vulnerability allows an attacker to construct Groovy scripts that escape the sandbox and execute shell commands as the user running the Elasticsearch Java VM. It was discovered that sudo did not perform any checks of the TZ environment variable value. If sudo was configured to preserve the TZ environment variable, a local user with privileges to execute commands via sudo could possibly use this flaw to achieve system state changes not permitted by the configured commands. Note: The default sudoers configuration in Red Hat Enterprise Linux removes the TZ variable from the environment in which commands run by sudo are executed. Quick Emulator (QEMU), compiled with qemu_map_ram_ptr to access guests' RAM block area, is vulnerable to an OOB r/w access issue. The crash can occur if a privileged user inside a guest conducts certain DMA operations, resulting in a DoS. An integer overflow flaw, leading to a heap-based buffer overflow, was found in the way CUPS handled compressed raster image files. An attacker could create a specially crafted image file that, when passed via the CUPS Raster filter, could cause the CUPS filter to crash. It was found that program-based automounter maps that used interpreted languages such as Python would use standard environment variables to locate and load modules of those languages. A local attacker could potentially use this flaw to escalate their privileges on the system. An integer overflow flaw was found in the way the Linux kernel randomized the stack for processes on certain 64-bit architecture systems, such as x86-64, causing the stack entropy to be reduced by four. It was found that the module-setup.sh script provided by kexec-tools created temporary files in an insecure way. A malicious, local user could use this flaw to conduct a symbolic link attack, allowing them to overwrite the contents of arbitrary files. It was found that the local log-viewing function of the redhat-access-plugin for OpenStack Dashboard (horizon) did not sanitize user input. An authenticated user could use this flaw to read an arbitrary file with the permissions of the web server. A flaw was found in the way BIND handled trust anchor management. A remote attacker could use this flaw to cause the BIND daemon (named) to crash under certain conditions. It was discovered that NetworkManager would set device MTUs based on MTU values received in IPv6 RAs (Router Advertisements), without sanity checking the MTU value first. A remote attacker could exploit this flaw to create a denial of service attack, by sending a specially crafted IPv6 RA packet to disturb IPv6 communication. A buffer overflow flaw was found in the way the Linux kernel's eCryptfs implementation decoded encrypted file names. A local, unprivileged user could use this flaw to crash the system or, potentially, escalate their privileges on the system. It was found that the krb5_read_message() function of MIT Kerberos did not correctly sanitize input, and could create invalid krb5_data objects. A remote, unauthenticated attacker could use this flaw to crash a Kerberos child process via a specially crafted request. A heap-based buffer overflow flaw was found in e2fsprogs. A specially crafted Ext2/3/4 file system could cause an application using the ext2fs library (for example, fsck) to crash or, possibly, execute arbitrary code. A flaw was found in the way the Linux kernel's ext4 file system handled the "page size > block size" condition when the fallocate zero range functionality was used. A local attacker could use this flaw to crash the system. Multiple flaws were found in the glance task API that could cause untracked image data to be left in the back end. A malicious user could use these flaws to deliberately accumulate untracked image data, and cause a denial of service via resource exhaustion. Multiple flaws were found in the glance task API that could cause untracked image data to be left in the back end. A malicious user could use these flaws to deliberately accumulate untracked image data, and cause a denial of service via resource exhaustion. A use-after-free flaw was found in the unserialize() function of PHP's DateTimeZone implementation. A malicious script author could possibly use this flaw to disclose certain portions of server memory. A flaw was found in the way PicketLink's Service Provider and Identity Provider handled certain requests. A remote attacker could use this flaw to log to a victim's account via PicketLink. A flaw was found in the way the Linux kernel's XFS file system handled replacing of remote attributes under certain conditions. A local user with access to XFS file system mount could potentially use this flaw to escalate their privileges on the system. An information leak flaw was found in the way Firefox implemented autocomplete forms. An attacker able to trick a user into specifying a local file in the form could use this flaw to access the contents of that file. It was found that the 'do' parameter permitted expression language (EL) injection, which could allow a remote attacker to execute Java methods on an affected server. It was found that GnuTLS did not verify whether a hashing algorithm listed in a signature matched the hashing algorithm listed in the certificate. An attacker could create a certificate that used a different hashing algorithm than it claimed, possibly causing GnuTLS to use an insecure, disallowed hashing algorithm during certificate verification. It was discovered that the slapi-nis Directory Server plug-in did not correctly perform memory reallocation when handling user account information. A request for information about a group with many members, or a request for a user that belongs to a large number of groups, would cause a Directory Server to enter an infinite loop and consume an excessive amount of CPU time. A cross-site scripting (XSS) flaw was found in how XML data was handled in Red Hat Satellite. A user able to use the XMLRPC API could exploit this flaw to perform XSS attacks against other Satellite users. It was discovered that GnuTLS did not check if all sections of X.509 certificates indicate the same signature algorithm. This flaw, in combination with a different flaw, could possibly lead to a bypass of the certificate signature check. A use-after-free flaw was found in the way the Linux kernel's SCTP implementation handled authentication key reference counting during INIT collisions. A remote attacker could use this flaw to crash the system or, potentially, escalate their privileges on the system. A use-after-free flaw was found in the way OpenSSL imported malformed Elliptic Curve private keys. A specially crafted key file could cause an application using OpenSSL to crash when imported. A flaw was found in the way the mod_cluster manager processed certain MCMP messages. An attacker with access to the network from which MCMP messages are allowed to be sent could use this flaw to execute arbitrary JavaScript code in the mod_cluster manager web interface. It was found that GnuTLS did not check activation and expiration dates of CA certificates. This could cause an application using GnuTLS to incorrectly accept a certificate as valid when its issuing CA is already expired. It was discovered that the JBoss Operations Network server did not correctly restrict access to certain remote APIs. A remote, unauthenticated attacker could use this flaw to execute arbitrary Java methods via ServerInvokerServlet or SchedulerService, and possibly exhaust all available disk space via ContentManager. It was found that the Linux kernel memory resource controller's (memcg) handling of OOM (out of memory) conditions could lead to deadlocks. An attacker able to continuously spawn new processes within a single memory-constrained cgroup during an OOM event could use this flaw to lock up the system. It was found that the Apache ActiveMQ broker exposed a remote shutdown command without requiring any authentication to use it. A remote, unauthenticated attacker could use this flaw to shut down ActiveMQ broker's listener. It was found that the Xen hypervisor x86 CPU emulator implementation did not correctly handle certain instructions with segment overrides, potentially resulting in a memory corruption. A malicious guest user could use this flaw to read arbitrary data relating to other guests, cause a denial of service on the host, or potentially escalate their privileges on the host. A NULL pointer dereference flaw was found in the way the Linux kernel's madvise MADV_WILLNEED functionality handled page table locking. A local, unprivileged user could use this flaw to crash the system. It was found that due to excessive files_lock locking, a soft lockup could be triggered in the Linux kernel when performing asynchronous I/O operations. A local, unprivileged user could use this flaw to crash the system. It was found that the Java Standard Tag Library (JSTL) allowed the processing of untrusted XML documents to utilize external entity references, which could access resources on the host system and, potentially, allowing arbitrary code execution. A flaw was found in the way the Xerces-C XML parser processed certain XML documents. A remote attacker could provide specially crafted XML input that, when parsed by an application using Xerces-C, would cause that application to crash. A buffer overflow flaw was found in the way glibc's gethostbyname_r() and other related functions computed the size of a buffer when passed a misaligned buffer as input. An attacker able to make an application call any of these functions with a misaligned buffer could use this flaw to crash the application or, potentially, execute arbitrary code with the permissions of the user running the application. It was found that the QEMU's websocket frame decoder processed incoming frames without limiting resources used to process the header and the payload. An attacker able to access a guest's VNC console could use this flaw to trigger a denial of service on the host by exhausting all available memory and CPU. A flaw was found in the way MongoDB processed certain BSON-serialized UTF-8 strings. A remote, unauthenticated attacker could use this flaw to crash a mongod server via a specially crafted BSON message. It was found that glusterfs-server RPM package would write file with predictable name into world readable /tmp directory. A local attacker could potentially use this flaw to escalate their privileges to root by modifying the shell script during the installation of the glusterfs-server package. An out of bound read, with a maximum of 5 bytes, was found in the way the is_utf8_well_formed() function parsed UTF-8 characters. If less was to be recompiled with an address sanitizer, a specially crafted input could crash less. It was found that PKIX trust components allowed an X.509 credential to be trusted if no trusted names were available for the entityID. An attacker could use a certificate issued by a shibmd:KeyAuthority trust anchor to impersonate an entity within the scope of that keyAuthority. It was discovered that noVNC did not properly set the 'secure' flag when issuing cookies. An attacker could use this flaw to intercept cookies via a man-in-the-middle attack. A flaw was found in the way the kex_agree_methods() function of libssh2 performed a key exchange when negotiating a new SSH session. A man-in-the-middle attacker could use a crafted SSH_MSG_KEXINIT packet to crash a connecting libssh2 client. A NULL pointer dereference flaw was found in the way the Linux kernel's virtual console implementation handled reference counting when accessing pseudo-terminal device files (/dev/pts/*). A local, unprivileged attacker could use this flaw to crash the system. A heap buffer overflow flaw was found in the enchant_broker_request_dict() function of PHP's enchant extension. A specially crafted tag input could possibly cause a PHP application to crash. A use-after-free flaw was found in PHP's phar (PHP Archive) paths implementation. A malicious script author could possibly use this flaw to disclose certain portions of server memory. A heap buffer overflow flaw was found in the regcomp() function of Henry Spencer's regular expression library. An attacker able to make an application process a specially crafted regular expression pattern with the regcomp() function could cause that application to crash and possibly execute arbitrary code. An invalid pointer use flaw was found in OpenSSL's ASN1_TYPE_cmp() function. A remote attacker could crash a TLS/SSL client or server using OpenSSL via a specially crafted X.509 certificate when the attacker-supplied certificate was verified by the application. An out-of-bounds write flaw was found in the way OpenSSL reused certain ASN.1 structures. A remote attacker could possibly use a specially crafted ASN.1 structure that, when parsed by an application, would cause that application to crash. A NULL pointer dereference was found in the way OpenSSL handled certain PKCS#7 inputs. An attacker able to make an application using OpenSSL verify, decrypt, or parse a specially crafted PKCS#7 input could cause that application to crash. TLS/SSL clients and servers using OpenSSL were not affected by this flaw. An integer underflow flaw, leading to a buffer overflow, was found in the way OpenSSL decoded malformed Base64-encoded inputs. An attacker able to make an application using OpenSSL decode a specially crafted Base64-encoded input (such as a PEM file) could use this flaw to cause the application to crash. Note: this flaw is not exploitable via the TLS/SSL protocol because the data being transferred is not Base64-encoded. A denial of service flaw was found in the way OpenSSL handled SSLv2 handshake messages. A remote attacker could use this flaw to cause a TLS/SSL server using OpenSSL to exit on a failed assertion if it had both the SSLv2 protocol and EXPORT-grade cipher suites enabled. A NULL pointer dereference flaw was found in OpenSSL's X.509 certificate handling implementation. A specially crafted X.509 certificate could cause an application using OpenSSL to crash if the application attempted to convert the certificate to a certificate request. It was found that ntpd did not check whether a Message Authentication Code (MAC) was present in a received packet when ntpd was configured to use symmetric cryptographic keys. A man-in-the-middle attacker could use this flaw to send crafted packets that would be accepted by a client or a peer without the attacker knowing the symmetric key. A denial of service flaw was found in the way NTP hosts that were peering with each other authenticated themselves before updating their internal state variables. An attacker could send packets to one peer host, which could cascade to other peers, and stop the synchronization process among the reached peers. It was found that the Linux kernel's implementation of vectored pipe read and write functionality did not take into account the I/O vectors that were already processed when retrying after a failed atomic access operation, potentially resulting in memory corruption due to an I/O vector array overrun. A local, unprivileged user could use this flaw to crash the system or, potentially, escalate their privileges on the system. A flaw was found in the way python-requests set the domain cookie parameter for certain HTTP responses. A remote attacker could use this flaw to modify a cookie to be sent to an arbitrary URL. A denial of service flaw was found in the way the mod_lua httpd module processed certain WebSocket Ping requests. A remote attacker could send a specially crafted WebSocket Ping packet that would cause the httpd child process to crash. It was found that Apache Camel performed XML External Entity (XXE) expansion when evaluating invalid XML Strings or invalid XML GenericFile objects. A remote attacker able to submit a crafted XML message could use this flaw to read files accessible to the user running the application server, and potentially perform other more advanced XXE attacks. It was found that Apache Camel's XML converter performed XML External Entity (XXE) expansion. A remote attacker able to submit an SAXSource containing an XXE declaration could use this flaw to read files accessible to the user running the application server, and potentially perform other more advanced XXE attacks. An integer overflow flaw was found in the way libXfont processed certain Glyph Bitmap Distribution Format (BDF) fonts. A malicious, local user could use this flaw to crash the X.Org server or, potentially, execute arbitrary code with the privileges of the X.Org server. A NULL pointer dereference flaw was discovered in the way libXfont processed certain Glyph Bitmap Distribution Format (BDF) fonts. A malicious, local user could use this flaw to crash the X.Org server. An integer truncation flaw was discovered in the way libXfont processed certain Glyph Bitmap Distribution Format (BDF) fonts. A malicious, local user could use this flaw to crash the X.Org server or, potentially, execute arbitrary code with the privileges of the X.Org server. It was found that batik was vulnerable to XML External Entity attacks when parsing SVG files. A remote attacker able to send malicious SVG content to the affected server could use this flaw to read files accessible to the user running the application server, and potentially perform other more advanced XXE attacks. It was found that setroubleshoot did not sanitize file names supplied in a shell command look-up for RPMs associated with access violation reports. An attacker could use this flaw to escalate their privileges on the system by supplying a specially crafted file to the underlying shell command. An integer overflow flaw, leading to a heap-based buffer overflow, was found in the way libzip, which is also embedded in PHP, processed certain ZIP archives. If an attacker were able to supply a specially crafted ZIP archive to an application using libzip, it could cause the application to crash or, possibly, execute arbitrary code. It was found that the OAuth implementation in librest, a helper library for RESTful services, incorrectly truncated the pointer returned by the rest_proxy_call_get_url call. An attacker could use this flaw to crash an application using the librest library. A stack-based buffer overflow flaw was found in the Linux kernel's early load microcode functionality. On a system with UEFI Secure Boot enabled, a local, privileged user could use this flaw to increase their privileges to the kernel (ring0) level, bypassing intended restrictions in place. A flaw was found in the dashbuilder import facility: the DocumentBuilders instantiated in org.jboss.dashboard.export.ImportManagerImpl did not disable external entities. This could allow an attacker to perform a variety of XML External Entity (XXE) and Server-Side Request Forgery (SSRF) attacks. A buffer over-read flaw was found in the GD library. A specially crafted GIF file could cause an application using the gdImageCreateFromGif() function to crash. It was found that JBoss Fuse would allow any user defined in the users.properties file to access the HawtIO console without having a valid admin role. This could allow a remote attacker to bypass intended authentication HawtIO console access restrictions. An assertion failure flaw was found in the way the SVN server processed certain requests with dynamically evaluated revision numbers. A remote attacker could use this flaw to cause the SVN server (both svnserve and httpd with the mod_dav_svn module) to crash. It was found that the mod_dav_svn module did not properly validate the svn:author property of certain requests. An attacker able to create new revisions could use this flaw to spoof the svn:author property. It was discovered that the IPA extdom Directory Server plug-in did not correctly perform memory reallocation when handling user account information. A request for a list of groups for a user that belongs to a large number of groups would cause a Directory Server to crash. Two cross-site scripting (XSS) flaws were found in Jenkins. A remote attacker could use these flaws to conduct XSS attacks against users of an application using Jenkins. Two cross-site scripting (XSS) flaws were found in Jenkins. A remote attacker could use these flaws to conduct XSS attacks against users of an application using Jenkins. A flaw was found in the Jenkins API token-issuing service. The service was not properly protected against anonymous users, potentially allowing remote attackers to escalate privileges. It was found that the combination filter Groovy script could allow a remote attacker to potentially execute arbitrary code on a Jenkins master. It was found that when building artifacts, the Jenkins server would follow symbolic links, potentially resulting in disclosure of information on the server. A denial of service flaw was found in the way Jenkins handled certain update center data. An authenticated user could provide specially crafted update center data to Jenkins, causing plug-in and tool installation to not work properly. It was found that Jenkins' XPath handling allowed XML External Entity (XXE) expansion. A remote attacker with read access could use this flaw to read arbitrary XML files on the Jenkins server. It was discovered that the internal Jenkins user database did not restrict access to reserved names, allowing users to escalate privileges. It was found that Jenkins' XML handling allowed XML External Entity (XXE) expansion. A remote attacker with the ability to pass XML data to Jenkins could use this flaw to read arbitrary XML files on the Jenkins server. A flaw was found in the way realmd parsed certain input when writing configuration into the sssd.conf or smb.conf file. A remote attacker could use this flaw to inject arbitrary configurations into these files via a newline character in an LDAP response. It was found that the idle timeout in the Red Hat Enterprise Virtualization Manager Web Admin interface failed to log out a session if a VM has been selected in the VM grid view. This could allow a local attacker to access the web interface if it was left unattended. It was discovered that the puppet manifests, as provided with the openstack-puppet-modules package, would configure the pcsd daemon with a known default password. If this password was not changed and an attacker was able to gain access to pcsd, they could potentially run shell commands as root. It was found that the fix for the CVE-2014-5277 issue was incomplete: the docker client could under certain circumstances erroneously fall back to HTTP when an HTTPS connection to a registry failed. This could allow a man-in-the-middle attacker to obtain authentication and image data from traffic sent from a client to the registry. A flaw was found in the way documents were loaded via resource URLs in, for example, Mozilla's PDF.js PDF file viewer. An attacker could use this flaw to bypass certain restrictions and under certain conditions even execute arbitrary code with the privileges of the user running Firefox. A flaw was found in the Beacon interface implementation in Firefox. A web page containing malicious content could allow a remote attacker to conduct a Cross-Site Request Forgery (CSRF) attack. A flaw was found in the way foreman authorized user actions on resources via the API when an organization was not explicitly set. A remote attacker could use this flaw to obtain additional information about resources they were not authorized to access. A flaws was discovered in the way PHP performed object unserialization. Specially crafted input processed by the unserialize() function could cause a PHP application to crash or, possibly, execute arbitrary code. It was found that PHP move_uploaded_file() function did not properly handle file names with a NULL character. A remote attacker could possibly use this flaw to make a PHP script access unexpected files and bypass intended file system access restrictions. A stack-based buffer overflow was found in the way libtasn1 decoded certain DER encoded data. An attacker could use this flaw to crash an application using the libtasn1 library. It was found that mailman did not sanitize the list name before passing it to certain MTAs. A local attacker could use this flaw to execute arbitrary code as the user running mailman. It was found that Apache Cassandra bound an unauthenticated JMX/RMI interface to all network interfaces. A remote attacker able to access the RMI, an API for the transport and remote execution of serialized Java, could use this flaw to execute arbitrary code as the user running Cassandra. It was found that the pcs daemon did not sign cookies containing session data that were sent to clients connecting via the pcsd web UI. A remote attacker could use this flaw to forge cookies and bypass authorization checks, possibly gaining elevated privileges in the pcsd web UI. It was found that when making an SSL connection to an LDAP authentication source in Foreman, the remote server certificate was accepted without any verification against known certificate authorities, potentially making TLS connections vulnerable to man-in-the-middle attacks. A flaw was found in the way the Linux kernel's 32-bit emulation implementation handled forking or closing of a task with an 'int80' entry. A local user could potentially use this flaw to escalate their privileges on the system. A stack overflow flaw was found in glibc's swscanf() function. An attacker able to make an application call the swscanf() function could use this flaw to crash that application or, potentially, execute arbitrary code with the permissions of the user running the application. It was found that the Linux kernel's TCP/IP protocol suite implementation for IPv6 allowed the Hop Limit value to be set to a smaller value than the default one. An attacker on a local network could use this flaw to prevent systems on that network from sending or receiving network packets. A flaw was found in the way the Linux kernel's file system implementation handled rename operations in which the source was inside and the destination was outside of a bind mount. A privileged user inside a container could use this flaw to escape the bind mount and, potentially, escalate their privileges on the system. It was discovered that some items in the S3Token paste configuration as used by python-keystonemiddleware (formerly python-keystoneclient) were incorrectly evaluated as strings, an issue similar to CVE-2014-7144. If the "insecure" option were set to "false", the option would be evaluated as true, resulting in TLS connections being vulnerable to man-in-the-middle attacks. Note: the "insecure" option defaults to false, so setups that do not specifically define "insecure=false" are not affected. A denial of service flaw was found in the way chrony hosts that were peering with each other authenticated themselves before updating their internal state variables. An attacker could send packets to one peer host, which could cascade to other peers, and stop the synchronization process among the reached peers. A flaw was found in the way Red Hat Directory Server performed authorization of modrdn operations. An unauthenticated attacker able to issue an ldapmodrdn call to the directory server could use this flaw to perform unauthorized modifications of entries in the directory server. An out-of-bounds write flaw was found in the way Chrony stored certain addresses when configuring NTP or cmdmon access. An attacker that has the command key and is allowed to access cmdmon (only localhost is allowed by default) could use this flaw to crash chronyd or, possibly, execute arbitrary code with the privileges of the chronyd process. An uninitialized pointer use flaw was found when allocating memory to save unacknowledged replies to authenticated command requests. An attacker that has the command key and is allowed to access cmdmon (only localhost is allowed by default) could use this flaw to crash chronyd or, possibly, execute arbitrary code with the privileges of the chronyd process. A flaw was found in the way NetworkManager handled router advertisements. An unprivileged user on a local network could use IPv6 Neighbor Discovery ICMP to broadcast a non-route with a low hop limit, causing machines to lower the hop limit on existing IPv6 routes. If this limit is small enough, IPv6 packets would be dropped before reaching the final destination. It was discovered that the Ruby OpenSSL extension was overly permissive when verifying host names against X.509 certificate names with wildcards. This could cause Ruby TLS/SSL clients to accept certain certificates as valid, which is a violation of the RFC 6125 recommendations. A flaw was found in OpenStack Object Storage that could allow an authenticated user to delete the most recent version of a versioned object regardless of ownership. To exploit this flaw, an attacker must know the name of the object and have listing access to the x-versions-location container. An integer overflow flaw was found in the way the Linux kernel's netfilter connection tracking implementation loaded extensions. An attacker on a local network could potentially send a sequence of specially crafted packets that would initiate the loading of a large number of extensions, causing the targeted system in that network to crash. A memory corruption flaw was found in the way Qt handled certain Bitmap (BMP) files. If a user loaded a specially crafted BMP image file with an application linked against Qt, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. A memory corruption flaw was found in the way Qt handled certain Icon (ICO) files. If a user loaded a specially crafted ICO image file with an application linked against Qt, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. A memory corruption flaw was found in the way Qt handled certain GIF image files. If a user loaded a specially crafted GIF image file with an application linked against Qt, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. It was discovered that ceph-deploy, a utility for deploying Red Hat Ceph Storage, would create the keyring file with world readable permissions, which could possibly allow a local user to obtain authentication credentials from the keyring file. A buffer overflow flaw was found in the way wpa_supplicant handled SSID information in the Wi-Fi Direct / P2P management frames. A specially crafted frame could allow an attacker within Wi-Fi radio range to cause wpa_supplicant to crash or, possibly, execute arbitrary code. A flaw was found in the way certain ABRT core handlers processed crash reports in a namespaced environment. A local, unprivileged user could use this flaw to escalate their privileges on the system. An off-by-one flaw, leading to a buffer overflow, was found in the font parsing code in the 2D component in OpenJDK. A specially crafted font file could possibly cause the Java Virtual Machine to execute arbitrary code, allowing an untrusted Java application or applet to bypass Java sandbox restrictions. A denial of service flaw was found in the way the libxml2 library parsed certain XML files. An attacker could provide a specially crafted XML file that, when parsed by an application using libxml2, could cause that application to use an excessive amount of memory. A flaw was found in the way the Hotspot component in OpenJDK handled phantom references. An untrusted Java application or applet could use this flaw to corrupt the Java Virtual Machine memory and, possibly, execute arbitrary code, bypassing Java sandbox restrictions. A flaw was discovered in the Beans component in OpenJDK. An untrusted Java application or applet could use these flaws to bypass certain Java sandbox restrictions. A flaw was found in the way pacemaker, a cluster resource manager, evaluated added nodes in certain situations. A user with read-only access could potentially assign any other existing roles to themselves and then add privileges to other users as well. A flaw was discovered in the Hotspot component in OpenJDK. An untrusted Java application or applet could use these flaws to bypass certain Java sandbox restrictions. It was found that the RSA implementation in the JCE component in OpenJDK did not follow recommended practices for implementing RSA signatures. A directory traversal flaw was found in the way the jar tool extracted JAR archive files. A specially crafted JAR archive could cause jar to overwrite arbitrary files writable by the user running jar when the archive was extracted. A flaw was found in the way the JSSE component in OpenJDK parsed X.509 certificate options. A specially crafted certificate could cause JSSE to raise an exception, possibly causing an application using JSSE to exit unexpectedly. It was found that ABRT was vulnerable to multiple race condition and symbolic link flaws. A local attacker could use either of these flaws to potentially escalate their privileges on the system. It was discovered that the kernel-invoked coredump processor provided by ABRT wrote core dumps to files owned by other system users. This could result in information disclosure if an application crashed while its current directory was a directory writable to by other users (such as /tmp). It was discovered that the default event handling scripts installed by ABRT did not handle symbolic links correctly. A local attacker with write access to an ABRT problem directory could use this flaw to escalate their privileges. It was found that the ABRT event scripts created a user-readable copy of an sosreport file in ABRT problem directories, and included excerpts of /var/log/messages selected by the user-controlled process name, leading to an information disclosure. The fix for this issue prevents non-privileged users from accessing any crash reports, even reports of crashes of processes owned by those users. Only administrators (the wheel group members) are allowed to access crash reports via the "System" tab in the ABRT GUI, or by running abrt-cli as root (that is, via "sudo abrt-cli" or "su -c abrt-cli"). It was discovered that, when moving problem reports between certain directories, abrt-handle-upload did not verify that the new problem directory had appropriate permissions and did not contain symbolic links. An attacker able to create a crafted problem report could use this flaw to expose other parts of ABRT, or to overwrite arbitrary files on the system. It was discovered that libcurl could incorrectly reuse NTLM-authenticated connections for subsequent unauthenticated requests to the same host. If an application using libcurl established an NTLM-authenticated connection to a server, and sent subsequent unauthenticated requests to the same server, the unauthenticated requests could be sent over the NTLM-authenticated connection, appearing as if they were sent by the NTLM authenticated user. A buffer overflow flaw was found in the way the Linux kernel's Intel AES-NI instructions optimized version of the RFC4106 GCM mode decryption functionality handled fragmented packets. A remote attacker could use this flaw to crash, or potentially escalate their privileges on, a system over a connection with an active AES-GCM mode IPSec security association. It was discovered that libcurl did not properly process zero-length host names. If an attacker could trick an application using libcurl into processing zero-length host names, this could lead to an out-of-bounds read, and possibly cause that application to crash. It was discovered that libcurl did not properly process cookies with a specially crafted "path" element. If an application using libcurl connected to a malicious HTTP server sending specially crafted "Set-Cookies" headers, this could lead to an out-of-bounds read, and possibly cause that application to crash. It was discovered that libcurl could incorrectly reuse Negotiate authenticated HTTP connections for subsequent requests. If an application using libcurl established a Negotiate authenticated HTTP connection to a server and sent subsequent requests with different credentials, the connection could be re-used with the initial set of credentials instead of using the new ones. A flaw was found in the way the PHP module for the Apache httpd web server handled pipelined requests. A remote attacker could use this flaw to trigger the execution of a PHP script in a deinitialized interpreter, causing it to crash or, possibly, execute arbitrary code. A buffer over-read flaw was found in PHP's phar (PHP Archive) paths implementation. A malicious script author could possibly use this flaw to disclose certain portions of server memory. A buffer overflow flaw was found in the way PHP's Phar extension parsed Phar archives. A specially crafted archive could cause PHP to crash or, possibly, execute arbitrary code when opened. A flaw was found in the processing of malformed web content. A web page containing malicious content could cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox. A race condition flaw was found between the chown and execve system calls. When changing the owner of a setuid user binary to root, the race condition could momentarily make the binary setuid root. A local, unprivileged user could potentially use this flaw to escalate their privileges on the system. A denial of service flaw was found in the way QEMU handled malformed Physical Region Descriptor Table (PRDT) data sent to the host's IDE and/or AHCI controller emulation. A privileged guest user could use this flaw to crash the system. Multiple directory traversal flaws were found in the abrt-dbus D-Bus service. A local attacker could use these flaws to read and write arbitrary files as the root user. It was discovered that the abrt-dbus D-Bus service did not properly check the validity of the problem directory argument in the ChownProblemDir, DeleteElement, and DeleteProblem methods. A local attacker could use this flaw take ownership of arbitrary files and directories, or to delete files and directories as the root user. A flaw was found in the way the ntp-keygen utility generated MD5 symmetric keys on big-endian systems. An attacker could possibly use this flaw to guess generated MD5 keys, which could then be used to spoof an NTP client or server. A divide-by-zero flaw was found in the way the X.Org server checked the dimensions of certain images. An attacker could potentially crash the X.Org server by tricking a suitable X application into displaying a specially crafted image file. It was found that Foreman did not set the HttpOnly flag on session cookies. This could allow a malicious script to access the session cookie. A flaw was found in the way the LibreOffice HWP (Hangul Word Processor) file filter processed certain HWP documents. An attacker able to trick a user into opening a specially crafted HWP document could possibly use this flaw to execute arbitrary code with the privileges of the user opening that document. A flaw was found in the way SQLite handled dequoting of collation-sequence names. A local attacker could submit a specially crafted COLLATE statement that would crash the SQLite process, or have other unspecified impacts. It was found that SQLite's sqlite3VdbeExec() function did not properly implement comparison operators. A local attacker could submit a specially crafted CHECK statement that would crash the SQLite process, or have other unspecified impacts. It was found that SQLite's sqlite3VXPrintf() function did not properly handle precision and width values during floating-point conversions. A local attacker could submit a specially crafted SELECT statement that would crash the SQLite process, or have other unspecified impacts. A flaw was found in the PicketLink Identity Provider Configuration (IDP) where, under specific conditions, the IDP ignores role-based authorization. This could lead to an authenticated user being able to access application resources that are not permitted for a given role. A flaw was found in the OTP kdcpreauth module of MIT Kerberos. A remote attacker could use this flaw to bypass the requires_preauth flag on a client principal and obtain a ciphertext encrypted in the principal's long-term key. This ciphertext could be used to conduct an off-line dictionary attack against the user's password. It was discovered that the abrt-action-install-debuginfo-to-abrt-cache helper program did not properly filter the process environment before invoking abrt-action-install-debuginfo. A local attacker could use this flaw to escalate their privileges on the system. It was found that the MySQL client library permitted but did not require a client to use SSL/TLS when establishing a secure connection to a MySQL server using the "--ssl" option. A man-in-the-middle attacker could use this flaw to strip the SSL/TLS protection from a connection between a client and a server. It was found that the Linux kernel's ping socket implementation did not properly handle socket unhashing during spurious disconnects, which could lead to a use-after-free flaw. On x86-64 architecture systems, a local user able to create ping sockets could use this flaw to crash the system. On non-x86-64 architecture systems, a local user able to create ping sockets could use this flaw to escalate their privileges on the system. It was found that Squid configured with client-first SSL-bump did not correctly validate X.509 server certificate host name fields. A man-in-the-middle attacker could use this flaw to spoof a Squid server using a specially crafted X.509 certificate. A heap-based buffer overflow flaw was found in the way the libtasn1 library decoded certain DER-encoded inputs. A specially crafted DER-encoded input could cause an application using libtasn1 to perform an invalid read, causing the application to crash. It was discovered that the jboss init script performed unsafe file handling which could result in local privilege escalation. An out-of-bounds memory access flaw was found in the way QEMU's virtual Floppy Disk Controller (FDC) handled FIFO buffer access while processing certain FDC commands. A privileged guest user could use this flaw to crash the guest or, potentially, execute arbitrary code on the host with the privileges of the host's QEMU process corresponding to the guest. It was discovered that EAP packages in certain versions of Red Hat Enterprise Linux use incorrect permissions for /etc/sysconfig/jbossas configuration files. The file is writable to jboss group (root:jboss, 664). On systems using classic /etc/init.d init scripts (i.e. on Red Hat Enterprise Linux 6 and earlier), the file is sourced by the jboss init script and its content executed with root privileges when jboss service is started, stopped, or restarted. A flaw was discovered in the way dcraw processed Raw images. An attacker could use this flaw to cause dcraw to crash by tricking a user into processing a specially crafted Raw image file. A double-free flaw was found in the way PostgreSQL handled connections. An unauthenticated attacker could possibly exploit this flaw to crash the PostgreSQL backend by disconnecting at approximately the same time as the authentication time out was triggered. It was discovered that PostgreSQL did not properly check the return values of certain standard library functions. If the system was in a state that would cause the standard library functions to fail (for example, memory exhaustion), an authenticated user could possibly exploit this flaw to disclose partial memory contents or cause the GSSAPI authentication to use an incorrect keytab file. It was discovered that the pgcrypto module could return different error messages when decrypting certain data with an incorrect key. This could potentially help an authenticated user to launch a possible cryptographic attack, although no suitable attack is currently known. It was discovered that the Thermostat web application stored database authentication credentials in a world-readable configuration file. A local user on a system running the Thermostat web application could use this flaw to access and modify monitored JVM data, or perform actions on connected JVMs. A flaw was found in WCP dissector of wireshark of which an attacker could crash wireshark by injecting a specially crafted packet onto the wire or by convincing wireshark user to read malformed packet trace file. A flaw was found in X11 dissector of wireshark of which an attacker could make wireshark consume excessive CPU resources which could make system unresponsive by injecting specially crafted packet onto the wire or by convincing wireshark user to read malformed packet trace file. A flaw was found in the way packet reassembly code of wireshark would parse a packet which could leak memory. An attacker could use this flaw to crash wireshark by sending a specially crafted packet onto the wire or by convincing wireshark user to read malformed packet trace file. It was found that the expression language resolver evaluated expressions within a privileged code section. A malicious web application could use this flaw to bypass security manager protections. It was found that the pcs daemon did not sign cookies containing session data that were sent to clients connecting via the pcsd web UI. A remote attacker could use this flaw to forge cookies and bypass authorization checks, possibly gaining elevated privileges in the pcsd web UI. A flaw was found in the way PHP parsed multipart HTTP POST requests. A specially crafted request could cause PHP to use an excessive amount of CPU time. A flaw was discovered in the OpenStack dashboard (horizon) handling of metadata. Potentially untrusted data was displayed from OpenStack Image service (glance) images, OpenStack Compute (nova) flavors, or host aggregates without correct sanitization. The flaw could be used by an authenticated user to conduct an XSS attack. The Java Portlet Specification JSR286 API jar file code could allow a remote attacker to obtain sensitive information, caused by the failure to restrict access to resources located within the web application. An attacker could exploit this vulnerability to obtain configuration data and other sensitive information. It was discovered that the xzgrep's xz helper script did not properly sanitize certain file names. A local attacker could use this flaw to inject and execute arbitrary commands by tricking a user into running the xzgrep script on a file with a specially crafted file name. A flaw was discovered in the way Libreswan's IKE daemon processed certain IKEv1 payloads. A remote attacker could send specially crafted IKEv1 payloads that, when processed, would lead to a denial of service (daemon crash). It was found that certain PHP functions did not properly handle file names containing a NULL character. A remote attacker could possibly use this flaw to make a PHP script access unexpected files and bypass intended file system access restrictions. It was found that certain PHP functions did not properly handle file names containing a NULL character. A remote attacker could possibly use this flaw to make a PHP script access unexpected files and bypass intended file system access restrictions. An integer underflow flaw leading to out-of-bounds memory access was found in the way PHP's Phar extension parsed Phar archives. A specially crafted archive could cause PHP to crash or, possibly, execute arbitrary code when opened. An integer overflow flaw leading to a heap-based buffer overflow was found in the way PHP's FTP extension parsed file listing FTP server responses. A malicious FTP server could use this flaw to cause a PHP application to crash or, possibly, execute arbitrary code. An invalid free flaw was found in the way PHP's Phar extension parsed Phar archives. A specially crafted archive could cause PHP to crash or, possibly, execute arbitrary code when opened. A flaw was found in the way the TLS protocol composes the Diffie-Hellman exchange (for both export and non-export grade cipher suites). An attacker could use this flaw to downgrade a DHE connection to use export-grade key sizes, which could then be broken by sufficient pre-computation. This can lead to a passive man-in-the-middle attack in which the attacker is able to decrypt all traffic. It was discovered that fusermount failed to properly sanitize its environment before executing mount and umount commands. A local user could possibly use this flaw to escalate their privileges on the system. It was discovered that ceph-deploy, a utility for deploying Red Hat Ceph Storage, would create the keyring file with world readable permissions, which could possibly allow a local user to obtain authentication credentials from the keyring file. A buffer overflow flaw was found in the way t1utils processed, for example, certain PFB (Printer Font Binary) files. An attacker could use this flaw to potentially execute arbitrary code by tricking a user into processing a specially crafted PFB file with t1utils. Multiple flaws were found in the way Python's SSL module performed matching of certificate names containing wildcards. A remote attacker able to obtain a valid certificate that contained certain names with wildcards could have them incorrectly accepted by Python SSL clients, not following the RFC 6125 recommendations. A flaw was found in the way QEMU's AMD PCnet Ethernet emulation handled multi-TMD packets with a length above 4096 bytes. A privileged guest user in a guest with an AMD PCNet ethernet card enabled could potentially use this flaw to execute arbitrary code on the host with the privileges of the hosting QEMU process. It was found that unsharing a mount namespace could allow a user to see data beneath their restricted namespace. An integer underflow flaw, leading to a buffer over-read, was found in the way wpa_supplicant handled WMM Action frames. A specially crafted frame could possibly allow an attacker within Wi-Fi radio range to cause wpa_supplicant to crash. A flaws was discovered in the way PHP performed object unserialization. Specially crafted input processed by the unserialize() function could cause a PHP application to crash or, possibly, execute arbitrary code. A flaws was discovered in the way PHP performed object unserialization. Specially crafted input processed by the unserialize() function could cause a PHP application to crash or, possibly, execute arbitrary code. A race condition flaw was found in the way the Linux kernel's SCTP implementation handled Address Configuration lists when performing Address Configuration Change (ASCONF). A local attacker could use this flaw to crash the system via a race condition triggered by setting certain ASCONF options on a socket. A flaw was found in the way clutter processed certain mouse and touch gestures. An attacker could use this flaw to bypass the screen lock. It was discovered that libwmf did not correctly process certain WMF (Windows Metafiles) containing BMP images. By tricking a victim into opening a specially crafted WMF file in an application using libwmf, a remote attacker could possibly use this flaw to execute arbitrary code with the privileges of the user running the application. A regression was found in the ssleay_rand_bytes() function in the versions of OpenSSL shipped with Red Hat Enterprise Linux 6 and 7. This regression could cause a multi-threaded application to crash. It was found that the Windows Virtio NIC driver did not sufficiently sanitize the length of the incoming IP packets, as demonstrated by a packet with IP options present but the overall packet length not being adjusted to reflect the length of those options. A remote attacker able to send a specially crafted IP packet to the guest could use this flaw to crash that guest. A flaw was discovered in the way the Linux kernel's TTY subsystem handled the tty shutdown phase. A local, unprivileged user could use this flaw to cause denial of service on the system by holding a reference to the ldisc lock during tty shutdown, causing a deadlock. An inode data validation error was found in Linux kernels built with UDF file system (CONFIG_UDF_FS) support. An attacker able to mount a corrupted/malicious UDF file system image could cause the kernel to crash. A path length checking flaw was found in Linux kernels built with UDF file system (CONFIG_UDF_FS) support. An attacker able to mount a corrupted/malicious UDF file system image could use this flaw to leak kernel memory to user-space. A symlink size validation was missing in Linux kernels built with UDF file system (CONFIG_UDF_FS) support, allowing the corruption of kernel memory. An attacker able to mount a corrupted/malicious UDF file system image could cause the kernel to crash. A symlink size validation was missing in Linux kernels built with UDF file system (CONFIG_UDF_FS) support, allowing the corruption of kernel memory. An attacker able to mount a corrupted/malicious UDF file system image could cause the kernel to crash. A symlink size validation was missing in Linux kernels built with UDF file system (CONFIG_UDF_FS) support, allowing the corruption of kernel memory. An attacker able to mount a corrupted/malicious UDF file system image could cause the kernel to crash. A cross-site scripting (XSS) flaw was found in the Horizon orchestration dashboard. An attacker able to trick a Horizon user into using a malicious template during the stack creation could use this flaw to perform an XSS attack on that user. It was reported that OpenSSL could enter an infinite loop when processing an ECParameters structure if the curve specified is over a specially malformed binary polynomial field. This can be used to perform denial of service attacks against any system which processes public keys, certificate requests or certificates, including TLS clients and TLS servers with client authentication enabled. An out-of-bounds read flaw was found in the X509_cmp_time() function of OpenSSL, which is used to test the expiry dates of SSL/TLS certificates. An attacker could possibly use a specially crafted SSL/TLS certificate or CRL (Certificate Revocation List), which when parsed by an application would cause that application to crash. A NULL pointer dereference was found in the way OpenSSL handled certain PKCS#7 inputs. An attacker able to make an application using OpenSSL verify, decrypt, or parse a specially crafted PKCS#7 input could cause that application to crash. TLS/SSL clients and servers using OpenSSL were not affected by this flaw. A denial of service flaw was found in the way OpenSSL verified certain signed messages using CMS (Cryptographic Message Syntax). A remote attacker could cause an application using OpenSSL to use excessive amounts of memory by sending a specially crafted message for verification. A race condition was found in the session handling code of OpenSSL. This issue could possibly cause a multi-threaded TLS/SSL client using OpenSSL to double free session ticket data and crash. An invalid-free flaw was found in the way OpenSSL handled certain DTLS handshake messages. A malicious DTLS client or server could send a specially crafted message to the peer, which could cause the application to crash or potentially result in arbitrary code execution. A flaw was discovered in redis that could allow an authenticated user, who was able to use the EVAL command to run Lua code, to break out of the Lua sandbox and execute arbitrary code on the system. A string reference count bug was found in cupsd, causing premature freeing of string objects. An attacker could submit a malicious print job that exploits this flaw to dismantle ACLs protecting privileged operations, allowing a replacement configuration file to be uploaded, which in turn allowed the attacker to run arbitrary code on the CUPS server. A cross-site scripting flaw was found in the cups web templating engine. An attacker could use this flaw to bypass the default configuration settings that bind the CUPS scheduler to the 'localhost' or loopback interface. A NULL-pointer dereference flaw was discovered in polkitd. A malicious, local user could exploit this flaw to crash polkitd. An out-of-bounds memory access flaw, leading to memory corruption or possibly an information leak, was found in QEMU's pit_ioport_read() function. A privileged guest user in a QEMU guest, which had QEMU PIT emulation enabled, could potentially, in rare cases, use this flaw to execute arbitrary code on the host with the privileges of the hosting QEMU process. A flaw was found in the Linux kernel SCSI subsystem, which allowed a local user to gain privileges or cause a denial of service (memory corruption and system crash) by issuing an SG_IO ioctl call while a device was being detached. A flaw was found in how the OpenStack Compute (nova) service handles the qemu-img functionality during a snapshot upload. An authenticated attacker could possibly use this flaw to trick Compute into disclosing any file to which the Compute service user has access. However, it is unlikely that the code path can currently be exploited by an attacker. A flaw was found in the OpenStack Block Storage (cinder) upload-to-image functionality. When processing a malicious qcow2 header, cinder could be tricked into reading an arbitrary file from the cinder host. It was discovered that the _unix_run_helper_binary() function of PAM's unix_pam module could write to a blocking pipe, possibly causing the function to become unresponsive. An attacker able to supply large passwords to the unix_pam module could use this flaw to enumerate valid user accounts, or cause a denial of service on the system. An off-by-one array indexing error was found in the libunwind API, which could cause an error when reading untrusted binaries or dwarf debug info data. Red Hat products do not call the API in this way; and it is unlikely that any exploitable attack vector exists in current builds or supported usage. A Denial-of-Service flaw was found in the OpenStack Networking (neutron) L2 agent when using the iptables firewall driver. By submitting an address pair that is rejected as invalid by the ipset tool (with zero prefix size), an authenticated attacker can cause the L2 agent to crash. A flaw was found in a way Rack processed parameters of incoming requests. An attacker could use this flaw to send a crafted request that would cause an application using Rack to crash. A flaw was discovered in the way Libreswan's IKE daemon processed IKE KE payloads. A remote attacker could send specially crafted IKE payload with a KE payload of g^x=0 that, when processed, would lead to a denial of service (daemon crash). It was discovered that in Foreman the edit_users permissions (for example, granted to the Manager role) allowed the user to edit admin user passwords. An attacker with the edit_users permissions could use this flaw to access an admin user account, leading to an escalation of privileges. A denial of service flaw was found in the OpenStack Compute (nova) instance migration process. Because the migration process does not terminate when an instance is deleted, an authenticated user could bypass user quota and deplete all available disk space by repeatedly re-sizing and deleting an instance. An integer overflow flaw was discovered in one of Ghostscript's memory allocation routines. A remote attacker could possibly exploit this flaw to cause a crash or, potentially, execute arbitrary code by tricking a user into processing a specially crafted file. It was found that certain PHP functions did not properly handle file names containing a NULL character. A remote attacker could possibly use this flaw to make a PHP script access unexpected files and bypass intended file system access restrictions. It was found that certain PHP functions did not properly handle file names containing a NULL character. A remote attacker could possibly use this flaw to make a PHP script access unexpected files and bypass intended file system access restrictions. It was found that certain PHP functions did not properly handle file names containing a NULL character. A remote attacker could possibly use this flaw to make a PHP script access unexpected files and bypass intended file system access restrictions. Multiple flaws were discovered in the way PHP's Soap extension performed object unserialization. Specially crafted input processed by the unserialize() function could cause a PHP application to disclose portion of its memory or crash. Multiple flaws were discovered in the way PHP's Soap extension performed object unserialization. Specially crafted input processed by the unserialize() function could cause a PHP application to disclose portion of its memory or crash. Multiple flaws were discovered in the way PHP's Soap extension performed object unserialization. Specially crafted input processed by the unserialize() function could cause a PHP application to disclose portion of its memory or crash. It was found that JavaServer Faces PortletBridge-based portlets using GenericPortlet's default resource serving did not restrict access to resources within the web application. An attacker could set the resource ID field of a URL to potentially bypass security constraints and gain access to restricted resources. A flaw was discovered in the way PHP performed object unserialization. Specially crafted input processed by the unserialize() function could cause a PHP application to crash or, possibly, execute arbitrary code. A flaw was discovered in the way PHP performed object unserialization. Specially crafted input processed by the unserialize() function could cause a PHP application to crash or, possibly, execute arbitrary code. It was found that libuser, as used by the chfn userhelper functionality, did not properly filter out newline characters in GECOS fields. A local, authenticated user could use this flaw to corrupt the /etc/passwd file, resulting in a denial-of-service on the system. A flaw was found in the way the libuser library handled the /etc/passwd file. A local attacker could use an application compiled against libuser (for example, userhelper) to manipulate the /etc/passwd file, which could result in a denial of service or possibly allow the attacker to escalate their privileges to root. A race condition flaw, leading to a heap-based memory corruption, was found in spice's worker_update_monitors_config() function, which runs under the QEMU-KVM context on the host. A user in a guest could leverage this flaw to crash the host QEMU-KVM process or, possibly, execute arbitrary code with the privileges of the host QEMU-KVM process. A flaw was found in the way rubygem-jquery-rails filtered CSRF tokens from HTTP requests. An attacker able to control the href attribute of an anchor tag or the action attribute of a form tag, could use this flaw to force an application to send a request that includes a CSRF token to an attacker-specified site, thus leaking the CSRF token. It was found that the "/var/lib/openhpi" directory provided by OpenHPI used world-writeable and world-readable permissions. A local user could use this flaw to view, modify, and delete OpenHPI-related data, or even fill up the storage device hosting the /var/lib directory. A DoS flaw was found for a Linux kernel built for the x86 architecture which had the KVM virtualization support(CONFIG_KVM) enabled. The kernel would be vulnerable to a NULL pointer dereference flaw in Linux kernel's kvm_apic_has_events() function while doing an ioctl. An unprivileged user able to access the "/dev/kvm" device could use this flaw to crash the system kernel. A heap-based buffer overflow was discovered in the way the texttopdf utility of cups-filter processed print jobs with a specially crafted line size. An attacker able to submit print jobs could use this flaw to crash texttopdf or, possibly, execute arbitrary code with the privileges of the "lp" user. It was discovered that libwmf did not properly process certain WMF files. By tricking a victim into opening a specially crafted WMF file in an application using libwmf, a remote attacker could possibly exploit this flaw to cause a crash or execute arbitrary code with the privileges of the user running the application. It was discovered that libwmf did not properly process certain WMF files. By tricking a victim into opening a specially crafted WMF file in an application using libwmf, a remote attacker could possibly exploit this flaw to cause a crash or execute arbitrary code with the privileges of the user running the application. A flaw was found in the kernel's implementation of the Berkeley Packet Filter (BPF). A local attacker could craft BPF code to crash the system by creating a situation in which the JIT compiler would fail to correctly optimize the JIT image on the last pass. This would lead to the CPU executing instructions that were not part of the JIT code. A flaw was found in a way rubygems verified the API endpoint hostname retrieved through a DNS SRV record. A man-in-the-middle attacker could use this flaw to force a client to download content from an untrusted domain. A flaw was found in the way NSS verified certain ECDSA (Elliptic Curve Digital Signature Algorithm) signatures. Under certain conditions, an attacker could use this flaw to conduct signature forgery attacks. It was found that Firefox skipped key-pinning checks when handling an error that could be overridden by the user (for example an expired certificate error). This flaw allowed a user to override a pinned certificate, which is an action the user should not be able to perform. A flaw was discovered in Mozilla's PDF.js PDF file viewer. When combined with another vulnerability, it could allow execution of arbitrary code with the privileges of the user running Firefox. It was found that NSS permitted skipping of the ServerKeyExchange packet during a handshake involving ECDHE (Elliptic Curve Diffie-Hellman key Exchange). A remote attacker could use this flaw to bypass the forward-secrecy of a TLS/SSL connection. It was discovered that a cross-site scripting (XSS) vulnerability on a JBoss Operations Network 404 error page allowed for session fixation attacks. An attacker could use this flaw to impersonate a legitimate user, resulting in compromised integrity of secure data. A flaw was found in the way BIND performed DNSSEC validation. An attacker able to make BIND (functioning as a DNS resolver with DNSSEC validation enabled) resolve a name in an attacker-controlled domain could cause named to exit unexpectedly with an assertion failure. A flaw was found in the way OpenLDAP parsed OpenSSL-style cipher strings. As a result, OpenLDAP could potentially use ciphers that were not intended to be enabled. A flaw was found in the way OpenSSL verified alternative certificate chains. An attacker able to supply a certificate chain to an SSL/TLS or DTLS client or an SSL/TLS or DTLS server using client authentication could use this flaw to bypass certain checks in the verification process, possibly allowing them to use one of the certificates in the supplied certificate chain as a CA certificate to generate an invalid certificate. It was found that the OpenSSH client did not properly enforce the ForwardX11Timeout setting. A malicious or compromised remote X application could possibly use this flaw to establish a trusted connection to the local X server, even if only untrusted X11 forwarding was requested. An integer overflow flaw, leading to a heap-based buffer overflow, was discovered in the way the texttopdf utility of cups-filter processed print jobs with a specially crafted line size. An attacker able to submit print jobs could use this flaw to crash texttopdf or, possibly, execute arbitrary code with the privileges of the "lp" user. A denial of service flaw was found in the way Spring processes inline DTD declarations. A remote attacker could submit a specially crafted XML file that would cause out-of-memory errors when parsed. A flaw was found in the Django session backend, which could allow an unauthenticated attacker to create session records in the configured session store, causing a denial of service by filling up the session store. A flaw was found in the way the Linux kernel's networking implementation handled UDP packets with incorrect checksum values. A remote attacker could potentially use this flaw to trigger an infinite loop in the kernel, resulting in a denial of service on the system, or cause a denial of service in applications using the edge triggered epoll functionality. A flaw was found in the way the Linux kernel's networking implementation handled UDP packets with incorrect checksum values. A remote attacker could potentially use this flaw to trigger an infinite loop in the kernel, resulting in a denial of service on the system, or cause a denial of service in applications using the edge triggered epoll functionality. An implementation error related to the memory management of request and responses was found within HAProxy's buffer_slow_realign() function. An unauthenticated remote attacker could possibly use this flaw to leak certain memory buffer contents from a past request or session. A flaw was found in the way the JSSE component in OpenJDK performed X.509 certificate identity verification when establishing a TLS/SSL connection to a host identified by an IP address. In certain cases, the certificate was accepted as valid if it was issued for a host name to which the IP address resolves rather than for the IP address. It was discovered that the JCE component in OpenJDK failed to use constant time comparisons in multiple cases. An attacker could possibly use these flaws to disclose sensitive information by measuring the time used to perform operations using these non-constant time comparisons. A flaw was found in the way the Libraries component of OpenJDK verified Online Certificate Status Protocol (OCSP) responses. An OCSP response with no nextUpdate date specified was incorrectly handled as having unlimited validity, possibly causing a revoked X.509 certificate to be interpreted as valid. An information leak flaw was found in the JMX component in OpenJDK. An untrusted Java application or applet could use this flaw to bypass certain Java sandbox restrictions. It was discovered that the JNDI component in OpenJDK did not handle DNS resolution errors correctly. An attacker able to trigger such DNS errors could cause a Java application using JNDI to consume memory and CPU time, and possibly block further DNS resolution. An information leak flaw was found in the 2D component in OpenJDK. An untrusted Java application or applet could use this flaw to bypass certain Java sandbox restrictions. A flaw was found in the way the Linux kernel's nested NMI handler and espfix64 functionalities interacted during NMI processing. A local, unprivileged user could use this flaw to crash the system or, potentially, escalate their privileges on the system. It was found that if a Non-Maskable Interrupt (NMI) occurred immediately after a SYSCALL call or before a SYSRET call with the user RSP pointing to the NMI IST stack, the kernel could skip that NMI. It was discovered that tidy did not properly process certain character sequences. By tricking an application that is using tidy into processing a specially crafted HTML document, a remote attacker could exploit this flaw to cause a crash or, possibly, execute arbitrary code with the privileges of the affected application. It was discovered that tidy did not properly process certain character sequences. By tricking an application that is using tidy into processing a specially crafted HTML document, a remote attacker could exploit this flaw to cause a crash or, possibly, execute arbitrary code with the privileges of the affected application. A heap buffer overflow flaw was found in the way QEMU's IDE subsystem handled I/O buffer access while processing certain ATAPI commands. A privileged guest user in a guest with the CDROM drive enabled could potentially use this flaw to execute arbitrary code on the host with the privileges of the host's QEMU process corresponding to the guest. A buffer overflow flaw was found in the way the Linux kernel's virtio-net subsystem handled certain fraglists when the GRO (Generic Receive Offload) functionality was enabled in a bridged network configuration. An attacker on the local network could potentially use this flaw to crash the system, or, although unlikely, elevate their privileges on the system. Multiple flaws were found in the way httpd parsed HTTP requests and responses using chunked transfer encoding. A remote attacker could use these flaws to create a specially crafted request, which httpd would decode differently from an HTTP proxy software in front of it, possibly leading to HTTP request smuggling attacks. It was discovered that in httpd 2.4, the internal API function ap_some_auth_required() could incorrectly indicate that a request was authenticated even when no authentication was used. An httpd module using this API function could consequently allow access that should have been denied. A NULL pointer dereference flaw was found in the way httpd generated certain error responses. A remote attacker could possibly use this flaw to crash the httpd child process using a request that triggers a certain HTTP error. A flaw was discovered in the way applications using Groovy used the standard Java serialization mechanism. A remote attacker could use a specially crafted serialized object that would execute code directly when deserialized. All applications which rely on serialization and do not isolate the code which deserializes objects are subject to this vulnerability. A flaw has been discovered in the QEMU emulator built with SCSI-device emulation support. The emulator is vulnerable to a stack buffer overflow issue, which can occur while parsing a SCSI command descriptor block with an invalid operation code. A privileged(CAP_SYS_RAWIO) user inside a guest could use this flaw to crash the QEMU instance resulting in a denial-of-service (DoS) attack. A flaw was found in the way the way PHP's Phar extension parsed Phar archives. A specially crafted archive could cause PHP to crash or, possibly, execute arbitrary code when opened. A flaw was found in the way the way PHP's Phar extension parsed Phar archives. A specially crafted archive could cause PHP to crash or, possibly, execute arbitrary code when opened. It was found that the libvirt daemon, when using RBD (RADOS Block Device), leaked private credentials to the process list. A local attacker could use this flaw to perform certain privileged operations within the cluster. It was found that the Linux kernel's keyring implementation would leak memory when adding a key to a keyring via the add_key() function. A local attacker could use this flaw to exhaust all available memory on the system. A denial of service flaw was found in how polkit handled authorization requests. A local, unprivileged user could send malicious requests to polkit, which could then cause the polkit daemon to corrupt its memory and crash. It was discovered that the OpenSSH sshd daemon did not check the list of keyboard-interactive authentication methods for duplicates. A remote attacker could use this flaw to bypass the MaxAuthTries limit, making it easier to perform password guessing attacks. It was found that the mod_authz_svn module did not properly restrict anonymous access to Subversion repositories under certain configurations when used with Apache httpd 2.4.x. This could allow a user to anonymously access files in a Subversion repository, which should only be accessible to authenticated users. It was found that when an SVN server (both svnserve and httpd with the mod_dav_svn module) searched the history of a file or a directory, it would disclose its location in the repository if that file or directory was not readable (for example, if it had been moved). A flaw was found in the way BIND handled requests for TKEY DNS resource records. A remote attacker could use this flaw to make named (functioning as an authoritative DNS server or a DNS resolver) exit unexpectedly with an assertion failure via a specially crafted DNS request packet. A flaw was found in the handling of Python pickle()-encoded messages in the Qpid server on Satellite 6. The Qpid server did not properly restrict message types that can be sent from managed content hosts. An attacker with administrative access to a managed content host could send arbitrary messages containing pickle()-encoded data, which would then be processed on the Satellite 6 server and result in possible code execution. It was found that PortletBridge PortletRequestDispatcher did not respect security constraints set by the servlet if a portlet request asked for rendering of a non-JSF resource such as JSP or HTML. A remote attacker could use this flaw to potentially bypass certain security constraints and gain access to restricted resources. A flaw was discovered in the kernel's collect_mounts function. If the kernel's audit subsystem called collect_mounts to audit an unmounted path, it could panic the system. With this flaw, an unprivileged user could call umount(MNT_DETACH) to launch a denial-of-service attack. It was discovered that the mktexlsr script of the texlive package creates temporary files in an insecure way. A local attacker could possibly use this flaw to perform a symbolic link attack and overwrite arbitrary files with the privileges of the user running mktexslr, or obtain sensitive information from the temporary files. It was discovered that the mktexlsr script of the texlive package creates temporary files in an insecure way. A local attacker could possibly use this flaw to perform a symbolic link attack and overwrite arbitrary files with the privileges of the user running mktexslr, or obtain sensitive information from the temporary files. An information leak flaw was found in the way QEMU's RTL8139 emulation implementation processed network packets under RTL8139 controller's C+ mode of operation. An unprivileged guest user could use this flaw to read up to 65 KB of uninitialized QEMU heap memory. It was discovered that the snmp_pdu_parse() function could leave incompletely parsed varBind variables in the list of variables. A remote, unauthenticated attacker could use this flaw to crash snmpd or, potentially, execute arbitrary code on the system with the privileges of the user running snmpd. A flaw has been found in the QEMU emulator built with IDE Emulation PCI PIIX3/4 support; the emulator is vulnerable to a use-after-free flaw, while writing data to an I/O port inside a guest. This issue is specific to the Xen platform. A privileged(CAP_SYS_RAWIO) guest user on the Xen platform could use this flaw to crash the QEMU instance or attempt to make a guest escape to QEMU-process privileges. A cross-boundary flaw was discovered in the Linux kernel software raid driver. The driver accessed a disabled bitmap where only the first byte of the buffer was initialized to zero. This meant that the rest of the request (up to 4095 bytes) was left and copied into user space. An attacker could use this flaw to read private information from user space that would not otherwise have been accessible. A flaw was found in the Linux kernel where the deletion of a file or directory could trigger an unmount and reveal data under a mount point. This flaw was inadvertently introduced with the new feature of being able to lazily unmount a mount tree when using file system user namespaces. A flaw was found in the Linux kernel which is related to the user namespace lazily unmounting file systems. The fs_pin struct has two members (m_list and s_list) which are usually initialized on use in the pin_insert_group function. However, these members might go unmodified; in this case, the system panics when it attempts to destroy or free them. This flaw could be used to launch a denial-of-service attack. An integer-overflow vulnerability was found in the scsi block-request handling code in function start_req(). A local attacker could use specially crafted IOV requests to overflow a counter used in bio_map_user_iov()'s page calculation, and write past the end of the array that contains kernel-page pointers. A use-after-free flaw was found in the Linux kernels function path_openat() in which incorrectly clears up twice (as part of path_lookupat() called by do_tmpfile()). Clearing twice can lead to a double fput(). A local, unauthenticated user could exploit this flaw to possibly cause a denial of service. A flaw was found in a way rubygems verified the API endpoint hostname retrieved through a DNS SRV record. A man-in-the-middle attacker could use this flaw to force a client to download content from an untrusted domain. It was discovered that the EAP Management Console could be opened in an IFRAME, which made it possible to intercept and manipulate requests. An attacker could use this flaw to trick a user into performing arbitrary actions in the Console (clickjacking). HTTP-request vulnerabilities have been found in the Golang net/http and net/textproto libraries. Request headers with double Content-Length fields do not generate a 400 error (the second field is ignored), and invalid fields are parsed as valid (for example, "Content Length:" with a space in the middle is accepted). A non-authenticated attacker could exploit these flaws to bypass security controls, perform web-cache poisoning, or alter the request/response map (denial of service). HTTP-request vulnerabilities have been found in the Golang net/http and net/textproto libraries. Request headers with double Content-Length fields do not generate a 400 error (the second field is ignored), and invalid fields are parsed as valid (for example, "Content Length:" with a space in the middle is accepted). A non-authenticated attacker could exploit these flaws to bypass security controls, perform web-cache poisoning, or alter the request/response map (denial of service). HTTP-request vulnerabilities have been found in the Golang net/http and net/textproto libraries. Request headers with double Content-Length fields do not generate a 400 error (the second field is ignored), and invalid fields are parsed as valid (for example, "Content Length:" with a space in the middle is accepted). A non-authenticated attacker could exploit these flaws to bypass security controls, perform web-cache poisoning, or alter the request/response map (denial of service). It was found that the JBoss A-MQ console would accept a string containing JavaScript as the name of a new message queue. Execution of the UI would subsequently execute the script. An attacker could use this flaw to access sensitive information or perform other attacks. It was found that JBoss A-MQ's Jolokia API does not have token or referrer checks, and could possibly allow a cross-site request forgery (CSRF) attack. An attacker could use this vulnerability to run application code with the same permissions as an authenticated user. It was found that JBoss A-MQ's Hawtio console does not set HTTPOnly or Secure attributes on cookies. An attacker could use this flaw to rerieve an authenticated user's SessionID, and possibly conduct further attacks with the permissions of the authenticated user. It was found that JBoss A-MQ's Hawtio console setting for the Access-Control-Allow-Origin header permits unrestricted sharing (allow all). An attacker could use this flaw to access sensitive information or perform other attacks. A flaw was discovered in Mozilla Firefox that could be used to violate the same-origin policy and inject web script into a non-privileged part of the built-in PDF file viewer (PDF.js). An attacker could create a malicious web page that, when viewed by a victim, could steal arbitrary files (including private SSH keys, the /etc/passwd file, and other potentially sensitive files) from the system running Firefox. An integer overflow, leading to a heap-based buffer overflow, was found in the way gdk-pixbuf, an image loading library for GNOME, scaled certain bitmap format images. An attacker could use a specially crafted BMP image file that, when processed by an application compiled against the gdk-pixbuf library, would cause that application to crash or execute arbitrary code with the permissions of the user running the application. A flaw was found in the OpenStack Image Service (glance) import task action. When processing a malicious qcow2 header, glance could be tricked into reading an arbitrary file from the glance host. Only setups using the glance V2 API are affected by this flaw. It was discovered that when uploading a file using a multipart/form-data submission to the EAP Web Console, the Console was vulnerable to Cross-Site Request Forgery (CSRF). This meant that an attacker could use the flaw together with a forgery attack to make changes to an authenticated instance. It was found that Django incorrectly handled the session store. A session could be created by anonymously accessing the django.contrib.auth.views.logout view if it was not decorated correctly with django.contrib.auth.decorators.login_required. A remote attacker could use this flaw to fill up the session store or cause other users' session records to be evicted by requesting a large number of new sessions. It was found that certain Django functions would, in certain circumstances, create empty sessions. A remote attacker could use this flaw to fill up the session store or cause other users' session records to be evicted by requesting a large number of new sessions. A race condition was found in the way the pcsd web UI backend performed authorization of user requests. An attacker could use this flaw to send a request that would be evaluated as originating from a different user, potentially allowing the attacker to perform actions with permissions of a more privileged user. A command injection flaw was found in the pcsd web UI. An attacker able to trick a victim that was logged in to the pcsd web UI into visiting a specially crafted URL could use this flaw to execute arbitrary code with root privileges on the server hosting the web UI. A flaw was found in the way the Satellite 6 server broker and capsule broker handled certificate-based authentication from content hosts. An attacker with privileged access on a content host could authenticate to a server or capsule broker and execute arbitrary commands. A use-after-free flaw was found in GnuTLS's _gnutls_x509_dn_to_string() function. A remote attacker could create a specially crafted certificate with very long DistinguishedName (DN) entries that, when processed by an application compiled against GnuTLS, could cause that application to crash. A flaw was found in the way the Linux kernel's vhost driver treated userspace provided log file descriptor when processing the VHOST_SET_LOG_FD ioctl command. The file descriptor was never released and continued to consume kernel memory. A privileged local user with access to the /dev/vhost-net files could use this flaw to create a denial-of-service attack. It was found that ntpd could crash due to an uninitialized variable when processing malformed logconfig configuration commands. It was found that ntpd would exit with a segmentation fault when a statistics type that was not enabled during compilation (e.g. timingstats) was referenced by the statistics or filegen configuration command. It was discovered that the sntp utility could become unresponsive due to being caught in an infinite loop when processing a crafted NTP packet. An improper permission check issue was discovered in the server admission control component in OpenShift. A user with build permissions could use this flaw to execute arbitrary shell commands on a build pod with the privileges of the root user. It was found that the Ipsilon IdP server used the default configuration of the Jinja templating engine, which did not HTML escape template variables. This could be exploited to perform an XSS attack if a value from untrusted input was used in the template and rendered in the user`s browser. A flaw was discovered in the Ipsilon IdP server in its use of Python templates, where JavaScript code could potentially be injected into an Python exception-message template. A remote, unauthorised attacker could use this flaw to perform an XXS attack. A flaw was discovered that the Ipsilon IdP server did not properly authorize a change of the provider's name. Non-administrative users could use this flaw to change the name to a duplicate value, which could possibly lead to denial-of-service attack. A NULL pointer dereference flaw was found in the way the lookupProviders() function processed certain requests without "className" information. An authenticated remote attacker could use this flaw to cause a denial of service (sfcbd crash) by sending a specially crafted request. It was discovered that sending requests containing large headers to the Web Console produced a Java OutOfMemoryError in the HTTP management interface. An attacker could use this flaw to cause a denial of service. A flaw was discovered in the OpenStack Object Storage service (swift) TempURLs. An attacker in possession of a TempURL key with PUT permissions could gain read access to other objects in the same project (tenant). A flaw was found in the way the Linux kernel's perf subsystem retrieved userlevel stack traces on PowerPC systems. A local, unprivileged user could use this flaw to cause a denial of service on the system by creating a special stack layout that would force the perf_callchain_user_64() function into an infinite loop. A heap-based buffer overflow issue was found in the QEMU emulator's VNC display driver. It could occur while refreshing the VNC server's display surface using the vnc_refresh_server_surface() routine. A privileged guest user could use this flaw to corrupt the heap memory and crash the QEMU process instance, or to potentially use it to execute arbitrary code on the host. It was discovered that the combination of Enable Discard and Wipe After Delete flags for VM disks managed by oVirt, could cause a disk to be incompletely zeroed when removed from a VM. If the same storage blocks happen to be later allocated to a new disk attached to another VM, potentially sensitive data could be revealed to privileged users of that VM. A buffer overflow flaw was found in the zsh shell symbolic link resolver. A local, unprivileged user can create a specially crafted directory path which leads to a buffer overflow in the context of the user trying to do symbolic link resolution in the aforementioned path. An attacker could exploit this vulnerability to cause a denial of service condition on the target. The madvise_willneed function in the Linux kernel allows local users to cause a denial of service (infinite loop) by triggering use of MADVISE_WILLNEED for a DAX mapping. An integer wraparound has been discovered in the Binary File Descriptor (BFD) library distributed in GNU Binutils up to version 2.30. An attacker could cause a crash by providing an ELF file with corrupted DWARF debug information. It was discovered that the calloc implementation in glibc could return memory areas which contain non-zero bytes. This could result in unexpected application behavior such as hangs or crashes. A use-after-free flaw was found in OpenSSH. An attacker able to fully compromise a non-privileged pre-authentication process using a different flaw could possibly cause sshd to crash or execute arbitrary code with root privileges. A flaw was found in the way OpenSSH handled PAM authentication when using privilege separation. An attacker with valid credentials on the system and able to fully compromise a non-privileged pre-authentication process using a different flaw could use this flaw to authenticate as other users. Multiple integer overflow flaws were found in the libevent's evbuffer API. An attacker able to make an application pass an excessively long input to libevent using the API could use these flaws to make the application enter an infinite loop, crash, and, possibly, execute arbitrary code. A flaw was found in the way Firefox handled installation of add-ons. An attacker could use this flaw to bypass the add-on installation prompt, and trick the user into installing an add-on from a malicious source. A flaw was found in the metadata constraints in Red Hat Gluster Storage's OpenStack Object Storage (swiftonfile). By adding metadata in several separate calls, a malicious user could bypass the max_meta_count constraint, and store more metadata than allowed by the configuration. It was discovered that IcedTea-Web did not properly sanitize applet URLs when storing applet trust settings. A malicious web page could use this flaw to inject trust-settings configuration, and cause applets to be executed without user approval. It was discovered that IcedTea-Web did not properly determine an applet's origin when asking the user if the applet should be run. A malicious page could use this flaw to cause IcedTea-Web to execute the applet without user approval, or confuse the user into approving applet execution based on an incorrectly indicated applet origin. An integer overflow issue was found in the VNC display driver of the QEMU emulator, which could be used by a privileged guest user to create a denial of service attack. The overflow occurred when processing a CLIENT_CUT_TEXT message with too large a payload size. The integer overflow led to an infinite loop inside the VNC driver, eventually crashing the QEMU process on the host. A flaw was found in the way OpenStack Compute (nova) handled the resize state. If an authenticated user deleted an instance while it was in the resize state, it could cause the original instance to not be deleted from the compute node it was running on, allowing the user to cause a denial of service. It was found that jsoup did not properly validate user-supplied HTML content; certain HTML snippets could get past the validator without being detected as unsafe. A remote attacker could use a specially crafted HTML snippet to execute arbitrary web script in the user's browser. A race-condition flaw leading to ACL bypass was discovered in OpenStack Networking (neutron). An authenticated user could change the owner of a port after it was created but before firewall rules were applied, thus preventing firewall control checks from occurring. All OpenStack Networking deployments that used either the ML2 plug-in or a plug-in that relied on the security groups AMQP API were affected. A flaw was found in the way swiftonfile (gluster-swift) serialized and stored metadata on disk by using Python's pickle module. A remote, authenticated user could use this flaw to execute arbitrary code on the storage node. A boundary check flaw was found in the way BIND parsed answers in certain DNS queries. A remote attacker able to provide a specially crafted response in an answer to a query could cause named functioning as a recursive resolver to crash. A denial of service flaw was found in the way BIND parsed certain malformed DNSSEC keys. A remote attacker could use this flaw to send a specially crafted DNS query (for example, a query requiring a response from a zone containing a deliberately malformed key) that would cause named functioning as a validating resolver to crash. A flaw was found in the way the Linux kernel handled IRET faults during the processing of NMIs. An unprivileged, local user could use this flaw to crash the system or, potentially (although highly unlikely), escalate their privileges on the system. It was found that improper error handling in the API server could cause the master process to crash. A user with network access to the master could use this flaw to crash the master process. A use-after-free vulnerability was found in ALSA pcm layer, which allows local users to cause a denial of service, memory corruption, or possibly other unspecified impact. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. A flaw was found in the way a QEMU-emulated e1000 network interface card processed transmit descriptor data when sending a network packet. A privileged guest user could use this flaw to crash the guest. A heap-based buffer overflow flaw was found in the way spice handled certain QXL commands related to the "surface_id" parameter. A user in a guest could use this flaw to crash the host QEMU-KVM process or, possibly, execute arbitrary code with the privileges of the host QEMU-KVM process. A flaw was discovered in the way PHP performed object unserialization. Specially crafted input processed by the unserialize() function could cause a PHP application to crash or, possibly, execute arbitrary code. A flaw was discovered in the way PHP performed object unserialization. Specially crafted input processed by the unserialize() function could cause a PHP application to crash or, possibly, execute arbitrary code. A flaw was discovered in the way PHP performed object unserialization. Specially crafted input processed by the unserialize() function could cause a PHP application to crash or, possibly, execute arbitrary code. A flaw was discovered in the way PHP performed object unserialization. Specially crafted input processed by the unserialize() function could cause a PHP application to crash or, possibly, execute arbitrary code. A NULL pointer dereference flaw was found in the XSLTProcessor class in PHP. An attacker could use this flaw to cause a PHP application to crash if it performed Extensible Stylesheet Language (XSL) transformations using untrusted XSLT files and allowed the use of PHP functions to be used as XSLT functions within XSL stylesheets. A NULL pointer dereference flaw was found in the XSLTProcessor class in PHP. An attacker could use this flaw to cause a PHP application to crash if it performed Extensible Stylesheet Language (XSL) transformations using untrusted XSLT files and allowed the use of PHP functions to be used as XSLT functions within XSL stylesheets. A flaw was discovered in the way PHP performed object unserialization. Specially crafted input processed by the unserialize() function could cause a PHP application to crash or, possibly, execute arbitrary code. A feature in Ceph Object Gateway (RGW) allows to return a specific HTTP header that contains the name of a bucket that was accessed. It was found that the returned HTTP headers were not sanitized. An unauthenticated attacker could use this flaw to craft HTTP headers in responses that would confuse the load balancer residing in front of RGW, potentially resulting in a denial of service. A flaw was discovered in the pipeline ordering of OpenStack Object Storage's staticweb middleware in the swiftproxy configuration generated from the openstack-tripleo-heat-templates package (OpenStack director). The staticweb middleware was incorrectly configured before the Identity Service, and under some conditions an attacker could use this flaw to gain unauthenticated access to private data. A heap-based buffer overflow flaw was found in the way SPICE handled certain guest QXL commands related to surface creation. A user in a guest could use this flaw to read and write arbitrary memory locations on the host. It has been discovered that a QEMU emulator built with IDE disk and CD/DVD-ROM emulation support is vulnerable to a divide-by-zero issue. The flaw could occur when executing IDE's WIN_READ_NATIVE_MAX command to determine the maximum size of a drive. A privileged user inside the guest could use this flaw to crash the QEMU instance, resulting in a denial of service. A flaw was found in the way the OpenLDAP server daemon (slapd) parsed certain Basic Encoding Rules (BER) data. A remote attacker could use this flaw to crash slapd via a specially crafted packet. A flaw was discovered where Satellite failed to properly enforce permissions on the show and delete actions for reports. An authenticated user with show or delete report permissions could use this flaw to view or delete any reports held in Foreman. A command injection flaw was found in the OpenShift Origin Management Console. A remote, authenticated user permitted to send requests to the Broker could use this flaw to execute arbitrary commands with elevated privileges on the Red Hat OpenShift server. It was found that the ABRT debug information installer (abrt-action-install-debuginfo-to-abrt-cache) did not use temporary directories in a secure way. A local attacker could use the flaw to create symbolic links and files at arbitrary locations as the abrt user. It was discovered that the nss_files backend for the Name Service Switch in glibc would return incorrect data to applications or corrupt the heap (depending on adjacent heap contents). A local attacker could potentially use this flaw to execute arbitrary code on the system. A heap buffer overflow flaw was found in the way QEMU's NE2000 NIC emulation implementation handled certain packets received over the network. A privileged user inside a guest could use this flaw to crash the QEMU instance (denial of service) or potentially execute arbitrary code on the host. A flaw was found where a QEMU emulator built with NE2000 NIC emulation support was vulnerable to an infinite loop issue that occurred when receiving packets over the network. A privileged user inside a guest could use this flaw to crash the QEMU instance, resulting in a denial of service. A NULL-pointer dereference vulnerability was discovered in the Linux kernel. The kernel's Reliable Datagram Sockets (RDS) protocol implementation did not verify that an underlying transport existed before creating a connection to a remote server. A local system user could exploit this flaw to crash the system by creating sockets at specific times to trigger a NULL pointer dereference. A double free vulnerability was found in netlink_dump, which could cause a denial of service or possibly other unspecified impact. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. A flaw was discovered in the OpenStack Image service (glance) where a tenant could manipulate the status of their images by submitting an HTTP PUT request together with an 'x-image-meta-status' header. A malicious tenant could exploit this flaw to reactivate disabled images, bypass storage quotas, and in some cases replace image contents (where they have owner access). Setups using the Image service's v1 API could allow the illegal modification of image status. Additionally, setups which also use the v2 API could allow a subsequent re-upload of image contents. It was discovered that grub2 builds for EFI systems contained modules that were not suitable to be loaded in a Secure Boot environment. An attacker could use this flaw to circumvent the Secure Boot mechanisms and load non-verified code. Attacks could use the boot menu if no password was set, or the grub2 configuration file if the attacker has root privileges on the system. A use-after-free flaw related to the PMAP_CALLIT operation and TCP/UDP connections was discovered in rpcbind. A remote, unauthenticated attacker could possibly exploit this flaw to crash the rpcbind service (denial of service) by performing a series of UDP and TCP calls. A NULL pointer dereference flaw was found in the SCTP implementation. A local user could use this flaw to cause a denial of service on the system by triggering a kernel panic when creating multiple sockets in parallel while the system did not have the SCTP module loaded. A flaw has been discovered in the QEMU emulator built with Virtual Network Device(virtio-net) support. If the guest's virtio-net driver did not support big or mergeable receive buffers, an issue could occur while receiving large packets over the tuntap/ macvtap interfaces. An attacker on the local network could use this flaw to disable the guest's networking; the user could send a large number of jumbo frames to the guest, which could exhaust all receive buffers, and lead to a denial of service. A directory traversal flaw was found in Tomcat's RequestUtil.java. A remote, authenticated user could use this flaw to bypass intended SecurityManager restrictions and list a parent directory via a '/..' in a pathname used by a web application in a getResource, getResourceAsStream, or getResourcePaths call. The runc component used by `docker exec` feature of docker allowed additional container processes to be ptraced by the pid 1 of the container. This allows the main processes of the container, if running as root, to gain low-level access to these new processes during initialization. An attacker can, depending on the nature of the incoming process, leverage this to elevate access to the host. This ranges from accessing host content through the file descriptors of the incoming process to, potentially, a complete container escape by leveraging memory access or syscall interception. It was discovered that the kernel-invoked coredump processor provided by ABRT did not handle symbolic links correctly when writing core dumps of ABRT programs to the ABRT dump directory (/var/spool/abrt). A local attacker with write access to an ABRT problem directory could use this flaw to escalate their privileges. A race-condition flaw was discovered in the OpenStack Image service (glance). When images in the upload state were deleted using a token close to expiration, untracked image data could accumulate in the back end. Because untracked data does not count towards the storage quota, an attacker could use this flaw to cause a denial of service through resource exhaustion. It was found that SSSD's Privilege Attribute Certificate (PAC) responder plug-in would leak a small amount of memory on each authentication request. A remote attacker could potentially use this flaw to exhaust all available memory on the system by making repeated requests to a Kerberized daemon application configured to authenticate using the PAC responder plug-in. It was discovered that the Libraries component of OpenJDK did not validate the length of the object identifier read from the DER input before allocating memory to store the OID. An attacker able to make a Java application decode a specially crafted DER input could cause the application to consume an excessive amount of memory. It was discovered that the Networking component of OpenJDK failed to properly parse user info from the URL. A remote attacker could cause a Java application to incorrectly parse an attacker supplied URL and interpret it differently from other applications processing the same URL. It was found that current implementation of kl5kusb105 driver failed to detect short transfers when attempting to read the line state and logged the content of the uninitialized heap transfer buffer. The vc4_get_bcl function in drivers/gpu/drm/vc4/vc4_gem.c in the VideoCore DRM driver in the Linux kernel before 4.9.7 does not set an errno value upon certain overflow detections allowing local users to cause a denial of service (incorrect pointer dereference and OOPS) via inconsistent size values in a VC4_SUBMIT_CL ioctl call. A race condition flaw was found in the way the Linux kernel's IPC subsystem initialized certain fields in an IPC object structure that were later used for permission checking before inserting the object into a globally visible list. A local, unprivileged user could potentially use this flaw to elevate their privileges on the system. A resource vulnerability in the OpenStack Compute (nova), Block Storage (cinder), and Image (glance) services was found in their use of qemu-img. An unprivileged user could consume as much as 4 GB of RAM on the compute host by uploading a malicious image. This flaw could lead possibly to host out-of-memory errors and negatively affect other running tenant instances. oslo.concurrency has been updated to support process limits ('prlimit'), which is needed to fix this flaw. A stack-based buffer overflow was found in the way the NTP autokey protocol was implemented. When an NTP client decrypted a secret received from an NTP server, it could cause that client to crash. It was found that because NTP's access control was based on a source IP address, an attacker could bypass source IP restrictions and send malicious control and configuration packets by spoofing ::1 addresses. A vulnerability was discovered in the way OpenStack Compute (nova) networking handled security group updates; changes were not applied to already running VM instances. A remote attacker could use this flaw to access running VM instances. A use-after-poison flaw was found in the way NSS parsed certain ASN.1 structures. An attacker could use this flaw to cause NSS to crash or execute arbitrary code with the permissions of the user running an application compiled against the NSS library. A heap-based buffer overflow flaw was found in the way NSS parsed certain ASN.1 structures. An attacker could use this flaw to cause NSS to crash or execute arbitrary code with the permissions of the user running an application compiled against the NSS library. A heap-based buffer overflow was found in NSPR. An attacker could use this flaw to cause NSPR to crash or execute arbitrary code with the permissions of the user running an application compiled against the NSPR library. A memory leak error was discovered in the crypt() function of the pgCrypto extension. An authenticated attacker could possibly use this flaw to disclose a limited amount of the server memory. A stack overflow flaw was discovered in the way the PostgreSQL core server processed certain JSON or JSONB input. An authenticated attacker could possibly use this flaw to crash the server backend by sending specially crafted JSON or JSONB input. It was discovered that ntpd as a client did not correctly check timestamps in Kiss-of-Death packets. A remote attacker could use this flaw to send a crafted Kiss-of-Death packet to an ntpd client that would increase the client's polling interval value, and effectively disable synchronization with the server. It was found that ntpd did not correctly implement the threshold limitation for the '-g' option, which is used to set the time without any restrictions. A man-in-the-middle attacker able to intercept NTP traffic between a connecting client and an NTP server could use this flaw to force that client to make multiple steps larger than the panic threshold, effectively changing the time to an arbitrary value at any time. A flaw was found in the way the way PHP's Phar extension parsed Phar archives. A specially crafted archive could cause PHP to crash or, possibly, execute arbitrary code when opened. A flaw was found in the way the way PHP's Phar extension parsed Phar archives. A specially crafted archive could cause PHP to crash or, possibly, execute arbitrary code when opened. A flaw was discovered in the Linux kernel where issuing certain ioctl() -s commands to the "/dev/ppp" device file could lead to a NULL pointer dereference. A privileged user could use this flaw to cause a kernel crash and denial of service. It was found that Ipsilon did not check whether a user is authorized to delete a service provider. An authenticated user could use this flaw to delete any service provider, potentially resulting in a denial of service. It was found that ABRT may have exposed non-public information to Red Hat Bugzilla during crash reporting. A bug in the libreport library caused changes made by a user in files included in a crash report to be discarded. As a result, Red Hat Bugzilla attachments may contain data that was not intended to be made public, including host names, IP addresses, or command line options. It was found that the x86 ISA (Instruction Set Architecture) is prone to a denial of service attack inside a virtualized environment in the form of an infinite loop in the microcode due to the way (sequential) delivering of benign exceptions such as #DB (debug exception) is handled. A privileged user inside a guest could use this flaw to create denial of service conditions on the host kernel. A stack-based buffer overflow was found in the way the NTP autokey protocol was implemented. When an NTP client decrypted a secret received from an NTP server, it could cause that client to crash. It was found that because NTP's access control was based on a source IP address, an attacker could bypass source IP restrictions and send malicious control and configuration packets by spoofing ::1 addresses. It was discovered that Director's NeutronMetadataProxySharedSecret parameter remained specified at the default value of 'unset'. This value is used by OpenStack Networking to sign instance headers; if unchanged, an attacker knowing the shared secret could use this flaw to spoof OpenStack Networking metadata requests. A flaw was found in the way the Linux kernel handled the securelevel functionality after performing a kexec operation. A local attacker could use this flaw to bypass the security mechanism of the securelevel/secureboot combination. A heap based buffer overflow was found in the ghostscript jbig2_decode_gray_scale_image() function used to decode halftone segments in a JBIG2 image. A document (PostScript or PDF) with an embedded, specially crafted, jbig2 image could trigger a segmentation fault in ghostscript. An out-of-bounds memory access flaw was found in the USBVision USB camera driver (usbvision_probe() function in drivers/media/usb/usbvision/usbvision-video.c). The driver assumes that the interfaces numbers of the USB device are always in 0,1,2,3... order. By using a specially crafted USB device which advertises an out-of-order number on one of its interfaces, an unprivileged user with physical access to the system can trigger a kernel NULL-pointer dereference causing a system freeze (denial of service). It was discovered that libwmf did not correctly process certain WMF (Windows Metafiles) with embedded BMP images. By tricking a victim into opening a specially crafted WMF file in an application using libwmf, a remote attacker could possibly use this flaw to execute arbitrary code with the privileges of the user running the application. It was found that JBoss EAP did not properly authorize a user performing a shut down. A remote user with the Monitor, Deployer, or Auditor role could use this flaw to shut down the EAP server, which is an action restricted to admin users. It was found that the Linux kernel's keys subsystem did not correctly garbage collect uninstantiated keyrings. A local attacker could use this flaw to crash the system or, potentially, escalate their privileges on the system. It was discovered that enabling debug mode in openstack-ironic-discoverd also enabled debug mode in the underlying Flask framework. If errors were encountered while Flask was in debug mode, a user experiencing an error might be able to access the debug console (effectively, a command shell). Kubernetes fails to validate object name types before passing the data to etcd. As the etcd service generates keys based on the object name type this can lead to a directory path traversal. It was found that the fix for CVE-2014-9750 was incomplete: three issues were found in the value length checks in NTP's ntp_crypto.c, where a packet with particular autokey operations that contained malicious data was not always being completely validated. A remote attacker could use a specially crafted NTP packet to crash ntpd. It was found that the fix for CVE-2014-9750 was incomplete: three issues were found in the value length checks in NTP's ntp_crypto.c, where a packet with particular autokey operations that contained malicious data was not always being completely validated. A remote attacker could use a specially crafted NTP packet to crash ntpd. It was found that the fix for CVE-2014-9750 was incomplete: three issues were found in the value length checks in NTP's ntp_crypto.c, where a packet with particular autokey operations that contained malicious data was not always being completely validated. A remote attacker could use a specially crafted NTP packet to crash ntpd. A memory leak flaw was found in ntpd's CRYPTO_ASSOC. If ntpd was configured to use autokey authentication, an attacker could send packets to ntpd that would, after several days of ongoing attack, cause it to run out of memory. An off-by-one flaw, leading to a buffer overflow, was found in cookedprint functionality of ntpq. A specially crafted NTP packet could potentially cause ntpq to crash. Multiple flaws were discovered in GStreamer's FLC/FLI/FLX media file format decoding plug-in. A remote attacker could use these flaws to cause an application using GStreamer to crash or, potentially, execute arbitrary code with the privileges of the user running the application. An out-of-bounds flaw was discovered in MIT Kerberos; the build_principal_va() function did not properly duplicate the realm. An authenticated remote attacker could possibly exploit this flaw by sending a TGS request containing a specially crafted realm field and crashing the KDC (denial of service). A type-confusion flaw was discovered in MIT Kerberos, where it incorrectly deals with IAKERB context handles. If an application calls gss_inquire_context() on a partially-established IAKERB context, an unauthenticated remote attacker could possibly exploit the flaw to crash the application (denial of service) by sending it a specially crafted IAKERB packet. A resource-access flaw was discovered in krb5; the SPNEGO mechanism operates under an incorrect assumption when dealing with its context handles. If an application calls gss_inquire_context() on a partially-established SPNEGO context, an unauthenticated, remote attacker could possibly exploit this flaw by sending a specially crafted SPNEGO packet and crashing the system. A type confusion vulnerability was discovered in the xsltStylePreCompute() function of libxslt. A remote attacker could possibly exploit this flaw to cause an application using libxslt to crash by tricking the application into processing a specially crafted XSLT document. A missing access control flaw was found in Samba. A remote, authenticated attacker could use this flaw to view the current snapshot on a Samba share, despite not having DIRECTORY_LIST access rights. It was found that bouncycastle is vulnerable to an invalid curve attack. An attacker could extract private keys used in elliptic curve cryptography with a few thousand queries. It was found that NTP's :config command could be used to set the pidfile and driftfile paths without any restrictions. A remote attacker could use this flaw to overwrite a file on the file system with a file containing the pid of the ntpd process (immediately) or the current estimated drift of the system clock (in hourly intervals). A denial of service flaw was found in libxml2. A remote attacker could provide a specially crafted XML or HTML file that, when processed by an application using libxml2, would cause that application to crash. A heap-based buffer overflow flaw was found in the way libxml2 parsed certain crafted XML input. A remote attacker could provide a specially crafted XML file that, when opened in an application linked against libxml2, would cause the application to crash causing a denial of service. It was found that NTP's :config command could be used to set the pidfile and driftfile paths without any restrictions. A remote attacker could use this flaw to overwrite a file on the file system with a file containing the pid of the ntpd process (immediately) or the current estimated drift of the system clock (in hourly intervals). An array-indexing error was discovered in the png_convert_to_rfc1123() function of libpng. An attacker could possibly use this flaw to cause an out-of-bounds read by tricking an unsuspecting user into processing a specially crafted PNG image. A denial of service flaw was discovered in the Linux kernel, where a race condition caused a NULL pointer dereference in the RDS socket-creation code. A local attacker could use this flaw to create a situation in which a NULL pointer crashed the kernel. A denial of service flaw was found in libxml2. A remote attacker could provide a specially crafted XML or HTML file that, when processed by an application using libxml2, would cause that application to use an excessive amount of CPU. A path-traversal flaw was found in the way the libvirt daemon handled filesystem names for storage volumes. A libvirt user with privileges to create storage volumes and without privileges to create and modify domains could possibly use this flaw to escalate their privileges. It was found that the x86 ISA (Instruction Set Architecture) is prone to a denial of service attack inside a virtualized environment in the form of an infinite loop in the microcode due to the way (sequential) delivering of benign exceptions such as #AC (alignment check exception) is handled. A privileged user inside a guest could use this flaw to create denial of service conditions on the host kernel. It was found that Spring Security does not consider URL path parameters when processing security constraints. By adding a URL path parameter with an encoded / to a request an attacker may be able to bypass a security constraint. A denial of service flaw was found in libxml2. A remote attacker could provide a specially crafted XML or HTML file that, when processed by an application using libxml2, would cause that application to crash. It was discovered that LibreOffice did not properly restrict automatic link updates. By tricking a victim into opening specially crafted documents, an attacker could possibly use this flaw to disclose contents of files accessible by the victim. It was found that the uniqueness_entry_to_config() function, used by the "attribute uniqueness" plugin of 389 Directory Server, did not properly NULL terminate an array used in some configuration. An authenticated, or possibly unauthenticated, attacker could use this flaw to force an out-of-bound heap memory read, possibly triggering a crash of the LDAP service. An integer underflow flaw leading to a heap-based buffer overflow when parsing PrinterSetup data was discovered. By tricking a user into opening a specially crafted document, an attacker could possibly exploit this flaw to execute arbitrary code with the privileges of the user opening the file. An integer overflow flaw, leading to a heap-based buffer overflow, was found in the way LibreOffice processed certain Microsoft Word .doc files. By tricking a user into opening a specially crafted Microsoft Word .doc document, an attacker could possibly use this flaw to execute arbitrary code with the privileges of the user opening the file. It was discovered that LibreOffice did not properly sanity check bookmark indexes. By tricking a user into opening a specially crafted document, an attacker could possibly use this flaw to execute arbitrary code with the privileges of the user opening the file. An integer-wraparound flaw leading to a stack-based overflow was found in Redis. A user with access to run Lua code in a Redis session could possibly use this flaw to crash the server (denial of service) or gain code execution outside of the Lua sandbox. A memory-read flaw was found in the way the libldb library processed LDB DN records with a null byte. An authenticated, remote attacker could use this flaw to read heap-memory pages from the server. A vulnerability was found in httpd's handling of the LimitRequestFields directive in mod_http2, affecting servers with HTTP/2 enabled. An attacker could send crafted requests with headers larger than the server's available memory, causing httpd to crash. It was discovered that the png_get_PLTE() and png_set_PLTE() functions of libpng did not correctly calculate the maximum palette sizes for bit depths of less than 8. In case an application tried to use these functions in combination with properly calculated palette sizes, this could lead to a buffer overflow or out-of-bounds reads. An attacker could exploit this to cause a crash or potentially execute arbitrary code by tricking an unsuspecting user into processing a specially crafted PNG image. However, the exact impact is dependent on the application using the library. A flaw was found in the director (openstack-tripleo-heat-templates) where the RabbitMQ credentials defaulted to guest/guest and supplied values in the configuration were not used. As a result, all deployed overclouds used the same credentials (guest/guest). A remote non-authenticated attacker could use this flaw to access RabbitMQ services in the deployed cloud. It was found that Samba always requested forwardable tickets when using Kerberos authentication. A service to which Samba authenticated using Kerberos could subsequently use the ticket to impersonate Samba to other services or domain users. It was found that Apache CXF permitted wrapping attacks in its support for SAML SSO. A malicious user could construct a SAML response that would bypass the login screen and possibly gain access to restricted information or resources. A vulnerability was discovered in SPICE in the server's protocol handling. An authenticated attacker could send crafted messages to the SPICE server causing a heap overflow leading to a crash or possible code execution. A denial of service flaw was found in libxml2. A remote attacker could provide a specially crafted XML or HTML file that, when processed by an application using libxml2, would cause that application to crash. A denial of service flaw was found in libxml2. A remote attacker could provide a specially crafted XML or HTML file that, when processed by an application using libxml2, would cause that application to crash. A denial of service flaw was found in libxml2. A remote attacker could provide a specially crafted XML or HTML file that, when processed by an application using libxml2, would cause that application to leak potentially sensitive information. A denial of service flaw was found in libxml2. A remote attacker could provide a specially crafted XML or HTML file that, when processed by an application using libxml2, would cause that application to crash. A flaw was found in the way Ceph Object Gateway would process cross-origin HTTP requests if the CORS policy was set to allow origin on a bucket. A remote unauthenticated attacker could use this flaw to cause denial of service by sending a specially-crafted cross-origin HTTP request. It was found that the Apache commons-collections library permitted code execution when deserializing objects involving a specially constructed chain of classes. A remote attacker could use this flaw to execute arbitrary code with the permissions of the application using the commons-collections library. An information-disclosure flaw was discovered in Red Hat OpenStack Platform director's installation of Object Storage (swift). During installation, the Puppet script responsible for deploying the service incorrectly removes and recreates the proxy-server.conf file with world-readable permissions. A privilege escalation flaw was discovered in CloudForms, where in certain situations, CloudForms could read encrypted data from the database and then write decrypted data back into the database. If the database was then exported or log files generated, a local attacker might be able to gain access to sensitive information. A flaw was found in the Linux kernel's implementation of Unix sockets. A server polling for client-socket data could put the peer socket on a wait list; the peer socket could then close the connection, making the reference on the wait list no longer valid. This could lead to bypassing the permissions on a Unix socket and packets being injected into the stream, and could also panic the machine (denial of service). It was found that the Linux kernel's IPv6 network stack did not properly validate the value of the MTU variable when it was set. A remote attacker could potentially use this flaw to disrupt a target system's networking (packet loss) by setting an invalid MTU value, for example, via a NetworkManager daemon that is processing router advertisement packets running on the target system. An integer overflow vulnerability was found in the ring_buffer_resize() calculations in which a privileged user can adjust the size of the ringbuffer message size. These calculations can create an issue where the kernel memory allocator will not allocate the correct count of pages yet expect them to be usable. This can lead to the ftrace() output to appear to corrupt kernel memory and possibly be used for privileged escalation or more likely kernel panic. It was found that gdm could crash due to a signal handler dispatched to an invalid conversation. An attacker could crash gdm by holding the escape key when the screen is locked, possibly bypassing the locked screen. An information-exposure flaw was found in the Django date filter. If an application allowed users to provide non-validated date formats, a malicious end user could expose application-settings data by providing the relevant applications-settings key instead of a valid date format. A denial of service flaw was found in libxml2. A remote attacker could provide a specially crafted XML or HTML file that, when processed by an application using libxml2, would cause that application to leak potentially sensitive information. A denial of service flaw was found in libxml2. A remote attacker could provide a specially crafted XML or HTML file that, when processed by an application using libxml2, would cause that application to leak potentially sensitive information. A flaw was found in the way the way PHP's Phar extension parsed Phar archives. A specially crafted archive could cause PHP to crash or, possibly, execute arbitrary code when opened. A heap-based buffer overflow flaw was discovered in the way QEMU's AMD PC-Net II Ethernet Controller emulation received certain packets in loopback mode. A privileged user (with the CAP_SYS_RAWIO capability) inside a guest could use this flaw to crash the host QEMU process (resulting in denial of service) or, potentially, execute arbitrary code with privileges of the host QEMU process. A denial of service vulnerability was found in the WhiteHEAT USB Serial Driver (whiteheat_attach function in drivers/usb/serial/whiteheat.c). In the driver, the COMMAND_PORT variable was hard coded and set to 4 (5th element). The driver assumed that the number of ports would always be 5 and used port number 5 as the command port. However, when using a USB device in which the number of ports was set to a number less than 5 (for example, 3), the driver triggered a kernel NULL-pointer dereference. A non-privileged attacker could use this flaw to panic the host. It was found that the improper default permissions on /tmp/auth directory in EAP 7 can allow any local user to connect to CLI and allow the user to execute any arbitary operations. A denial of service vulnerability was found in the WhiteHEAT USB Serial Driver (whiteheat_attach function in drivers/usb/serial/whiteheat.c). In the driver, the COMMAND_PORT variable was hard coded and set to 4 (5th element). The driver assumed that the number of ports would always be 5 and used port number 5 as the command port. However, when using a USB device in which the number of ports was set to a number less than 5 (for example, 3), the driver triggered a kernel NULL-pointer dereference. A non-privileged attacker could use this flaw to panic the host. A denial of service flaw was found in libxml2. A remote attacker could provide a specially crafted XML or HTML file that, when processed by an application using libxml2, would cause that application to leak potentially sensitive information. A flaw was found in the way the Linux kernel's ext4 file system driver handled non-journal file systems with an orphan list. An attacker with physical access to the system could use this flaw to crash the system or, although unlikely, escalate their privileges on the system. A privilege escalation flaw was found in the way Nagios handled log files. An attacker able to control the Nagios logging configuration (the 'nagios' user/group) could use this flaw to elevate their privileges to root. A NULL pointer dereference flaw was found in the way the Linux kernel's ext4 file system driver handled certain corrupted file system images. An attacker with physical access to the system could use this flaw to crash the system. A divide-by-zero flaw was discovered in the Linux kernel built with KVM virtualization support(CONFIG_KVM). The flaw occurs in the KVM module's Programmable Interval Timer(PIT) emulation, when PIT counters for channel 1 or 2 are set to zero(0) and a privileged user inside the guest attempts to read these counters. A privileged guest user with access to PIT I/O ports could exploit this issue to crash the host kernel (denial of service). A buffer overflow flaw was found in the way QEMU's AMD PC-Net II emulation validated certain received packets from a remote host in non-loopback mode. A remote, unprivileged attacker could potentially use this flaw to execute arbitrary code on the host with the privileges of the QEMU process. Note that to exploit this flaw, the guest network interface must have a large MTU limit. A flaw was found in the way Samba handled PAC (Privilege Attribute Certificate) checksums. A remote, authenticated attacker could use this flaw to crash the winbindd process. A vulnerability was discovered in SPICE in the server's protocol handling. An attacker able to connect to the SPICE server could send crafted messages which would cause the process to crash. An out-of-bounds memory access flaw was found in the Linux kernel's aiptek USB tablet driver (aiptek_probe() function in drivers/input/tablet/aiptek.c). The driver assumed that the interface always had at least one endpoint. By using a specially crafted USB device with no endpoints on one of its interfaces, an unprivileged user with physical access to the system could trigger a kernel NULL pointer dereference, causing the system to panic. The icmp6_send function in net/ipv6/icmp.c in the Linux kernel through 4.8.12 omits a certain check of the dst data structure which allows remote attackers to cause a denial of service (panic) via a fragmented IPv6 packet. An infinite-loop flaw was discovered in the QEMU emulator built with i8255x (PRO100) emulation support. When processing a chain of commands located in the Command Block List(CBL), each Command Block(CB) points to the next command in the list. If the link to the next CB pointed to the same block or if there was a closed loop in the chain, an infinite loop would execute the same command over and over again. A privileged user inside the guest could use this flaw to crash the QEMU instance, resulting in denial of service. It was discovered that the LDAPCertStore class in the Security component of OpenJDK followed LDAP referrals to arbitrary URLs. A specially crafted LDAP referral URL could cause LDAPCertStore to communicate with non-LDAP servers. A malicious guest administrator may be able to deny service by crashing the host or causing a deadlock by timing memory handling events between the guest and the host. A malicious guest administrator may be able to deny service by crashing the host or causing a deadlock by timing memory handling events between the guest and the host. A flaw was discovered in xen host that prevented the use of a physical CPU for a significant period of time. This can cause a softlockup or watchdog timeout in both the host and other guests. A stored cross-site scripting (XSS) flaw was found in the smart class parameters/variables field. By sending a specially crafted request to Satellite, a remote, authenticated attacker could embed HTML content into the stored data, allowing them to inject malicious content into the web page that is used to view that data. An information-leak vulnerability was found in the kernel when it truncated a file to a smaller size which consisted of an inline extent that was compressed. The data between the new file size and the old file size was not discarded and the number of bytes used by the inode were not correctly decremented, which gave the wrong report for callers of the stat(2) syscall. This wasted metadata space and allowed for the truncated data to be leaked, and data corruption or loss to occur. A caller of the clone ioctl could exploit this flaw by using only standard file-system operations without root access to read the truncated data. It was found that OpenShift's API back end did not verify requests for pod log locations, allowing a pod on a Node to request logs for any other pod on that Node. A remote attacker could use this flaw to view sensitive information via pod logs that they would normally not have access to. An insecure temporary file use flaw was found in the way sos created certain sosreport files. A local attacker could possibly use this flaw to perform a symbolic link attack to reveal the contents of sosreport files, or in some cases modify arbitrary files and escalate their privileges on the system. A flaw was found in the way grub2 handled backspace characters entered in username and password prompts. An attacker with access to the system console could use this flaw to bypass grub2 password protection and gain administrative access to the system. An invalid memory read access flaw was found in GStreamer's FLC/FLI/FLX media file format decoding plug-in. A remote attacker could use this flaw to cause an application using GStreamer to crash. It was discovered that foomatic-rip failed to remove all shell special characters from inputs used to construct command lines for external programs run by the filter. An attacker could possibly use this flaw to execute arbitrary commands. The xc2028_set_config function in drivers/media/tuners/tuner-xc2028.c in the Linux kernel before 4.6 allows local users to gain privileges or cause a denial of service (use-after-free) via vectors involving omission of the firmware name from a certain data structure. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. A NULL pointer dereference flaw was found in the way OpenSSL verified signatures using the RSA PSS algorithm. A remote attacker could possibly use this flaw to crash a TLS/SSL client using OpenSSL, or a TLS/SSL server using OpenSSL if it enabled client authentication. A memory leak vulnerability was found in the way OpenSSL parsed PKCS#7 and CMS data. A remote attacker could use this flaw to cause an application that parses PKCS#7 or CMS data from untrusted sources to use an excessive amount of memory and possibly crash. A race condition flaw, leading to a double free, was found in the way OpenSSL handled pre-shared key (PSK) identify hints. A remote attacker could use this flaw to crash a multi-threaded SSL/TLS client using OpenSSL. A denial of service flaw was found in the LDAP server provided by the AD DC in the Samba process daemon. A remote attacker could exploit this flaw by sending a specially crafted packet, which could cause the server to consume an excessive amount of memory and crash. It was discovered that the png_get_PLTE() and png_set_PLTE() functions of libpng did not correctly calculate the maximum palette sizes for bit depths of less than 8. In case an application tried to use these functions in combination with properly calculated palette sizes, this could lead to a buffer overflow or out-of-bounds reads. An attacker could exploit this to cause a crash or potentially execute arbitrary code by tricking an unsuspecting user into processing a specially crafted PNG image. However, the exact impact is dependent on the application using the library. An out-of-bounds heap read flaw was found in GStreamer's H.264 parser. A remote attacker could use this flaw to cause an application using GStreamer to crash. It was found that redhat-support-plugin-rhev passed a user-specified path and file name directly to the command line in the log viewer component. This could allow users with the SuperUser role on any Entity to execute arbitrary commands on any host in the RHEV environment. A flaw was found in the way the git-remote-ext helper processed certain URLs. If a user had Git configured to automatically clone submodules from untrusted repositories, an attacker could inject commands into the URL of a submodule, allowing them to execute arbitrary code on the user's system. It was found that the blk_rq_map_user_iov() function in the Linux kernel's block device implementation did not properly restrict the type of iterator, which could allow a local attacker to read or write to arbitrary kernel memory locations or cause a denial of service (use-after-free) by leveraging write access to a /dev/sg device. arch/arm/kernel/sys_oabi-compat.c in the Linux kernel before 4.4 allows local users to gain privileges via a crafted (1) F_OFD_GETLK, (2) F_OFD_SETLK, or (3) F_OFD_SETLKW command in an fcntl64 system call. An arithmetic-exception flaw was found in the QEMU emulator built with VNC display-driver support. The VNC server incorrectly handled 'SetPixelFormat' messages sent from clients. A privileged remote client could use this flaw to crash the guest resulting in denial of service. A stack overflow flaw was found in the way Qt parsed XML input with several nested opening tags. An application using Qt's QXmlSimpleReader to parse specially crafted XML input could crash. A denial of service flaw was found in the ldb_wildcard_compare() function of libldb. A remote attacker could send a specially crafted packet that, when processed by an application using libldb (for example the AD LDAP server in Samba), would cause that application to consume an excessive amount of memory and crash. An access flaw was found in the way Samba verified symbolic links when creating new files on a Samba share. A remote attacker could exploit this flaw to gain access to files outside of Samba's share path. A man-in-the-middle vulnerability was found in the way "connection signing" was implemented by Samba. A remote attacker could use this flaw to downgrade an existing Samba client connection and force the use of plain text. A flaw was found in the way TLS 1.2 could use the MD5 hash function for signing ServerKeyExchange and Client Authentication packets during a TLS handshake. A man-in-the-middle attacker able to force a TLS connection to use the MD5 hash function could use this flaw to conduct collision attacks to impersonate a TLS server or an authenticated TLS client. A bug was discovered in the error handling of the send file code for the NIO HTTP connector. This led to the current Processor object being added to the Processor cache multiple times allowing information leakage between requests including, and not limited to, session ID and the response body. A flaw was discovered in the OpenStack Compute (nova) snapshot feature when using the libvirt driver. A compute user could overwrite an attached instance disk with a malicious header specifying a backing file, and then request a snapshot, causing a file from the compute host to be leaked. This flaw only affects LVM or Ceph setups, or setups using filesystem storage with "use_cow_images = False". A NULL pointer dereference vulnerability was found in the QEMU emulator built with PCI MSI-X support. Because MSI-X MMIO support did not define the .write method, when the controller tried to write to the pending bit array(PBA) memory region, a segmentation fault occurred. A privileged attacker inside the guest could use this flaw to crash the QEMU process resulting in denial of service. A denial of service flaw was found in the way BIND processed certain records with malformed class attributes. A remote attacker could use this flaw to send a query to request a cached record with a malformed class attribute that would cause named functioning as an authoritative or recursive server to crash. Note: This issue affects authoritative servers as well as recursive servers, however authoritative servers are at limited risk if they perform authentication when making recursive queries to resolve addresses for servers listed in NS RRSETs. A NULL-pointer dereference flaw was found in the kernel, which is caused by a race between revoking a user-type key and reading from it. The issue could be triggered by an unprivileged user with a local account, causing the kernel to crash (denial of service). A flaw was found in the Linux kernel's key management system where it was possible for an attacker to escalate privileges or crash the machine. If a user key gets negatively instantiated, an error code is cached in the payload area. A negatively instantiated key may be then be positively instantiated by updating it with valid data. However, the ->update key type method must be aware that the error code may be there. It was found that use of a JMS ObjectMessage does not safely handle user supplied data when deserializing objects. A remote attacker could use this flaw to execute arbitrary code with the permissions of the application using a JMS ObjectMessage. An infinite-loop issue was found in the QEMU emulator built with USB EHCI emulation support. The flaw occurred during communication between the host controller interface(EHCI) and a respective device driver. These two communicate using an isochronous transfer descriptor list(iTD); an infinite loop unfolded if there was a closed loop in the list. A privileged user inside a guest could use this flaw to consume excessive resources and cause denial of service. A race-condition flaw was discovered in the kernel's netlink module creation, which can trigger a kernel panic in netlink_release->module_put for local users creating netlink sockets. The flaw is specific to Red Hat Enterprise Linux and does not affect upstream kernels. The nfnetlink_log module must be loaded before the flaw can occur. It was discovered that foomatic-rip failed to remove all shell special characters from inputs used to construct command lines for external programs run by the filter. An attacker could possibly use this flaw to execute arbitrary commands. A memory-leak flaw was found in the QEMU emulator built with VMWARE VMXNET3 paravirtual NIC emulator support. The flaw occurred when a guest repeatedly tried to activate the VMXNET3 device. A privileged guest attacker could use this flaw to leak host memory, resulting in denial of service on the host. A memory-leak flaw was found in the QEMU emulator built with VMWARE VMXNET3 paravirtual NIC emulator support. The flaw occurred when a guest repeatedly tried to activate the VMXNET3 device. A privileged guest attacker could use this flaw to leak host memory, resulting in denial of service on the host. An out-of-bounds flaw was found in the kernel, where the length of the sockaddr parameter was not checked in the pptp_bind() and pptp_connect() functions. As a result, more kernel memory was copied out than required, leaking information from the kernel stack (including kernel addresses). A local system user could exploit this flaw to bypass kernel ASLR or leak other information. A Time of Creation To Time of Usage (TOCTTOU) flaw was discovered in the QEMU emulator built with VirtFS(file system pass-through) support to share folders between host and guest. The flaw occurs if the 'virtfs-proxy-helper' program is installed with SUID permissions or has 'CAP_CHOWN' capability. An unprivileged, local attacker could exploit this flaw to potentially escalate their privileges and gain root access to the system. A NULL pointer dereference flaw was found in the way the Linux kernel's network subsystem handled socket creation with an invalid protocol identifier. A local user could use this flaw to crash the system. An out-of-bounds flaw was found in the kernel, where the sco_sock_bind() function (bluetooth/sco) did not check the length of its sockaddr parameter. As a result, more kernel memory was copied out than required, leaking information from the kernel stack (including kernel addresses). A local user could exploit this flaw to bypass kernel ASLR or leak other information. It was found that Apache Camel's Jetty/Servlet usage is vulnerable to Java object de-serialisation vulnerability. If using camel-jetty, or camel-servlet as a consumer in Camel routes, then Camel will automatically de-serialize HTTP requests that uses the content-header: application/x-java-serialized-object. A stack-based buffer overflow was found in the way the libresolv library performed dual A/AAAA DNS queries. A remote attacker could create a specially crafted DNS response which could cause libresolv to crash or, potentially, execute code with the permissions of the user running the library. Note: this issue is only exposed when libresolv is called from the nss_dns NSS service module. A stack buffer-overflow vulnerability has been discovered in the QEMU emulator built with SCSI MegaRAID SAS HBA emulation support. The flaw occurs when processing the SCSI controller's CTRL_GET_INFO command. A privileged guest user could exploit this flaw to crash the QEMU process instance (denial of service). An out-of-bounds write vulnerability has been found in the QEMU emulator built with Human Monitor Interface(HMP) support. The issue occurs when the 'sendkey' command (in hmp_sendkey) is processed with a 'keyname_len' that is greater than the 'keyname_buf' array size. A user or process could exploit this flaw to crash the QEMU process instance (denial of service). It was found that the Apache ActiveMQ client exposed a remote shutdown command in the ActiveMQConnection class. An attacker logged into a compromised broker could use this flaw to achieve denial of service on a connected client. It was found that IdM's certprofile-mod command did not properly check the user's permissions while modifying certificate profiles. An authenticated, unprivileged attacker could use this flaw to modify profiles to issue certificates with arbitrary naming or key usage information and subsequently use such certificates for other attacks. The ovl_setattr function in fs/overlayfs/inode.c in the Linux kernel through 4.3.3 attempts to merge distinct setattr operations, which allows local users to bypass intended access restrictions and modify the attributes of arbitrary overlay files via a crafted application. A heap-based buffer overflow flaw was discovered in the QEMU emulator built with the Q35-chipset-based PC system emulator. During VM-guest migration, more data (8 bytes) is moved than the allocated memory area. A privileged guest user could use this flaw to corrupt the VM guest image, which could potentially lead to a denial of service. An off-by-one vulnerability was discovered in the QEMU emulator built with Rocker-switch emulation support. The flaw occurred when processing transmit(tx) descriptors in the 'tx_consume' routine, if a descriptor had more than the allowed fragments (ROCKER_TX_FRAGS_MAX=16). A privilege-escalation vulnerability was discovered in the Linux kernel built with User Namespace (CONFIG_USER_NS) support. The flaw occurred when the ptrace() system call was used on a root-owned process to enter a user namespace. A privileged namespace user could exploit this flaw to potentially escalate their privileges on the system, outside the original namespace. An out-of-bounds read-write access flaw was found in the QEMU emulator built with NE2000-device emulation support. The flaw occurred while performing 'ioport' read-write operations. A privileged (CAP_SYS_RAWIO) user or process could exploit the flaw to leak or corrupt QEMU memory bytes. It was discovered that libxml2 could access out-of-bounds memory when parsing unclosed HTML comments. A remote attacker could provide a specially crafted XML file that, when processed by an application linked against libxml2, could cause the application to disclose heap memory contents. A reachable-assertion flaw was found in the QEMU emulator built with VMWARE-VMXNET3 paravirtualized NIC emulator support. The flaw occurs if a guest sends a Layer-2 packet that was smaller than 22 bytes. A privileged (CAP_SYS_RAWIO) guest user could exploit this flaw to crash the QEMU process instance, resulting in denial of service. A reachable-assertion flaw was found in the QEMU emulator built with VMWARE-VMXNET3 paravirtualized NIC emulator support. The flaw could occur while reading Interrupt Mask Registers (IMR). A privileged (CAP_SYS_RAWIO) guest user could exploit this flaw to crash the QEMU process instance, resulting in denial of service. Use-after-free vulnerability in the ffs_user_copy_worker function in drivers/usb/gadget/function/f_fs.c in the Linux kernel before 4.5.3 allows local users to gain privileges by accessing an I/O data structure after a certain callback call. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. An out-of-bounds read flaw was found in the way Expat processed certain input. A remote attacker could send specially crafted XML that, when parsed by an application using the Expat library, would cause that application to crash or, possibly, execute arbitrary code with the permission of the user running the application. A NULL pointer dereference flaw was found in the Linux kernel: the NFSv4.2 migration code improperly initialized the kernel structure. A local, authenticated user could use this flaw to cause a panic of the NFS client (denial of service). A use-after-free flaw was discovered in the Linux kernel's tty subsystem, which allows for the disclosure of uncontrolled memory location and possible kernel panic. The information leak is caused by a race condition when attempting to set and read the tty line discipline. A local attacker could use the TIOCSETD (via tty_set_ldisc ) to switch to a new line discipline; a concurrent call to a TIOCGETD ioctl performing a read on a given tty could then access previously allocated memory. Up to 4 bytes could be leaked when querying the line discipline or the kernel could panic with a NULL-pointer dereference. A flaw was found in the way the Linux kernel visor driver handles certain invalid USB device descriptors. The driver assumes that the device always has at least one bulk OUT endpoint. By using a specially crafted USB device (without a bulk OUT endpoint), an unprivileged user with physical access could trigger a kernel NULL-pointer dereference and cause a system panic (denial of service). A use-after-free flaw was found in the way QEMU's IDE AHCI emulator processed certain AHCI Native Command Queuing (NCQ) AIO commands. A privileged guest user could use this flaw to crash the QEMU process instance or, potentially, execute arbitrary code on the host with privileges of the QEMU process. A flaw was found in the way NTP verified trusted keys during symmetric key authentication. An authenticated client (A) could use this flaw to modify a packet sent between a server (B) and a client (C) using a key that is different from the one known to the client (A). A use-after-free flaw was found in the way the Linux kernel's key management subsystem handled keyring object reference counting in certain error path of the join_session_keyring() function. A local, unprivileged user could use this flaw to escalate their privileges on the system. A race condition flaw was found in the way the Linux kernel's SCTP implementation handled sctp_accept() during the processing of heartbeat timeout events. A remote attacker could use this flaw to prevent further connections to be accepted by the SCTP server running on the system, resulting in a denial of service. A flaw was found in the Linux networking subsystem where a local attacker with CAP_NET_ADMIN capabilities could cause an out-of-bounds memory access by creating a smaller-than-expected ICMP header and sending to its destination via sendto(). It was found that the Linux kernel did not properly account file descriptors passed over the unix socket against the process limit. A local user could use this flaw to exhaust all available memory on the system. An information leak flaw was found in the way the OpenSSH client roaming feature was implemented. A malicious server could potentially use this flaw to leak portions of memory (possibly including private SSH keys) of a successfully authenticated OpenSSH client. A buffer overflow flaw was found in the way the OpenSSH client roaming feature was implemented. A malicious server could potentially use this flaw to execute arbitrary code on a successfully authenticated OpenSSH client if that client used certain non-default configuration options. An out-of-bounds read/write flaw was discovered in the way QEMU's Firmware Configuration device emulation processed certain firmware configurations. A privileged (CAP_SYS_RAWIO) guest user could use this flaw to crash the QEMU process instance or, potentially, execute arbitrary code on the host with privileges of the QEMU process. An out-of-bounds heap buffer read flaw was found in the way advancecomp handled processing of ZIP files. An attacker could potentially use this flaw to crash the advzip utility by tricking it into processing crafted ZIP files. A vulnerability was discovered in the OpenStack Orchestration service (heat), where a specially formatted template could be used to trick the heat-engine service into opening a local file. Although the file contents are never disclosed to the end user, an OpenStack-authenticated attacker could use this flaw to cause a denial of service or determine whether a given file name is present on the server. It was discovered that the hawtio servlet uses a single HttpClient instance to proxy requests with a persistent cookie store (cookies are stored locally and are not passed between the client and the end URL) which means all clients using that proxy are sharing the same cookies. An authorization flaw was discovered in Kubernetes; the API server did not properly check user permissions when handling certain requests. An authenticated remote attacker could use this flaw to gain additional access to resources such as RAM and disk space. An authorization flaw was discovered in Kubernetes; the API server did not properly check user permissions when handling certain build-configuration strategies. A remote attacker could create build configurations with strategies that violate policy. Although the attacker could not launch the build themselves (launch fails when the policy is violated), if the build configuration files were later launched by other privileged services (such as automated triggers), user privileges could be bypassed allowing attacker escalation. A buffer over-read flaw was found in the GD library used by the PHP gd extension. A specially crafted image file could cause a PHP application using the imagerotate() function to disclose portions of the server memory or crash the PHP application. A memory-leak issue was found in OpenStack Object Storage (swift), in the proxy-to-server connection. An OpenStack-authenticated attacker could remotely trigger this flaw to cause denial of service through excess memory consumption. A memory-leak issue was found in OpenStack Object Storage (swift), in the client-to-proxy connection. An OpenStack-authenticated attacker could remotely trigger this flaw to cause denial of service through excess memory consumption. It was discovered that the password-based encryption (PBE) implementation in the Libraries component in OpenJDK used an incorrect key length. This could, in certain cases, lead to generation of keys that were weaker than expected. An access flaw was discovered in OpenSSH; the OpenSSH client did not correctly handle failures to generate authentication cookies for untrusted X11 forwarding. A malicious or compromised remote X application could possibly use this flaw to establish a trusted connection to the local X server, even if only untrusted X11 forwarding was requested. A NULL-pointer dereference flaw was found in the QEMU emulator built with TPR optimization for 32-bit Windows guests support. The flaw occurs when doing I/O-port write operations from the HMP interface. The 'current_cpu' value remains null because it is not called from the cpu_exec() loop, and dereferencing it results in the flaw. An attacker with access to the HMP interface could use this flaw to crash the QEMU instance (denial of service). A denial of service flaw was found in the way BIND processed certain malformed Address Prefix List (APL) records. A remote, authenticated attacker could use this flaw to cause named to crash. It was discovered that the JAXP component in OpenJDK did not properly enforce the totalEntitySizeLimit limit. An attacker able to make a Java application process a specially crafted XML file could use this flaw to make the application consume an excessive amount of memory. An infinite-loop vulnerability was discovered in the 389 directory server, where the server failed to correctly handle unexpectedly closed client connections. A remote attacker able to connect to the server could use this flaw to make the directory server consume an excessive amount of CPU and stop accepting connections (denial of service). An out-of-bounds write flaw was found in the JPEG image format decoder in the AWT component in OpenJDK. A specially crafted JPEG image could cause a Java application to crash or, possibly execute arbitrary code. An untrusted Java application or applet could use this flaw to bypass Java sandbox restrictions. It was discovered that ntpd as a client did not correctly check the originate timestamp in received packets. A remote attacker could use this flaw to send a crafted packet to an ntpd client that would effectively disable synchronization with the server, or push arbitrary offset/delay measurements to modify the time on the client. An out-of-bounds read vulnerability was found in OpenJPEG, in the j2k_to_image tool. Converting a specially crafted JPEG2000 file to another format could cause the application to crash or, potentially, disclose some data from the heap. A Cross-Site Request Forgery (CSRF) flaw was found in the pcsd web UI. A remote attacker could provide a specially crafted web page that, when visited by a user with a valid pcsd session, would allow the attacker to trigger requests on behalf of the user, for example removing resources or restarting/removing nodes. It was found that pcsd did not invalidate cookies on the server side when a user logged out. This could potentially allow an attacker to perform session fixation attacks on pcsd. It was found that the dynamic loader did not sanitize the LD_POINTER_GUARD environment variable. An attacker could use this flaw to bypass the pointer guarding protection on set-user-ID or set-group-ID programs to execute arbitrary code with the permissions of the user running the application. A NULL pointer dereference flaw was found in the way ntpd processed 'ntpdc reslist' commands that queried restriction lists with a large amount of entries. A remote attacker could potentially use this flaw to crash ntpd. A stack-based buffer overflow flaw was found in the way ntpd processed 'ntpdc reslist' commands that queried restriction lists with a large amount of entries. A remote attacker could use this flaw to crash ntpd. It was found that when NTP was configured in broadcast mode, a remote attacker could broadcast packets with bad authentication to all clients. The clients, upon receiving the malformed packets, would break the association with the broadcast server, causing them to become out of sync over a longer period of time. A flaw was found in the way the ntpq client processed certain incoming packets in a loop in the getresponse() function. A remote attacker could potentially use this flaw to crash an ntpq client instance. It was found that out-of-range time values passed to the strftime() function could result in an out-of-bounds memory access. This could lead to application crash or, potentially, information disclosure. An integer overflow vulnerability was found in hcreate() and hcreate_r() functions which could result in an out-of-bounds memory access. This could lead to application crash or, potentially, arbitrary code execution. A stack overflow vulnerability was found in nan* functions that could cause applications, which process long strings with the nan function, to crash or, potentially, execute arbitrary code. A stack based buffer overflow vulnerability was found in the catopen() function. An excessively long string passed to the function could cause it to crash or, potentially, execute arbitrary code. The hotrod java client in infinispan automatically deserializes bytearray message contents in certain events. A malicious user could exploit this flaw by injecting a specially-crafted serialized object to attain remote code execution or conduct other attacks. A memory allocation flaw, leading to a heap-based buffer overflow, was found in spice's smartcard interaction, which runs under the QEMU-KVM context on the host. A user connecting to a guest VM using spice could potentially use this flaw to crash the QEMU-KVM process or execute arbitrary code with the privileges of the host's QEMU-KVM process. An infinite loop flaw was found in the way QEMU's e1000 NIC emulation implementation processed data using transmit or receive descriptors under certain conditions. A privileged user inside a guest could use this flaw to crash the QEMU instance. It was discovered that rsync did not properly perform sanity checks on certain meta-information. By sending specially crafted meta-information, a remote attacker could possibly exploit this flaw to cause an rsync endpoint to write data to files outside of the expected destination path. A syntax vulnerability was discovered in the kernel's ASN1.1 DER decoder, which could lead to memory corruption or a complete local denial of service through x509 certificate DER files. A local system user could use a specially created key file to trigger BUG_ON() in the public_key_verify_signature() function (crypto/asymmetric_keys/public_key.c), to cause a kernel panic and crash the system. An infinite-loop flaw was found in the kernel. When a local user calls the sys_writev syscall with a specially crafted sequence of iov structs, the fuse_fill_write_pages kernel function might never terminate, instead continuing in a tight loop. This process cannot be terminated and requires a reboot. It was found that OpenSSL used weak Diffie-Hellman parameters based on unsafe primes, which were generated and stored in X9.42-style parameter files. An attacker who could force the peer to perform multiple handshakes using the same private DH component could use this flaw to conduct man-in-the-middle attacks on the SSL/TLS connection. A flaw was found in the way malicious SSLv2 clients could negotiate SSLv2 ciphers that were disabled on the server. This could result in weak SSLv2 ciphers being used for SSLv2 connections, making them vulnerable to man-in-the-middle attacks. It was found that the MariaDB client library did not properly check host names against server identities noted in the X.509 certificates when establishing secure connections using TLS/SSL. A man-in-the-middle attacker could possibly use this flaw to impersonate a server to a client. A flaw was discovered in the way the Linux kernel dealt with paging structures. When the kernel invalidated a paging structure that was not in use locally, it could, in principle, race against another CPU that is switching to a process that uses the paging structure in question. A local user could use a thread running with a stale cached virtual->physical translation to potentially escalate their privileges if the translation in question were writable and the physical page got reused for something critical (for example, a page table). A flaw was found in the way the Action Controller component compared user names and passwords when performing HTTP basic authentication. Time taken to compare strings could differ depending on input, possibly allowing a remote attacker to determine valid user names and passwords using a timing attack. A flaw was found in the way the Action Pack component performed MIME type lookups. Since queries were cached in a global cache of MIME types, an attacker could use this flaw to grow the cache indefinitely, potentially resulting in a denial of service. A flaw was found in the Active Record component's handling of nested attributes in combination with the destroy flag. An attacker could possibly use this flaw to set attributes to invalid values or clear all attributes. A directory traversal flaw was found in the way the Action View component searched for templates for rendering. If an application passed untrusted input to the 'render' method, a remote, unauthenticated attacker could use this flaw to render unexpected files and, possibly, execute arbitrary code. A flaw was found in the way the Active Model based models processed attributes. An attacker with the ability to pass arbitrary attributes to models could possibly use this flaw to bypass input validation. A flaw was found in the Action Pack component's caching of controller references. An attacker could use this flaw to cause unbounded memory growth, potentially resulting in a denial of service. A divide-by-zero vulnerability was found in a way the kernel processes TCP connections. The error can occur if a connection starts another cwnd reduction phase by setting tp->prior_cwnd to the current cwnd (0) in tcp_init_cwnd_reduction(). A remote, unauthenticated attacker could use this flaw to crash the kernel (denial of service). It was discovered that nginx could perform an out of bound read and dereference an invalid pointer when resolving CNAME DNS records. An attacker able to manipulate DNS responses received by nginx could use this flaw to cause a worker process to crash if nginx enabled the resolver in its configuration. A use-after-free flaw was found in the way nginx resolved certain CNAME DNS records. An attacker able to manipulate DNS responses received by nginx could use this flaw to cause a worker process to crash or, possibly, execute arbitrary code if nginx enabled the resolver in its configuration. It was discovered that nginx did not limit recursion when resolving CNAME DNS records. An attacker able to manipulate DNS responses received by nginx could use this flaw to cause a worker process to use an excessive amount of resources if nginx enabled the resolver in its configuration. An authorization vulnerability in OpenStack Image service was discovered, which allowed image-status manipulation using locations. By removing the last location of an image, an authenticated user could change the status from 'active' to 'queue'. A malicious tenant could exploit this flaw to silently replace owned image data, regardless of its original creator or visibility settings. Only environments with show_multiple_locations set to true (not default) were affected. An out-of-bounds read flaw was found in the kadmind service of MIT Kerberos. An authenticated attacker could send a maliciously crafted message to force kadmind to read beyond the end of allocated memory, and write the memory contents to the KDC database if the attacker has write permission, leading to information disclosure. A NULL pointer dereference flaw was found in the procedure used by the MIT Kerberos kadmind service to store policies: the kadm5_create_principal_3() and kadm5_modify_principal() function did not ensure that a policy was given when KADM5_POLICY was set. An authenticated attacker with permissions to modify the database could use this flaw to add or modify a principal with a policy set to NULL, causing the kadmind service to crash. A memory leak flaw was found in the krb5_unparse_name() function of the MIT Kerberos kadmind service. An authenticated attacker could repeatedly send specially crafted requests to the server, which could cause the server to consume large amounts of memory resources, ultimately leading to a denial of service due to memory exhaustion. A NULL-pointer dereference vulnerability was found in the Linux kernel's TCP stack, in net/netfilter/nf_nat_redirect.c in the nf_nat_redirect_ipv4() function. A remote, unauthenticated user could exploit this flaw to create a system crash (denial of service). It was discovered that the JAAS component of OpenJDK did not use the correct way to extract user DN from the result of the user search LDAP query. A specially crafted user LDAP entry could cause the application to use an incorrect DN. Multiple flaws were found in the way the mysqld_safe script handled creation of error log file. The mysql operating system user could use these flaws to escalate their privileges to root. A flaw was found in the way the Linux kernel's ASN.1 DER decoder processed certain certificate files with tags of indefinite length. A local, unprivileged user could use a specially crafted X.509 certificate DER file to crash the system or, potentially, escalate their privileges on the system. A NULL pointer dereference flaw was found in the QEMU emulator built with IDE AHCI emulation support. The flaw occurs when unmapping the Frame Information Structure(FIS) & Command List Block(CLB) entries. A privileged user inside a guest could use this flaw to crash the QEMU process instance (denial of service). A NULL pointer dereference flaw was found in the QEMU emulator built with USB EHCI emulation support. The flaw could occur when an application attempts to write to EHCI-capability registers. A privileged user inside a quest could exploit this flaw to crash the QEMU process instance (denial of service). It was found that Apache Camel's camel-xstream component was vulnerable to Java object deserialization. This vulnerability permits deserialization of data which could lead to information disclosure, code execution, or other possible attacks. It was found that Python's smtplib library did not return an exception when StartTLS failed to be established in the SMTP.starttls() function. A man in the middle attacker could strip out the STARTTLS command without generating an exception on the Python SMTP client application, preventing the establishment of the TLS layer. An integer overflow flaw, leading to a heap-based buffer overflow, was found in the PostgreSQL handling code for regular expressions. A remote attacker could use a specially crafted regular expression to cause PostgreSQL to crash or possibly execute arbitrary code. It was found that the fix for CVE-2015-1805 incorrectly kept buffer offset and buffer length in sync on a failed atomic read, potentially resulting in a pipe buffer state corruption. A local, unprivileged user could use this flaw to crash the system or leak kernel memory to user space. An out-of-bounds heap read flaw was found in GStreamer's MPEG-TS decoder. A remote attacker could use this flaw to cause an application using GStreamer to crash. A resource-management flaw was found in the Linux kernel's hugetlbfs handling of punching holes in hugetlbfs files with either truncate or fallocate. When truncating a hugetlbfs file, this bug could prevent some pages from being unmapped, which panics the system. With fallocate, pages could be prevented from being unmapped and then not removed, or more pages than desired could be unmapped (causing page faults to reestablish the mappings on subsequent page access). A local, non-privileged attacker could exploit this flaw by issuing a sequence of huge-page memory requests that crash the system (denial of service). A vulnerability has been discovered in Graphite2. An attacker able to trick an unsuspecting user into opening specially crafted font files in an application using Graphite2 could exploit these flaws to cause the application to crash or, potentially, execute arbitrary code with the privileges of the application. A vulnerability has been discovered in Graphite2. An attacker able to trick an unsuspecting user into opening specially crafted font files in an application using Graphite2 could exploit these flaws to cause the application to crash or, potentially, execute arbitrary code with the privileges of the application. A vulnerability has been discovered in Graphite2. An attacker able to trick an unsuspecting user into opening specially crafted font files in an application using Graphite2 could exploit these flaws to cause the application to crash or, potentially, execute arbitrary code with the privileges of the application. A type confusion issue was found in the way libssh generated ephemeral secrets for the diffie-hellman-group1 and diffie-hellman-group14 key exchange methods. This would cause an SSHv2 Diffie-Hellman handshake to use significantly less secure random parameters. A type confusion issue was found in the way libssh2 generated ephemeral secrets for the diffie-hellman-group1 and diffie-hellman-group14 key exchange methods. This would cause an SSHv2 Diffie-Hellman handshake to use significantly less secure random parameters. Race condition in kernel/events/core.c in the Linux kernel before 4.4 allows local users to gain privileges or cause a denial of service via use-after-free vulnerability by leveraging incorrect handling of an swevent data structure during a CPU unplug operation. A vulnerability was found in icoutils, in the wrestool program. An attacker could create a crafted executable that, when read by wrestool, could result in memory corruption leading to a crash or potential code execution. An incomplete-blacklist flaw was found in the blacklisting of URLs in Wildfly. A remote, unauthenticated user could exploit this flaw to expose sensitive files. Multiple flaws were found in the Lotus Word Pro (LWP) document format parser in LibreOffice. By tricking a user into opening a specially crafted LWP document, an attacker could possibly use this flaw to execute arbitrary code with the privileges of the user opening the file. A use-after-free flaw was found in the CXGB3 kernel driver when the network was considered to be congested. The kernel incorrectly misinterpreted the congestion as an error condition and incorrectly freed or cleaned up the socket buffer (skb). When the device then sent the skb's queued data, these structures were referenced. A local attacker could use this flaw to panic the system (denial of service) or, with a local account, escalate their privileges. A flaw was found in the USB-MIDI Linux kernel driver: a double-free error could be triggered for the 'umidi' object. An attacker with physical access to the system could use this flaw to escalate their privileges. Multiple flaws were found in the Lotus Word Pro (LWP) document format parser in LibreOffice. By tricking a user into opening a specially crafted LWP document, an attacker could possibly use this flaw to execute arbitrary code with the privileges of the user opening the file. A vulnerability has been discovered in Graphite2. An attacker able to trick an unsuspecting user into opening specially crafted font files in an application using Graphite2 could exploit these flaws to cause the application to crash or, potentially, execute arbitrary code with the privileges of the application. It was discovered that the unhtmlify() function of foomatic-rip did not correctly calculate buffer sizes, possibly leading to a heap-based memory corruption. A malicious attacker could exploit this flaw to cause foomatic-rip to crash or, possibly, execute arbitrary code. A NULL pointer dereference flaw was found in the QEMU emulator built with USB OHCI emulation support. The flaw could occur when OHCI transitions to the OHCI_USB_OPERATIONAL state, leading to the creation of multiple EOF timers. A privileged user inside a guest could exploit this flaw to crash the QEMU process on the host (denial of service). A NULL pointer dereference flaw was found in the QEMU emulator built with USB Net device emulation support. The flaw could occur while processing remote NDIS control message packets, if the USB configuration descriptor object is NULL. A privileged user inside a guest could exploit this flaw to crash the QEMU process instance (denial of service). A NULL pointer dereference flaw was found in GStreamer's MPEG-TS parser. A remote attacker could use this flaw to cause an application using GStreamer to crash. A read-timeout flaw was found in the HTTPS NIO Connector handling of SSL handshakes. A remote, unauthenticated attacker could create a socket and cause a thread to remain occupied indefinitely so long as the socket remained open (denial of service). Multiple flaws were found in Samba's DCE/RPC protocol implementation. A remote, authenticated attacker could use these flaws to cause a denial of service against the Samba server (high CPU load or a crash) or, possibly, execute arbitrary code with the permissions of the user running Samba (root). This flaw could also be used to downgrade a secure DCE/RPC connection by a man-in-the-middle attacker taking control of an Active Directory (AD) object and compromising the security of a Samba Active Directory Domain Controller (DC). A flaw was found in the way Samba handled ACLs on symbolic links. An authenticated user could use this flaw to gain access to an arbitrary file or directory by overwriting its ACL. A directory traversal flaw was found in the way the Action View component searched for templates for rendering. If an application passed untrusted input to the 'render' method, a remote, unauthenticated attacker could use this flaw to render unexpected files and, possibly, execute arbitrary code. A code injection flaw was found in the way Action View component searched for templates for rendering. If an application passed untrusted input to the 'render' method, a remote, unauthenticated attacker could use this flaw to execute arbitrary code. A vulnerability was found in icoutils, in the wrestool program. An attacker could create a crafted executable that, when read by wrestool, could result in memory corruption leading to a crash or potential code execution. A heap-based buffer overflow flaw was found in the way NSS parsed certain ASN.1 structures. An attacker could use this flaw to create a specially crafted certificate which, when parsed by NSS, could cause it to crash, or execute arbitrary code, using the permissions of the user running an application compiled against the NSS library. A padding oracle flaw was found in the Secure Sockets Layer version 2.0 (SSLv2) protocol. An attacker could potentially use this flaw to decrypt RSA-encrypted cipher text from a connection using a newer SSL/TLS protocol version, allowing them to decrypt such connections. This cross-protocol attack is publicly referred to as DROWN. A double-free flaw was found in the way OpenSSL parsed certain malformed DSA (Digital Signature Algorithm) private keys. An attacker could create specially crafted DSA private keys that, when processed by an application compiled against OpenSSL, could cause the application to crash. A side-channel attack was found that makes use of cache-bank conflicts on the Intel Sandy-Bridge microarchitecture. An attacker who has the ability to control code in a thread running on the same hyper-threaded core as the victim's thread that is performing decryption, could use this flaw to recover RSA private keys. A deserialization flaw allowing remote code execution was found in the BeanShell library. If BeanShell was on the classpath, it could permit code execution if another part of the application deserialized objects involving a specially constructed chain of classes. A remote attacker could use this flaw to execute arbitrary code with the permissions of the application using the BeanShell library. A vulnerability was found in icoutils, in the wrestool program. An attacker could create a crafted executable that, when read by wrestool, could result in failure to allocate memory or an over-large memcpy operation, leading to a crash. It was discovered that the SSLv2 servers using OpenSSL accepted SSLv2 connection handshakes that indicated non-zero clear key length for non-export cipher suites. An attacker could use this flaw to decrypt recorded SSLv2 sessions with the server by using it as a decryption oracle. It was discovered that the SSLv2 protocol implementation in OpenSSL did not properly implement the Bleichenbacher protection for export cipher suites. An attacker could use a SSLv2 server using OpenSSL as a Bleichenbacher oracle. It was found that access to private bookmarks of users is not properly restricted in Foreman. This could allow an attacker to view the search terms used in these bookmarks which should be private. A CSRF flaw was found in Tomcat's the index pages for the Manager and Host Manager applications. These applications included a valid CSRF token when issuing a redirect as a result of an unauthenticated request to the root of the web application. This token could then be used by an attacker to perform a CSRF attack. A session fixation flaw was found in the way Tomcat recycled the requestedSessionSSL field. If at least one web application was configured to use the SSL session ID as the HTTP session ID, an attacker could reuse a previously used session ID for further requests. It was found that several Tomcat session persistence mechanisms could allow a remote, authenticated user to bypass intended SecurityManager restrictions and execute arbitrary code in a privileged context via a web application that placed a crafted object in a session. It was found that Tomcat allowed the StatusManagerServlet to be loaded by a web application when a security manager was configured. This allowed a web application to list all deployed web applications and expose sensitive information such as session IDs. It was found that Tomcat could reveal the presence of a directory even when that directory was protected by a security constraint. A user could make a request to a directory via a URL not ending with a slash and, depending on whether Tomcat redirected that request, could confirm whether that directory existed. A security manager bypass flaw was found in Tomcat that could allow remote, authenticated users to access arbitrary application data, potentially resulting in a denial of service. An integer-overflow issue was found in the QEMU emulator built with USB Net device emulation support. The flaw could occur while processing remote NDIS control message packets because the incoming informationBufferOffset & Length combination could cross the integer range. A privileged user inside a guest could use this flaw to leak host memory bytes to the guest, or crash the QEMU process instance (denial of service). Multiple cross-site scripting (XSS) flaws were found in the way certain form data was handled in Red Hat Satellite. A user able to enter form data could use these flaws to perform XSS attacks against other Satellite users. Multiple cross-site scripting (XSS) flaws were found in the way HTTP GET parameter data was handled in Red Hat Satellite. A user able to provide malicious links to a Satellite user could use these flaws to perform XSS attacks against other Satellite users. An open-redirect flaw was found in the way Django's django.utils.http.is_safe_url() function filtered authentication URLs. An attacker able to trick a victim into visiting a crafted URL could use this flaw to redirect that victim to a malicious site. A timing attack flaw was found in the way Django's PBKDF2PasswordHasher performed password hashing. Passwords hashed with an older version of PBKDF2PasswordHasher used less hashing iterations, and thus allowed an attacker to enumerate existing users based on the time differences in the login requests. A resource-exhaustion vulnerability was found in the kernel, where an unprivileged process could allocate and accumulate far more file descriptors than the process' limit. A local, unauthenticated user could exploit this flaw by sending file descriptors over a Unix socket and then closing them to keep the process' fd count low, thereby creating kernel-memory or file-descriptors exhaustion (denial of service). A memory leak flaw was found in the way OpenSSL performed SRP user database look-ups using the SRP_VBASE_get_by_user() function. A remote attacker connecting to certain SRP servers with an invalid user name could leak approximately 300 bytes of the server's memory per connection. An integer overflow flaw, leading to a NULL pointer dereference or a heap-based memory corruption, was found in the way some BIGNUM functions of OpenSSL were implemented. Applications that use these functions with large untrusted input could crash or, potentially, execute arbitrary code. Several flaws were found in Samba's implementation of NTLMSSP authentication. An unauthenticated, man-in-the-middle attacker could use this flaw to clear the encryption and integrity flags of a connection, causing data to be transmitted in plain text. The attacker could also force the client or server into sending data in plain text even if encryption was explicitly requested for that connection. It was discovered that Samba configured as a Domain Controller would establish a secure communication channel with a machine using a spoofed computer name. A remote attacker able to observe network traffic could use this flaw to obtain session-related information about the spoofed machine. It was found that Samba's LDAP implementation did not enforce integrity protection for LDAP connections. A man-in-the-middle attacker could use this flaw to downgrade LDAP connections to use no integrity protection, allowing them to hijack such connections. It was found that Samba did not validate SSL/TLS certificates in certain connections. A man-in-the-middle attacker could use this flaw to spoof a Samba server using a specially crafted SSL/TLS certificate. It was discovered that Samba did not enforce Server Message Block (SMB) signing for clients using the SMB1 protocol. A man-in-the-middle attacker could use this flaw to modify traffic between a client and a server. It was found that Samba did not enable integrity protection for IPC traffic by default. A man-in-the-middle attacker could use this flaw to view and modify the data sent between a Samba server and a client. Several flaws were found in the way BIO_*printf functions were implemented in OpenSSL. Applications which passed large amounts of untrusted data through these functions could crash or potentially execute code with the permissions of the user running such an application. It was found that pkexec was vulnerable to TIOCSTI ioctl attacks, allowing the executed program to push characters to its TTY's input buffer. While being executed as a non-privileged user, a specially crafted program could force its parent TTY to enter commands, interpreted by the shell when pkexec exits. It was discovered that the Xerces-C XML parser did not properly process certain XML input. By providing specially crafted XML data to an application using Xerces-C for XML processing, a remote attacker could exploit this flaw to cause an application crash or, possibly, execute arbitrary code with the privileges of the application. Incorrect boundary checks were found in the way squid handled headers in HTTP responses, which could lead to an assertion failure. A malicious HTTP server could use this flaw to crash squid using a specially crafted HTTP response. Incorrect boundary checks were found in the way squid handled headers in HTTP responses, which could lead to an assertion failure. A malicious HTTP server could use this flaw to crash squid using a specially crafted HTTP response. It was found that squid did not properly handle errors when failing to parse an HTTP response, possibly leading to an assertion failure. A malicious HTTP server could use this flaw to crash squid using a specially crafted HTTP response. It was found that squid did not properly handle errors when failing to parse an HTTP response, possibly leading to an assertion failure. A malicious HTTP server could use this flaw to crash squid using a specially crafted HTTP response. It was found that runuser was vulnerable to TIOCSTI ioctl attacks, allowing the executed program to push characters to its TTY's input buffer. While being executed as a non-privileged user, a specially crafted program could force its parent TTY to enter commands, interpreted by the shell when runuser exits. It was found that chroot was vulnerable to TIOCSTI ioctl attacks, allowing the executed program to push characters to its TTY's input buffer. While being executed as a non-privileged user, a specially crafted program could force its parent TTY to enter commands, interpreted by the shell when chroot exits. It was discovered that the atl2_probe() function in the Atheros L2 Ethernet driver in the Linux kernel incorrectly enabled scatter/gather I/O. A remote attacker could use this flaw to obtain potentially sensitive information from the kernel memory. An information-exposure flaw was found in the OpenStack Compute (nova) resize and migrate functionality. An authenticated user could write a malicious qcow header to an ephemeral or root disk, referencing a block device as a backing file. With a subsequent resize or migration, file system content on the specified device would be leaked to the user. Only setups using libvirt with raw storage and "use_cow_images = False" were affected. A denial of service flaw was found in the way BIND processed a response to an ANY query. A remote attacker could use this flaw to make named exit unexpectedly with an assertion failure via a specially crafted DNS response. It was found that JGroups did not require necessary headers for encrypt and auth protocols from new nodes joining the cluster. An attacker could use this flaw to bypass security restrictions, and use this vulnerability to send and receive messages within the cluster, leading to information disclosure, message spoofing, or further possible attacks. An out-of-bounds flaw was found in the QEMU emulator built using 'address_space_translate' to map an address to a MemoryRegionSection. The flaw could occur while doing pci_dma_read/write calls, resulting in an out-of-bounds read-write access error. A privileged user inside a guest could use this flaw to crash the guest instance (denial of service). An out-of-bounds flaw was found in the QEMU emulator built using 'address_space_translate' to map an address to a MemoryRegionSection. The flaw could occur while doing pci_dma_read/write calls, resulting in an out-of-bounds read-write access error. A privileged user inside a guest could use this flaw to crash the guest instance (denial of service). An access flaw was discovered in OpenShift; the /etc/origin/master/master-config.yaml configuration file, which could contain Active Directory credentials, was world-readable. A local user could exploit this flaw to obtain authentication credentials from the master-config.yaml file. It was discovered that the Libraries component of OpenJDK accepted ECDSA signatures using non-canonical DER encoding. This could cause a Java application to accept signature in an incorrect format not accepted by other cryptographic tools. An infinite-loop flaw was found in the QEMU emulator built with NE2000 NIC emulation support. The flaw could occur when receiving packets over the network. A privileged user inside a guest could exploit this flaw to crash the QEMU instance (denial of service). It was found that AIO interface didn't use the proper rw_verify_area() helper function with extended functionality, for example, mandatory locking on the file. Also rw_verify_area() makes extended checks, for example, that the size of the access doesn't cause overflow of the provided offset limits. This integer overflow in fs/aio.c in the Linux kernel before 3.4.1 allows local users to cause a denial of service or possibly have unspecified other impact via a large AIO iovec. It was reported that on s390x, the fork of a process with four page table levels will cause memory corruption with a variety of symptoms. All processes are created with three level page table and a limit of 4TB for the address space. If the parent process has four page table levels with a limit of 8PB, the function that duplicates the address space will try to copy memory areas outside of the address space limit for the child process. Several flaws were found in the way BIO_*printf functions were implemented in OpenSSL. Applications which passed large amounts of untrusted data through these functions could crash or potentially execute code with the permissions of the user running such an application. An out-of-bounds read-access flaw was found in the QEMU emulator built with IP checksum routines. The flaw could occur when computing a TCP/UDP packet's checksum, because a QEMU function used the packet's payload length without checking against the data buffer's size. A user inside a guest could use this flaw to crash the QEMU process (denial of service). A use-after-free flaw was found in the way NSS processed certain DER (Distinguished Encoding Rules) encoded cryptographic keys. An attacker could use this flaw to create a specially crafted DER encoded certificate which, when parsed by an application compiled against the NSS library, could cause that application to crash, or execute arbitrary code using the permissions of the user running the application. It is possible for a single process to cause an OOM condition by filling large pipes with data that are never read. A typical process filling 4096 pipes with 1 MB of data will use 4 GB of memory and there can be multiple such processes, up to a per-user-limit. A resource-consumption flaw was discovered in the DHCP server. dhcpd did not restrict the number of open connections to OMAPI and failover ports. A remote attacker able to establish TCP connections to one of these ports could use this flaw to cause dhcpd to exit unexpectedly, stop responding requests, or exhaust system sockets (denial of service). A use-after-free flaw was found in the way NSS handled DHE (Diffie–Hellman key exchange) and ECDHE (Elliptic Curve Diffie-Hellman key exchange) handshake messages. A remote attacker could send a specially crafted handshake message that, when parsed by an application linked against NSS, would cause that application to crash or, under certain special conditions, execute arbitrary code using the permissions of the user running the application. A denial of service flaw was found in the way BIND processed certain control channel input. A remote attacker able to send a malformed packet to the control channel could use this flaw to cause named to crash. A denial of service flaw was found in the way BIND parsed signature records for DNAME records. By sending a specially crafted query, a remote attacker could use this flaw to cause named to crash. A flaw was found in the Linux kernel's implementation of setsockopt for the SO_{SND|RCV}BUFFORCE setsockopt() system call. Users with non-namespace CAP_NET_ADMIN are able to trigger this call and create a situation in which the sockets sendbuff data size could be negative. This could adversely affect memory allocations and create situations where the system could crash or cause memory corruption. A resource-consumption flaw was found in RabbitMQ Server, where the lengths_age or lengths_incr parameters were not validated in the management plugin. Remote, authenticated users with certain privileges could exploit this flaw to cause a denial of service by passing values which were too large. It was found that OpenShift Enterprise would disclose log file contents from reclaimed namespaces. An attacker could create a new namespace to access log files present in a previously deleted namespace using the same name. A memory access flaw was found in the way spice handled certain guests using crafted primary surface parameters. A user in a guest could use this flaw to read from and write to arbitrary memory locations on the host. A flaw was found in the building of containers within OpenShift Enterprise. An attacker could submit an image for building that executes commands within the container as root, allowing them to potentially escalate privileges. It was discovered that the OpenSSH server did not sanitize data received in requests to enable X11 forwarding. An authenticated client with restricted SSH access could possibly use this flaw to bypass intended restrictions. A flaw was found in the Linux kernel's implementation of setsockopt for the SO_{SND|RCV}BUF setsockopt() system call. Users with non-namespace CAP_NET_ADMIN are able to trigger this call and create a situation in which the sockets sendbuff data size could be negative. A security flaw was found in the Linux kernel in the mark_source_chains() function in "net/ipv4/netfilter/ip_tables.c". It is possible for a user-supplied "ipt_entry" structure to have a large "next_offset" field. This field is not bounds checked prior to writing to a counter value at the supplied offset. An integer overflow vulnerability was found in the Linux kernel in xt_alloc_table_info, which on 32-bit systems can lead to small structure allocation and a copy_from_user based heap corruption. A covert timing channel flaw was found in the DSA implementation in the JCE component of OpenJDK. A remote attacker able to make a Java application generate DSA signatures on demand could possibly use this flaw to extract certain information about the used key via a timing side channel. A stack-based buffer overflow flaw was found in the way the Quagga BGP routing daemon (bgpd) handled Labeled-VPN SAFI routes data. A remote attacker could use this flaw to crash the bgpd daemon resulting in denial of service. It was found that Apache Active MQ administration web console did not validate input correctly when creating a queue. An authenticated attacker could exploit this flaw via cross-site scripting and use it to access sensitive information or further attacks. It was reported that the web based administration console does not set the X-Frame-Options header in HTTP responses. This allows the console to be embedded in a frame or iframe which could then be used to cause a user to perform an unintended action in the console. An integer truncation flaw and an integer overflow flaw, both leading to a heap-based buffer overflow, were found in the way Git processed certain path information. A remote attacker could create a specially crafted Git repository that would cause a Git client or server to crash or, possibly, execute arbitrary code. An integer truncation flaw and an integer overflow flaw, both leading to a heap-based buffer overflow, were found in the way Git processed certain path information. A remote attacker could create a specially crafted Git repository that would cause a Git client or server to crash or, possibly, execute arbitrary code. A protocol flaw, publicly referred to as Badlock, was found in the Security Account Manager Remote Protocol (MS-SAMR) and the Local Security Authority (Domain Policy) Remote Protocol (MS-LSAD). Any authenticated DCE/RPC connection that a client initiates against a server could be used by a man-in-the-middle attacker to impersonate the authenticated user against the SAMR or LSA service on the server. As a result, the attacker would be able to get read/write access to the Security Account Manager database, and use this to reveal all passwords or any other potentially sensitive information in that database. A flaw in the Linux kernel was found in the way IOPL was handled during context switches in 64-bit Xen PV guests. A local guest user could potentially use this flaw to escalate their privileges in the guest. A security flaw was found in the Linux kernel's networking subsystem that destroying the network interface with huge number of ipv4 addresses assigned keeps "rtnl_lock" spinlock for a very long time (up to hour). This blocks many network-related operations, including creation of new incoming ssh connections. The problem is especially important for containers, as the container owner has enough permissions to trigger this and block a network access on a whole host, outside the container. A buffer overflow flaw was discovered in the OVS processing of MPLS labels. A remote attacker able to deliver a frame containing a malicious MPLS label that would be processed by OVS could trigger the flaw and use the resulting memory corruption to cause a denial of service (DoS) or, possibly, execute arbitrary code. A NULL pointer dereference flaw was found in MIT Kerberos kadmind service. An authenticated attacker with permission to modify a principal entry could use this flaw to cause kadmind to dereference a null pointer and crash by supplying an empty DB argument to the modify_principal command, if kadmind was configured to use the LDAP KDB module. A use-after-free flaw was found in bzip2recover, leading to a null pointer dereference, or a write to a closed file descriptor. An attacker could use this flaw by sending a specially crafted bzip2 file to recover and force the program to crash. Missing recursive loop detection checks were found in the xmlParserEntityCheck() and xmlStringGetNodeList() functions of libxml2, causing application using the library to crash by stack exhaustion while building the associated data. An attacker able to send XML data to be parsed in recovery mode could launch a Denial of Service on the application. An improper type safety check was discovered in the Hotspot component. An untrusted Java application or applet could use this flaw to bypass Java Sandbox restrictions. A security flaw was found in the Linux kernel that an attempt to move page mapped by AIO ring buffer to the other node triggers NULL pointer dereference at trace_writeback_dirty_page(), because aio_fs_backing_dev_info.dev is 0. It was found that several XML parsers used by XStream had default settings that would expand entity references. A remote, unauthenticated attacker could use this flaw to read files accessible to the user running the application server, and potentially perform other more advanced XXE attacks. A stack overflow vulnerability was found in _nss_dns_getnetbyname_r. On systems with nsswitch configured to include "networks: dns" with a privileged or network-facing service that would attempt to resolve user-provided network names, an attacker could provide an excessively long network name, resulting in stack corruption and code execution. An input sanitization flaw was found in the scoped search parameters sort_by and sort_order in the REST API. An authenticated user could use this flaw to perform an SQL injection attack on the Katello back end database. Multiple cross-site scripting (XSS) flaws were found in the way certain form data was handled in Red Hat Satellite. A user able to enter form data could use these flaws to perform XSS attacks against other Satellite users. A stored cross-site scripting (XSS) flaw was found in the way spacewalk-java displayed monitoring probes. An attacker can embed HTML and Javascript in the values for RHNMD User or Filesystem parameters in Satellite, allowing them to inject malicious content into the web page that is then displayed with that probe data. A stored cross-site scripting (XSS) flaw was found in the way spacewalk-java displayed group names. An attacker can embed HTML and Javascript in the values for group names in Satellite, allowing them to inject malicious content into the web page that is then displayed when viewing the snapshot data. A flaw was found in the Linux kernel when attempting to "punch a hole" in files existing on an ext4 filesystem. When punching holes into a file races with the page fault of the same area, it is possible that freed blocks remain referenced from page cache pages mapped to process' address space. An incorrect boundary check was found in the way squid handled the Vary header in HTTP responses, which could lead to an assertion failure. A malicious HTTP server could use this flaw to crash squid using a specially crafted HTTP response. It was discovered that Mercurial failed to properly check Git sub-repository URLs. A Mercurial repository that includes a Git sub-repository with a specially crafted URL could cause Mercurial to execute arbitrary code. It was discovered that the Mercurial convert extension failed to sanitize special characters in Git repository names. A Git repository with a specially crafted name could cause Mercurial to execute arbitrary code when the Git repository was converted to a Mercurial repository. A flaw was found in the way mod_nss parsed certain OpenSSL-style cipher strings. As a result, mod_nss could potentially use ciphers that were not intended to be enabled. A race condition vulnerability was discovered in NetworkManager. Temporary files were created insecurely when saving or updating connection settings, which could allow local users to read connection secrets such as VPN passwords or WiFi keys. A denial of service vulnerability was found in Go's verification of DSA public keys. An attacker could provide a crafted key to HTTPS client or SSH server libraries which would cause the application to enter an infinite loop. A weakness was found in the Linux ASLR implementation. Any user able to running 32-bit applications in a x86 machine can disable ASLR by setting the RLIMIT_STACK resource to unlimited. It was found that the private key for the node certificate was contained in a world-readable file. A local user could possibly use this flaw to gain access to the private key information in the file. It was found that the private key for the node certificate was contained in a world-readable temporary file. A local user could possibly use this flaw to gain access to the private key information in the temporary file. It was discovered that it is possible to remotely Segfault Apache http server with a specially crafted string sent to the mod_cluster via service messages (MCMP). It was found that the private RSA key was created in a directory that is world-readable for a small amount of time. A local user could possibly use this flaw to gain access to the private key information in the file. It was found that the private key for the agent certificate was contained in a world-readable file. A local user could possibly use this flaw to gain access to the private key information in the file. A flaw was found in the Linux kernel which could cause a kernel panic when restoring machine specific registers on the PowerPC platform. Incorrect transactional memory state registers could inadvertently change the call path on return from userspace and cause the kernel to enter an unknown state and crash. A flaw was found in the Linux kernel which could cause a kernel panic when restoring machine specific registers on the PowerPC platform. Incorrect transactional memory state registers could inadvertently change the call path on return from userspace and cause the kernel to enter an unknown state and crash. It was discovered that the LegacyInvokerServlet is exposed on all network interfaces and deserializes objects sent to it. An attacker could use this flaw to cause remote code execution in the JVM running it. It was found that NodeJS node-uuid used Math.random() to create a GUID (Globally Unique Identifier) which does not provide enough entropy (on some platforms it only provides 32 bits) which can result in collisions of GUIDs. An attacker could use this to guess GUID values and leverage further attacks against a system using node-uuid. An information-exposure flaw was found in Quick Emulator (QEMU) in Task Priority Register (TPR) optimizations for 32-bit Windows guests. The flaw could occur while accessing TPR. A privileged user inside a guest could use this issue to read portions of the host memory. A flaw was found in the provisioning template handling in foreman. An attacker, with permissions to create templates, can cause internal Rails information to be displayed when it is processed, resulting in potentially sensitive information being disclosed. It was discovered that the OpenSSH sshd daemon fetched PAM environment settings before running the login program. In configurations with UseLogin=yes and the pam_env PAM module configured to read user environment settings, a local user could use this flaw to execute arbitrary code as root. It was discovered that the Security component in OpenJDK failed to check the digest algorithm strength when generating DSA signatures. The use of a digest weaker than the key strength could lead to the generation of signatures that were weaker than expected. It was discovered that the JAXP component in OpenJDK failed to properly handle Unicode surrogate pairs used as part of the XML attribute values. Specially crafted XML input could cause a Java application to use an excessive amount of memory when parsed. It was discovered that the GCM (Galois/Counter Mode) implementation in the JCE component in OpenJDK used a non-constant time comparison when comparing GCM authentication tags. A remote attacker could possibly use this flaw to determine the value of the authentication tag. It was discovered that the RMI server implementation in the JMX component in OpenJDK did not restrict which classes can be deserialized when deserializing authentication credentials. A remote, unauthenticated attacker able to connect to a JMX port could possibly use this flaw to trigger deserialization flaws. It was found that the private CA key was created in a directory that is world-readable for a small amount of time. A local user could possibly use this flaw to gain access to the private key information in the file. A buffer overflow flaw was found in the way the Squid cachemgr.cgi utility processed remotely relayed Squid input. When the CGI interface utility is used, a remote attacker could possibly use this flaw to execute arbitrary code. Buffer overflow and input validation flaws were found in the way Squid processed ESI responses. If Squid was used as a reverse proxy, or for TLS/HTTPS interception, a remote attacker able to control ESI components on an HTTP server could use these flaws to crash Squid, disclose parts of the stack memory, or possibly execute arbitrary code as the user running Squid. Buffer overflow and input validation flaws were found in the way Squid processed ESI responses. If Squid was used as a reverse proxy, or for TLS/HTTPS interception, a remote attacker able to control ESI components on an HTTP server could use these flaws to crash Squid, disclose parts of the stack memory, or possibly execute arbitrary code as the user running Squid. Buffer overflow and input validation flaws were found in the way Squid processed ESI responses. If Squid was used as a reverse proxy, or for TLS/HTTPS interception, a remote attacker able to control ESI components on an HTTP server could use these flaws to crash Squid, disclose parts of the stack memory, or possibly execute arbitrary code as the user running Squid. A flaw was found in the way nodejs-tar, a Node.js module for reading and writing of tar archives, handled symbolic links when processing NPM packages. An attacker could potentially use this flaw to rewrite arbitrary files on the system. It was found that Docker would launch containers under the specified UID instead of a username. An attacker able to launch a container could use this flaw to escalate their privileges to root within the launched container. A denial of service flaw was found in the way semver, the semantic version comparison library for Node.js, parsed certain package versions. A remote attacker could use a specially crafted version string that, when processed, would lead to excessive CPU consumption. It was found that libndp did not properly validate and check the origin of Neighbor Discovery Protocol (NDP) messages. An attacker on a non-local network could use this flaw to advertise a node as a router, allowing them to perform man-in-the-middle attacks on a connecting client, or disrupt the network connectivity of that client. A heap-based buffer overflow flaw was found in jq's tokenadd() function. By tricking a victim into processing a specially crafted JSON file, an attacker could use this flaw to crash jq or, potentially, execute arbitrary code on the victim's system. A denial of service flaw was found in the way OpenSSL parsed certain ASN.1-encoded data from BIO (OpenSSL's I/O abstraction) inputs. An application using OpenSSL that accepts untrusted ASN.1 BIO input could be forced to allocate an excessive amount of data. A heap-buffer overflow was found in the poppler library. An attacker could create a malicious PDF file that would cause applications that use poppler (such as Evince) to crash or, potentially, execute arbitrary code when opened. A padding oracle flaw was found in the encryption of sensitive information stored within the backend database used by CloudForms. An attacker able to submit forged cipher texts could observe the results of encryption and determine information that could, in turn, lead to the disclosure of encrypted data within the database. An origin validation vulnerability was found in OpenShift Enterprise. An attacker could potentially access API credentials stored in a web browser's localStorage if anonymous access was granted to a service/proxy or pod/proxy API for a specific pod, and an authorized access_token was provided in the query parameter. Pulp makes unsafe use of Bash's $RANDOM to generate a NSS DB password and seed resulting in insufficient randomness. An attacker could potentially guess the seed used given enough time and compute resources. A covert timing channel flaw was found in the PKCS#8 implementation in the JCE component of OpenJDK. A remote attacker able to make a Java application repeatedly compare PKCS#8 key against an attacker controlled value could possibly use this flaw to determine the key via a timing side channel. A flaw was found in the way the realtime kernel processed specially crafted ICMP echo requests. A remote attacker could use this flaw to trigger a sysrql function based on values in the ICMP packet, allowing them to remotely restart the system. Note that this feature is not enabled by default and requires elevated privileges to be configured. A denial of service flaw was found in the way BIND handled a query response containing inconsistent DNSSEC information. A remote attacker could use this flaw to make named exit unexpectedly with an assertion failure via a specially crafted DNS response. A flaw was found in OpenShift Enterprise when multi-tenant SDN is enabled and a build is run within a namespace that would normally be isolated from pods in other namespaces. If an s2i build is run in such an environment the container being built can access network resources on pods that should not be available to it. A denial of service flaw was found in the Quagga BGP routing daemon (bgpd). Under certain circumstances, a remote attacker could send a crafted packet to crash the bgpd daemon resulting in denial of service. An out-of-bounds read/write access flaw was found in the way QEMU's VGA emulation with VESA BIOS Extensions (VBE) support performed read/write operations using I/O port methods. A privileged guest user could use this flaw to execute arbitrary code on the host with the privileges of the host's QEMU process. A flaw was found in the way OpenSSL encoded certain ASN.1 data structures. An attacker could use this flaw to create a specially crafted certificate which, when verified or re-encoded by OpenSSL, could cause it to crash, or execute arbitrary code using the permissions of the user running an application compiled against the OpenSSL library. It was discovered that OpenSSL leaked timing information when decrypting TLS/SSL and DTLS protocol encrypted records when the connection used the AES CBC cipher suite and the server supported AES-NI. A remote attacker could possibly use this flaw to retrieve plain text from encrypted packets by using a TLS/SSL or DTLS server as a padding oracle. An integer overflow flaw, leading to a buffer overflow, was found in the way the EVP_EncodeUpdate() function of OpenSSL parsed very large amounts of input data. A remote attacker could use this flaw to crash an application using OpenSSL or, possibly, execute arbitrary code with the permissions of the user running that application. A denial of service flaw was found in the way NTP handled preemptable client associations. A remote attacker could send several crypto NAK packets to a victim client, each with a spoofed source address of an existing associated peer, preventing that client from synchronizing its time. It was found that an ntpd client could be forced to change from basic client/server mode to the interleaved symmetric mode. A remote attacker could use a spoofed packet that, when processed by an ntpd client, would cause that client to reject all future legitimate server responses, effectively disabling time synchronization on that client. A flaw was found in the way NTP's libntp performed message authentication. An attacker able to observe the timing of the comparison function used in packet authentication could potentially use this flaw to recover the message digest. An out-of-bounds access flaw was found in the way ntpd processed certain packets. An authenticated attacker could use a crafted packet to create a peer association with hmode of 7 and larger, which could potentially (although highly unlikely) cause ntpd to crash. An integer overflow flaw, leading to a buffer overflow, was found in the way the EVP_EncryptUpdate() function of OpenSSL parsed very large amounts of input data. A remote attacker could use this flaw to crash an application using OpenSSL or, possibly, execute arbitrary code with the permissions of the user running that application. A covert timing channel flaw was found in the DSA implementation in the Libraries component of OpenJDK. A remote attacker could possibly use this flaw to extract certain information about the used key via a timing side channel. An information disclosure flaw was discovered in haproxy as used by OpenShift Enterprise; a cookie with the name "OPENSHIFT_[namespace]_SERVERID" was set, which contained the internal IP address of a pod. An integer conversion flaw was found in the way OCaml's String handled its length. Certain operations on an excessively long String could trigger a buffer overflow or result in an information leak. An integer overflow flaw and an out-of-bounds read flaw were found in the way QEMU's VGA emulator set certain VGA registers while in VBE mode. A privileged guest user could use this flaw to crash the QEMU process instance. A denial of service flaw was found in the way BIND handled an unusually-formed DS record response. A remote attacker could use this flaw to make named exit unexpectedly with an assertion failure via a specially crafted DNS response. Missing incrementation of recursion depth counter were found in the xmlParserEntityCheck() and xmlParseAttValueComplex() functions used for parsing XML data. An attacker could launch a Denial of Service attack by passing specially crafted XML data to an application, forcing it to crash due to stack exhaustion. It was discovered that certain ImageMagick coders and pseudo-protocols did not properly prevent security sensitive operations when processing specially crafted images. A remote attacker could create a specially crafted image that, when processed by an application using ImageMagick or an unsuspecting user using the ImageMagick utilities, would allow the attacker to delete arbitrary files. It was discovered that ImageMagick did not properly sanitize certain input before passing it to the delegate functionality. A remote attacker could create a specially crafted image that, when processed by an application using ImageMagick or an unsuspecting user using the ImageMagick utilities, would lead to arbitrary execution of shell commands with the privileges of the user running the application. It was discovered that certain ImageMagick coders and pseudo-protocols did not properly prevent security sensitive operations when processing specially crafted images. A remote attacker could create a specially crafted image that, when processed by an application using ImageMagick or an unsuspecting user using the ImageMagick utilities, would allow the attacker to move arbitrary files. It was discovered that certain ImageMagick coders and pseudo-protocols did not properly prevent security sensitive operations when processing specially crafted images. A remote attacker could create a specially crafted image that, when processed by an application using ImageMagick or an unsuspecting user using the ImageMagick utilities, would allow the attacker to disclose the contents of arbitrary files. A server-side request forgery flaw was discovered in the way ImageMagick processed certain images. A remote attacker could exploit this flaw to mislead an application using ImageMagick or an unsuspecting user using the ImageMagick utilities into, for example, performing HTTP(S) requests or opening FTP sessions via specially crafted images. A process that is in the same process group as the ''init'' process (group id zero) can crash the Linux kernel with several system calls by passing in a process ID or process group ID of zero; a special value that indicates the current process ID or process group. The proc_connectinfo() function in 'drivers/usb/core/devio.c' in the Linux kernel through 4.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel stack memory via a crafted USBDEVFS_CONNECTINFO ioctl call. The stack object 'ci' has a total size of 8 bytes. Its last 3 bytes are padding bytes which are not initialized and are leaked to userland. It was discovered that the Mercurial convert extension invoked Git in a way that could cause Git to interpret local repository name as remote repository URL. A Git repository with a specially crafted name could cause Mercurial to execute arbitrary code when the Git repository was converted to a Mercurial repository. It was found that the “variant” parameter in the TFTP API of Foreman was passed to the eval() function. An attacker could possibly use this flaw to execute arbitrary code with the privileges of the Foreman user. It was discovered that sending specially crafted HTTP request to the JON server would allow deserialization of that message without authentication. An attacker could use this flaw to cause remote code execution. A vulnerability was found in the STI build process in OpenShift Enterprise. Access to STI builds was not properly restricted, allowing an attacker to use STI builds to access the Docker socket and escalate their privileges. A vulnerability was found in libarchive. A specially crafted zip file can provide an incorrect compressed size, which may allow an attacker to place arbitrary code on the heap and execute it in the context of the application. An input validation flaw was found in the way Squid handled intercepted HTTP Request messages. An attacker could use this flaw to bypass the protection against issues related to CVE-2009-0801, and perform cache poisoning attacks on Squid. An input validation flaw was found in Squid's mime_get_header_field() function, which is used to search for headers within HTTP requests. An attacker could send an HTTP request from the client side with specially crafted header Host header that bypasses same-origin security protections, causing Squid operating as interception or reverse-proxy to contact the wrong origin server. It could also be used for cache poisoning for client not following RFC 7230. A NULL pointer dereference flaw was found in the way Squid processes ESI responses. If Squid was used as a reverse proxy or for TLS/HTTPS interception, a malicious server could use this flaw to crash the Squid worker process. It was found that IdM's ca-del, ca-disable, and ca-enable commands did not properly check the user's permissions while modifying CAs in Dogtag. An authenticated, unauthorized attacker could use this flaw to delete, disable, or enable CAs causing various denial of service problems with certificate issuance, OCSP signing, and deletion of secret keys. A flaw was found in the Linux kernel's implementation of BPF in which systems can application can overflow a 32 bit refcount in both program and map refcount. This refcount can wrap and end up a user after free. A vulnerability was found in Linux kernel. There is an information leak in file "sound/core/timer.c" of the latest mainline Linux kernel, the stack object “tread” has a total size of 32 bytes. It contains a 8-bytes padding, which is not initialized but sent to user via copy_to_user(), resulting a kernel leak. An incorrect reference counting flaw was found in the way Squid processes ESI responses. If Squid is configured as reverse-proxy, for for TLS/HTTPS interception, an attacker controlling a server accessed by Squid, could crash the squid worker, causing a Denial of Service attack. A vulnerability was found in Linux kernel. There is an information leak in file sound/core/timer.c of the latest mainline Linux kernel. The stack object “r1” has a total size of 32 bytes. Its field “event” and “val” both contain 4 bytes padding. These 8 bytes padding bytes are sent to user without being initialized. An integer-overflow flaw was found in V8's Zone class when allocating new memory (Zone::New() and Zone::NewExpand()). An attacker with the ability to manipulate a large zone could crash the application or, potentially, execute arbitrary code with the application privileges. Use after free vulnerability was found in percpu using previously allocated memory in bpf. First __alloc_percpu_gfp() is called, then the memory is freed with free_percpu() which triggers async pcpu_balance_work and then pcpu_extend_area_map could use a chunk after it has been freed. A flaw in 'arch/arm64/kernel/sys.c' in the Linux kernel allows local users to bypass the 'strict page permissions' protection mechanism and modify the system-call table and, consequently, gain privileges by leveraging write access. A denial of service flaw was found in httpd's mod_http2 module. A remote attacker could use this flaw to block server threads for long times, causing starvation of worker threads, by manipulating the flow control windows on streams. A flaw was found in the way certain interfaces of the Linux kernel's Infiniband subsystem used write() as bi-directional ioctl() replacement, which could lead to insufficient memory security checks when being invoked using the splice() system call. A local unprivileged user on a system with either Infiniband hardware present or RDMA Userspace Connection Manager Access module explicitly loaded, could use this flaw to escalate their privileges on the system. A vulnerability was found in the Linux kernel. Payloads of NM entries are not supposed to contain NUL. When such entry is processed, only the part prior to the first NUL goes into the concatenation (i.e. the directory entry name being encoded by a bunch of NM entries). The process stops when the amount collected so far + the claimed amount in the current NM entry exceed 254. However, the value returned as the total length is the sum of *claimed* sizes, not the actual amount collected. And that's what will be passed to readdir() callback as the name length - 8Kb __copy_to_user() from a buffer allocated by __get_free_page(). A flaw was found in RHEV Manager, where it wrote sensitive data to the engine-setup log file. A local attacker could exploit this flaw to view sensitive information such as encryption keys and certificates (which could then be used to steal other sensitive information such as passwords). It was discovered that the RMI registry and DCG implementations in the RMI component of OpenJDK performed deserialization of untrusted inputs. A remote attacker could possibly use this flaw to execute arbitrary code with the privileges of RMI registry or a Java RMI application. A vulnerability was found in the Linux kernel. The pointer to the netlink socket attribute is not checked, which could cause a null pointer dereference when parsing the nested attributes in function tipc_nl_publ_dump(). This allows local users to cause a DoS. Quick Emulator(Qemu) built with the VMWARE PVSCSI paravirtual SCSI bus emulation support is vulnerable to an OOB r/w access issue. It could occur while processing SCSI commands 'PVSCSI_CMD_SETUP_RINGS' or 'PVSCSI_CMD_SETUP_MSG_RING'. A privileged user inside guest could use this flaw to crash the Qemu process resulting in DoS. A shell command injection flaw was found in the way the setroubleshoot allow_execmod plugin executed external commands. A local attacker able to trigger an execmod SELinux denial could use this flaw to execute arbitrary code with root privileges. A shell command injection flaw was found in the way the setroubleshoot executed external commands. A local attacker able to trigger certain SELinux denials could use this flaw to execute arbitrary code with root privileges. A shell command injection flaw was found in the way the setroubleshoot allow_execstack plugin executed external commands. A local attacker able to trigger an execstack SELinux denial could use this flaw to execute arbitrary code with root privileges. It was found that Satellite 6 did not properly enforce access controls on certain resources. An attacker, with access to the API and knowledge of the ID name, can potentially access other resources in other organizations. It was discovered that the JPEGImageReader implementation in the 2D component of OpenJDK would, in certain cases, read all image data even if it was not used later. A specially crafted image could cause a Java application to temporarily use an excessive amount of CPU and memory. It was found that the parsing of OOXML, XMP in PDF, and some other file formats by Apache Tika would expand entity references. A remote, unauthenticated attacker could use this flaw to read files accessible to the user running the application server, and potentially perform other more advanced XXE attacks. It was found that the parsing of XMP and other XML formats in PDF by Apache PDFBox would expand entity references. A remote, unauthenticated attacker could use this flaw to read files accessible to the user running the application server, and potentially perform other more advanced XXE attacks. Quick Emulator(Qemu) built with the VMware-SVGA "chipset" emulation support is vulnerable to an infinite loop issue. It could occur while processing VGA commands via its FIFO buffer. A privileged user inside guest could use this flaw to crash the Qemu process resulting in DoS. Quick Emulator(Qemu) built with the VMware-SVGA "chipset" emulation support is vulnerable to an information disclosure issue. It could occur while processing VGA commands via its FIFO buffer. A privileged user inside guest could use this flaw to leak host memory bytes or crash the Qemu process resulting in DoS. It was found that subscription-manager set weak permissions on files in /var/lib/rhsm/, causing an information disclosure. A local, unprivileged user could use this flaw to access sensitive data that could potentially be used in a social engineering attack. An out-of-bounds write flaw was found in the fpm_log_write() logging function of PHP's FastCGI Process Manager service. A remote attacker could repeatedly send maliciously crafted requests to force FPM to exhaust file system space, creating a denial of service and preventing further logging. It was discovered that ImageMagick did not properly sanitize certain input before using it to invoke processes. A remote attacker could create a specially crafted image that, when processed by an application using ImageMagick or an unsuspecting user using the ImageMagick utilities, would lead to arbitrary execution of shell commands with the privileges of the user running the application. Quick Emulator(QEMU) built with the Block driver for iSCSI images support (virtio-blk) is vulnerable to a heap-based buffer overflow issue. The flaw could occur while processing iSCSI asynchronous I/O ioctl(2) calls. A user inside a guest could exploit this flaw to crash the QEMU process resulting in denial of service, or potentially leverage it to execute arbitrary code with QEMU-process privileges on the host. CloudForms includes a default SSL/TLS certificate for the web server. This certificate is replaced at install time. However if an attacker were able to man-in-the-middle an administrator while installing the new certificate, the attacker could get a copy of the uploaded private key allowing for future attacks. A NULL pointer dereference flaw was found in the nginx code responsible for saving client request body to a temporary file. A remote attacker could send a specially crafted request that would cause nginx worker process to crash. It was discovered that specifying configuration with a JVMRoute path longer than 80 characters will cause segmentation fault leading to a server crash. Multiple integer overflow flaws were found in the way OpenSSL performed pointer arithmetic. A remote attacker could possibly use these flaws to cause a TLS/SSL server or client using OpenSSL to crash. A flaw was found in the Linux kernel's keyring handling code: the key_reject_and_link() function could be forced to free an arbitrary memory block. An attacker could use this flaw to trigger a use-after-free condition on the system, potentially allowing for privilege escalation. An issue was discovered in the image build process for the overcloud images, as used by director, resulting in all previous images to have a default root password of "rootpw". Remote root access via SSH is disabled by default. It was found that the foreman API and UI actions and URLs are not properly limited to the organizations and locations they were assigned to. This could allow an attacker to view and update other organizations and locations in the system that they should not be allowed to. A leak of information was possible when issuing a netlink command of the stack memory area leading up to this function call. An attacker could use this to determine stack information for use in a later exploit. A vulnerability was found in the Linux kernel in function rds_inc_info_copy of file net/rds/recv.c. The last field "flags" of object "minfo" is not initialized. This can leak data previously at the flags location to userspace. It was found that Apache Shiro uses a default cipher key for its "remember me" feature. An attacker could use this to devise a malicious request parameter and gain access to unauthorized content. It was discovered that OpenSSL did not always use constant time operations when computing Digital Signature Algorithm (DSA) signatures. A local attacker could possibly use this flaw to obtain a private DSA key belonging to another user or service running on the same system. It was discovered that ImageMagick did not properly sanitize certain input before passing it to the gnuplot delegate functionality. A remote attacker could create a specially crafted image that, when processed by an application using ImageMagick or an unsuspecting user using the ImageMagick utilities, would lead to arbitrary execution of shell commands with the privileges of the user running the application. An attacker on a network could abuse a flaw in the IPv6 stack fragment reassembly code to induce kernel memory corruption on the system, possibly leading to a system crash. It was found that wget used a file name provided by the server for the downloaded file when following a HTTP redirect to a FTP server resource. This could cause wget to create a file with a different name than expected, possibly allowing the server to execute arbitrary code on the client. A DOM-based, cross-site scripting vulnerability was found in the OpenStack dashboard, where user input was not filtered correctly. An authenticated dashboard user could exploit the flaw by injecting an AngularJS template into a dashboard form (for example, using an image's description), triggering the vulnerability when another user browsed the affected page. As a result, this flaw could result in user accounts being compromised (for example, user-access credentials being stolen). It was discovered that the Nashorn JavaScript engine in the Scripting component of OpenJDK could allow scripts to access Java APIs even when access to Java APIs was disabled. An untrusted JavaScript executed by Nashorn could use this flaw to bypass intended restrictions. It was found that keycloak's implementation of HMAC verification for JWS tokens uses a method that runs in non-constant time, potentially leaving the application vulnerable to timing attacks. A flaw was discovered in openstack-murano processing. Using extended YAML tags in Murano-application YAML files, an attacker could perform remote code execution. It was found that targets using gcc's libssp library for Stack Smashing Protection (among others: Cygwin, MinGW, newlib, RTEMS; but not Glibc, Bionic, NetBSD which provide SSP in libc), are missing the Object Size Checking feature, even when explicitly requested with _FORTIFY_SOURCE. Vulnerable binaries compiled against such targets do not benefit of such protection, increasing the chances of success of a buffer overflow attack. A traffic amplification flaw was found in the Internet Key Exchange version 1 (IKEv1) protocol. A remote attacker could use a libreswan server with IKEv1 enabled in a network traffic amplification denial of service attack against other hosts on the network by sending UDP packets with a spoofed source address to that server. It was found that stacking a file system over procfs in the Linux kernel could lead to a kernel stack overflow due to deep nesting, as demonstrated by mounting ecryptfs over procfs and creating a recursion by mapping /proc/environ. An unprivileged, local user could potentially use this flaw to escalate their privileges on the system. Neutron functionality includes internal firewall management between networks. Due to the relaxed nature of particular rules, it is possible for machines on the same layer 2 networks to forge non-IP traffic, such as ARP and DHCP requests. Neutron functionality includes internal firewall management between networks. Due to the relaxed nature of particular rules, it is possible for machines on the same layer 2 networks to forge non-IP traffic, such as ARP and DHCP requests. Neutron functionality includes internal firewall management between networks. Due to the relaxed nature of particular rules, it is possible for machines on the same layer 2 networks to forge non-IP traffic, such as ARP and DHCP requests. An information-disclosure flaw was found in oslo.middleware. Software using the CatchError class could include sensitive values in a traceback's error message. System users could exploit this flaw to obtain sensitive information from OpenStack component error logs (for example, keystone tokens). An authentication vulnerability was found in openstack-ironic. A client with network access to the ironic-api service could bypass OpenStack Identity authentication, and retrieve all information about any node registered with OpenStack Bare Metal. If an unprivileged attacker knew (or was able to guess) the MAC address of a network card belonging to a node, the flaw could be exploited by sending a crafted POST request to the node's /v1/drivers/$DRIVER_NAME/vendor_passthru resource. The response included the node's full details, including management passwords, even if the /etc/ironic/policy.json file was configured to hide passwords in API responses. Shell command injection flaws were found in the way the setroubleshoot executed external commands. A local attacker able to trigger certain SELinux denials could use these flaws to execute arbitrary code with root privileges. It was discovered xmlsec1's use of libxml2 inadvertently enabled external entity expansion (XXE) along with validation. An attacker could craft an XML file that would cause xmlsec1 to try and read local files or HTTP/FTP URLs, leading to information disclosure or denial of service. It was found that the JMX endpoint of Red Hat JBoss EAP 5 deserializes the credentials passed to it. An attacker could use this flaw to cause a denial of service. It was found that the reason argument in ServerResponse#writeHead() was not properly validated. A remote attacker could possibly use this flaw to conduct an HTTP response splitting attack via a specially-crafted HTTP request. A vulnerability was found in libarchive. A specially crafted cpio archive containing a symbolic link to a ridiculously large target path can cause memory allocation to fail, resulting in any attempt to view or extract the archive crashing. A vulnerability was discovered in Python, in the built-in zipimporter. A specially crafted zip file placed in a module path such that it would be loaded by a later "import" statement could cause a heap overflow, leading to arbitrary code execution. It was found that the Python's httplib library (used by urllib, urllib2 and others) did not properly check HTTPConnection.putheader() function arguments. An attacker could use this flaw to inject additional headers in a Python application that allowed user provided header names or values. An information disclosure flaw was found in 389 Directory Server. A user with no access to objects in certain LDAP sub-tree could send LDAP ADD operations with a specific object name. The error message returned to the user was different based on whether the target object existed or not. Multiple buffer handling flaws were found in the way NSS handled cryptographic data from the network. A remote attacker could use these flaws to crash an application using NSS or, possibly, execute arbitrary code with the permission of the user running the application. It was found that JBoss EAP 7 Header Cache was inefficient. An attacker could use this flaw to cause a denial of service attack. A vulnerability was found in libarchive. A specially crafted RAR file could cause the application dereference a NULL pointer, leading to a crash. A vulnerability was found in libarchive. A specially crafted CAB file could cause the application dereference a NULL pointer, leading to a crash. A vulnerability was found in libarchive. A specially crafted LZA/LZH file could cause a small out-of-bounds read, potentially disclosing a few bytes of application memory. A vulnerability was found in libarchive. A specially crafted AR archive could cause the application to read a single byte of application memory, potentially disclosing it to the attacker. A vulnerability was found in libarchive. A specially crafted 7Z file could trigger a NULL pointer dereference, causing the application to crash. A vulnerability was found in libarchive. A specially crafted TAR file could trigger an out-of-bounds read, potentially causing the application to disclose a small amount of application memory. A vulnerability was found in libarchive. A specially crafted MTREE file could cause a small out-of-bounds read, potentially disclosing a small amount of application memory. A vulnerability was found in libarchive. A specially crafted RAR file could cause the application to disclose a 128k block of memory from an uncontrolled location. A vulnerability was found in libarchive. A specially crafted MTREE file could cause a limited out-of-bounds read, potentially disclosing contents of application memory. A vulnerability was found in libarchive's handling of 7zip data. A specially crafted 7zip file can cause a integer overflow resulting in memory corruption that can lead to code execution. An exploitable stack based buffer overflow vulnerability exists in the mtree parse_device functionality of libarchive. A specially crafted mtree file can cause a buffer overflow resulting in memory corruption and potential code execution in the context of the application. A vulnerability was found in libarchive's handling of RAR archives. A specially crafted RAR file can cause a heap overflow, potentially leading to code execution in the context of the application. It was reported that EAP 7 Application Server/Undertow web server is vulnerable to the injection of arbitrary HTTP headers, and also response splitting, due to insufficient sanitization and validation of user input before the input is used as part of an HTTP header value. Multiple use-after-free vulnerabilities were found in GIMP in the channel and layer properties parsing process when loading XCF files. An attacker could create a specially crafted XCF file which could cause GIMP to crash. A vulnerability was found in libarchive. A specially crafted TAR file could cause the application to leak small amounts of memory, eventually leading to denial of service. A vulnerability was found in libarchive. A specially crafted mtree file could cause libarchive to read beyond a statically declared structure, potentially disclosing application memory. A vulnerability was found in libarchive. A specially crafted ZIP file could cause a few bytes of application memory in a 256-byte region to be disclosed. Undefined behavior (signed integer overflow) was discovered in libarchive, in the MTREE parser's calculation of maximum and minimum dates. A crafted mtree file could potentially cause denial of service. Undefined behavior (invalid left shift) was discovered in libarchive, in how Compress streams are identified. This could cause certain files to be mistakenly identified as Compress archives and fail to read. A stack exhaustion flaw was found in the way Xerces-C XML parser handled deeply nested DTDs. An attacker could potentially use this flaw to crash an application using Xerces-C by tricking it into processing specially crafted data. The header() PHP function allowed header stings containing line break followed by a space or tab, as allowed by RFC 2616. Certain browsers handled the continuation line as new header, making it possible to conduct a HTTP response splitting attack against such browsers. The header() function was updated to follow RFC 7230 and not allow any line breaks. A flaw was found in foreman's handling of template previews. An attacker with permissions to preview host templates can access the template preview for any host if they are able to guess the host name, disclosing potentially sensitive information. A flaw was found in discovery-debug in foreman. An attacker, with permissions to view the debug results, would be able to view the root password associated with that system, potentially allowing them to access it. An infinite recursion flaw was found in the gdImageFillToBorder() function from the gd library; also used by PHP imagefilltoborder() function, when passing a negative integer as the color parameter, triggering a stack overflow. A remote attacker with ability to force a negative color identifier when calling the function could crash the PHP application, causing a Denial of Service. A vulnerability was found in libarchive. A specially crafted ISO file could cause the application to consume resources until it hit a memory limit, leading to a crash or denial of service. A vulnerability was found in libarchive. A specially crafted RAR file could cause the application to read memory beyond the end of the decompression buffer. A denial of service vulnerability was identified in Commons FileUpload that occurred when the length of the multipart boundary was just below the size of the buffer (4096 bytes) used to read the uploaded file if the boundary was the typical tens of bytes long. A flaw was discovered in processing setsockopt for 32 bit processes on 64 bit systems. This flaw will allow attackers to alter arbitrary kernel memory when unloading a kernel module. This action is usually restricted to root-privileged users but can also be leveraged if the kernel is compiled with CONFIG_USER_NS and CONFIG_NET_NS and the user is granted elevated privileges. It was found that an attacker who could control the content of an RSS feed could execute code remotely using the Nagios web interface. This flaw could be used to gain access to the remote system and in some scenarios control over the system. An out-of-bounds heap memory access leading to a Denial of Service, heap disclosure, or further impact was found in setsockopt(). The function call is normally restricted to root, however some processes with cap_sys_admin may also be able to trigger this flaw in privileged container environments. A security flaw was found in the way Dashbuilder performed SQL datasets lookup requests in the Data Set Authoring UI or the Displayer editor UI. A remote attacker could use this flaw to conduct SQL injection attacks via specially-crafted string filter parameter. Undefined behavior (signed integer overflow) was discovered in libarchive, in the ISO parser. A crafted file could potentially cause denial of service. A vulnerability in the handling of Transactional Memory on powerpc systems was found. An unprivileged local user can crash the kernel by starting a transaction, suspending it, and then calling any of the exec() class system calls. A heap-based buffer overflow vulnerability was found in the Linux kernel's hiddev driver. This flaw could allow a local attacker to corrupt kernel memory, possible privilege escalation or crashing the system. Race condition vulnerability was found in drivers/misc/mic/vop/vop_vringh.c in the MIC VOP driver in the Linux kernel before 4.6.1. MIC VOP driver does two successive reads from user space to read a variable length data structure. Local user can obtain sensitive information from kernel memory or can cause DoS by corrupting kernel memory if the data structure changes between the two reads. It was found that nfsd is missing permissions check when setting ACL on files, this may allow a local users to gain access to any file by setting a crafted ACL. Algorithms not compatible with mcryptd could be spawned by mcryptd with a direct crypto_alloc_tfm invocation using a "mcryptd(alg)" name construct. This causes mcryptd to crash the kernel if an arbitrary "alg" is incompatible and not intended to be used with mcryptd. Multiple flaws were found in the way the MySQL init script handled initialization of the database data directory and permission setting on the error log file. The mysql operating system user could use these flaws to escalate their privileges to root. An integer overflow flaw, leading to a heap-based buffer overflow was found in the imagecreatefromgd2() function of PHP's gd extension. A remote attacker could use this flaw to crash a PHP application or execute arbitrary code with the privileges of the user running that PHP application using gd via a specially crafted GD2 image. An integer overflow flaw, leading to a heap-based buffer overflow was found in the gdImagePaletteToTrueColor() function of PHP's gd extension. A remote attacker could use this flaw to crash a PHP application or execute arbitrary code with the privileges of the user running that PHP application using gd via a specially crafted image buffer. A double free flaw was found in the mb_ereg_replace_callback() function of php which is used to perform regex search. This flaw could possibly cause a PHP application to crash. A type confusion issue was found in the SPLFileObject fread() function. A remote attacker able to submit a specially crafted input to a PHP application, which uses this function, could use this flaw to execute arbitrary code with the privileges of the user running that PHP application. A use-after-free vulnerability was found in the Rich Text Format (RTF) document format parser in LibreOffice. By tricking a user into opening a specially crafted RTF document, an attacker could possibly use this flaw to execute arbitrary code with the privileges of the user opening the file. A flaw was found in the way handle_command() function would validate prefix value from user. An authenticated attacker could send a specially crafted prefix value resulting in ceph monitor crash. It was found that setting a VNC password to an empty string in libvirt did not disable all access to the VNC server as documented, instead it allowed access with no authentication required. An attacker could use this flaw to access a VNC server with an empty VNC password without any authentication. It was found that libgd did not properly handle invalid color indexes in GD files. An attacker who could submit a crafted GD file for conversion could cause applications using libgd to crash, leading to denial of service. An arbitrary command execution flaw was found in the way Go's "go get" command handled gcc and clang sensitive options during the build. A remote attacker capable of hosting malicious repositories could potentially use this flaw to cause arbitrary command execution on the client side. A flaw was found in the way Samba initiated signed DCE/RPC connections. A man-in-the-middle attacker could use this flaw to downgrade the connection to not use signing and therefore impersonate the server. The tty_set_termios_ldisc() function in 'drivers/tty/tty_ldisc.c' in the Linux kernel before 4.5 allows local users to obtain sensitive information from kernel memory by reading a tty data structure. A flaw was found in the way httpd performed client authentication using X.509 client certificates. When the HTTP/2 protocol was enabled, a remote attacker could use this flaw to access resources protected by certificate authentication without providing a valid client certificate. It was found that util-linux's libblkid library did not properly handle Extended Boot Record (EBR) partitions when reading MS-DOS partition tables. An attacker with physical USB access to a protected machine could insert a storage device with a specially crafted partition table that could, for example, trigger an infinite loop in systemd-udevd, resulting in a denial of service on that machine. A timing flaw was found in the Chrome EC driver in the Linux kernel. An attacker could abuse timing to skip validation checks to copy additional data from userspace possibly increasing privilege or crashing the system. When creating audit records for parameters to executed children processes, an attacker can convince the Linux kernel audit subsystem can create corrupt records which may allow an attacker to misrepresent or evade logging of executing commands. An out-of-bounds read flaw was found in gd. A maliciously crafted .gd2 file when converted to .gif could result in information disclosure from the process linking libgd. It was found that bind does not implement reasonable restrictions for zone sizes. This allows an explicitly configured primary DNS server for a zone to crash a secondary DNS server, affecting service of other zones hosted on the same secondary server. It was found that the CloudForms web UI did not properly filter input in certain fields. A remote, authenticated attacker could use this flaw to execute arbitrary code on the system running CloudForms. It was found that Exim leaked DKIM signing private keys to the "mainlog" log file. As a result, an attacker with access to system log files could potentially access these leaked DKIM private keys. It was found that cache files were insufficiently validated in fontconfig. A local attacker could create a specially crafted cache file to trigger arbitrary free() calls, which in turn could lead to arbitrary code execution. Race condition in the environ_read() function in 'fs/proc/base.c' in the Linux kernel before 4.5.4 allows local users to obtain sensitive information from kernel memory by reading a '/proc/*/environ' file during a process-setup time interval in which environment-variable copying is incomplete. A flaw was found where a volume fails to detach, which causes the delete operation to fail with 'VolumeInUse' error. Since the delete operation is retried every 30 seconds for each volume, this could lead to a denial of service attack as the number of API requests being sent to the cloud-provider exceeds the API's rate-limit. It was found that differences in the strictness of Spring Security, and Spring Framework request mapping could lead to resources not being secured. An attacker could use this flaw to bypass authentication. A vulnerability leading to a local privilege escalation was found in apparmor in the Linux kernel. When proc_pid_attr_write() was changed to use memdup_user apparmor's (interface violating) assumption that the setprocattr buffer was always a single page was violated. It was discovered that PHP did not properly protect against the HTTP_PROXY variable name clash. A remote attacker could possibly use this flaw to redirect HTTP requests performed by a PHP script to an attacker-controlled proxy via a malicious HTTP request. An input-validation flaw was discovered in the Go programming language built in CGI implementation, which set the environment variable "HTTP_PROXY" using the incoming "Proxy" HTTP-request header. The environment variable "HTTP_PROXY" is used by numerous web clients, including Go's net/http package, to specify a proxy server to use for HTTP and, in some cases, HTTPS requests. This meant that when a CGI-based web application ran, an attacker could specify a proxy server which the application then used for subsequent outgoing requests, allowing a man-in-the-middle attack. It was discovered that httpd used the value of the Proxy header from HTTP requests to initialize the HTTP_PROXY environment variable for CGI scripts, which in turn was incorrectly used by certain HTTP client implementations to configure the proxy for outgoing HTTP requests. A remote attacker could possibly use this flaw to redirect HTTP requests performed by a CGI script to an attacker-controlled proxy via a malicious HTTP request. It was discovered that tomcat used the value of the Proxy header from HTTP requests to initialize the HTTP_PROXY environment variable for CGI scripts, which in turn was incorrectly used by certain HTTP client implementations to configure the proxy for outgoing HTTP requests. A remote attacker could possibly use this flaw to redirect HTTP requests performed by a CGI script to an attacker-controlled proxy via a malicious HTTP request. It was found that the unlink and rename functionality in overlayfs did not verify the upper dentry for staleness. A local, unprivileged user could use the rename syscall on overlayfs on top of xfs to panic or crash the system. A flaw was found that the vfs_rename() function did not detect hard links on overlayfs. A local, unprivileged user could use the rename syscall on overlayfs on top of xfs to crash the system. A cross-site scripting (XSS) flaw was found in Django. An attacker could exploit the unsafe usage of JavaScript's Element.innerHTML to forge content in the admin's add/change related pop-up. Element.textContent is now used to prevent XSS data execution. It was found that the RFC 5961 challenge ACK rate limiting as implemented in the Linux kernel's networking subsystem allowed an off-path attacker to leak certain information about a given connection by creating congestion on the global challenge ACK rate limit counter and then measuring the changes by probing packets. An off-path attacker could use this flaw to either terminate TCP connection and/or inject payload into non-secured TCP connection between two endpoints on the network. It was found that perl can load modules from the current directory if not found in the module directories, via the @INC path. A local, authenticated attacker could create a specially crafted module in a writable directory and trick a user into running a perl program from that directory; if the module is not found in previous @INC paths, it will load and execute the attacker's module. A regular expression denial of service flaw was found in Minimatch. An attacker able to make an application using Minimatch to perform matching using a specially crafted glob pattern could cause the application to consume an excessive amount of CPU. A regular expression denial of service flaw was found in Negotiator. An attacker able to make an application using Negotiator to perform matching using a specially crafted glob pattern could cause the application to consume an excessive amount of CPU. The Kubernetes API server contains a watch cache that speeds up performance. Due to an input validation error OpenShift Enterprise may return data for other users and projects when queried by a user. An attacker with knowledge of other project names could use this vulnerability to view their information. A user supplied GET parameter is used to create the value used as the src value of an iframe displayed on all pages. It allows for CSRF and javascript insertion techniques among others. An attacker could forge a malicious URL that could include javascript execution in the main browser frame context, force the target to view a malicious web page (client side) or take advantage of concurrent cookies / sessions and perform a CSRF attack against other openstack components such as horizon. It was found that in Linux kernel the mount table expands by a power-of-two with each bind mount command. If a system is configured to allow non-privileged user to do bind mounts, or allows to do so in a container or unprivileged mount namespace, then non-privileged user is able to cause a local DoS by overflowing the mount table, which causes a deadlock for the whole system. It was discovered that the Python CGIHandler class did not properly protect against the HTTP_PROXY variable name clash in a CGI context. A remote attacker could possibly use this flaw to redirect HTTP requests performed by a Python CGI script to an attacker-controlled proxy via a malicious HTTP request. It was discovered that python-twisted-web used the value of the Proxy header from HTTP requests to initialize the HTTP_PROXY environment variable for CGI scripts, which in turn was incorrectly used by certain HTTP client implementations to configure the proxy for outgoing HTTP requests. A remote attacker could possibly use this flaw to redirect HTTP requests performed by a CGI script to an attacker-controlled proxy via a malicious HTTP request. A covert timing channel flaw was found in the way OpenSSH handled authentication of non-existent users. A remote unauthenticated attacker could possibly use this flaw to determine valid user names by measuring the timing of server responses. It was found that the lightweight resolver protocol implementation in BIND could enter an infinite recursion and crash when asked to resolve a query name which, when combined with a search list entry, exceeds the maximum allowable length. A remote attacker could use this flaw to crash lwresd or named when using the "lwres" statement in named.conf. A code injection flaw was found in the way capacity and utilization imported control files are processed. A remote, authenticated attacker with access to the capacity and utilization feature could use this flaw to execute arbitrary code as the user CFME runs as. The hid_input_field() function in 'drivers/hid/hid-core.c' in the Linux kernel before 4.6 allows physically proximate attackers to obtain sensitive information from kernel memory or cause a denial of service (out-of-bounds read) by connecting a device. Linux kernel built with the KVM visualization support (CONFIG_KVM), with nested visualization(nVMX) feature enabled(nested=1), is vulnerable to an uncaught exception issue. It could occur if an L2 guest was to throw an exception which is not handled by an L1 guest. A flaw was found in the linux kernel's implementation of the airspy USB device driver in which a leak was found when a subdev or SDR are plugged into the host. An attacker can create an targeted USB device which can emulate 64 of these devices. Then by emulating an additional device which continuously connects and disconnects, each connection attempt will leak memory which can not be recovered. It was found that squid did not properly remove connection specific headers when answering conditional requests using a cached request. A remote attacker could send a specially crafted request to an HTTP server via the squid proxy and steal private data from other connections. Quick Emulator (QEMU) built with the virtio framework is vulnerable to an unbounded memory allocation issue. It was found that a malicious guest user could submit more requests than the virtqueue size permits. Processing a request allocates a VirtQueueElement results in unbounded memory allocation on the host controlled by the guest. A flaw was found in the way certain error conditions were handled by bzread() function in PHP. An attacker could use this flaw to upload a specially crafted bz2 archive which, when parsed via the vulnerable function, could cause the application to crash or execute arbitrary code with the permissions of the user running the PHP application. An insufficient permission check issue was found in the way IPA server treats certificate revocation requests. An attacker logged in with the 'retrieve certificate' permission enabled could use this flaw to revoke certificates, possibly triggering a denial of service attack. A security flaw was found in the way Business Process Editor displays the business process details to the user. A remote authenticated attacker with privilege to create business processes could use this flaw to conduct stored XSS attacks against other users. A vulnerability was found Xen's MMU emulation for x86 PV guests. A malicious administrator of an x86 PV guest could control some of the page table bits, allowing potential control of memory and code execution in the host. x86 HVM and ARM guests could not exploit this flaw. A vulnerability was found in libarchive. An attempt to create an ISO9660 volume with 2GB or 4GB filenames could cause the application to crash. It was found that 389 Directory Server was vulnerable to a remote password disclosure via timing attack. A remote attacker could possibly use this flaw to retrieve directory server password after many tries. The domain controller will not propagate its administrative RBAC configuration to some slaves. An attacker could use this to escalate their privileges. It was found that the fix for CVE-2016-4051 released via RHSA-2016:1138 did not properly prevent the stack overflow in the munge_other_line() function. A remote attacker could send specially crafted data to the Squid proxy, which would exploit the cachemgr CGI utility, possibly triggering execution of arbitrary code. An out of bounds read flaw was found in the way OpenSSL formatted Public Key Infrastructure Time-Stamp Protocol data for printing. An attacker could possibly cause an application using OpenSSL to crash if it printed time stamp data from the attacker. A flaw was found in the way firewalld allowed certain firewall configurations to be modified by unauthenticated users. Any locally logged in user could use this flaw to tamper or change firewall settings. A heap-based buffer overflow flaw was found in collectd's network plugin. The flaw allowed a remote attacker to crash the collectd daemon (denial of service) or possibly execute remote code using a crafted network packet. For this flaw to be exploited, the network plugin must be enabled. The assoc_array_insert_into_terminal_node() function in 'lib/assoc_array.c' in the Linux kernel before 4.5.3 does not check whether a slot is a leaf, which allows local users to obtain sensitive information from kernel memory or cause a denial of service (invalid pointer dereference and out-of-bounds read) via an application that uses associative-array data structures. A NULL pointer dereference flaw was found in MIT Kerberos krb5kdc service. An authenticated attacker could use this flaw to cause krb5kdc to dereference a null pointer and crash by making an S4U2Self request, if the restrict_anonymous_to_tgt option was set to true. It was found that ssh-agent could load PKCS#11 modules from arbitrary paths. An attacker having control of the forwarded agent-socket on the server, and the ability to write to the filesystem of the client host, could use this flaw to execute arbitrary code with the privileges of the user running ssh-agent. It was found that 389 Directory Server was vulnerable to a flaw in which the default ACI (Access Control Instructions) could be read by an anonymous user. This could lead to leakage of sensitive information. It was found that while parsing the SAML messages the StaxParserUtil class of Picketlink replaces special strings for obtaining attribute values with system property. This could allow an attacker to determine values of system properties at the attacked system by formatting the SAML request ID field to be the chosen system property which could be obtained in the "InResponseTo" field in the response. It was found that JBoss Operations Network allowed regular users to add a new super user by sending a specially crafted request to the web console. This attacks allows escalation of privileges. It was found that nettle's RSA and DSA decryption code was vulnerable to cache-related side channel attacks. An attacker could use this flaw to recover the private key from a co-located virtual-machine instance. It was found that the libcurl library did not prevent TLS session resumption when the client certificate had changed. An attacker could potentially use this flaw to hijack the authentication of the connection by leveraging a previously created connection with a different client certificate. It was found that the libcurl library did not check the client certificate when choosing the TLS connection to reuse. An attacker could potentially use this flaw to hijack the authentication of the connection by leveraging a previously created connection with a different client certificate. A race condition flaw was found in the ioctl_send_fib() function in the Linux kernel's aacraid implementation. A local attacker could use this flaw to cause a denial of service (out-of-bounds access or system crash) by changing a certain size value. It was discovered that the Tomcat packages installed configuration file /usr/lib/tmpfiles.d/tomcat.conf writeable to the tomcat group. A member of the group or a malicious web application deployed on Tomcat could use this flaw to escalate their privileges. A flaw was found in the way libarchive handled hardlink archive entries of non-zero size. Combined with flaws in libarchive's file system sandboxing, this issue could cause an application using libarchive to overwrite arbitrary files with arbitrary data from the archive. A permissions flaw was found in Redis, where redis-cli stores its history in ~/.rediscli_history. The file is created with permissions 0644, which could lead to the exposure of sensitive data for users with world-readable home directories. An integer overflow, leading to a heap buffer overflow, was found in openjpeg, also affecting the PDF viewer in Chromium. A specially crafted JPEG2000 image could cause an incorrect calculation when allocating precinct data structures, which could lead to a crash, or potentially, code execution. A flaw was found in the way PostgreSQL server handled certain SQL statements containing CASE/WHEN commands. A remote, authenticated attacker could use a specially crafted SQL statement to cause PostgreSQL to crash or disclose a few bytes of server memory or possibly execute arbitrary code. A flaw was found in the way PostgreSQL client programs handled database and role names containing newlines, carriage returns, double quotes, or backslashes. By crafting such an object name, roles with the CREATEDB or CREATEROLE option could escalate their privileges to superuser when a superuser next executes maintenance with a vulnerable client program. A denial of service vulnerability was found in subversion. The mod_dontdothat component of the mod_dav_svn Apache module did not properly protect against exponential XML entity expansion attacks. An attacker with credentials to the webdav repository could send a crafted message that would result in resource exhaustion and denial of service to httpd. It was found that when issuing a GET request which results in a 302 redirect and when the request header 'Host' field was not set, the response header field 'Location' contains the internal IP address of the server. An attacker could use this disclose information which they are not authorized to access. An input validation vulnerability was found in Ansible's handling of data sent from client systems. An attacker with control over a client system being managed by Ansible and the ability to send facts back to the Ansible server could use this flaw to execute arbitrary code on the Ansible server using the Ansible server privileges. It was found that OpenSSH did not limit password lengths for password authentication. A remote unauthenticated attacker could use this flaw to temporarily trigger high CPU consumption in sshd by sending long passwords. It was found that the Linux kernel's IPv6 implementation mishandled socket options. A local attacker could abuse concurrent access to the socket options to escalate their privileges, or cause a denial of service (use-after-free and system crash) via a crafted sendmsg system call. It was discovered that Action View tag helpers did not escape quotes when using strings declared as HTML safe as attribute values. A remote attacker could use this flaw to conduct a cross-site scripting (XSS) attack. A flaw was found in the way Active Record handled certain special values in dynamic finders and relations. If a Ruby on Rails application performed JSON parameter parsing, a remote attacker could possibly manipulate search conditions in SQL queries generated by the application. A cross-site scripting (XSS) flaw was found in the "Device Identifier" field of the new host provisioning components of Red Hat Satellite. A user able to create a new host could exploit this flaw to perform XSS attacks against other Satellite users. It was found that foreman is vulnerable to a stored XSS via a job template with a malformed name. This could allow an attacker with privileges to set the name in a template to display arbitrary HTML including scripting code within the web interface. A design flaw was found in the libgcrypt PRNG (Pseudo-Random Number Generator). An attacker able to obtain the first 580 bytes of the PRNG output could predict the following 20 bytes. An out of bounds write flaw was discovered in the OpenSSL BN_bn2dec() function. An attacker able to make an application using OpenSSL to process a large BIGNUM could cause the application to crash or, possibly, execute arbitrary code. It was discovered that the Tomcat packages installed certain configuration files read by the Tomcat initialization script as writeable to the tomcat group. A member of the group or a malicious web application deployed on Tomcat could use this flaw to escalate their privileges. A use-after-free vulnerability was found in tcp_xmit_retransmit_queue and other tcp_* functions. This condition could allow an attacker to send an incorrect selective acknowledgment to existing connections, possibly resetting a connection. System using the infiniband support module ib_srpt were vulnerable to a denial of service by system crash by a local attacker who is able to abort writes to a device using this initiator. Quick Emulator (QEMU) built with the VMWARE VMXNET3 NIC device support is vulnerable to an information leakage issue. The vulnerability could occur while processing the transmit(tx) queue when it reaches the end of a packet. A privileged user inside guest could use this vulnerability to leak host memory bytes to a guest. It was found that the host private key material could possibly leak to the privilege-separated child processes via re-allocated memory. An attacker able to compromise the privilege-separated process could therefore obtain the leaked key information. A flaw was found in the Datagram TLS (DTLS) replay protection implementation in OpenSSL. A remote attacker could possibly use this flaw to make a DTLS server using OpenSSL to reject further packets sent from a DTLS client over an established DTLS connection. It was discovered that the ovirt-engine webadmin session would not properly enforce timeouts. Browser sessions would remain logged in beyond the administratively configured session timeout period. It was discovered that the mysqld_safe script honored the ledir option value set in a MySQL configuration file. A user able to modify one of the MySQL configuration files could use this flaw to escalate their privileges to root. Linux kernel built with the Kernel-based Virtual Machine (CONFIG_KVM) support was vulnerable to an incorrect segment selector(SS) value error. The error could occur while loading values into the SS register in long mode. A user or process inside a guest could use this flaw to crash the guest, resulting in DoS or potentially escalate their privileges inside the guest. A flaw was found in the way the DES/3DES cipher was used as part of the TLS/SSL protocol. A man-in-the-middle attacker could use this flaw to recover some plaintext data by capturing large amounts of encrypted traffic between TLS/SSL server and client if the communication used a DES/3DES based ciphersuite. It was discovered that the Datagram TLS (DTLS) implementation could fail to release memory in certain cases. A malicious DTLS client could cause a DTLS server using OpenSSL to consume an excessive amount of memory and, possibly, exit unexpectedly after exhausting all available memory. An integer underflow flaw leading to a buffer over-read was found in the way OpenSSL parsed TLS session tickets. A remote attacker could use this flaw to crash a TLS server using OpenSSL if it used SHA-512 as HMAC for session tickets. It was discovered that the default sudo configuration preserved the value of INPUTRC from the user's environment, which could lead to information disclosure. A local user with sudo access to a restricted program that uses readline could use this flaw to read content from specially formatted files with elevated privileges provided by sudo. A design flaw was found in the file extended attribute handling of the Linux kernel's handling of cached attributes. Too many entries in the cache cause a soft lockup while attempting to iterate the cache and access relevant locks. A flaw was found in the Linux kernel's implementation of overlayfs. An attacker can leak file resources in the system by opening a large file with write permissions on a overlay filesystem that is insufficient to deal with the size of the write. When unmounting the underlying device, the system is unable to free an inode and this will consume resources. Repeating this for all available inodes and memory will create a denial of service situation. It was found that a parameter of the dialog box feature of jQuery UI was vulnerable to cross site scripting. An attacker could use this flaw to execute a malicious script via the dialog box when it was displayed to a user. It was found that when file permissions were modified via chmod and the user modifying them was not in the owning group or capable of CAP_FSETID, the setgid bit would be cleared. Setting a POSIX ACL via setxattr sets the file permissions as well as the new ACL, but doesn't clear the setgid bit in a similar way. This could allow a local user to gain group privileges via certain setgid applications. It was found that the ovirt-engine-provisiondb utility did not correctly sanitize the authentication details used with the “—provision*db” options from the output before storing them in log files. This could allow an attacker with read access to these log files to obtain sensitive information such as passwords. JBoss BPM Suite 6 is vulnerable to a reflected XSS via dashbuilder. Remote attackers can entice authenticated users that have privileges to access dashbuilder (usually admins) to click on links to /dashbuilder/Controller containing malicious scripts. Successful exploitation would allow execution of script code within the context of the affected user. It was discovered that JBoss BRMS 6 and BPM Suite 6 are not setting HttpOnly flags on sensitive cookies. Remote attackers can access these cookies by using client-side scripts, usually through XSS. It was discovered that the default IdM password policies that lock out accounts after a certain number of failed login attempts were also applied to host and service accounts. A remote unauthenticated user could use this flaw to cause a denial of service attack against kerberized services. It was found that there was insufficient use of randam values in RESTEasy async jobs. An attacker could use this flaw to steal user data. It was found that GZIPInterceptor is enabled when not necessarily required in RESTEasy. An attacker could use this flaw to launch a Denial of Service attack. It was found that the default exception handler in RESTEasy did not properly validate user input. An attacker could use this flaw to launch a relected XSS attack. It was found that in some configurations the JacksonJsonpInterceptor is activated by default in RESTEasy. An attacker could use this flaw to launch a Cross Site Scripting Inclusion attack. An integer overflow, leading to a heap buffer overflow, was found in openjpeg, also affecting the PDF viewer in Chromium. A specially crafted JPEG2000 image could cause incorrect calculations when allocating various data structures, which could lead to a crash, or potentially, code execution. An integer overflow, leading to a heap buffer overflow, was found in openjpeg, also affecting the PDF viewer in Chromium. A specially crafted JPEG2000 image could cause an incorrect calculation when allocating memory for code blocks, which could lead to a crash, or potentially, code execution. A flaw was found in Ceph RGW code which allows an anonymous user to list contents of RGW bucket by bypassing ACL which should only allow authenticated users to list contents of bucket. It was discovered that the sudo noexec restriction could have been bypassed if application run via sudo executed system() or popen() C library functions with a user supplied argument. A local user permitted to run such application via sudo with noexec restriction could use this flaw to execute arbitrary commands with elevated privileges. It was found that the boundary checks in the code implementing support for pre-authentication compression could have been optimized out by certain compilers. An attacker able to compromise the privilege-separated process could possibly use this flaw for further attacks against the privileged monitor process. JBoss BRMS 6 and BPM Suite 6 are vulnerable to a stored XSS via dashbuilder. Remote, authenticated attackers that have privileges to access dashbuilder (usually admins) can store scripts in several editable fields, which are not properly sanitized before showing to other users, including other admins. It has been reported that CSRF tokens are not properly handled in JBoss BPM suite dashbuilder. Old tokens generated during an active session can be used to bypass CSRF protection. In addition, the tokens are sent in query string so they can be exposed through the browser's history, referrers, web logs, and other sources. Attackers may be able to obtain old tokens from various sources in the network and perform CSRF attacks successfully. It was found that the libcurl library using the NSS (Network Security Services) library as TLS/SSL backend incorrectly re-used client certificates for subsequent TLS connections in certain cases. An attacker could potentially use this flaw to hijack the authentication of the connection by leveraging a previously created connection with a different client certificate. An authorization flaw was found in Pacemaker, where it did not properly guard its IPC interface. An attacker with an unprivileged account on a Pacemaker node could use this flaw to, for example, force the Local Resource Manager daemon to execute a script as root and thereby gain root access on the machine. It was discovered that shotwell did not validate TLS certificates when publishing photos to online service. A man-in-the-middle attacker could intercept requests and provide crafted responses, obtaining users' photos and potentially sensitive data. A path traversal flaw was found in file-roller. If a user were tricked into opening a specially crafted archive and clicking on a symbolic link, file deletion could occur. An integer overflow, leading to a heap buffer overflow, was found in OpenJPEG. An attacker could create a crafted JPEG2000 image that, when loaded by an application using openjpeg, could lead to a crash or, potentially, code execution. A vulnerability was found in libarchive. A specially crafted gzip file can cause libarchive to allocate memory without limit, eventually leading to a crash. An off-by-one error leading to a crash was discovered in openldap's processing of DNS SRV messages. If slapd was configured to use the dnssrv backend, an attacker could crash the service with crafted DNS responses. Quick Emulator (QEMU) built with the VMware-SVGA chipset emulation support is vulnerable to an OOB stack memory write issue. It could occur while processing VGA commands in 'vmsvga_fifo_run' routine. A privileged user inside guest could use this flaw to crash the QEMU process resulting in DoS. A flaw was found in Kibana's logging functionality. If custom logging output was configured in Kibana, private user data could be written to the Kibana log files. A system attacker could use this data to hijack sessions of other users when using Kibana behind some form of authentication such as Shield. A cross-site scripting (XSS) flaw was found in Kibana. A remote attacker could use this flaw to inject arbitrary web script into pages served to other users. An input validation flaw was found in the way CloudForms regular expressions were passed to the expression engine via both the JSON API and the web based UI. A user with the ability to view collections and filter them could use this flaw to execute arbitrary shell commands on the host with the privileges of the CloudForms process. A cross-site scripting flaw was discovered in openstack-manila-ui's Metadata field contained in its "Create Share" form. A user could inject malicious HTML/JavaScript code that would then be reflected in the "Shares" overview. Remote, authenticated, but unprivileged users could exploit this vulnerability to steal session cookies and escalate their privileges. It was discovered that the MySQL logging functionality allowed writing to MySQL configuration files. An administrative database user, or a database user with FILE privileges, could possibly use this flaw to run arbitrary commands with root privileges on the system running the database server. An out of bounds read flaw related to "graphite2::Pass::readPass" has been reported in graphite2. An attacker could possibly exploit this flaw to disclose potentially sensitive memory or cause an application crash. Drools Workbench contains the path traversal vulnerability. The vulnerability allows a remote, authenticated attacker to bypass the directory restrictions and retrieve arbitrary files from the affected host. Multiple integer overflow flaws leading to heap-based buffer overflows were found in the way curl handled escaping and unescaping of data. An attacker could potentially use these flaws to crash an application using libcurl by sending a specially crafted input to the affected libcurl functions. A vulnerability was discovered in JSch that allows a malicious sftp server to force a client-side relative path traversal in jsch's implementation for recursive sftp-get. An attacker could leverage this to write files outside the client's download basedir with effective permissions of the jsch sftp client process. It was found that when the gcc stack protector was enabled, reading the /proc/keys file could cause a panic in the Linux kernel due to stack corruption. This happened because an incorrect buffer size was used to hold a 64-bit timeout value rendered as weeks. Linux kernel built with the 802.1Q/802.1ad VLAN(CONFIG_VLAN_8021Q) OR Virtual eXtensible Local Area Network(CONFIG_VXLAN) with Transparent Ethernet Bridging(TEB) GRO support, is vulnerable to a stack overflow issue. It could occur while receiving large packets via GRO path, as an unlimited recursion could unfold in both VLAN and TEB modules, leading to a stack corruption in the kernel. It was found that Apache was vulnerable to a HTTP response splitting attack for sites which use mod_userdir. An attacker could use this flaw to inject CRLF characters into the HTTP header and could possibly gain access to secure data. It was found that docker-distribution did not properly restrict memory allocation size for a registry instance through the manifest endpoint. An attacker could send a specially crafted request that would exhaust the memory of the docker-distribution service. It was discovered that a long URL sent to EAP 7 Server operating as a reverse proxy with default buffer sizes causes a Denial of Service. It was reported that the Tomcat init script performed unsafe file handling, which could result in local privilege escalation. A flaw was found in the CloudForms API. A user with permissions to use the MiqReportResults capability within the API could potentially view data from other tenants or groups to which they should not have access. A flaw was found in the Quick Emulator(QEMU) built with LSI SAS1068 Host Bus emulation support, where it is vulnerable to an invalid memory-access issue. The flaw could occur while processing SCSI IO requests in the mptsas_process_scsi_io_request routine. A privileged user inside the guest could use this flaw to crash the QEMU-process instance on the host (denial of service). A flaw was found in the way GnuTLS validated certificates using OCSP responses. This could falsely report a certificate as valid under certain circumstances. A heap-buffer overflow vulnerability was found in the arcmsr_iop_message_xfer() function in 'drivers/scsi/arcmsr/arcmsr_hba.c' file in the Linux kernel through 4.8.2. The function does not restrict a certain length field, which allows local users to gain privileges or cause a denial of service via an ARCMSR_MESSAGE_WRITE_WQBUFFER control code. This can potentially cause kernel heap corruption and arbitrary kernel code execution. A CSRF flaw was found in Django, where an interaction between Google Analytics and Django's cookie parsing could allow an attacker to set arbitrary cookies leading to a bypass of CSRF protection. In this update, the parser for ''request.COOKIES'' has been simplified to better match browser behavior and to mitigate this attack. ''request.COOKIES'' may now contain cookies that are invalid according to RFC 6265 but are possible to set using ''document.cookie''. A regular expression denial of service flaw was found in Tough-Cookie. An attacker able to make an application using Touch-Cookie to parse an HTTP header with many semicolons could cause the application to consume an excessive amount of CPU. It was found that swagger-ui contains a cross site scripting (XSS) vulnerability in the key names in the JSON document. An attacker could use this flaw to supply a key name with script tags which could cause arbitrary code execution. Additionally it is possible to load the arbitrary JSON files remotely via the URL query-string parameter. Multiple out of bounds read flaws were found in the way OpenSSL handled certain TLS/SSL protocol handshake messages. A remote attacker could possibly use these flaws to crash a TLS/SSL server or client using OpenSSL. A memory leak flaw was found in the way OpenSSL handled TLS status request extension data during session renegotiation. A remote attacker could cause a TLS server using OpenSSL to consume an excessive amount of memory and, possibly, exit unexpectedly after exhausting all available memory, if it enabled OCSP stapling support. An arbitrary command injection flaw was found in the way bash processed the hostname value. A malicious DHCP server could use this flaw to execute arbitrary commands on the DHCP client machines running bash under specific circumstances. A memory-leak flaw was found in the Quick Emulator(QEMU) built with USB xHCI controller emulation support. The flaw could occur while doing a USB-device unplug operation. Unplugging the device repeatedly resulted in leaking host memory, which affected other services on the host. A privileged user inside the guest could exploit this flaw to cause a denial of service on the host or potentially crash the host's QEMU process instance. It was found that a flaw in Apache groovy library allows remote code execution wherever deserialization occurs in the application. It is possible for an attacker to craft a special serialized object that will execute code directly when deserialized. All applications which rely on serialization and do not isolate the code which deserializes objects are subject to this vulnerability. A heap-based buffer overflow flaw related to "lz4::decompress" has been reported in graphite2. An attacker could exploit this issue to cause a crash or, possibly, execute arbitrary code. A denial of service flaw was found in the way BIND constructed a response to a query that met certain criteria. A remote attacker could use this flaw to make named exit unexpectedly with an assertion failure via a specially crafted DNS request packet. It was discovered that under certain conditions RESTEasy could be forced to parse a request with SerializableProvider, resulting in deserialization of potentially untrusted data. An attacker could possibly use this flaw execute arbitrary code with the permissions of the application using RESTEasy. A race condition was found in the way MySQL performed MyISAM engine table repair. A database user with shell access to the server running mysqld could use this flaw to change permissions of arbitrary files writable by the mysql system user. It was found that use of a JMS ObjectMessage does not safely handle user supplied data when deserializing objects. A remote attacker could use this flaw to execute arbitrary code with the permissions of the application using a JMS ObjectMessage. It was found that the sandbox tool provided in policycoreutils was vulnerable to a TIOCSTI ioctl attack. A specially crafted program executed via the sandbox command could use this flaw to execute arbitrary commands in the context of the parent shell, escaping the sandbox. An arbitrary command injection flaw was found in the way bash processed the SHELLOPTS and PS4 environment variables. A local, authenticated attacker could use this flaw to exploit poorly written setuid programs to elevate their privileges under certain circumstances. It was found that several password fields in QCI failed to properly mask the password while it was being entered. An attacker with physical access or the ability to view the screen would be able to see the passwords as they are being entered, allowing them to later access accounts and services protected by those passwords. An XML entity expansion vulnerability was found in python-pysaml2. A remote attacker could send a crafted request which would cause denial of service through resource exhaustion. It was discovered that a remote attacker could leverage the generation of IPv6 atomic fragments to trigger the use of fragmentation in an arbitrary IPv6 flow (in scenarios in which actual fragmentation of packets is not needed) and could subsequently perform any type of a fragmentation-based attack against legacy IPv6 nodes that do not implement RFC6946. drivers/hid/hid-corsair.c in the Linux kernel 4.9.x before 4.9.6 interacts incorrectly with the CONFIG_VMAP_STACK option which allows local users to cause a denial of service (system crash or memory corruption) or possibly have unspecified other impact by leveraging use of more than one virtual page for a DMA scatterlist. A vulnerability was found in the Linux kernel in 'tmpfs' file system. When file permissions are modified via 'chmod' and the user is not in the owning group or capable of CAP_FSETID, the setgid bit is cleared in inode_change_ok(). Setting a POSIX ACL via 'setxattr' sets the file permissions as well as the new ACL, but doesn't clear the setgid bit in a similar way; this allows to bypass the check in 'chmod'. It was found that the ghostscript functions getenv and filenameforall did not honor the -dSAFER option, usually used when processing untrusted documents, leading to information disclosure. A specially crafted postscript document could read environment variable and list directory respectively, from the target. An integer overflow flaw, leading to a heap-based buffer overflow, was found in gd. A specially crafted image, when converted to webp, could cause the application to crash or potentially execute arbitrary code. A vulnerability was found in c-ares. A hostname with an escaped trailing dot (such as "hello\.") would have its size calculated incorrectly, leading to a single byte written beyond the end of a buffer on the heap. An attacker able to provide such a hostname to an application using c-ares, could potentially cause that application to crash. A vulnerability was discovered in several OSPF implementations, including Quagga. A malicious OSPF peer, or an attacker able to spoof messages from an OSPF peer, could send a crafted message that would result in erasure or alteration of the routing table, resulting in denial of service or incorrect routing of traffic. A flaw was found in the way systemd handled empty notification messages. A local attacker could use this flaw to make systemd freeze its execution, preventing further management of system services, system shutdown, or zombie process collection via systemd. It was found that the connection between a pacemaker cluster and a pacemaker_remote node could be shut down using a new unauthenticated connection. A remote attacker could use this flaw to cause a denial of service. It was discovered that when configuring RBAC and marking information as sensitive, users with a Monitor role are able to view the sensitive information. A flaw was found in the way authentication details were passed between rhscon-ceph and rhscon-core. An authenticated, local attacker could use this flaw to recover the cleartext password. A flaw was found in the way systemd handled empty notification messages. A local attacker could use this flaw to make systemd freeze its execution, preventing further management of system services, system shutdown, or zombie process collection via systemd. A use-after-free vulnerability was found in the kernel's socket recvmmsg subsystem. This may allow remote attackers to corrupt memory and may allow execution of arbitrary code. This corruption takes place during the error handling routines within __sys_recvmmsg() function. It was found that ghostscript function .libfile did not honor the -dSAFER option, usually used when processing untrusted documents, leading to information disclosure. A specially crafted postscript document could, in the context of the gs process, retrieve file content on the target machine. It was found that the ghostscript function .setdevice suffered a use-after-free vulnerability due to an incorrect reference count. A specially crafted postscript document could trigger code execution in the context of the gs process. It was found that the ghostscript function .initialize_dsc_parser did not validate its parameter before using it, allowing a type confusion flaw. A specially crafted postscript document could cause a crash code execution in the context of the gs process. It was found that the length checks prior to writing to the target buffer for creating a virtual host mapping rule did not take account of the length of the virtual host name, creating the potential for a buffer overflow. A flaw was found in the Linux kernel which does not initialize certain data structures used by DMA transfer on ARM64 based systems. This could allow local users to obtain sensitive information from kernel memory by triggering a dma_mmap call and reconstructing the data. The rfcomm_sock_bind function in net/bluetooth/rfcomm/sock.c in the Linux kernel before 4.2 allows local users to obtain sensitive information or cause a denial of service (NULL pointer dereference) via vectors involving a bind system call on a Bluetooth RFCOMM socket. A heap-based buffer overflow flaw related to "lz4::decompress" (src/Decompressor) has been reported in graphite2. An attacker could exploit this issue to cause a crash or, possibly, execute arbitrary code. The nfnetlink_rcv_batch() function in 'net/netfilter/nfnetlink.c' in the Linux kernel before 4.5 does not check whether a batch message's length field is large enough, which allows local users to obtain sensitive information from kernel memory or cause a denial of service (infinite loop or out-of-bounds read) by leveraging the CAP_NET_ADMIN capability. A NULL pointer dereference flaw was found in the way NSS handled invalid Diffie-Hellman keys. A remote client could use this flaw to crash a TLS/SSL server using NSS. It was found that ghostscript did not sufficiently check the validity of parameters given to the .sethalftone5 function. A specially crafted postscript document could cause a crash, or execute arbitrary code in the context of the gs process. A vulnerability was found in guile, in the mkdir procedure's usage of umask(2). Under particular circumstances, an attacker could influence an application written in guile to create directories or files insecurely, potentially exposing them to being read or manipulated by local users. A vulnerability was found in guile's REPL server (--listen), making it vulnerable to HTTP inter-protocol attacks. A crafted website, when visited by a developer with an instance of the REPL server, could cause arbitrary code execution within the guile scheme interpreter. It was found that Kubernetes did not correctly validate X.509 client intermediate certificate host name fields. An attacker could use this flaw to bypass authentication requirements by using a specially crafted X.509 certificate. It was found that the CloudForms did not properly apply permissions controls to VM IDs passed by users. A remote, authenticated attacker could use this flaw to execute arbitrary VMs on systems managed by CloudForms if they know the ID of the VM. A race condition was found in the way the Linux kernel's memory subsystem handled the copy-on-write (COW) breakage of private read-only memory mappings. An unprivileged, local user could use this flaw to gain write access to otherwise read-only memory mappings and thus increase their privileges on the system. Stack-based buffer overflow in the brcmf_cfg80211_start_ap() function in 'drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c' in the Linux kernel before 4.7.5 allows local users to cause a denial of service (system crash) or possibly have unspecified other impact via a long SSID Information Element in a command to a Netlink socket. The XFS subsystem in the Linux kernel 4.4 and later allows local users to cause a denial of service (fdatasync() failure and system hang) by using the vfs syscall group in the 'trinity' program, as a result of a page lock order bug in the XFS seek hole/data implementation. It was discovered that the sudo noexec restriction could have been bypassed if application run via sudo executed wordexp() C library function with a user supplied argument. A local user permitted to run such application via sudo with noexec restriction could possibly use this flaw to execute arbitrary commands with elevated privileges. A flaw was found in the way the Linux kernel's networking subsystem handled offloaded packets with multiple layers of encapsulation in the GRO (Generic Receive Offload) code path. A remote attacker could use this flaw to trigger unbounded recursion in the kernel that could lead to stack corruption, resulting in a system crash. It was discovered that the Hotspot component of OpenJDK did not properly check arguments of the System.arraycopy() function in certain cases. An untrusted Java application or applet could use this flaw to corrupt virtual machine's memory and completely bypass Java sandbox restrictions. A denial of service flaw was found in the way BIND handled packets with malformed options. A remote attacker could use this flaw to make named exit unexpectedly with an assertion failure via a specially crafted DNS packet. It was discovered that the Hotspot component of OpenJDK did not properly check received Java Debug Wire Protocol (JDWP) packets. An attacker could possibly use this flaw to send debugging commands to a Java program running with debugging enabled if they could make victim's browser send HTTP requests to the JDWP port of the debugged application. A vulnerability was found in FormattedServiceListWriter in Apache CXF HTTP transport module that could allow an attacker to inject unexpected matrix parameters into the request URL. On a successful injection these matrix parameters will find their way back to the client in the services list page which represents an XSS risk to the client. A flaw was found in the way the JMX component of OpenJDK handled classloaders. An untrusted Java application or applet could use this flaw to bypass certain Java sandbox restrictions. It was discovered that the Libraries component of OpenJDK did not restrict the set of algorithms used for JAR integrity verification. This flaw could allow an attacker to modify content of the JAR file that used weak signing key or hash algorithm. A flaw was found in the way the Networking component of OpenJDK handled HTTP proxy authentication. A Java application could possibly expose HTTPS server authentication credentials via a plain text network connection to an HTTP proxy if proxy asked for authentication. A stack-based buffer overflow flaw was found in the way Quagga handled IPv6 router advertisement messages. A remote attacker could use this flaw to crash the zebra daemon resulting in denial of service. An out of bounds read flaw related to "graphite2::Silf::readGraphite" has been reported in graphite2. An attacker could possibly exploit this flaw to disclose potentially sensitive memory or cause an application crash. A flaw was found in the way the mysqld_safe script handled creation of error log file. The mysql operating system user could use this flaw to escalate their privileges to root. JBoss BRMS 6 and BPM Suite 6 are vulnerable to a stored XSS via business process editor. The flaw is due to an incomplete fix for CVE-2016-5398. Remote, authenticated attackers that have privileges to create business processes can store scripts in them, which are not properly sanitized before showing to other users, including admins. A denial of service flaw was found in the way the TLS/SSL protocol defined processing of ALERT packets during a connection handshake. A remote attacker could use this flaw to make a TLS/SSL server consume an excessive amount of CPU and fail to accept connections from other clients. It was found that the keycloak did not implement authentication flow correctly. An attacker could use this flaw to construct a phishing URL, from which he could hijack the user's session. This could lead to information disclosure, or permit further possible attacks. An error was found in protocol parsing logic of mod_cluster load balancer Apache HTTP Server modules. An attacker could use this flaw to cause a Segmentation Fault in the serving httpd process. An EAP feature to download server log files allows logs to be available via GET requests making them vulnerable to cross-origin attacks. An attacker could trigger the user's browser to request the log files consuming enough resources that normal server functioning could be impaired. A flaw was found in foreman-debug's logging. An attacker with access to the foreman log file would be able to view passwords, allowing them to access those systems. It was discovered that the mod_session_crypto module of httpd did not use any mechanisms to verify integrity of the encrypted session data stored in the user's browser. A remote attacker could use this flaw to decrypt and modify session data using a padding oracle attack. Ansible fails to properly sanitize fact variables sent from the Ansible controller. An attacker with the ability to create special variables on the controller could execute arbitrary commands on Ansible clients as the user Ansible runs as. A vulnerability was found in gd. The function dynamicGetbuf() failed to check for out of bounds reads. An attacker could create a crafted image that would lead to a crash or, potentially, information disclosure. An assertion error has been reported in graphite2. An attacker could possibly exploit this flaw to cause an application crash. Apache CXF JAX-RS implementation provides a number of Atom MessageBodyReaders. These readers use Apache Abdera Parser to parse Atom feeds or Entries, with this Parser expanding XML entities by default. It was found that this represents a major XXE risk. A timing attack flaw was found in OpenSSL that could allow a malicious user with local access to recover ECDSA P-256 private keys. A flaw was found in the way Ceph Object Gateway handles POST object requests. An authenticated attacker could launch a denial of service attack by sending null or specially crafted POST object requests. A flaw was discovered in the Linux kernel's implementation of VFIO. An attacker issuing an ioctl can create a situation where memory is corrupted and modify memory outside of the expected area. This may overwrite kernel memory and subvert kernel execution. The use of a kzalloc with an integer multiplication allowed an integer overflow condition to be reached in vfio_pci_intrs.c. This combined with CVE-2016-9083 may allow an attacker to craft an attack and use unallocated memory, potentially crashing the machine. It was found that keycloak did not correctly check permissions when handling service account user deletion requests sent to the rest server. An attacker with service account authentication could use this flaw to bypass normal permissions and delete users in a separate realm. A denial of service flaw was found in the way BIND handled responses containing a DNAME answer. A remote attacker could use this flaw to make named exit unexpectedly with an assertion failure via a specially crafted DNS response. A vulnerability was discovered in nginx. An attacker who could already run commands under the nginx user id could use this access to append data to files owned by root, potentially elevating their own privileges to root. An integer overflow flaw leading to a heap-based buffer overflow was found in libXpm. An attacker could use this flaw to crash an application using libXpm via a specially crafted XPM file. It was discovered that it was possible for a web application to access any global JNDI resource whether an explicit ResourceLink had been configured or not. An integer overflow flaw, leading to a heap-based buffer overflow, was found in the memcached binary protocol. An attacker could create a specially crafted message that would cause the memcached server to crash or, potentially, execute arbitrary code. An integer overflow flaw, leading to a heap-based buffer overflow, was found in the memcached binary protocol. An attacker could create a specially crafted message that would cause the memcached server to crash or, potentially, execute arbitrary code. An integer overflow flaw, leading to a heap-based buffer overflow, was found in memcached's parsing of SASL authentication messages. An attacker could create a specially crafted message that would cause the memcached server to crash or, potentially, execute arbitrary code. It was discovered that a malicious web application could bypass a configured SecurityManager via manipulation of the configuration parameters for the JSP Servlet. It was discovered that when a SecurityManager was configured, Tomcat's system property replacement feature for configuration files could be used by a malicious web application to bypass the SecurityManager and read system properties that should not be visible. It was discovered that a malicious web application could bypass a configured SecurityManager via a Tomcat utility method that was accessible to web applications. The Realm implementations did not process the supplied password if the supplied user name did not exist. This made a timing attack possible to determine valid user names. Note that the default configuration includes the LockOutRealm which makes exploitation of this vulnerability harder. A permissions flaw was found in redis, which sets weak permissions on certain files and directories that could potentially contain sensitive information. A local, unprivileged user could possibly use this flaw to access unauthorized system information. The OpenShift Enterprise 3 router does not properly sort routes when processing newly added routes. An attacker with access to create routes can potentially overwrite existing routes and redirect network traffic for other users to their own site. A buffer overflow vulnerability due to a lack of input filtering of incoming fragmented datagrams was found in the IP-over-1394 driver [firewire-net] in a fragment handling code in the Linux kernel. The vulnerability exists since firewire supported IPv4, i.e. since version 2.6.31 (year 2009) till version v4.9-rc4. A maliciously formed fragment with a respectively large datagram offset would cause a memcpy() past the datagram buffer, which would cause a system panic or possible arbitrary code execution. The flaw requires [firewire-net] module to be loaded and is remotely exploitable from connected firewire devices, but not over a local network. An out of bounds read flaw related to "graphite2::Silf::getClassGlyph" has been reported in graphite2. An attacker could possibly exploit this flaw to disclose potentially sensitive memory or cause an application crash. It was discovered that the mod_auth_digest module of httpd did not properly check for memory allocation failures. A remote attacker could use this flaw to cause httpd child processes to repeatedly crash if the server used HTTP digest authentication. A race condition was found in the way MySQL performed MyISAM engine table repair. A database user with shell access to the server running mysqld could use this flaw to change permissions of arbitrary files writable by the mysql system user. A flaw was found in the way the mysqld_safe script handled creation of error log file. The mysql operating system user could use this flaw to escalate their privileges to root. It was discovered that the HTTP parser in httpd incorrectly allowed certain characters not permitted by the HTTP protocol specification to appear unencoded in HTTP request headers. If httpd was used in conjunction with a proxy or backend server that interpreted those characters differently, a remote attacker could possibly use this flaw to inject data into HTTP responses, resulting in proxy cache poisoning. A vulnerability was found in perl-XML-Twig. External entity expansion (XXE) took place regardless of the setting 'expand_external_ents', which was supposed to disable this functionality if set to 0 (the default) or -1. An attacker could craft an XML message which, when processed by an application using perl-XML-Twig, could cause denial of service or, potentially, information disclosure. A vulnerability was found in perl-ImageInfo. When parsing an SVG file, external entity expansion (XXE) was not disabled. An attacker could craft an SVG file which, when processed by an application using perl-Image-Info, could cause denial of service or, potentially, information disclosure. It was found that Diffie Hellman Client key exchange handling in NSS was vulnerable to small subgroup confinement attack. An attacker could use this flaw to recover private keys by confining the client DH key to small subgroup of the desired group. The lrw_crypt() function in 'crypto/lrw.c' in the Linux kernel before 4.5 allows local users to cause a system crash and a denial of service by the NULL pointer dereference via accept(2) system call for AF_ALG socket without calling setkey() first to set a cipher key. An information-leak vulnerability was found in the OpenStack Orchestration (heat) service. Launching a new stack with a local URL resulted in a detailed error message, allowing an authenticated user to conduct network discovery and reveal the details of internal network services. The __get_user_asm_ex macro in arch/x86/include/asm/uaccess.h in the Linux kernel before 4.7.5 does not initialize a certain integer variable, which allows local users to obtain sensitive information from kernel stack memory by triggering failure of a get_user_ex call. A flaw was found in the TIPC networking subsystem which could allow for memory corruption and possible privilege escalation. The flaw involves a system with an unusually low MTU (60) on networking devices configured as bearers for the TIPC protocol. An attacker could create a packet which will overwrite memory outside of allocated space and allow for privilege escalation. A vulnerability was found in python-pillow. A crafted image file with negative dimensions could cause a buffer to be under-allocated, leading to arbitrary writes on the heap which could cause a crash or, potentially, code execution. A memory disclosure vulnerability was found in python-pillow. Functions in map.c failed to check for image overflow and check that an offset parameter was within bounds, allowing a crafted image to cause a crash or disclosure of memory. A vulnerability was found in ipsilon in the SAML2 provider's handling of sessions. An attacker able to hit the logout URL could determine what service providers other users are logged in to and terminate their sessions. It was found that foreman is vulnerable to a stored XSS via an organization or location name. This could allow an attacker with privileges to set the organization or location name to display arbitrary HTML including scripting code within the web interface. Linux kernel built with the Kernel-based Virtual Machine (CONFIG_KVM) support is vulnerable to a null pointer dereference flaw. It could occur on x86 platform, when emulating an undefined instruction. An attacker could use this flaw to crash the host kernel resulting in DoS. A path traversal issue was found in Spark version 2.5 and potentially earlier versions. The vulnerability resides in the functionality to serve static files where there's no protection against directory traversal attacks. This could allow attackers access to private files including sensitive data. It was found that a path traversal vulnerability in hawtio leads to a NullPointerException with a full stacktrace. An attacker could use this flaw to gather undisclosed information from within hawtio's root. A denial of service flaw affecting various daemons in Quagga was found. A remote attacker could use this flaw to cause the various Quagga daemons, which expose their telnet interface, to crash. A buffer overflow flaw, leading to memory corruption, was found in TigerVNC viewer. A remote malicious VNC server could use this flaw to crash the client vncviewer process resulting in denial of service. A vulnerability was found in the Linux kernel. An unprivileged local user could trigger oops in shash_async_export() by attempting to force the in-kernel hashing algorithms into decrypting an empty data set. It was discovered that the Linux kernel since 3.6-rc1 with 'net.ipv4.tcp_fastopen' set to 1 can hit BUG() statement in tcp_collapse() function after making a number of certain syscalls leading to a possible system crash. The use of uninitialized memory related to "graphite2::GlyphCache::Loader::read_glyph" has been reported in graphite2. An attacker could possibly exploit this flaw to negatively impact the execution of an application using graphite2 in unknown ways. A flaw was found in the way Add-on update process was handled by Firefox. A Man-in-the-Middle attacker could use this flaw to install a malicious signed add-on update. A password-check vulnerability was found in the way initramfs, generated by dracut, handles the decryption of LUKS-encrypted data partitions. An attacker having physical access to the machine or access to the boot console may be able to brute-force the LUKS password using the dracut shell, and may be able to copy off the encrypted partition for an offline brute-force attack or, in certain conditions, install malicious boot images in the /boot partition. An out-of-bounds heap read was discovered in libtiff. A crafted file could cause the application to crash or, potentially, disclose process memory. An out-of-bounds heap read was discovered in libtiff. A crafted file could cause the application to crash or, potentially, disclose process memory. It was found that the Karaf container used by Red Hat JBoss Fuse 6.x, and Red Hat JBoss A-MQ 6.x, deserializes objects passed to MBeans via JMX operations. An attacker could use this flaw to execute remote code on the server as the user running the Java Virtual Machine if the target MBean contain deserialization gadgets in its classpath. An input validation vulnerability was found in Ansible's mysql_user module which may fail to correctly change a password in certain circumstances. Thus the previous password would still be active when it should have been changed. A denial of service flaw was found in the way bash handled popd commands. A poorly written shell script could cause bash to crash resulting in a local denial of service limited to a specific bash session. A vulnerability was discovered in tcpdump's handling of LINKTYPE_SLIP pcap files. An attacker could craft a malicious pcap file that would cause tcpdump to crash when attempting to print a summary of packet data within the file. It was discovered that the 2D component of OpenJDK performed parsing of iTXt and zTXt PNG image chunks even when configured to ignore metadata. An attacker able to make a Java application parse a specially crafted PNG image could cause the application to consume an excessive amount of memory. It was discovered that the wsdlimport tool in the JAX-WS component of OpenJDK did not use secure XML parser settings when parsing WSDL XML documents. A specially crafted WSDL document could cause wsdlimport to use an excessive amount of CPU and memory, open connections to other hosts, or leak information. A memory corruption flaw was found in GStreamer's Nintendo NSF music file format decoding plug-in. A remote attacker could use this flaw to cause an application using GStreamer to crash or, potentially, execute arbitrary code with the privileges of the user running the application. A use-after-free flaw was found in the way JasPer, before version 2.0.12, decode certain JPEG 2000 image files. A specially crafted file could cause an application using JasPer to crash. An integer overflow flaw, leading to a heap-based buffer overflow, was found in GStreamer's VMware VMnc video file format decoding plug-in. A remote attacker could use this flaw to cause an application using GStreamer to crash or, potentially, execute arbitrary code with the privileges of the user running the application. A flaw was found in the control mode functionality of ntpd. A remote attacker could send a crafted control mode packet which could lead to information disclosure or result in DDoS amplification attacks. A flaw was found in the way ntpd running on a host with multiple network interfaces handled certain server responses. A remote attacker could use this flaw which would cause ntpd to not synchronize with the source. It was found that when ntp is configured with rate limiting for all associations the limits are also applied to responses received from its configured sources. A remote attacker who knows the sources can cause a denial of service by preventing ntpd from accepting valid responses from its sources. A flaw was found in the way ntpd calculated the root delay. A remote attacker could send a specially-crafted spoofed packet to cause denial of service or in some special cases even crash. It was discovered that the code that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information from requests other then their own. The JmxRemoteLifecycleListener was not updated to take account of Oracle's fix for CVE-2016-3427. JMXRemoteLifecycleListener is only included in EWS 2.x and JWS 3.x source distributions. If you deploy a Tomcat instance built from source, using the EWS 2.x, or JWS 3.x distributions, an attacker could use this flaw to launch a remote code execution attack on your deployed instance. A race-condition flaw was discovered in openstack-neutron where, following a minor overcloud update, neutron security groups were disabled. Specifically, the following were reset to 0: net.bridge.bridge-nf-call-ip6tables and net.bridge.bridge-nf-call-iptables. The race was only triggered by an update, at which point an attacker could access exposed tenant VMs and network resources. A flaw was found in the Linux kernel key management subsystem in which a local attacker could crash the kernel or corrupt the stack and additional memory (denial of service) by supplying a specially crafted RSA key. This flaw panics the machine during the verification of the RSA key. Multiple heap overflows were found in HDF5. These issues could be used to gain code execution in any program that exposes the affected functions to untrusted input. While HDF5 is shipped as a dependency, no Red Hat products are known to expose these issues in any supported use case at this time. Multiple heap overflows were found in HDF5. These issues could be used to gain code execution in any program that exposes the affected functions to untrusted input. While HDF5 is shipped as a dependency, no Red Hat products are known to expose these issues in any supported use case at this time. Multiple heap overflows were found in HDF5. These issues could be used to gain code execution in any program that exposes the affected functions to untrusted input. While HDF5 is shipped as a dependency, no Red Hat products are known to expose these issues in any supported use case at this time. Multiple heap overflows were found in HDF5. These issues could be used to gain code execution in any program that exposes the affected functions to untrusted input. While HDF5 is shipped as a dependency, no Red Hat products are known to expose these issues in any supported use case at this time. A flaw was found in the Linux kernel's implementation of the SCTP protocol. A remote attacker could trigger an out-of-bounds read with an offset of up to 64kB potentially causing the system to crash. An input validation flaw was found in the way OpenShift handles requests for images. A user, with a copy of the manifest associated with an image, can pull an image even if they do not have access to the image normally, resulting in the disclosure of any information contained within the image. A vulnerability was discovered in tcpdump's handling of LINKTYPE_SLIP pcap files. An attacker could craft a malicious pcap file that would cause tcpdump to crash when attempting to print a summary of packet data within the file. A vulnerability was found in vim in how certain modeline options were treated. An attacker could craft a file that, when opened in vim with modelines enabled, could execute arbitrary commands with privileges of the user running vim. An out of bounds array access issue was found in the Xen virtual machine monitor, built with the QEMU ioport support. It could occur while doing ioport read/write operations, if guest was to supply a 32bit address parameter. A privileged guest user/process could use this flaw to potentially escalate their privileges on a host. Multiple flaws were discovered in GStreamer's FLC/FLI/FLX media file format decoding plug-in. A remote attacker could use these flaws to cause an application using GStreamer to crash or, potentially, execute arbitrary code with the privileges of the user running the application. Multiple flaws were discovered in GStreamer's FLC/FLI/FLX media file format decoding plug-in. A remote attacker could use these flaws to cause an application using GStreamer to crash or, potentially, execute arbitrary code with the privileges of the user running the application. Multiple flaws were discovered in GStreamer's FLC/FLI/FLX media file format decoding plug-in. A remote attacker could use these flaws to cause an application using GStreamer to crash or, potentially, execute arbitrary code with the privileges of the user running the application. A flaw was found in the way ntpd implemented the trap service. A remote attacker could send a specially crafted packet to cause a null pointer dereference that will crash ntpd, resulting in a denial of service. It was found that the log file viewer in Red Hat JBoss Enterprise Application 6 and 7 allows arbitrary file read to authenticated user via path traversal. Integer overflow in the vc4_get_bcl function in drivers/gpu/drm/vc4/vc4_gem.c in the VideoCore DRM driver in the Linux kernel before 4.9.7 allows local users to cause a denial of service or possibly have unspecified other impact via a crafted size value in a VC4_SUBMIT_CL ioctl call. An integer underflow leading to an out of bounds read flaw was found in OpenSSL. A remote attacker could possibly use this flaw to crash a 32-bit TLS/SSL server or client using OpenSSL if it used the RC4-MD5 cipher suite. When updating a password in the rhvm database the ovirt-aaa-jdbc-tool tools fail to correctly check for the current password if it is expired. This would allow access to an attacker with access to change the password on accounts with expired passwords, gaining access to those accounts. Linux kernel built with the KVM visualization support (CONFIG_KVM), with nested visualization(nVMX) feature enabled(nested=1), is vulnerable to host memory leakage issue. It could occur while emulating VMXON instruction in 'handle_vmon'. An L1 guest user could use this flaw to leak host memory potentially resulting in DoS. Quick emulator (QEMU) built with the Cirrus CLGD 54xx VGA emulator support is vulnerable to an out-of-bounds access issue. It could occur while copying VGA data via bitblt copy in backward mode. A privileged user inside a guest could use this flaw to crash the QEMU process resulting in DoS or potentially execute arbitrary code on the host with privileges of QEMU process on the host. A vulnerability was found in libevent with the parsing of DNS requests and replies. An attacker could send a forged DNS response to an application using libevent which could lead to reading data out of bounds on the heap, potentially disclosing a small amount of application memory. A vulnerability was found in libevent with the parsing of IPv6 addresses. If an attacker could cause an application using libevent to parse a malformed address in IPv6 notation of more than 2GiB in length, a stack overflow would occur leading to a crash. An out of bounds read vulnerability was found in libevent in the search_make_new function. If an attacker could cause an application using libevent to attempt resolving an empty hostname, an out of bounds read could occur possibly leading to a crash. A race condition was found in the way su handled the management of child processes. A local authenticated attacker could use this flaw to kill other processes with root privileges under specific conditions. A vulnerability was found in php-pear where if a malicious server responded to a pear An uncontrolled memory allocation was found in ZZIPlib that could lead to a crash in the __zzip_parse_root_directory function of zzip/zip.c if the package is compiled with Address Sanitizer. Remote attackers could leverage this vulnerability to cause a denial of service via a crafted zip file. A null pointer dereference flaw was found in libgd. An attacker could use a specially-crafted .gd2 file to cause an application linked with libgd to crash, leading to denial of service. An integer overflow flaw, leading to a heap-based buffer overflow was found in the way libgd read some specially-crafted gd2 files. A remote attacker could use this flaw to crash an application compiled with libgd or in certain cases execute arbitrary code with the privileges of the user running that application. It was found that the exif_convert_any_to_int() function in PHP was vulnerable to floating point exceptions when parsing tags in image files. A remote attacker with the ability to upload a malicious image could crash PHP, causing a Denial of Service. A denial of service flaw was found in the IEEE 802.11 dissector in Wireshark. A remote network attacker could potentially use this flaw to crash Wireshark by tricking it into processing a crafted packet. Kernel memory corruption due to a buffer overflow was found in brcmf_cfg80211_mgmt_tx() function in Linux kernels from v3.9-rc1 to v4.13-rc1. The vulnerability can be triggered by sending a crafted NL80211_CMD_FRAME packet via netlink. This flaw is unlikely to be triggered remotely as certain userspace code is needed for this. An unprivileged local user could use this flaw to induce kernel memory corruption on the system, leading to a crash. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although it is unlikely. It was found that a flaw in hawtio could cause remote code execution via file upload. An attacker could use this vulnerability to upload crafted file which could be executed on a target machine where hawtio is deployed. Mounting a crafted EXT4 image read-only leads to an attacker controlled memory corruption and SLAB-Out-of-Bounds reads. A vulnerability was found in the XML-RPC interface in supervisord. When processing malformed commands, an attacker can cause arbitrary shell commands to be executed on the server as the same user as supervisord. Exploitation requires the attacker to first be authenticated to the supervisord service. A denial of service flaw was found in the TigerVNC's Xvnc server. A remote unauthenticated attacker could use this flaw to make Xvnc crash by terminating the TLS handshake process early. It was found that gtk-vnc lacked proper bounds checking while processing messages using RRE, hextile, or copyrect encodings. A remote malicious VNC server could use this flaw to crash VNC viewers which are based on the gtk-vnc library. An integer overflow flaw was found in gtk-vnc. A remote malicious VNC server could use this flaw to crash VNC viewers which are based on the gtk-vnc library. It was discovered that the XmlUtils class in jbpmmigration performed expansion of external parameter entities while parsing XML files. A remote attacker could use this flaw to read files accessible to the user running the application server and, potentially, perform other more advanced XML eXternal Entity (XXE) attacks. An integer overflow flaw was found in Quick Emulator (QEMU) in the CCID Card device support. The flaw could occur while passing messages via command/response packets to and from the host. A privileged user inside a guest could use this flaw to crash the QEMU process. An issue was found in the Linux kernel ipv6 implementation of GRE tunnels which allows a remote attacker to trigger an out-of-bounds access. At this time we understand no trust barrier has been crossed and there is no security implications in this flaw. A flaw was found in the Linux kernel's handling of clearing SELinux attributes on /proc/pid/attr files. An empty (null) write to this file can crash the system by causing the system to attempt to access unmapped kernel memory. A denial of service flaw was found in the way BIND handled query responses when both DNS64 and RPZ were used. A remote attacker could use this flaw to make named exit unexpectedly with an assertion failure or a null pointer dereference via a specially crafted DNS response. The aio_mount function in fs/aio.c in the Linux kernel does not properly restrict execute access, which makes it easier for local users to bypass intended SELinux W^X policy restrictions. A race condition in the ip4_datagram_release_cb function in net/ipv4/datagram.c in the Linux kernel allows local users to gain privileges or cause a denial of service (use-after-free) by leveraging incorrect expectations about locking during multithreaded access to internal data structures for IPv4 UDP sockets. Quick emulator (QEMU) built with the Cirrus CLGD 54xx VGA Emulator support is vulnerable to an out-of-bounds access issue. The issue could occur while copying VGA data in cirrus_bitblt_cputovideo. A privileged user inside guest could use this flaw to crash the QEMU process OR potentially execute arbitrary code on host with privileges of the QEMU process. It was found that Apache Camel's camel-jackson and camel-jacksonxml components are vulnerable to Java object de-serialisation vulnerability. Camel allows such a type through the 'CamelJacksonUnmarshalType' property. De-serializing untrusted data can lead to security flaws as demonstrated in various similar reports about Java de-serialization issues. It was found that the camel-snakeyaml component is exploitable for code execution. An attacker could use this vulnerability to send specially crafted payload to a camel-snakeyaml endpoint and causing a remote code execution attack. An access-control flaw was found in the OpenStack Orchestration (heat) service where a service log directory was improperly made world readable. A malicious system user could exploit this flaw to access sensitive information. An accessibility flaw was found in the OpenStack Workflow (mistral) service where a service log directory was improperly made world readable. A malicious system user could exploit this flaw to access sensitive information. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. Multiple out of bounds read and integer overflow vulnerabilities were found in tcpdump affecting the decoding of various protocols. An attacker could create a crafted pcap file or send specially crafted packets to the network segment where tcpdump is running in live capture mode (without -w) which could cause it to display incorrect data, crash or enter an infinite loop. A vulnerability was found in the Linux kernel where having malicious IP options present would cause the ipv4_pktinfo_prepare() function to drop/free the dst. This could result in a system crash or possible privilege escalation. It was found that changing the ciphersuite during a renegotiation of the Encrypt-Then-Mac extension could result in a crash of the OpenSSL server or client. It was discovered that the Security component of OpenJDK could fail to properly enforce restrictions defined for processing of X.509 certificate chains. A remote attacker could possibly use this flaw to make Java accept certificate using one of the disabled algorithms. A NULL pointer dereference was discovered in libxml2, when using xmllint --recover. A maliciously crafted file, when parsed in recovery mode, could cause the application to crash. A flaw was found in the way MySQL client library (libmysqlclient) handled prepared statements when server connection was lost. A malicious server or a man-in-the-middle attacker could possibly use this flaw to crash an application using libmysqlclient. It was reported that with Linux kernel, earlier than version v4.10-rc8, an application may trigger a BUG_ON in sctp_wait_for_sndbuf if the socket tx buffer is full, a thread is waiting on it to queue more data, and meanwhile another thread peels off the association being used by the first thread. The time subsystem in the Linux kernel, when CONFIG_TIMER_STATS is enabled, allows local users to discover real PID values (as distinguished from PID values inside a PID namespace) by reading the /proc/timer_list file, related to the print_timer function in kernel/time/timer_list.c and the __timer_stats_timer_set_start_info function in kernel/time/timer.c. It was discovered that rpm-ostree and rpm-ostree-client fail to properly check GPG signatures on packages when doing layering. Packages with unsigned or badly signed content could fail to be rejected as expected. This issue is partially mitigated on RHEL Atomic Host, where certificate pinning is used by default. A flaw was found in the way glibc's fnmatch() function processed certain malformed patterns. An attacker able to make an application call this function could use this flaw to crash that application. An integer overflow flaw, leading to a heap-based buffer overflow, was found in glibc's _IO_wstr_overflow() function. An attacker able to make an application call this function could use this flaw to crash that application or, potentially, execute arbitrary code with the permissions of the user running the application. A stack buffer overflow flaw was found in the Quick Emulator (QEMU) built with the Network Block Device (NBD) client support. The flaw could occur while processing server's response to a 'NBD_OPT_LIST' request. A malicious NBD server could use this issue to crash a remote NBD client resulting in DoS or potentially execute arbitrary code on client host with privileges of the QEMU process. It was found that the fix for CVE-2015-3148 in curl was incomplete. An application using libcurl with HTTP Negotiate authentication could incorrectly re-use credentials for subsequent requests to the same server. It was found that the original fix for CVE-2016-6786 was incomplete. There exist a race between two concurrent sys_perf_event_open() calls when both try and move the same pre-existing software group into a hardware context. A vulnerability was found in icoutils, in the wrestool program. An attacker could create a crafted executable that, when read by wrestool, could result in memory corruption leading to a crash or potential code execution. A vulnerability was found in icoutils, in the icotool program. An attacker could create a crafted ICO or CUR file that, when read by icotool, could result in memory corruption leading to a crash or potential code execution. A vulnerability was found in icoutils, in the icotool program. An attacker could create a crafted ICO or CUR file that, when read by icotool, could result in memory corruption leading to a crash or potential code execution. It was discovered that a programming error in the processing of HTTPS requests in the Apache Tomcat servlet and JSP engine may result in denial of service via an infinite loop. A logic error in valid_role() in CloudForms role validation could allow a tenant administrator to create groups with a higher privilege level than the tenant administrator should have. This would allow an attacker with tenant administration access to elevate privileges. It was discovered that libXdmcp used weak entropy to generate session keys. On a multi-user system using xdmcp, a local attacker could potentially use information available from the process list to brute force the key, allowing them to hijack other users' sessions. It was discovered that libICE used a weak entropy to generate keys. A local attacker could potentially use this flaw for session hijacking using the information available from the process list. A text injection flaw was found in how mod_auth_openidc handled error pages. An attacker could potentially use this flaw to conduct content spoofing and phishing attacks by tricking users into opening specially crafted URLs. A use-after-free flaw was found in the TLS 1.2 implementation in the NSS library when client authentication was used. A malicious client could use this flaw to cause an application compiled against NSS to crash or, potentially, execute arbitrary code with the permission of the user running the application. A denial of service flaw was found in MIT Kerberos krb5kdc service. An authenticated attacker could use this flaw to cause krb5kdc to exit with an assertion failure by making an invalid S4U2Self or S4U2Proxy request. An assertion-failure flaw was found in the Network Block Device (NBD) server's initial connection negotiation, where the I/O coroutine was undefined. This could crash the qemu-nbd server if a client sent unexpected data during connection negotiation. A remote user or process could use this flaw to crash the qemu-nbd server resulting in denial of service. A data leak was found in gdImageCreateFromGifCtx() in GD Graphics Library used in PHP before 5.6.31 and 7.1.7. An attacker could craft a malicious GIF image and read up to 762 bytes from stack. A denial of service flaw was found in the UMTS MAC dissector in Wireshark. A remote network attacker could potentially use this flaw to crash Wireshark by tricking it into processing a crafted packet. It was found that Apache CXF OAuth2 Hawk and JOSE MAC Validation code is not using a constant time MAC signature comparison algorithm which may be exploited by some sophisticated timing attacks. It may only affect OAuth2 Hawk or JWT access tokens or JOSE JWS/JWE interceptors which depend on HMAC secret key algorithms. A use-after-free flaw was found in the way the Linux kernel's Datagram Congestion Control Protocol (DCCP) implementation freed SKB (socket buffer) resources for a DCCP_PKT_REQUEST packet when the IPV6_RECVPKTINFO option is set on the socket. A local, unprivileged user could use this flaw to alter the kernel memory, allowing them to escalate their privileges on the system. It was found that LibreOffice disclosed contents of a file specified in an embedded object's preview. An attacker could potentially use this flaw to expose details of a system running LibreOffice as an online service via a crafted document. An out-of-bounds memory access issue was found in Quick Emulator (QEMU) in the VNC display driver. This flaw could occur while refreshing the VNC display surface area in the 'vnc_refresh_server_surface'. A user inside a guest could use this flaw to crash the QEMU process. An information disclosure vulnerability in Linux kernel could enable a local malicious application to access data outside of its permission levels. To exploit the flaw it is first required to compromise a privileged process. It was found that the Linux kernel's Datagram Congestion Control Protocol (DCCP) implementation used the IPv4-only inet_sk_rebuild_header() function for both IPv4 and IPv6 DCCP connections, which could result in memory corruptions. A remote attacker could use this flaw to crash the system. A flaw was found in the Linux kernel's handling of packets with the URG flag. Applications using the splice() and tcp_splice_read() functionality could allow a remote attacker to force the kernel to enter a condition in which it could loop indefinitely. A NULL pointer deference flaw was found in the way libvirt handled empty drives. A remote authenticated attacker could use this flaw to crash libvirtd daemon resulting in denial of service. An out-of-bounds read flaw was found in the way GdkPixbuf handled ICO format files. A maliciously crafted ICO file could cause the application using GdkPixbuf to crash. The do_shmat function in ipc/shm.c in the Linux kernel, through 4.9.12, does not restrict the address calculated by a certain rounding operation. This allows privileged local users to map page zero and, consequently, bypass a protection mechanism that exists for the mmap system call. This is possible by making crafted shmget and shmat system calls in a privileged context. An integer overflow flaw was found in the way vim handled undo files. This bug could result in vim crashing when trying to process corrupted undo files. An integer overflow flaw was found in the way vim handled tree length values when reading an undo file. This bug could result in vim crashing when trying to process corrupted undo files. The skbs processed by ip_cmsg_recv() are not guaranteed to be linear (e.g. when sending UDP packets over loopback with MSGMORE). Using csum_partial() on potentially the whole skb len is dangerous; instead be on the safe side and use skb_checksum(). This may lead to an infoleak as the kernel memory may be checksummed and sent as part of the packet. A design flaw issue was found in the Red Hat OpenStack Platform director use of TripleO to enable libvirtd based live-migration. Libvirtd is deployed by default (by director) listening on 0.0.0.0 (all interfaces) with no-authentication or encryption. Anyone able to make a TCP connection to any compute host IP address, including 127.0.0.1, other loopback interface addresses, or in some cases possibly addresses that have been exposed beyond the management interface, could use this to open a virsh session to the libvirtd instance and gain control of virtual machine instances or possibly take over the host. A flaw was found in libreoffice before 5.4.5 and before 6.0.1. Arbitrary remote file disclosure may be achieved by the use of the WEBSERVICE formula in a specially crafted ODS file. A race condition flaw was found in the N_HLDC Linux kernel driver when accessing n_hdlc.tbuf list that can lead to double free. A local, unprivileged user able to set the HDLC line discipline on the tty device could use this flaw to increase their privileges on the system. The LLC subsystem in the Linux kernel does not ensure that a certain destructor exists in required circumstances, which allows local users to cause a denial of service (BUG_ON) or possibly have unspecified other impact via crafted system calls. Race condition in net/packet/af_packet.c in the Linux kernel allows local users to cause a denial of service (use-after-free) or possibly have unspecified other impact via a multithreaded application that makes PACKET_FANOUT setsockopt system calls. The hashbin_delete function in net/irda/irqueue.c in the Linux kernel improperly manages lock dropping, which allows local users to cause a denial of service (deadlock) via crafted operations on IrDA devices. It was found that mod_auth_openidc did not properly sanitize HTTP headers for certain request paths. A remote attacker could potentially use this flaw to bypass authentication and access sensitive information by sending crafted HTTP requests. An information disclosure flaw was found in the way saned handled SANE_NET_CONTROL_OPTION requests. A remote attacker, able to connect to the saned daemon, could use this flaw to disclose portions of saned process memory. It was found that the code in net/sctp/socket.c in the Linux kernel through 4.10.1 does not properly restrict association peel-off operations during certain wait states, which allows local users to cause a denial of service (invalid unlock and double free) via a multithreaded application. This vulnerability was introduced by CVE-2017-5986 fix (commit 2dcab5984841). It was found that the REST API in infinispan did not properly enforce auth constraints. An attacker could use this vulnerability to read or modify data in the default cache or a known cache name. A race condition was found in samba server. A malicious samba client could use this flaw to access files and directories in areas of the server file system not exported under the share definitions. It was found that CloudForms does not verify that the server hostname matches the domain name in the certificate when using a custom CA and communicating with Red Hat Virtualization (RHEV) and OpenShift. This would allow an attacker to spoof RHEV or OpenShift systems and potentially harvest sensitive information from CloudForms. A CRLF injection flaw was found in the way wget handled URLs. A remote attacker could use this flaw to inject arbitrary HTTP headers in requests, via CRLF sequences in the host sub-component of a URL, by tricking a user running wget into processing crafted URLs. An out-of-bounds write flaw was found in the way Pidgin processed XML content. A malicious remote server could potentially use this flaw to crash Pidgin or execute arbitrary code in the context of the pidgin process. A heap buffer overflow flaw was found in QEMU's Cirrus CLGD 54xx VGA emulator's VNC display driver support; the issue could occur when a VNC client attempted to update its display after a VGA operation is performed by a guest. A privileged user/process inside a guest could use this flaw to crash the QEMU process or, potentially, execute arbitrary code on the host with privileges of the QEMU process. A flaw was reported in Apache Struts 2 that could allow an attacker to perform remote code execution with a malicious Content-Type value. A use-after-free flaw was found in the Linux kernel which enables a race condition in the L2TPv3 IP Encapsulation feature. A local user could use this flaw to escalate their privileges or crash the system. It was discovered that the DCG implementation in the RMI component of OpenJDK failed to correctly handle references. A remote attacker could possibly use this flaw to execute arbitrary code with the privileges of RMI registry or a Java RMI application. Buffer overflow in the mp_override_legacy_irq() function in arch/x86/kernel/acpi/boot.c in the Linux kernel through 4.12.2 allows local users to gain privileges via a crafted ACPI table. An integer overflow vulnerability in ip6_find_1stfragopt() function was found. A local attacker that has privileges (of CAP_NET_RAW) to open raw socket can cause an infinite loop inside the ip6_find_1stfragopt() function. It was discovered that root can gain direct access to an internal keyring, such as '.dns_resolver' in RHEL-7 or '.builtin_trusted_keys' upstream, by joining it as its session keyring. This allows root to bypass module signature verification by adding a new public key of its own devising to the keyring. It was found that mod_auth_mellon was vulnerable to a cross-site session transfer attack. An attacker with access to one web site on a server could use the same session to get access to a different site running on the same server. A flaw was found that can be triggered in keyring_search_iterator in keyring.c if type->match is NULL. A local user could use this flaw to crash the system or, potentially, escalate their privileges. A number of unused delete routes are present in CloudForms which can be accessed via GET requests instead of just POST requests. This could allow an attacker to bypass the protect_from_forgery XSRF protection causing the routes to be used. This attack would require additional cross-site scripting or similar attacks in order to execute. It was discovered that the MySQL client command line tools only checked after authentication whether server supported SSL. A man-in-the-middle attacker could use this flaw to hijack client's authentication to the server even if the client was configured to require SSL connection. It was found that logback is vulnerable to a deserialization issue. Logback can be configured to allow remote logging through SocketServer/ServerSocketReceiver interfaces that can accept untrusted serialized data. Authenticated attackers on the adjacent network can leverage this vulnerability to execute arbitrary code through deserialization of custom gadget chains. An out-of-bounds read flaw was found in libplist. A specially crafted plist file could be used by an attacker to crash the application using libplist. It was discovered that the Dashbuilder login page could be opened in an IFRAME, which made it possible to intercept and manipulate requests. An attacker could use this flaw to trick a user into performing arbitrary actions in the Console (clickjacking). A flaw was found in the processing of malformed web content. A web page containing malicious content could cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox. The keyring_search_aux function in security/keys/keyring.c in the Linux kernel allows local users to cause a denial of service via a request_key system call for the "dead" key type. It was found that Apache Camel's validation component evaluates DTD headers of XML stream sources, although a validation against XML schemas (XSD) is executed. Remote attackers can use this feature to make Server-Side Request Forgery (SSRF) attacks by sending XML documents with remote DTDs URLs or XML External Entities (XXE). The vulnerability is not given for SAX or StAX sources. A vulnerability was discovered in the NTP server's parsing of configuration directives. A remote, authenticated attacker could cause ntpd to crash by sending a crafted message. A vulnerability was found in NTP, in the parsing of packets from the /dev/datum device. A malicious device could send crafted messages, causing ntpd to crash. A vulnerability was discovered in the NTP server's parsing of configuration directives. A remote, authenticated attacker could cause ntpd to crash by sending a crafted message. A vulnerability was found in NTP, in the building of response packets with custom fields. If custom fields were configured in ntp.conf with particularly long names, inclusion of these fields in the response packet could cause a buffer overflow, leading to a crash. A vulnerability was found in NTP, in the legacy MX4200 refclock implementation. If this refclock was compiled in and used, an attacker may be able to induce stack overflow, leading to a crash or potential code execution. A vulnerability was found in NTP, in the ntpq program. A malicious server could send a specially crafted response which would cause a stack buffer overflow, leading to a crash or potential code execution. A vulnerability was found in NTP, affecting the origin timestamp check function. An attacker able to spoof messages from all of the configured peers could send crafted packets to ntpd, causing later replies from those peers to be discarded, resulting in denial of service. It was found that pcsd was vulnerable to reflected cross-site scripting (XSS) attacks while handling node names during creation or import of a cluster. An attacker could use this flaw to run javascript code in an authenticated session. The copy_from feature in Image Service API v1 allows an attacker to perform masked network port scans. It is possible to create images with a URL such as 'http://localhost:22'. This could allow an attacker to enumerate internal network details while appearing masked, because the scan appears to originate from the Image Service. This is classified as a Server-Side Request Forgery (SSRF). Note: Some knowledge of the internal network might be necessary to exploit this flaw internally (apart from localhost). It was found that subscription-manager's DBus interface let unprivileged user access the com.redhat.RHSM1.Facts.GetFacts and com.redhat.RHSM1.Config.Set methods. An unprivileged local attacker could use these methods to gain access to private information, or launch a privilege escalation attack. The sg_ioctl function in drivers/scsi/sg.c in the Linux kernel allows local users to cause a denial of service (stack-based buffer overflow) or possibly have unspecified other impacts via a large command size in an SG_NEXT_CMD_LEN ioctl call, leading to out-of-bounds write access in the sg_write function. A NULL pointer dereference flaw was found in ghostscript's mem_get_bits_rectangle function. A specially crafted postscript document could cause a crash in the context of the gs process. It was found that the git-prompt.sh script shipped with git failed to correctly handle branch names containing special characters. A specially crafted git repository could use this flaw to execute arbitrary commands if a user working with the repository configured their shell to include repository information in the prompt. The acpi_ns_terminate() function in drivers/acpi/acpica/nsutils.c in the Linux kernel before 4.12 does not flush the operand cache and causes a kernel stack dump. A local users could obtain sensitive information from kernel memory and bypass the KASLR protection mechanism (in the kernel through 4.9) via a crafted ACPI table. An information exposure issue was discovered in OpenStack Compute's exception_wrapper.py. Legacy notification exception contexts appearing in ERROR-level logs could include sensitive information such as account passwords and authorization tokens. Out-of-bounds kernel heap access vulnerability was found in xfrm, kernel's IP framework for transforming packets. An error dealing with netlink messages from an unprivileged user leads to arbitrary read/write and privilege escalation. CloudForms lacks RBAC controls on certain methods in the rails application portion of CloudForms. An attacker with access could use a variety of methods within the rails applications portion of CloudForms to escalate privileges. A vulnerability was found in the readelf utility; part of binutils. A crafted ELF executable or shared library could cause readelf to write arbitrary locations on the heap while processing relocations, leading to a crash or potential code execution. A vulnerability was found in readelf; part of binutils. A crafted executable or shared library could cause use-after-free and out-of-bounds writes, leading to a crash or possible code execution. A denial of service flaw was found in the DOCSIS dissector in Wireshark. A remote network attacker could potentially use this flaw to crash Wireshark by tricking it into processing a crafted packet. It was discovered that the code that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information from requests other than their own. In was found that in the Linux kernel, in vmw_surface_define_ioctl() function in 'drivers/gpu/drm/vmwgfx/vmwgfx_surface.c' file, a 'num_sizes' parameter is assigned a user-controlled value which is not checked if it is zero. This is used in a call to kmalloc() and later leads to dereferencing ZERO_SIZE_PTR, which in turn leads to a GPF and possibly to a kernel panic. It was found that the hammer_cli command line client disables SSL/TLS certificate verification by default. A man-in-the-middle (MITM) attacker could use this flaw to spoof a valid certificate. It was discovered that under certain conditions RESTEasy could be forced to parse a request with YamlProvider, resulting in unmarshalling of potentially untrusted data. An attacker could possibly use this flaw execute arbitrary code with the permissions of the application using RESTEasy. The TCP stack in the Linux kernel through 4.10.6 mishandles the SCM_TIMESTAMPING_OPT_STATS feature, which allows local users to obtain sensitive information from the kernel's internal socket data structures or cause a denial of service (out-of-bounds read) via crafted system calls, related to net/core/skbuff.c and net/socket.c. An out-of-bounds write vulnerability was found in the Linux kernel's vmw_surface_define_ioctl() function, in the 'drivers/gpu/drm/vmwgfx/vmwgfx_surface.c' file. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. An invalid pointer dereference flaw was found in the way 389-ds-base handled LDAP bind requests. A remote unauthenticated attacker could use this flaw to make ns-slapd crash via a specially crafted LDAP bind request, resulting in denial of service. A redirect flaw, where the is_safe_url() function did not correctly sanitize numeric-URL user input, was found in python-django. A remote attacker could exploit this flaw to perform XSS attacks against the OpenStack dashboard. It was found that the packet_set_ring() function of the Linux kernel's networking implementation did not properly validate certain block-size data. A local attacker with CAP_NET_RAW capability could use this flaw to trigger a buffer overflow resulting in a system crash or a privilege escalation. In the Linux kernel's vmw_gb_surface_define_ioctl() function, in 'drivers/gpu/drm/vmwgfx/vmwgfx_surface.c' file, a 'req->mip_levels' is a user-controlled value which is later used as a loop count limit. This allows local unprivileged user to cause a denial of service by a kernel lockup via a crafted ioctl call for a '/dev/dri/renderD*' device. A denial of service flaw was found in the FCP dissector in Wireshark. A remote network attacker could potentially use this flaw to crash Wireshark by tricking it into processing a crafted packet. A NULL pointer dereference flaw was found in the way libcdio handled processing of ISO files. An attacker could potentially use this flaw to crash applications using libcdio by tricking them into processing crafted ISO files. A use-after-free flaw was found in the Linux kernel's file system encryption implementation. A local user could revoke keyring keys being used for ext4, f2fs, or ubifs encryption, causing a denial of service on the system. A memory leak flaw was found in the way TigerVNC handled termination of VeNCrypt connections. A remote unauthenticated attacker could repeatedly send connection requests to the Xvnc server, causing it to consume large amounts of memory resources over time, and ultimately leading to a denial of service due to memory exhaustion. A double free flaw was found in the way TigerVNC handled ClientFence messages. A remote, authenticated attacker could use this flaw to make Xvnc crash by sending specially crafted ClientFence messages, resulting in denial of service. A missing input sanitization flaw was found in the way TigerVNC handled credentials. A remote unauthenticated attacker could use this flaw to make Xvnc crash by sending specially crafted usernames, resulting in denial of service. An integer overflow flaw was found in the way TigerVNC handled ClientCutText messages. A remote, authenticated attacker could use this flaw to make Xvnc crash by sending specially crafted ClientCutText messages, resulting in denial of service. A memory leak flaw was found in the way TigerVNC handled client connections. A remote unauthenticated attacker could repeatedly send connection requests to the Xvnc server, causing it to consume large amounts of memory resources over time, and ultimately leading to a denial of service due to memory exhaustion. It was found that with non-clean TCP close, Websocket server gets into infinite loop on every IO thread, effectively causing DoS. A race condition leading to a NULL pointer dereference was found in the Linux kernel's Link Layer Control implementation. A local attacker with access to ping sockets could use this flaw to crash the system. A flaw was discovered in the way the kernel allows stackable filesystems to overlay. A local attacker who is able to mount filesystems can abuse this flaw to escalate privileges. A flaw was found in foreman's logging during the adding or registering of images. An attacker with access to the foreman log file would be able to view passwords for provisioned systems in the log file, allowing them to access those systems. An authorization-check flaw was discovered in federation configurations of the OpenStack Identity service (keystone). An authenticated federated user could request permissions to a project and unintentionally be granted all related roles including administrative roles. A cross-site scripting flaw was discovered in the OpenStack dashboard (horizon) which allowed remote authenticated administrators to conduct XSS attacks using a crafted federation mapping rule. For this flaw to be exploited, federation mapping must be enabled in the dashboard. collectd contains an infinite loop due to how the parse_packet() and parse_part_sign_sha256() functions interact. If an instance of collectd is configured with "SecurityLevel None" and empty "AuthFile" options, an attacker can send crafted UDP packets that trigger the infinite loop, causing a denial of service. The Linux kernel allows remote attackers to execute arbitrary code via UDP traffic that triggers an unsafe second checksum calculation during execution of a recv system call with the MSG_PEEK flag. This may create a kernel panic or memory corruption leading to privilege escalation. A missing authorization check in the fscrypt_process_policy function in fs/crypto/policy.c in the ext4 and f2fs filesystem encryption support in the Linux kernel allows a user to assign an encryption policy to a directory owned by a different user, potentially creating a denial of service. JBoss BRMS 6 and BPM Suite 6 are vulnerable to a stored XSS via several lists in Business Central. The flaw is due to lack of sanitation of user input when creating new lists. Remote, authenticated attackers that have privileges to create lists can store scripts in them, which are not properly sanitized before showing to other users, including admins. JBoss BRMS 6 and BPM Suite 6 are vulnerable to a reflected XSS via artifact upload. A malformed XML file, if uploaded, causes an error message to appear that includes part of the bad XML code verbatim without filtering out scripts. Successful exploitation would allow execution of script code within the context of the affected user. It was found that the JAXP implementation used in EAP 7.0 for SAX and DOM parsing is vulnerable to certain XXE flaws. An attacker could use this flaw to cause DoS, SSRF, or information disclosure if they are able to provide XML content for parsing. It was found that the JAXP implementation used in EAP 7.0 for XSLT processing is vulnerable to code injection. An attacker could use this flaw to cause remote code execution if they are able to provide XSLT content for parsing. An input validation vulnerability was found in Ansible's handling of data sent from client systems. An attacker with control over a client system being managed by Ansible, and the ability to send facts back to the Ansible server, could use this flaw to execute arbitrary code on the Ansible server using the Ansible server privileges. It was found that Intel® Ethernet Controller X710 family and Intel® Ethernet Controller XL710 family of products (aka Fortville) can possibly lock up and not receive any packets after a period of IPv6 fragment flood. A buffer overflow flaw was found in the way libsndfile handled FLAC files. This flaw could potentially be used to crash the application using libsndfile by tricking the application into processing specially crafted FLAC files. A buffer overflow flaw was found in the way libsndfile handled ID3 tags. This flaw could potentially be used to crash the application using libsndfile by tricking the application into processing specially crafted FLAC files. An integer overflow leading to a heap-buffer overflow was found in the libnl library. An attacker could use this flaw to cause an application compiled with libnl to crash or possibly execute arbitrary code in the context of the user running such an application. A NULL pointer dereference flaw was found in the way sblim-sfcb handled processing of POST requests to the /cimom URI. A remote attacker could use this flaw to cause a sblim-sfcb child process to crash via a specially crafted HTTP POST request. Incorrect error handling in the set_mempolicy() and mbind() compat syscalls in 'mm/mempolicy.c' in the Linux kernel allows local users to obtain sensitive information from uninitialized stack data by triggering failure of a certain bitmap operation. A vulnerability was found in crypto/ahash.c in the Linux kernel which allows attackers to cause a denial of service (API operation calling its own callback, and infinite recursion) by triggering EBUSY on a full queue. A denial of service flaw was found in the way BIND handled query requests when using DNS64 with "break-dnssec yes" option. A remote attacker could use this flaw to make named exit unexpectedly with an assertion failure via a specially crafted DNS request. A denial of service flaw was found in the way BIND handled a query response containing CNAME or DNAME resource records in an unusual order. A remote attacker could use this flaw to make named exit unexpectedly with an assertion failure via a specially crafted DNS response. A denial of service flaw was found in the way BIND processed control channel commands. A remote attacker with access to the BIND control channel could use this flaw to make named exit unexpectedly with an assertion failure via a specially crafted command. A vulnerability was discovered in Tomcat's handling of pipelined requests when "Sendfile" was used. If sendfile processing completed quickly, it was possible for the Processor to be added to the processor cache twice. This could lead to invalid responses or information disclosure. A vulnerability was discovered in tomcat. When running an untrusted application under a SecurityManager it was possible, under some circumstances, for that application to retain references to the request or response objects and thereby access and/or modify information associated with another web application. A buffer overflow flaw was found in the way minicom handled VT100 escape sequences. A malicious terminal device could potentially use this flaw to crash minicom, or execute arbitrary code in the context of the minicom process. It was found that spacewalk-channel can be used by a non-admin user or disabled users to perform administrative tasks due to an incorrect authorization check in backend/server/rhnChannel.py. An out-of-bounds write flaw was found in the way NSS performed certain Base64-decoding operations. An attacker could use this flaw to create a specially crafted certificate which, when parsed by NSS, could cause it to crash or execute arbitrary code, using the permissions of the user running an application compiled against the NSS library. An untrusted library search path flaw was found in the JCE component of OpenJDK. A local attacker could possibly use this flaw to cause a Java application using JCE to load an attacker-controlled library and hence escalate their privileges. It was discovered that the HTTP client implementation in the Networking component of OpenJDK could cache and re-use an NTLM authenticated connection in a different security context. A remote attacker could possibly use this flaw to make a Java application perform HTTP requests authenticated with credentials of a different user. A newline injection flaw was discovered in the SMTP client implementation in the Networking component in OpenJDK. A remote attacker could possibly use this flaw to manipulate SMTP connections established by a Java application. A newline injection flaw was discovered in the FTP client implementation in the Networking component in OpenJDK. A remote attacker could possibly use this flaw to manipulate FTP connections established by a Java application. It was discovered that the Security component of OpenJDK did not allow users to restrict the set of algorithms allowed for Jar integrity verification. This flaw could allow an attacker to modify content of the Jar file that used weak signing key or hash algorithm. It was found that the JAXP component of OpenJDK failed to correctly enforce parse tree size limits when parsing XML document. An attacker able to make a Java application parse a specially crafted XML document could use this flaw to make it consume an excessive amount of CPU and memory. A vulnerability was found in the Linux kernel where the keyctl_set_reqkey_keyring() function leaks the thread keyring. This allows an unprivileged local user to exhaust kernel memory and thus cause a DoS. An integer overflow flaw leading to a buffer overflow was found in the way MySQL parsed connection handshake packets. An unauthenticated remote attacker with access to the MySQL port could use this flaw to crash the mysqld daemon. An unbounded recursion flaw was found in the way Ruby handled regular expressions. A specially crafted regular expression could be used by an attacker to crash an Ruby application processing such crafted input. An out-of-bounds access issue was found in QEMU's Cirrus CLGD 54xx VGA Emulator support. The vulnerability could occur while copying VGA data using bitblt functions (for example, cirrus_bitblt_rop_fwd_transp_). A privileged user inside a guest could use this flaw to crash the QEMU process, resulting in denial of service. A double-free flaw was found in the way OpenCV handled processing of image files. This flaw could potentially be used to crash applications using OpenCV by tricking users into processing specially crafted image files. A denial of service flaw was found in the way OpenCV handled processing of image files. This flaw could potentially be used to crash applications using OpenCV by tricking users into processing specially crafted image files. An XXE vulnerability was found in Apache Batik which could allow a remote attacker to retrieve the files on the vulnerable server's filesystem by uploading specially crafted SVG images. The vulnerability could also allow a denial of service condition by performing an amplification attack. The NFS2/3 RPC client could send long arguments to the NFS server. These encoded arguments are stored in an array of memory pages, and accessed using pointer variables. Arbitrarily long arguments could make these pointers point outside the array and cause an out-of-bounds memory access. A remote user or program could use this flaw to crash the kernel, resulting in denial of service. It was found that when using remote logging with log4j socket server the log4j server would deserialize any log event received via TCP or UDP. An attacker could use this flaw to send a specially crafted log event that, during deserialization, would execute arbitrary code in the context of the logger application. The xfrm_migrate() function in the net/xfrm/xfrm_policy.c file in the Linux kernel built with CONFIG_XFRM_MIGRATE does not verify if the dir parameter is less than XFRM_POLICY_MAX. This allows a local attacker to cause a denial of service (out-of-bounds access) or possibly have unspecified other impact by sending a XFRM_MSG_MIGRATE netlink message. This flaw is present in the Linux kernel since an introduction of XFRM_MSG_MIGRATE in 2.6.21-rc1, up to 4.13-rc3. Ansible versions 2.2.3 and earlier are vulnerable to an information disclosure flaw due to the interaction of call back plugins and the no_log directive (information may not be sanitized properly). It was found that an information disclosure flaw in Bouncy Castle could enable a local malicious application to gain access to user's private information. An out-of-bounds write flaw was found in the way Libreoffice rendered certain documents containing Polygon images. By tricking a user into opening a specially crafted LibreOffice file, an attacker could possibly use this flaw to execute arbitrary code with the privileges of the user opening the file. A vulnerability was found in the International Components for Unicode (ICU). Specially crafted invalid utf-8 text, when parsed or manipulated using particular functions in libicu, could cause out-of-bounds heap reads and writes potentially leading to a crash, memory disclosure, or possibly code execution. An out-of-bounds r/w access issue was found in QEMU's Cirrus CLGD 54xx VGA Emulator support. The vulnerability could occur while copying VGA data via various bitblt functions. A privileged user inside a guest could use this flaw to crash the QEMU process or, potentially, execute arbitrary code on the host with privileges of the QEMU process. The mm subsystem in the Linux kernel through 4.10.10 does not properly enforce the CONFIG_STRICT_DEVMEM protection mechanism, which allows local users to read or write to kernel memory locations in the first megabyte (and bypass slab-allocation access restrictions) via an application that opens the /dev/mem file, related to arch/x86/mm/init.c and drivers/char/mem.c. It was discovered that the mysql and mysqldump tools did not correctly handle database and table names containing newline characters. A database user with privileges to create databases or tables could cause the mysql command to execute arbitrary shell or SQL commands while restoring database backup created using the mysqldump tool. It was discovered that the MySQL Connector/J client could deserialize certain database contents, regardless of the "autoDeserialize" option. If the client processes data received from an untrusted or compromised database server, a remote attacker could exploit this flaw to cause remote code execution. A flaw was found in the way Linux kernel allocates heap memory to build the scattergather list from a fragment list(skb_shinfo(skb)->frag_list) in the socket buffer(skb_buff). The heap overflow occurred if 'MAX_SKB_FRAGS + 1' parameter and 'NETIF_F_FRAGLIST' feature are both used together. A remote user or process could use this flaw to potentially escalate their privilege on a system. It was found that the Keycloak Node.js adapter did not handle invalid tokens correctly. An attacker could use this flaw to bypass authentication and gain access to restricted information, or to possibly conduct further attacks. It was found that a flaw exists in JAX-RS clients using the streaming approach for XML signatures and encryption, where it does not enforce the message to be signed/encrypted. This could allow an attacker to subvert the integrity of the message. It was found that the token cacher in Apache cxf uses a flawed way of caching tokens that are associated with the delegation token received from Security Token Service (STS). This vulnerability could allow an attacker to craft a token which could return an identifier corresponding to a cached token for another user. It was discovered that the mysql and mysqldump tools did not correctly handle database and table names containing newline characters. A database user with privileges to create databases or tables could cause the mysql command to execute arbitrary shell or SQL commands while restoring database backup created using the mysqldump tool. Context relabeling of filesystems is vulnerable to symbolic link attack, allowing a local, unprivileged malicious entity to change the SELinux context of an arbitrary file to a context with few restrictions. This only happens when the relabeling process is done, usually when taking SELinux state from disabled to enable (permissive or enforcing). It was found that ghostscript did not properly validate the parameters passed to the .rsdparams and .eqproc functions. During its execution, a specially crafted PostScript document could execute code in the context of the ghostscript process, bypassing the -dSAFER protection. The NFSv2 and NFSv3 server implementations in the Linux kernel through 4.10.13 lacked certain checks for the end of a buffer. A remote attacker could trigger a pointer-arithmetic error or possibly cause other unspecified impacts using crafted requests related to fs/nfsd/nfs3xdr.c and fs/nfsd/nfsxdr.c. Keberos 5 tickets being decoded when using the RXRPC keys incorrectly assumes the size of a field. This could lead to the size-remaining variable wrapping and the data pointer going over the end of the buffer. This could possibly lead to memory corruption and possible privilege escalation. An integer wraparound has been discovered in the Binary File Descriptor (BFD) library distributed in GNU Binutils up to version 2.30. An attacker could cause a crash by providing an ELF file with corrupted DWARF debug information. It was found that XStream contains a vulnerability that allows a maliciously crafted file to be parsed successfully which could cause an application crash. The crash occurs if the file that is being fed into XStream input stream contains an instances of the primitive type 'void'. An attacker could use this flaw to create a denial of service on the target system. It was found that kernel/events/core.c in the Linux kernel mishandles counter grouping, which allows local users to gain privileges via a crafted application, related to the perf_pmu_register and perf_event_open functions. A reference counter leak in Linux kernel in ipxitf_ioctl function was found which results in a use after free vulnerability that's triggerable from unprivileged userspace when IPX interface is configured. A flaw was found where authconfig could configure sssd in a way that treats existing and non-existing logins differently, leaking information on existence of a user. An attacker with physical or network access to the machine could enumerate users via a timing attack. It was found that some selectivity estimation functions did not check user privileges before providing information from pg_statistic, possibly leaking information. A non-administrative database user could use this flaw to steal some information from tables they are otherwise not allowed to access. It was discovered that the PostgreSQL client library (libpq) did not enforce the use of TLS/SSL for a connection to a PostgreSQL server when the PGREQUIRESSL environment variable was set. An man-in-the-middle attacker could use this flaw to strip the SSL/TLS protection from a connection between a client and a server. It was found that the pg_user_mappings view could disclose information about user mappings to a foreign database to non-administrative database users. A database user with USAGE privilege for this mapping could, when querying the view, obtain user mapping data, such as the username and password used to connect to the foreign database. It was found that due to the way rpcbind uses libtirpc (libntirpc), a memory leak can occur when parsing specially crafted XDR messages. An attacker sending thousands of messages to rpcbind could cause its memory usage to grow without bound, eventually causing it to be terminated by the OOM killer. A denial of service flaw was found in the way BIND handled DNSSEC validation. A remote attacker could use this flaw to make named exit unexpectedly with an assertion failure via a specially crafted DNS response. It was found that Node.js was using a non-randomized seed when populating hash tables. An attacker, able to supply a large number of inputs, could send specially crafted entries to the Node.js application, maximizing hash collisions to trigger an excessive amount of CPU usage, resulting in a denial of service. The regulator_ena_gpio_free function in drivers/regulator/core.c in the Linux kernel allows local users to gain privileges or cause a denial of service (use-after-free) via a crafted application. A privilege escalation flaw was found in the way kdelibs handled D-Bus messages. A local user could potentially use this flaw to gain root privileges by spoofing a callerID and leveraging a privileged helper application. The saa7164_bus_get function in drivers/media/pci/saa7164/saa7164-bus.c in the Linux kernel through 4.10.14 allows local users to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact by changing a certain sequence-number value, aka a "double fetch" vulnerability. An input validation flaw was found in Ansible, where it fails to properly mark lookup-plugin results as unsafe. If an attacker could control the results of lookup() calls, they could inject Unicode strings to be parsed by the jinja2 templating system, resulting in code execution. By default, the jinja2 templating language is now marked as 'unsafe' and is not evaluated. The dialog for creating cloud volumes (cinder provider) in CloudForms does not filter cloud tenants by user. An attacker with the ability to create storage volumes could use this to create storage volumes for any other tenant. The futex_requeue function in kernel/futex.c in the Linux kernel, before 4.14.15, might allow attackers to cause a denial of service (integer overflow) or possibly have unspecified other impacts by triggering a negative wake or requeue value. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. A remote code execution flaw was found in Samba. A malicious authenticated samba client, having write access to the samba share, could use this flaw to execute arbitrary code as root. A flaw was found in the way git-shell handled command-line options for the restricted set of git-shell commands. A remote, authenticated attacker could use this flaw to bypass git-shell restrictions, to view and manipulate files, by abusing the instance of the less command launched using crafted command-line options. A vulnerability was found in the Linux kernel where filesystems mounted with data=ordered mode may allow an attacker to read stale data from recently allocated blocks in new files after a system 'reset' by abusing ext4 mechanics of delayed allocation. The inet_csk_clone_lock function in net/ipv4/inet_connection_sock.c in the Linux kernel allows attackers to cause a denial of service (double free) or possibly have unspecified other impact by leveraging use of the accept system call. An unprivileged local user could use this flaw to induce kernel memory corruption on the system, leading to a crash. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. The edge_bulk_in_callback function in drivers/usb/serial/io_ti.c in the Linux kernel allows local users to obtain sensitive information (in the dmesg ringbuffer and syslog) from uninitialized kernel memory by using a crafted USB device (posing as an io_ti USB serial device) to trigger an integer underflow. It was found that rpm did not properly handle RPM installations when a destination path was a symbolic link to a directory, possibly changing ownership and permissions of an arbitrary directory, and RPM files being placed in an arbitrary destination. An attacker, with write access to a directory in which a subdirectory will be installed, could redirect that directory to an arbitrary location and gain root privilege. A vulnerability was found in the Linux kernel's lp_setup() function where it doesn't apply any bounds checking when passing "lp=none". This can result into overflow of the parport_nr[] array. An attacker with control over kernel command line can overwrite kernel code and data with fixed (0xff) values. A heap-based buffer overflow flaw was found within libtiff's tiff2pdf tool. A remote attacker could potentially exploit this flaw to execute arbitrary code by tricking a user into converting a specially crafted file using the tiff2pdf tool. A null pointer dereference flaw was found in the way NSS handled empty SSLv2 messages. An attacker could use this flaw to crash a server application compiled against the NSS library. It was found that the Red Hat JBoss EAP 7.0.5 implementation of javax.xml.transform.TransformerFactory is vulnerable to XXE. An attacker could use this flaw to launch DoS or SSRF attacks, or read files from the server where EAP is deployed. It was found that rpm uses temporary files with predictable names when installing an RPM. An attacker with ability to write in a directory where files will be installed could create symbolic links to an arbitrary location and modify content, and possibly permissions to arbitrary files, which could be used for denial of service or possibly privilege escalation. The IPv6 fragmentation implementation in the Linux kernel does not consider that the nexthdr field may be associated with an invalid option, which allows local users to cause a denial of service (out-of-bounds read and BUG) or possibly have unspecified other impact via crafted socket and send system calls. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. The IPv6 DCCP implementation in the Linux kernel mishandles inheritance, which allows local users to cause a denial of service or possibly have unspecified other impact via crafted system calls, a related issue to CVE-2017-8890. An unprivileged local user could use this flaw to induce kernel memory corruption on the system, leading to a crash. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. The sctp_v6_create_accept_sk function in net/sctp/ipv6.c in the Linux kernel mishandles inheritance, which allows local users to cause a denial of service or possibly have unspecified other impact via crafted system calls, a related issue to CVE-2017-8890. An unprivileged local user could use this flaw to induce kernel memory corruption on the system, leading to a crash. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. The tcp_v6_syn_recv_sock function in net/ipv6/tcp_ipv6.c in the Linux kernel mishandles inheritance, which allows local users to cause a denial of service or possibly have unspecified other impact via crafted system calls, a related issue to CVE-2017-8890. An unprivileged local user could use this flaw to induce kernel memory corruption on the system, leading to a crash. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. It was discovered that ImageMagick does not properly guarantee that initialized memory is used when reading RLE images. A remote attacker could possibly exploit this flaw to disclose potentially sensitive memory contents by, for example, tricking ImageMagick into converting a specially crafted RLE image into another format. A flaw was found in the way memory was being allocated on the stack for user space binaries. If heap (or different memory region) and stack memory regions were adjacent to each other, an attacker could use this flaw to jump over the stack guard gap, cause controlled memory corruption on process stack or the adjacent memory region, and thus increase their privileges on the system. This is glibc-side mitigation which blocks processing of LD_LIBRARY_PATH for programs running in secure-execution mode and reduces the number of allocations performed by the processing of LD_AUDIT, LD_PRELOAD, and LD_HWCAP_MASK, making successful exploitation of this issue more difficult. A flaw was found in the way sudo parsed tty information from the process status file in the proc filesystem. A local user with privileges to execute commands via sudo could use this flaw to escalate their privileges to root. The do_check function in kernel/bpf/verifier.c in the Linux kernel before 4.11.1 does not make the allow_ptr_leaks value available for restricting the output of the print_bpf_insn function, which allows local users to obtain sensitive address information via crafted bpf system calls. The crypto_skcipher_init_tfm function in crypto/skcipher.c in the Linux kernel through 4.11.2 relies on a setkey function that lacks a key-size check, which allows local users to cause a denial of service (NULL pointer dereference) via a crafted application. A denial of service vulnerability was discovered in ZooKeeper which allows an attacker to dramatically increase CPU utilization by abusing "wchp/wchc" commands, leading to the server being unable to serve legitimate requests. A carry propagation flaw was found in the implementation of the P-256 elliptic curve in golang. An attacker could possibly use this flaw to extract private keys when static ECDH was used. A vulnerability was discovered in spice server's protocol handling. An authenticated attacker could send specially crafted messages to the spice server, causing out-of-bounds memory accesses, leading to parts of server memory being leaked or a crash. A vulnerability was found in Jasypt that would allow an attacker to perform a timing attack on password hash comparison. A null pointer dereference flaw was found in the way GnuTLS processed ClientHello messages with status_request extension. A remote attacker could use this flaw to cause an application compiled with GnuTLS to crash. An input validation error was found in Red Hat Certificate System's handling of client provided certificates. If the certreq field is not present in a certificate an assertion error is triggered causing a denial of service. The __ip6_append_data function in net/ipv6/ip6_output.c in the Linux kernel through 4.11.3 is too late in checking whether an overwrite of an skb data structure may occur, which allows local users to cause a denial of service (system crash) via crafted system calls. An authentication bypass flaw was found in the way the EAP module in FreeRADIUS handled TLS session resumption. A remote unauthenticated attacker could potentially use this flaw to bypass the inner authentication check in FreeRADIUS by resuming an older unauthenticated TLS session. A double-free flaw was found in the way OpenLDAP's slapd server using the MDB backend handled LDAP searches. A remote attacker with access to search the directory could potentially use this flaw to crash slapd by issuing a specially crafted LDAP search query. An unsigned integer wrap around that led to a buffer over-read was found when parsing OFPT_QUEUE_GET_CONFIG_REPLY messages in Open vSwitch (OvS). An attacker could use this issue to cause a remote denial of service attack. While parsing an OpenFlow role status message Open vSwitch (OvS), a call to the abort() function for undefined role status reasons in the function 'ofp_print_role_status_message' in 'lib/ofp-print.c' could be misused for a remote denial of service attack by a malicious switch. A buffer over-read was found in the Open vSwitch (OvS) firewall implementation. This flaw can be triggered by parsing a specially crafted TCP, UDP, or IPv6 packet. A remote attack could use this flaw to cause a Denial of Service (DoS). A buffer over-read issue was found in Open vSwitch (OvS) which emerged while parsing the GroupMod OpenFlow messages sent from the controller. The issue could enable an attacker to cause a denial of service type of attack. It was found that RH-3scale AMP would permit creation of an access token without a client secret. An attacker could use this flaw to circumvent authentication controls and gain access to restricted APIs. A cross-site scripting (XSS) flaw was found in how the failed action entry is processed in Satellite 5. A user able to specify a failed action could exploit this flaw to perform XSS attacks against other Satellite users. It was found that Satellite 5 configured with SSL/TLS for the PostgreSQL backend failed to correctly validate X.509 server certificate host name fields. A man-in-the-middle attacker could use this flaw to spoof a PostgreSQL server using a specially crafted X.509 certificate. A denial of service flaw was found in the pcapng file parser in Wireshark. A remote network attacker could potentially use this flaw to crash Wireshark by tricking it into processing a crafted packet. It was found that the original fix for CVE-2017-1000367 was incomplete. A flaw was found in the way sudo parsed tty information from the process status file in the proc filesystem. A local user with privileges to execute commands via sudo could use this flaw to escalate their privileges to root. A vulnerability was discovered in the error page mechanism in Tomcat's DefaultServlet implementation. A crafted HTTP request could cause undesired side effects, possibly including the removal or replacement of the custom error page. A null pointer dereference was found in the way irssi handles DCC messages that do not contain a source nick/host. A malicious IRC server could be used to crash an irssi client by sending a specially crafted DCC message. An out-of-bound heap read was found in irssi's get_file_params_count() function, during the parsing of a DCC SEND request. An IRC client connected to the same IRC network as the target could send a specially crafted request that would force irssi to read 1 byte outside of an allocated string, which could, possibly, lead to an invalid memory read. A flaw was found in the way Samba handled dangling symlinks. An authenticated malicious Samba client could use this flaw to cause the smbd daemon to enter an infinite loop and use an excessive amount of CPU and memory. A flaw was found in the way "hg serve --stdio" command in Mercurial handled command-line options. A remote, authenticated attacker could use this flaw to execute arbitrary code on the Mercurial server by using specially crafted command-line options. Quick Emulator (QEMU) built with Network Block Device (NBD) Server support was vulnerable to a null-pointer dereference issue. The flaw could occur when releasing a client that was not initialized due to failed negotiation. A remote user or process could exploit this flaw to crash the qemu-nbd server (denial of service). It was found that loading a yaml format Databook from an untrusted source could lead to arbitrary code execution in python-tablib as the safe_load method was not used to load the content. A denial of service flaw was found in the way BIND handled processing of NSDNAME and NSIP rules. A remote attacker could use this flaw to make named enter an infinite loop by sending a specially crafted query, thus resulting in denial-of-service. A flaw was found in the way memory was being allocated on the stack for user space binaries. If heap (or different memory region) and stack memory regions were adjacent to each other, an attacker could use this flaw to jump over the stack guard gap, cause controlled memory corruption on process stack or the adjacent memory region, and thus increase their privileges on the system. This is a kernel-side mitigation which increases the stack guard gap size from one page to 1 MiB to make successful exploitation of this issue more difficult. It was found that KMail's Send Later with Delay function bypassed OpenPGP signing and encryption, causing the message to be sent unsigned and in plain-text. A remote attacker, with access to the user's network traffic, could potentially use this flaw to obtain sensitive information from the plain-text email messages. A SMTP command injection flaw was found in the way Ruby's Net::SMTP module handled CRLF sequences in certain SMTP commands. An attacker could potentially use this flaw to inject SMTP commands in a SMTP session in order to facilitate phishing attacks or spam campaigns. The Linux Kernel imposes a size restriction on the arguments and environmental strings passed through RLIMIT_STACK/RLIMIT_INFINITY, but does not take the argument and environment pointers into account, which allows attackers to bypass this limitation. A flaw was found in the Linux kernel's implementation of mapping ELF PIE binary loading to allow evasion of the stack-guard page protection mechanisms that intend to mitigate this behavior. The vmw_gb_surface_define_ioctl function (accessible via DRM_IOCTL_VMW_GB_SURFACE_CREATE) in drivers/gpu/drm/vmwgfx/vmwgfx_surface.c in the Linux kernel through 4.11.4 defines a backup_handle variable but does not give it an initial value. If one attempts to create a GB surface, with a previously allocated DMA buffer to be used as a backup buffer, the backup_handle variable does not get written to and is then later returned to user space, allowing local users to obtain sensitive information from uninitialized kernel memory via a crafted ioctl call. A vulnerability was discovered in Apache Thrift client libraries that allows remote, authenticated attackers to cause an infinite recursion via vectors involving the skip function; resulting in a denial of service (DoS) condition. A deserialization flaw was discovered in the jackson-databind which could allow an unauthenticated user to perform code execution by sending the maliciously crafted input to the readValue method of the ObjectMapper. It was discovered that the use of httpd's ap_get_basic_auth_pw() API function outside of the authentication phase could lead to authentication bypass. A remote attacker could possibly use this flaw to bypass required authentication if the API was used incorrectly by one of the modules used by httpd. A NULL pointer dereference flaw was found in the httpd's mod_ssl module. A remote attacker could use this flaw to cause an httpd child process to crash if another module used by httpd called a certain API function during the processing of an HTTPS request. A NULL pointer dereference flaw was found in the mod_http2 module of httpd. A remote attacker could use this flaw to cause httpd child process to crash via a specially crafted HTTP/2 request. A buffer over-read flaw was found in the httpd's ap_find_token() function. A remote attacker could use this flaw to cause httpd child process to crash via a specially crafted HTTP request. A buffer over-read flaw was found in the httpd's mod_mime module. A user permitted to modify httpd's MIME configuration could use this flaw to cause httpd child process to crash. It was found that the timer functionality in the Linux kernel ALSA subsystem is prone to a race condition between read and ioctl system call handlers, resulting in an uninitialized memory disclosure to user space. A local user could use this flaw to read information belonging to other users. An out-of-bounds write flaw was found in the way systemd-resolved daemon handled processing of DNS responses. A remote attacker could potentially use this flaw to crash the daemon or execute arbitrary code in the context of the daemon process. A flaw was found in the way the Linux KVM module processed the trap flag(TF) bit in EFLAGS during emulation of the syscall instruction, which leads to a debug exception(#DB) being raised in the guest stack. A user/process inside a guest could use this flaw to potentially escalate their privileges inside the guest. Linux guests are not affected by this. A race condition was found in the block multi queue subsystem of the Linux kernel. This may lead to a kernel panic or have another unknown side affect. A flaw was found in the way BIND handled TSIG authentication of AXFR requests. A remote attacker, able to communicate with an authoritative BIND server, could use this flaw to view the entire contents of a zone by sending a specially constructed request packet. Quick Emulator (QEMU) built with the Network Block Device (NBD) Server support is vulnerable to a crash via a SIGPIPE signal. The crash can occur if a client aborts a connection due to any failure during negotiation or read operation. A remote user/process could use this flaw to crash the qemu-nbd server resulting in a Denial of Service (DoS). A flaw was found in the way BIND handled TSIG authentication for dynamic updates. A remote attacker able to communicate with an authoritative BIND server could use this flaw to manipulate the contents of a zone, by forging a valid TSIG or SIG(0) signature for a dynamic update request. An immutability flaw was discovered in openstack-glance, where the glance-manage DB allows deleted image IDs to be reassigned. The flaw could be exploited to allow remote authenticated users to cause other users to boot into a malicious image without knowing it. It was found that the NFSv4 server in the Linux kernel did not properly validate layout type when processing NFSv4 pNFS LAYOUTGET and GETDEVICEINFO operands. A remote attacker could use this flaw to soft-lockup the system and thus cause denial of service. A stack-based buffer overflow was found in the poppler library. An attacker could create a malicious PDF file that would cause applications that use poppler (such as Evince) to crash, or potentially execute arbitrary code when opened. An integer overflow leading to heap-based buffer overflow was found in the poppler library. An attacker could create a malicious PDF file that would cause applications that use poppler (such as Evince) to crash, or potentially execute arbitrary code when opened. A denial of service flaw was found in the IPMI dissector in Wireshark. A remote network attacker could potentially use this flaw to crash Wireshark by tricking it into processing a crafted packet. The f2fs implementation in the Linux kernel, before 4.14, mishandles reference counts associated with f2fs_wait_discard_bios calls. This allows local users to cause a denial of service (BUG), as demonstrated by fstrim. A double-free flaw was found in the way libcdio handled processing of ISO files. An attacker could potentially use this flaw to crash applications using libcdio by tricking them into processing crafted ISO files. It was found that privilege check is missing when invoking arbitrary methods via filtering on VMs that MiqExpression will execute that is triggerable by API users. An attacker could use this to execute actions they should not be allowed to (e.g. destroying VMs). In drivers/net/ethernet/hisilicon/hns/hns_enet.c in the Linux kernel, before 4.13, local users can cause a denial of service (use-after-free and BUG) or possibly have unspecified other impact by leveraging differences in skb handling between hns_nic_net_xmit_hw and hns_nic_net_xmit. An out-of-bounds read and write flaw was found in the way FreeRADIUS server handled RADIUS packets. A remote attacker could use this flaw to crash the FreeRADIUS server by sending a specially crafted RADIUS packet. An out-of-bounds write flaw was found in the way FreeRADIUS server handled certain attributes in request packets. A remote attacker could use this flaw to crash the FreeRADIUS server or to execute arbitrary code in the context of the FreeRADIUS server process by sending a specially crafted request packet. A memory leak flaw was found in the way FreeRADIUS server handles decoding of DHCP packets. A remote attacker could use this flaw to cause the FreeRADIUS server to consume an increasing amount of memory resources over time possibly leading to a crash due to memory exhaustion. A memory leak flaw was found in the way FreeRADIUS server handles decoding of DHCP packets. A remote attacker could use this flaw to cause the FreeRADIUS server to consume an increasing amount of memory resources over time, possibly leading to a crash due to memory exhaustion, by sending specially crafted DHCP packets. An out-of-bounds read flaw was found in the way FreeRADIUS server handles decoding of DHCP packets. A remote attacker could use this flaw to crash the FreeRADIUS server by sending a specially crafted DHCP request. An out-of-bounds read flaw was found in the way FreeRADIUS server handled decoding of DHCP packets. A remote attacker could use this flaw to crash the FreeRADIUS server by sending a specially crafted DHCP request. An out-of-bounds write flaw was found in the way FreeRADIUS server handled certain attributes in request packets. A remote attacker could use this flaw to crash the FreeRADIUS server or to execute arbitrary code in the context of the FreeRADIUS server process by sending a specially crafted request packet. A denial of service flaw was found in the way FreeRADIUS server handled certain attributes in request packets. A remote attacker could use this flaw to cause the FreeRADIUS server to enter an infinite loop, consume increasing amounts of memory resources, and ultimately crash by sending a specially crafted request packet. An out-of-bounds read flaw was found in the way FreeRADIUS server handled decoding of DHCP packets. A remote attacker could use this flaw to crash the FreeRADIUS server by sending a specially crafted DHCP request. An out-of-bounds read flaw was found in the way FreeRADIUS server handled decoding of DHCP packets. A remote attacker could use this flaw to crash the FreeRADIUS server by sending a specially crafted DHCP request. A flaw within the processing of ranged HTTP requests has been discovered in the range filter module of nginx. A remote attacker could possibly exploit this flaw to disclose parts of the cache file header, or, if used in combination with third party modules, disclose potentially sensitive memory by sending specially crafted HTTP requests. It has been discovered that systemd-tmpfiles mishandles symbolic links present in non-terminal path components. In some configurations a local user could use this vulnerability to get access to arbitrary files when the systemd-tmpfiles command is run. A NULL pointer dereference flaw was found in the way patch processed patch files. An attacker could potentially use this flaw to crash patch by tricking it into processing crafted patches. An out-of-bounds read vulnerability was discovered in Quagga. A BGP peer could send a specially crafted message which would cause Quagga to read out of bounds, potentially causing a crash or disclosure of up to 64KB process memory to the peer. An integer wraparound, leading to heap-based out-of-bound read, was found in the way Exiv2 library reads ICC profiles embedded in a JP2 image. By persuading a victim to open a crafted JP2 image, a remote attacker could crash the application or possibly retrieve a portion of memory. It was found that evince did not properly sanitize the command line which is run to untar Comic Book Tar (CBT) files, thereby allowing command injection. A specially crafted CBT file, when opened by evince or evince-thumbnailer, could execute arbitrary commands in the context of the evince program. Sensu's redaction function fails to handle the redaction of sensitive data in deeply nested data structures, resulting in sensitive data, such as passwords, being logged in clear-text. A race condition was found in the Linux kernel, present since v3.14-rc1 through v4.12. The race happens between threads of inotify_handle_event() and vfs_rename() while running the rename operation against the same file. As a result of the race the next slab data or the slab's free list pointer can be corrupted with attacker-controlled data, which may lead to the privilege escalation. An input validation vulnerability exists in Openshift Enterprise due to a 1:1 mapping of tenants in Hawkular Metrics and projects/namespaces in OpenShift. If a user creates a project called "MyProject", and then later deletes it another user can then create a project called "MyProject" and access the metrics stored from the original "MyProject" instance. OpenShift Enterprise is vulnerable to a stored XSS via the log viewer for pods. The flaw is due to lack of sanitation of user input, specifically terminal escape characters, and the creation of clickable links automatically when viewing the log files for a pod. A use-after-free flaw was found in the Netlink functionality of the Linux kernel networking subsystem. Due to the insufficient cleanup in the mq_notify function, a local attacker could potentially use this flaw to escalate their privileges on the system. It was found that when the security manager's reflective permissions, which allows it to access the private members of the class, are granted to Hibernate Validator, a potential privilege escalation can occur. By allowing the calling code to access those private members without the permission an attacker may be able to validate an invalid instance and access the private member value via ConstraintViolation#getInvalidValue(). A denial-of-service flaw was found in the way gnome-session handled ICE connections. A local, authenticated attacker could potentially use this flaw to cause the gnome-session process to exhaust its file descriptors and enter an infinite loop, thereby leading to denial of service. It was discovered that the httpd's mod_auth_digest module did not properly initialize memory before using it when processing certain headers related to digest authentication. A remote attacker could possibly use this flaw to disclose potentially sensitive information or cause httpd child process to crash by sending specially crafted requests to a server. It was found that a mock CMC authentication plugin with a hardcoded secret was accidentally enabled by default in the pki-core package. An attacker could potentially use this flaw to bypass the regular authentication process and trick the CA server into issuing certificates. Subversion Plugin improperly checked permissions, requiring just Item/Build instead of Item/Configure when used. This allows a user to specify an attacker-controlled Subversion server which can then be used to collect credentials used by the Subversion plugin. The jenkins-plugin-pipeline-build-step fails to check permissions correctly allowing attackers with access to it to specify the triggering of any other project in Jenkins. This potentially gives an attacker access to projects they should not have access to. The Git Plugin can leak credentials (username and password) used to access a git repo if an attacker-supplied URL is provided to the plugin. To supply the URL to the plugin, the attacker would need to guess a username/password ID and then trick a developer into following a specific URL. The jenkins-plugin-script-security improperly whitelisted "DefaultGroovyMethods.putAt(Object, String, Object)" and "DefaultGroovyMethods.getAt(Object, String)" which allows attackers to bypass many restrictions and potentially trigger builds or access data they should not have access to. Exploitation of this requires the attacker to have access to the Jenkins instance, and for that Jenkins instance to be hosting other projects as well that the attacker should not have access to. The jenkins-plugin-script-security has incomplete sandbox protection which allows attackers to execute arbitrary code via constructors, instance variable initializers, and instance initializers in Pipeline scripts. Exploitation of this requires the attacker to have permission to configure Pipelines in Jenkins or be a trusted committers to repositories containing Jenkinsfiles and for that Jenkins instance to be hosting other projects as well that the attacker should not have access to. A cross-site scripting (XSS) flaw was found in how an organization name is displayed in Satellite 5. A user able to change an organization's name could exploit this flaw to perform XSS attacks against other Satellite users. A double-free flaw was found in the way the patch utility processed patch files. An attacker could potentially use this flaw to crash the patch utility by tricking it into processing crafted patches. A double-free vulnerability was found in Quagga. A BGP peer could send a specially crafted UPDATE message which would cause allocated blocks of memory to be free()d more than once, potentially leading to a crash or other issues. An integer underflow, leading to heap-based out-of-bound read, was found in the way Exiv2 library prints IPTC Photo Metadata embedded in an image. By persuading a victim to open a crafted image, a remote attacker could crash the application or possibly retrieve a portion of memory. It was found that authenticating to a PostgreSQL database account with an empty password was possible despite libpq's refusal to send an empty password. A remote attacker could potentially use this flaw to gain access to database accounts with empty passwords. An authorization flaw was found in the way PostgreSQL handled access to the pg_user_mappings view on foreign servers. A remote, authenticated attacker could potentially use this flaw to retrieve passwords from the user mappings defined by the foreign server owners without actually having the privileges to do so. An authorization flaw was found in the way PostgreSQL handled large objects. A remote, authenticated attacker with no privileges on a large object could potentially use this flaw to overwrite the entire content of the object, thus resulting in denial of service. A denial of service flaw was found in the SIGCOMP dissector in Wireshark. A remote network attacker could potentially use this flaw to crash Wireshark by tricking it into processing a crafted packet. A flaw was found in instack-undercloud where pre-install and security policy scripts used insecure temporary files. A local user could exploit this flaw to conduct a symbolic-link attack, allowing them to overwrite the contents of arbitrary files. fs/f2fs/extent_cache.c in the Linux kernel, before 4.13, mishandles extent trees. This allows local users to cause a denial of service via an application with multiple threads. A flaw was found in the way Ansible passed certain parameters to the jenkins_plugin module. A remote attacker could use this flaw to expose sensitive information from a remote host's logs. This flaw was fixed by not allowing passwords to be specified in the "params" argument, and noting this in the module documentation. In fs/ocfs2/cluster/nodemanager.c in the Linux kernel before 4.15, local users can cause a denial of service (NULL pointer dereference and BUG) because a required mutex is not used. A flaw was found in the Linux kernel's implementation of 32-bit syscall interface for bridging. This allowed a privileged user to arbitrarily write to a limited range of kernel memory. A flaw was found in the way 389-ds-base handled authentication attempts against locked accounts. A remote attacker could potentially use this flaw to continue password brute-forcing attacks against LDAP accounts, thereby bypassing the protection offered by the directory server's password lockout policy. A flaw was discovered in the file editor of millicore which allows files to be executed as well as created. An attacker could use this flaw to compromise other users or teams projects stored in source control management of the RHMAP Core installation. An integer overflow flaw, leading to assertion failure, was found in the way Varnish handled chunk sizes in HTTP requests. A remote attacker could use this flaw to make the Varnish daemon restart unexpectedly due to an assertion failure by sending a specially crafted HTTP request. A buffer overflow flaw leading to heap memory corruption was found in the shadow-utils's newusers utility. A local, authenticated attacker could potentially use this flaw to crash the newusers process by supplying crafted data to it. A flaw was found where the App Studio component of RHMAP 4.4 executes javascript provided by a user. An attacker could use this flaw to execute a stored XSS attack on an application administrator using App Studio. The external_request api call in App Studio (millicore) allows server side request forgery (SSRF). An attacker could use this flaw to probe the network internal resources and access restricted endpoints. A stack-based buffer overflow flaw was discovered within the HTTP processing of libsoup. A remote attacker could exploit this flaw to cause a crash or, potentially, execute arbitrary code by sending a specially crafted HTTP request to a server using the libsoup HTTP server functionality or by tricking a user into connecting to a malicious HTTP server with an application using the libsoup HTTP client functionality. A race condition issue was found in the way the raw packet socket implementation in the Linux kernel networking subsystem handled synchronization. A local user able to open a raw packet socket (requires the CAP_NET_RAW capability) could use this to waste resources in the kernel's ring buffer or possibly cause an out-of-bounds read on the heap leading to a system crash. An exploitable memory corruption flaw was found in the Linux kernel. The append path can be erroneously switched from UFO to non-UFO in ip_ufo_append_data() when building an UFO packet with MSG_MORE option. If unprivileged user namespaces are available, this flaw can be exploited to gain root privileges. A vulnerability was found in Quagga, in the log formatting code. Specially crafted messages sent by BGP peers could cause Quagga to read one element past the end of certain static arrays, causing arbitrary binary data to appear in the logs or potentially, a crash. A reachable assertion was found in Exiv2 while reading the header of a BigTIFF image. By persuading a victim to open a crafted BigTIFF image, a remote attacker could crash the application. A heap-based out-of-bounds read flaw was found in the way the patch utility parsed patch files. An attacker could potentially use this flaw to crash the patch utility by tricking it into processing crafted patch files. A shell command injection flaw related to the handling of "svn+ssh" URLs has been discovered in Subversion. An attacker could use this flaw to execute shell commands with the privileges of the user running the Subversion client, for example when performing a "checkout" or "update" action on a malicious repository, or a legitimate repository containing a malicious commit. A vulnerability was discovered in augeas affecting the handling of escaped strings. An attacker could send crafted strings that would cause the application using augeas to copy past the end of a buffer, leading to a crash or possible code execution. A shell command injection flaw related to the handling of "ssh" URLs has been discovered in Mercurial. This can be exploited to execute shell commands with the privileges of the user running the Mercurial client, for example, when performing a "checkout" or "update" action on a sub-repository within a malicious repository or a legitimate repository containing a malicious commit. It was found that hawtio contains a CSRF flaw that allows unrelated websites to perform actions as the authenticated user. Attackers could use this vulnerability to trick the user to visit his website that contains a malicious script which can be submitted to hawtio server on behalf of the user. A vulnerability was found in the way Mercurial handles path auditing and caches the results. An attacker could abuse a repository with a series of commits mixing symlinks and regular files/directories to trick Mercurial into writing outside of a given repository. A shell command injection flaw related to the handling of "ssh" URLs has been discovered in Git. An attacker could use this flaw to execute shell commands with the privileges of the user running the Git client, for example, when performing a "clone" action on a malicious repository or a legitimate repository containing a malicious commit. A vulnerability was discovered in Tomcat where the CORS Filter did not send a "Vary: Origin" HTTP header. This potentially allowed sensitive data to be leaked to other visitors through both client-side and server-side caches. It was found that foreman in Satellite 6 did not properly enforce access controls on certain resources. An attacker with access to the API and knowledge of the resource name can access resources in other organizations. A race condition was found in the Linux kernel before version 4.11-rc1 in 'fs/timerfd.c' file which allows a local user to cause a kernel list corruption or use-after-free via simultaneous operations with a file descriptor which leverage improper 'might_cancel' queuing. An unprivileged local user could use this flaw to cause a denial of service of the system. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. It was found that the sanity_check_raw_super() function in 'fs/f2fs/super.c' file in the Linux kernel before version 4.12-rc1 does not validate the f2fs filesystem segment count. This allows an unprivileged local user to cause a system panic and DoS. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. The sanity_check_ckpt function in fs/f2fs/super.c in the Linux kernel before version 4.12.4 does not validate the blkoff and segno arrays. This allows an unprivileged, local user to cause a system panic and DoS. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. A buffer overflow was found in the Linux kernel's isdn_net_newslave() function in the /drivers/isdn/i4l/isdn_net.c file. An overflow happens when the user-controlled buffer is copied into a local buffer of constant size using strcpy() without a length check. Multiple format string vulnerabilities were found in the zmq3 modules in rsyslog. A local attacker could potentially use these flaws to crash the rsyslog daemon under certain circumstances. An infinite loop vulnerability was discovered in Quagga. A BGP peer could send specially crafted packets that would cause the daemon to enter an infinite loop, denying service and consuming CPU until it is restarted. An integer wraparound, leading to heap-based out-of-bound read, was found in the way Exiv2 library prints Image File Directory(IFD) in TIFF images. By persuading a victim to open a crafted TIFF image, a remote attacker could crash the application or possibly retrieve a portion of memory. It was found that the fix for CVE-2017-2666 was incomplete and invalid characters are still allowed in the query string and path parameters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information from requests other than their own. A kernel data leak due to an out-of-bound read was found in the Linux kernel in inet_diag_msg_sctp{,l}addr_fill() and sctp_get_sctp_info() functions present since version 4.7-rc1 through version 4.13. A data leak happens when these functions fill in sockaddr data structures used to export socket's diagnostic information. As a result, up to 100 bytes of the slab data could be leaked to a userspace. It was found that string comparisons in .NET Core did not use a secure hashing algorithm. This could allow an attacker to predict string hashes and cause a denial of service by intentionally creating collisions thus forcing long look up times. It was discovered that the CORS Filter did not add an HTTP Vary header indicating that the response varies depending on Origin. This permitted client and server side cache poisoning in some circumstances. An unbounded recursion flaw leading to stack exhaustion was found in the way QPDF parsed PDF files. An attacker could potentially use this flaw to crash QPDF by tricking it into processing crafted PDF files. A flaw was found in the kernel's ACPI interpreter when it does not flush the operand cache and causes a kernel stack dump. This allows local users to obtain sensitive information from kernel memory and bypass the KASLR protection mechanism. The ACPI parsing functionality in the Linux kernel does not flush the node and node_ext caches which causes a kernel stack dump. This allows local users to obtain sensitive information from kernel memory and use this information to bypass the KASLR protection mechanism by creating and applying crafted ACPI table. A flaw was found in the Linux kernel's ACPI subsystem where a function does not flush the operand cache and causes a kernel stack dump. This allows local users to obtain sensitive information from kernel memory and bypass the KASLR protection mechanism when using a specially crafted ACPI table. A flaw was found in Tower's interface with SCM repositories. If a Tower project (SCM repository) definition does not have the 'delete before update' flag set, an attacker with commit access to the upstream playbook source repository could create a Trojan playbook that, when executed by Tower, modifies the checked out SCM repository to add git hooks. These git hooks could, in turn, cause arbitrary command and code execution as the user Tower runs as. An authentication bypass flaw was found in the way krb5's certauth interface handled the validation of client certificates. A remote attacker able to communicate with the KDC could potentially use this flaw to impersonate arbitrary principals under rare and erroneous circumstances. It was found that ljharb's qs module for Node.js did not properly parse query strings. An attacker could send a specially crafted query that overwrites the resulting object's prototype properties (such as toString() or hasOwnProperty()), resulting in a denial of service when the overwritten function would be executed. It was found that in the Linux kernel version 4.2-rc1 to 4.3-rc1, a use of uninitialized 'n_proto', 'ip_proto', and 'thoff' variables in __skb_flow_dissect() function can lead to a remote denial-of-service via malformed MPLS packet. A use-after-free issue was found in the Slirp networking implementation of the Quick emulator (QEMU). It occurs when a Socket referenced from multiple packets is freed while responding to a message. A user/process could use this flaw to crash the QEMU process on the host resulting in denial of service. It was found that the doFilter method in the ReadOnlyAccessFilter of the HTTP Invoker does not restrict classes for which it performs deserialization. This allows an attacker to execute arbitrary code via crafted serialized data. An out-of-bounds read access issue was found in the VGA display emulator built into the Quick emulator (QEMU). It could occur while reading VGA memory to update graphics display. A privileged user/process inside guest could use this flaw to crash the QEMU process on the host resulting in denial of service situation. An assert failure issue was found in the VGA display emulator built into the Quick emulator (QEMU). It could occur while updating graphics display, due to miscalculating region for dirty bitmap snapshot in split screen mode. A privileged user/process inside guest could use this flaw to crash the QEMU process on the host resulting in denial of service. A denial of service flaw was found in the NBAP dissector in Wireshark. A remote network attacker could potentially use this flaw to crash Wireshark by tricking it into processing a crafted packet. The blkcg_init_queue function in block/blk-cgroup.c in the Linux kernel, before 4.11, allows local users to cause a denial of service (double free) or possibly have unspecified other impact by triggering a creation failure. An integer overflow was discovered in the qla2x00_sysfs_write_optrom_ctl function in drivers/scsi/qla2xxx/qla_attr.c in the Linux kernel through 4.12.10. This flaw allows local users to cause a denial of service (memory corruption and system crash) by leveraging root access. A flaw was found in the implementation of CheckConfig method in handler_glfs.so of the tcmu-runner daemon. A local, non-root user with access to the D-Bus system bus could send a specially crafted string to CheckConfig method resulting in various kinds of segmentation fault. A NULL pointer dereference flaw was found in the UnregisterHandler method implemented in the tcmu-runner daemon. A local, non-root user with access to the D-Bus system bus could call UnregisterHandler method with non-existing tcmu handler as paramater to trigger DoS. A NULL pointer dereference flaw was found in the UnregisterHandler method implemented in the tcmu-runner daemon. A local, non-root user with access to the D-Bus system bus could call the UnregisterHandler method with the name of a handler loaded internally in tcmu-runner via dlopen() to trigger DoS. A file information leak flaw was found in implementation of the CheckConfig method in handler_qcow.so of the tcmu-runner daemon. A local, non-root user with access to the D-Bus system bus could use this flaw to leak arbitrary file names which might not be retrievable by non-root user. A buffer overflow vulnerability was found in the JSON extension of ruby. An attacker with the ability to pass a specially crafted JSON input to the extension could use this flaw to expose the interpreter's heap memory. It was found that rubygems did not sanitize gem names during installation of a given gem. A specially crafted gem could use this flaw to install files outside of the regular directory. It was found that rubygems could use an excessive amount of CPU while parsing a sufficiently long gem summary. A specially crafted gem from a gem repository could freeze gem commands attempting to parse its summary. A vulnerability was found where rubygems did not sanitize DNS responses when requesting the hostname of the rubygems server for a domain, via a _rubygems._tcp DNS SRV query. An attacker with the ability to manipulate DNS responses could direct the gem command towards a different domain. A vulnerability was found where rubygems did not properly sanitize gems' specification text. A specially crafted gem could interact with the terminal via the use of escape sequences. A divide-by-zero vulnerability was found in the __tcp_select_window function in the Linux kernel. This can result in a kernel panic causing a local denial of service. An unbounded recursion flaw leading to stack exhaustion was found in the way QPDF parsed PDF files. An attacker could potentially use this flaw to crash QPDF by tricking it into processing crafted QPDF files. A flaw was found in the way samba client used encryption with the max protocol set as SMB3. The connection could lose the requirement for signing and encrypting to any DFS redirects, allowing an attacker to read or alter the contents of the connection via a man-in-the-middle attack. The move_pages system call in mm/migrate.c in the Linux kernel doesn't check the effective uid of the target process. This enables a local attacker to learn the memory layout of a setuid executable allowing mitigation of ASLR. It was found that samba did not enforce "SMB signing" when certain configuration options were enabled. A remote attacker could launch a man-in-the-middle attack and retrieve information in plain-text. A flaw was found in the Struts REST plugin when using an outdated XStream library. An attacker could perform a denial of service attack using a malicious request with specially crafted XML payload. The REST Plugin in Apache Struts2 is using a XStreamHandler with an instance of XStream for deserialization without any type filtering which could lead to Remote Code Execution when deserializing XML payloads. An attacker could use this flaw to execute arbitrary code or conduct further attacks. Multiple flaws were found in the processing of translation tables in liblouis. An attacker could crash or potentially execute arbitrary code using malicious translation tables. It was found that the driver_override implementation in base/platform.c in the Linux kernel is susceptible to race condition when different threads are reading vs storing a different driver override. A flaw was found where the kernel truncated the value used to indicate the size of a buffer which it would later become zero using an untruncated value. This can corrupt memory outside of the original allocation. A resource-permission flaw was found in the openstack-tripleo-heat-templates package where ceph.client.openstack.keyring is created as world-readable. A local attacker with access to the key could read or modify data on Ceph cluster pools for OpenStack as though the attacker were the OpenStack service, thus potentially reading or modifying data in an OpenStack Block Storage volume. To exploit this flaw, the attacker must have local access to an overcloud node. However by default, access to overcloud nodes is restricted and accessible only from the management undercloud server on an internal network. Follow good security principles in your networking environment to ensure that network access is properly controlled. Quick Emulator (QEMU), compiled with the PC System Emulator with multiboot feature support, is vulnerable to an OOB r/w memory access issue. The issue could occur due to an integer overflow while loading a kernel image during a guest boot. A user or process could use this flaw to potentially achieve arbitrary code execution on a host. It was found that Freemarker in Struts would permit using read-only properties in value assignment of tag expressions. An attacker could use this to execute arbitrary code. It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session. An attacker could use this flaw to gain access to an authenticated user session, leading to possible information disclosure or further attacks. It was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh token pair from the authentication server, permitting indefinite usage in the case of permission revocation. An attacker on an already compromised resource could use this flaw to grant himself continued permissions and possibly conduct further attacks. it was found that keycloak would permit misuse of a client-side /etc/hosts entry to spoof a URL in a password reset request. An attacker could use this flaw to craft a malicious password reset request and gain a valid reset token, leading to information disclosure or further attacks. It was found that keycloak would accept a HOST header URL in the admin console and use it to determine web resource locations. An attacker could use this flaw against an authenticated user to attain reflected XSS via a malicious server. A stack-based out-of-bounds read flaw was found in the way QPDF parsed PDF files. An attacker could potentially use this flaw to crash QPDF, under certain conditions, by tricking it into processing crafted QPDF files. A stack buffer overflow flaw was found in the way the Bluetooth subsystem of the Linux kernel processed pending L2CAP configuration responses from a client. On systems with the stack protection feature enabled in the kernel (CONFIG_CC_STACKPROTECTOR=y, which is enabled on all architectures other than s390x and ppc64[le]), an unauthenticated attacker able to initiate a connection to a system via Bluetooth could use this flaw to crash the system. Due to the nature of the stack protection feature, code execution cannot be fully ruled out, although we believe it is unlikely. On systems without the stack protection feature (ppc64[le]; the Bluetooth modules are not built on s390x), an unauthenticated attacker able to initiate a connection to a system via Bluetooth could use this flaw to remotely execute arbitrary code on the system with ring 0 (kernel) privileges. An information-disclosure flaw was found in the bluetoothd implementation of the Service Discovery Protocol (SDP). A specially crafted Bluetooth device could, without prior pairing or user interaction, retrieve portions of the bluetoothd process memory, including potentially sensitive information such as Bluetooth encryption keys. A NULL pointer dereference was found in net/rds/rdma.c:__rds_rdma_map() function in the Linux kernel allowing local attackers to cause a system panic and a denial-of-service. A use-after-free flaw was found in the way httpd handled invalid and previously unregistered HTTP methods specified in the Limit directive used in an .htaccess file. A remote attacker could possibly use this flaw to disclose portions of the server memory, or cause httpd child process to crash. A flaw was discovered in the gdm where gdm greeter was no longer setting the ran_once boolean during autologin. If autologin was enable for a victim, an attacker could simply select 'login as another user' to unlock their screen. A vulnerability was found in tcpdump's verbose printing of packet data. A crafted pcap file or specially crafted network traffic could cause tcpdump to write out of bounds in the BSS segment, potentially causing tcpdump to display truncated or incorrectly decoded fields or crash with a segmentation violation. This does not affect tcpdump when used with the -w option to save a pcap file. It was discovered that Undertow processes http request headers with unusual whitespaces which can cause possible http request smuggling. A reachable assertion failure flaw was found in the Linux kernel built with KVM virtualisation(CONFIG_KVM) support with Virtual Function I/O feature (CONFIG_VFIO) enabled. This failure could occur if a malicious guest device sent a virtual interrupt (guest IRQ) with a larger (>1024) index value. An integer overflow flaw leading to heap-based out-of-bounds read was found in the way QPDF parsed PDF files. An attacker could potentially use this flaw to crash QPDF by tricking it into processing crafted QPDF files. OpenStack Nova has a vulnerability in the handling of encrypted volumes. By detaching and reattaching an encrypted volume, an attacker may access the underlying raw volume and corrupt the LUKS header, resulting in a denial of service attack on the compute host. All Nova installations supporting encrypted volumes are affected. A flaw was found in the way Postgresql allowed a user to modify the behavior of a query for other users. An attacker with a user account could use this flaw to execute code with the permissions of superuser in the database. A security flaw was discovered in nl80211_set_rekey_data() function in the Linux kernel since v3.1-rc1 through v4.13. This function does not check whether the required attributes are present in a netlink request. This request can be issued by a user with CAP_NET_ADMIN privilege and may result in NULL dereference and a system crash. An information leak flaw was found in the way SMB1 protocol was implemented by Samba. A malicious client could use this flaw to dump server memory contents to a file on the samba share or to a shared printer, though the exact area of server memory cannot be controlled by the attacker. Linux kernel built with the KVM visualization support (CONFIG_KVM), with nested visualization (nVMX) feature enabled (nested=1), is vulnerable to a crash due to disabled external interrupts. As L2 guest could access (r/w) hardware CR8 register of the host(L0). In a nested visualization setup, L2 guest user could use this flaw to potentially crash the host(L0) resulting in DoS. A flaw was found where the XFS filesystem code mishandles a user-settable inode flag in the Linux kernel prior to 4.14-rc1. This can cause a local denial of service via a kernel panic. In the Linux kernel, through 4.15.4, the floppy driver reveals the addresses of kernel functions and global variables using printk calls within the function show_floppy in drivers/block/floppy.c. An attacker can read this information from dmesg and use the addresses to find the locations of kernel code and data and bypass kernel security protections such as KASLR. It was found that properties based files of the management and the application realm configuration that contain user to role mapping are world readable allowing access to users and roles information to all the users logged in to the system. A new exploitation technique called key reinstallation attacks (KRACKs) affecting WPA2 has been discovered. A remote attacker within Wi-Fi range could exploit this attack to decrypt Wi-Fi traffic or possibly inject forged Wi-Fi packets by reinstalling a previously used pairwise key (PTK-TK) during a 4-way handshake. A new exploitation technique called key reinstallation attacks (KRACK) affecting WPA2 has been discovered. A remote attacker within Wi-Fi range could exploit this attack to decrypt Wi-Fi traffic or possibly inject forged Wi-Fi packets by reinstalling a previously used group key (GTK) during a 4-way handshake. A new exploitation technique called key reinstallation attacks (KRACK) affecting WPA2 has been discovered. A remote attacker within Wi-Fi range could exploit this attack to decrypt Wi-Fi traffic or possibly inject forged Wi-Fi packets by reinstalling a previously used group key (GTK) during a group key handshake. A new exploitation technique called key reinstallation attacks (KRACK) affecting WPA2 has been discovered. A remote attacker within Wi-Fi range could exploit this attack to decrypt Wi-Fi traffic or possibly inject forged Wi-Fi packets by reinstalling a previously used pairwise key (PTK-TK) by retransmitting Fast BSS Transition (FT) Reassociation Requests. It was found that the decode method of the OpenSSL::ASN1 module was vulnerable to buffer underrun. An attacker could pass a specially crafted string to the application in order to crash the ruby interpreter, causing a denial of service. A command injection flaw within the Emacs "enriched mode" handling has been discovered. By tricking an unsuspecting user into opening a specially crafted file using Emacs, a remote attacker could exploit this flaw to execute arbitrary commands with the privileges of the Emacs user. It was found that WEBrick did not sanitize all its log messages. If logs were printed in a terminal, an attacker could interact with the terminal via the use of escape sequences. A buffer underflow was found in ruby's sprintf function. An attacker, with ability to control its format string parameter, could send a specially crafted string that would disclose heap memory or crash the interpreter. The iscsi_if_rx() function in 'drivers/scsi/scsi_transport_iscsi.c' in the Linux kernel from v2.6.24-rc1 through 4.13.2 allows local users to cause a denial of service (a system panic) by making a number of certain syscalls by leveraging incorrect length validation in the kernel code. A heap write buffer overflow was found in perl's S_regatom() function, which is used in the compilation of regular expressions, resulting in the crash of the perl interpreter. An attacker, able to provide a specially crafted regular expression, could cause a denial of service. A heap buffer overread was found in perl's grok_bslash_N() function, which is used in the compilation of Unicode nodes in regular expressions, possibly leading to crash or dump of memory segments via the error output. An attacker, able to provide a specially crafted regular expression, could look for sensible information in the error message, or crash perl. A flaw was found in the way the Linux kernel loaded ELF executables. Provided that an application was built as Position Independent Executable (PIE), the loader could allow part of that application's data segment to map over the memory area reserved for its stack, potentially resulting in memory corruption. An unprivileged local user with access to SUID (or otherwise privileged) PIE binary could use this flaw to escalate their privileges on the system. A buffer overflow was discovered in tpacket_rcv() function in the Linux kernel since v4.6-rc1 through v4.13. A number of socket-related syscalls can be made to set up a configuration when each packet received by a network interface can cause writing up to 10 bytes to a kernel memory outside of a kernel buffer. This can cause unspecified kernel data corruption effects, including damage of in-memory and on-disk XFS data. Quick Emulator (QEMU), compiled with the PC System Emulator with multiboot feature support, is vulnerable to an OOB r/w memory access issue. The issue could occur while loading a kernel image during the guest boot, if mh_load_end_addr address is greater than the mh_bss_end_addr address. A user or process could use this flaw to potentially achieve arbitrary code execution on a host. An assertion failure issue was found in the Linux kernel's KVM hypervisor module built to support visualization on ARM64 architecture platforms. The failure could occur while accessing Performance Monitors Cycle Count Register (PMCCNTR) from a guest. A privileged guest user could use this flaw to crash the host kernel resulting in denial of service. It was found that IPA could disclose password hashes to users having the 'System: Read Stage Users' permission. A remote, authenticated attacker could potentially use this flaw to disclose the password hashes belonging to Stage Users. This security issue does not result in disclosure of password hashes belonging to active standard users. A regression was found in the Red Hat Enterprise Linux 6.9 version of httpd, causing comments in the "Allow" and "Deny" configuration lines to be parsed incorrectly. A web administrator could unintentionally allow any client to access a restricted HTTP resource. A vulnerability was discovered in Tomcat where if a servlet context was configured with readonly=false and HTTP PUT requests were allowed, an attacker could upload a JSP file to that context and achieve code execution. ALSA sequencer core initializes the event pool on demand by invoking snd_seq_pool_init() when the first write happens and the pool is empty. A user can reset the pool size manually via ioctl concurrently, and this may lead to UAF or out-of-bound access. An untrusted .desktop file with executable permission set could choose its displayed name and icon, and execute commands without warning when opened by the user. An attacker could use this flaw to trick a user into opening a .desktop file disguised as a document, such as a PDF, and execute arbitrary commands. A denial of service flaw was found in the way QPDF parsed PDF files. An attacker could potentially use this flaw to cause QPDF to enter an infinite loop by tricking it into processing crafted QPDF files. A vulnerability was discovered in Tomcat where if a servlet context was configured with readonly=false and HTTP PUT requests were allowed, an attacker could upload a JSP file to that context and achieve code execution. A stack buffer overflow flaw was found in the way dcraw handled processing of RAW image files. This flaw could potentially be used to crash the dcraw process by supplying it a specially crafted image file . A heap buffer overflow was found in dnsmasq in the code responsible for building DNS replies. An attacker could send crafted DNS packets to dnsmasq which would cause it to crash or, potentially, execute arbitrary code. A heap buffer overflow was discovered in dnsmasq in the IPv6 router advertisement (RA) handling code. An attacker on the local network segment could send crafted RAs to dnsmasq which would cause it to crash or, potentially, execute arbitrary code. This issue only affected configurations using one of these options: enable-ra, ra-only, slaac, ra-names, ra-advrouter, or ra-stateless. A stack buffer overflow was found in dnsmasq in the DHCPv6 code. An attacker on the local network could send a crafted DHCPv6 request to dnsmasq which would cause it to a crash or, potentially, execute arbitrary code. An information leak was found in dnsmasq in the DHCPv6 relay code. An attacker on the local network could send crafted DHCPv6 packets to dnsmasq causing it to forward the contents of process memory, potentially leaking sensitive data. A memory exhaustion flaw was found in dnsmasq in the EDNS0 code. An attacker could send crafted DNS packets which would trigger memory allocations which would never be freed, leading to unbounded memory consumption and eventually a crash. This issue only affected configurations using one of the options: add-mac, add-cpe-id, or add-subnet. An integer underflow flaw leading to a buffer over-read was found in dnsmasq in the EDNS0 code. An attacker could send crafted DNS packets to dnsmasq which would cause it to crash. This issue only affected configurations using one of the options: add-mac, add-cpe-id, or add-subnet. An integer underflow flaw leading to a buffer over-read was found in dnsmasq in the DNS code. An attacker could send crafted DNS packets to dnsmasq which would cause it to crash. The waitid implementation in kernel/exit.c in the Linux kernel through 4.13.4 accesses rusage data structures in unintended cases. This can allow local users to obtain sensitive information and bypass the KASLR protection mechanism via a crafted system call. A regular expression denial of service flaw was found in Tough-Cookie. An attacker able to make an application using Touch-Cookie to parse a sufficiently large HTTP request Cookie header could cause the application to consume an excessive amount of CPU. It was found that sssd's sysdb_search_user_by_upn_res() function did not sanitize requests when querying its local cache and was vulnerable to injection. In a centralized login environment, if a password hash was locally cached for a given user, an authenticated attacker could use this flaw to retrieve it. It was found that when Artemis and HornetQ are configured with UDP discovery and JGroups discovery a huge byte array is created when receiving an unexpected multicast message. This may result in a heap memory exhaustion, full GC, or OutOfMemoryError. A flaw was found in the Linux kernel's handling of signal frame on PowerPC systems. A malicious local user process could craft a signal frame allowing an attacker to corrupt memory. An arbitrary command execution flaw was found in the way Go's "go get" command handled the checkout of source code repositories. A remote attacker capable of hosting malicious repositories could potentially use this flaw to cause arbitrary command execution on the client side. It was found that smtp.PlainAuth authentication scheme in Go did not verify the TLS requirement properly. A remote man-in-the-middle attacker could potentially use this flaw to sniff SMTP credentials sent by a Go application. It was found that spring security uses Jackson's enableDefaultTyping() polymorphic capability for object deserialization. Jackson has already addressed this issue by blacklisting well-known gadget classes. However, under a right circumstances (e.g. an existence of an old JDK and vulnerable Jackson in classpath), an attacker could use this vulnerability to craft a malicious payload which would be deserialized by Jackson via spring security. This execution could potentially lead to remote code execution on the target machine. It was discovered that the jboss init script performed unsafe file handling which could result in local privilege escalation. An invalid free flaw was found in the way libvorbis handled processing of Ogg Vorbis format files. This flaw could potentially be used to crash an application using libvorbis by tricking the application into processing specially crafted files. An out-of-bounds read flaw was found in the way libvorbis handled processing of Ogg Vorbis format files. This flaw could potentially be used to crash an application using libvorbis by tricking the application into processing specially crafted files. The waitid implementation in upstream kernels did not restrict the target destination to copy information results. This can allow local users to write to otherwise protected kernel memory, which can lead to privilege escalation. It was found that in the Linux kernel through v4.14-rc5, bio_map_user_iov() and bio_unmap_user() in 'block/bio.c' do unbalanced pages refcounting if IO vector has small consecutive buffers belonging to the same page. bio_add_pc_page() merges them into one, but the page reference is never dropped, causing a memory leak and possible system lockup due to out-of-memory condition. A new exploitation technique called key reinstallation attacks (KRACK) affecting WPA2 has been discovered. A remote attacker within Wi-Fi range could exploit this attack to decrypt Wi-Fi traffic or possibly inject forged Wi-Fi packets by reinstalling a previously used Tunneled Direct-Link Setup (TDLS) Peerkey (TPK) key during a TDLS handshake. A new exploitation technique called key reinstallation attacks (KRACK) affecting WPA2 has been discovered. A remote attacker within Wi-Fi range could exploit this attack to decrypt Wi-Fi traffic or possibly inject forged Wi-Fi packets by reinstalling a previously used group key (GTK) during a Wireless Network Management (WNM) Sleep Mode handshake. A new exploitation technique called key reinstallation attacks (KRACK) affecting WPA2 has been discovered. A remote attacker within Wi-Fi range could exploit this attack to decrypt Wi-Fi traffic or possibly inject forged Wi-Fi packets by reinstalling a previously used integrity group key (IGTK) during a Wireless Network Management (WNM) Sleep Mode handshake. The sg_ioctl() function in 'drivers/scsi/sg.c' in the Linux kernel, from version 4.12-rc1 to 4.14-rc2, allows local users to obtain sensitive information from uninitialized kernel heap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for '/dev/sg0'. The Linux kernel built with the KVM visualization support (CONFIG_KVM), with nested visualization(nVMX) feature enabled (nested=1), was vulnerable to a stack buffer overflow issue. The vulnerability could occur while traversing guest page table entries to resolve guest virtual address(gva). An L1 guest could use this flaw to crash the host kernel resulting in denial of service (DoS) or potentially execute arbitrary code on the host to gain privileges on the system. A vulnerability was found where the rubygems module was vulnerable to an unsafe YAML deserialization when inspecting a gem. Applications inspecting gem files without installing them can be tricked to execute arbitrary code in the context of the ruby interpreter. A flaw was found in the CloudForms account configuration when using VMware. By default, a shared account is used that has privileged access to VMRC (VMWare Remote Console) functions that may not be appropriate for users of CloudForms (and thus this account). An attacker could use this vulnerability to view and make changes to settings in the VMRC and virtual machines controlled by it that they should not have access to. A vulnerability was found in the Key Management sub component of the Linux kernel, where when trying to issue a KEYTCL_READ on a negative key would lead to a NULL pointer dereference. A local attacker could use this flaw to crash the kernel. A flaw was found in the way spice-client processed certain messages sent from the server. An attacker, having control of malicious spice-server, could use this flaw to crash the client or execute arbitrary code with permissions of the user running the client. A flaw was found in the Linux kernel's implementation of associative arrays introduced in 3.13. This functionality was backported to the 3.10 kernels in Red Hat Enterprise Linux 7. The flaw involved a null pointer dereference in assoc_array_apply_edit() due to incorrect node-splitting in assoc_array implementation. This affects the keyring key type and thus key addition and link creation operations may cause the kernel to panic. A flaw was found in the implementation of associative arrays where the add_key systemcall and KEYCTL_UPDATE operations allowed for a NULL payload with a nonzero length. When accessing the payload within this length parameters value, an unprivileged user could trivially cause a NULL pointer dereference (kernel oops). Quick emulator (QEMU), compiled with the Cirrus CLGD 54xx VGA Emulator support, is vulnerable to an OOB write access issue. The issue could occur while writing to VGA memory via mode4and5 write functions. A privileged user inside guest could use this flaw to crash the QEMU process resulting in Denial of Serivce (DoS). It was found that Apache Lucene would accept an object from an unauthenticated user that could be manipulated through subsequent post requests. An attacker could use this flaw to assemble an object that could permit execution of arbitrary code if the server enabled Apache Solr's Config API. A memory leakage issue was found in the I/O channels websockets implementation of the Quick Emulator (QEMU). It could occur while sending screen updates to a client, which is slow to read and process them further. A privileged guest user could use this flaw to cause a denial of service on the host and/or potentially crash the QEMU process instance on the host. A use-after-free vulnerability was found when issuing an ioctl to a sound device. This could allow a user to exploit a race condition and create memory corruption or possibly privilege escalation. An attacker with knowledge of the given name used to authenticate and access Elasticsearch can later access it without the token, bypassing authentication. This attack also requires that the Elasticsearch be configured with an external route, and the data accessed is limited to the indices. It was discovered that the Kerberos client implementation in the Libraries component of OpenJDK used the sname field from the plain text part rather than encrypted part of the KDC reply message. A man-in-the-middle attacker could possibly use this flaw to impersonate Kerberos services to Java applications acting as Kerberos clients. This vulnerability allows containers using a secret, configMap, projected, or downwardAPI volume to trigger deletion of arbitrary files and directories on the nodes where they are running. An attacker could use this flaw to delete arbitrary file or directories on node host. A vulnerability was found in the key management subsystem of the Linux kernel. An update on an uninstantiated key could cause a kernel panic, leading to denial of service (DoS). It was found that the HttpURLConnection and HttpsURLConnection classes in the Networking component of OpenJDK failed to check for newline characters embedded in URLs. An attacker able to make a Java application perform an HTTP request using an attacker provided URL could possibly inject additional headers into the request. It was found that the FtpClient implementation in the Networking component of OpenJDK did not set connect and read timeouts by default. A malicious FTP server or a man-in-the-middle attacker could use this flaw to block execution of a Java application connecting to an FTP server. It was discovered that when using Digest authentication, the server does not ensure that the value of the URI in the authorization header matches the URI in the HTTP request line. This allows the attacker to execute a MITM attack and access the desired content on the server. It was discovered that the Security component of OpenJDK generated weak password-based encryption keys used to protect private keys stored in key stores. This made it easier to perform password guessing attacks to decrypt stored keys if an attacker could gain access to a key store. It was found that libpam4j did not properly validate user accounts when authenticating. A user with a valid password for a disabled account would be able to bypass security restrictions and possibly access sensitive information. A NULL pointer dereference flaw found in the way SoX handled processing of AIFF files. An attacker could potentially use this flaw to crash the SoX application by tricking it into processing crafted AIFF files. A use-after-free was found in the way Irssi, version 0.8.18 and later, handled out of order SASL messages sent by an IRC server. A remote attacker, who controls an IRC server, could crash the application by exploiting this flaw. An API-exposure flaw was found in cobbler, where it exported CobblerXMLRPCInterface private functions over XMLRPC. A remote, unauthenticated attacker could use this flaw to gain important privileges within cobbler, as well as upload files to an arbitrary location in the daemon context. An out-of-bounds heap read flaw was found in the way WavPack handled processing of DSD files. An attacker could potentially use this flaw to crash WavPack by tricking it into processing crafted DSD files. An incomplete fix for CVE-2018-5748 that affects QEMU monitor leading to a resource exhaustion but now also triggered via QEMU guest agent. A flaw was found in the netfilter/iptables subsystem. A user with the netfilter modification capabilities could insert a rule which could panic the system. The Linux kernel, before version 4.14.3, is vulnerable to a denial of service in drivers/md/dm.c:dm_get_from_kobject() which can be caused by local users leveraging a race condition with __dm_destroy() during creation and removal of DM devices. Only privileged local users (with CAP_SYS_ADMIN capability) can directly perform the ioctl operations for dm device creation and removal and this would typically be outside the direct control of the unprivileged attacker. It was discovered that the memcached connections using UDP transport protocol can be abused for efficient traffic amplification distributed denial of service (DDoS) attacks. A remote attacker could send a malicious UDP request using a spoofed source IP address of a target system to memcached, causing it to send a significantly larger response to the target. The resv_map_release function in mm/hugetlb.c in the Linux kernel, through 4.15.7, allows local users to cause a denial of service (BUG) via a crafted application that makes mmap system calls and has a large pgoff argument to the remap_file_pages system call. Improper input validation of the Openshift Routing configuration can cause an entire shard to be brought down. A malicious user can use this vulnerability to cause a Denial of Service attack for other users of the router shard. Memory leak in the sas_smp_get_phy_events function in drivers/scsi/libsas/sas_expander.c in the Linux kernel allows local users to cause a denial of service (kernel memory exhaustion) via multiple read accesses to files in the /sys/class/sas_phy directory. A flaw was found in ovirt-engine. When engine-backup was run with one of the options "--provision*db", the database username and password were logged in cleartext. Sharing the provisioning log might inadvertently leak database passwords. A race condition in the store_int_with_restart() function in arch/x86/kernel/cpu/mcheck/mce.c in the Linux kernel allows local users to cause a denial of service (panic) by leveraging root access to write to the check_interval file in a /sys/devices/system/machinecheck/machinecheck<cpu number> directory. The Linux kernel was found vulnerable to a NULL pointer dereference in the drivers/net/phy/mdio-bcm-unimac.c:unimac_mdio_probe() function caused by an unchecked return value from the platform_get_resource() function. A successful flaw exploitation can cause a system panic and a denial of service. This flaw is believed not to be an attacker triggerable as bad return value can be caused by hardware misconfiguration. An out of bounds read was found in function zzip_disk_fread of ZZIPlib, up to 0.13.68, when ZZIPlib mem_disk functionality is used. Remote attackers could leverage this vulnerability to cause a denial of service via a crafted zip file. A memory leak was found in unzip-mem.c and unzzip-mem.c of ZZIPlib, up to v0.13.68, that could lead to resource exhaustion. Local attackers could leverage this vulnerability to cause a denial of service via a crafted zip file. An out-of-bounds read vulnerability has been discovered in Exempi in the way it handles Extensible Metadata Platform (XMP) data in TIFF images. An attacker could cause a denial of service by convincing a user to open a crafted TIFF image file. Spacewalk includes an API endpoint that can be abused by attackers to execute an XXE (XML External Entity Reference) allowing for the disclosure of potentially sensitive information. It was found that the REST interface of the pcsd service did not properly sanitize the file name from the /remote/put_file query. If the /etc/booth directory exists, an authenticated attacker with write permissions could create or overwrite arbitrary files with arbitrary data outside of the /etc/booth directory, in the context of the pcsd process. It was found that all flows, including active and inactive, in the config datastore are installed back in the switch upon reconnection, as part of the node reconciliation process in OpenDayLight. This may lead to denial of service via table overflow or possibly circumventing of the controller's control. It was found that when acting as an SSH server, paramiko did not properly check whether authentication is completed before processing other requests. A customized SSH client could use this to bypass authentication when accessing any resources controlled by paramiko. An out of bounds write flaw was found in the processing of vorbis audio data. A maliciously crafted file or audio stream could cause the application to crash or, potentially, execute arbitrary code. A flaw was found in the Linux kernel that fs/ocfs2/aops.c omits use of a semaphore and consequently has a race condition for access to the extent tree during read operations in DIRECT mode. This allows local users to cause a denial of service by modifying a certain e_cpos field. OpenShift and Atomic Enterprise Ansible deploys a misconfigured etcd file that causes the SSL client certificate authentication to be disabled. Quotations around the values of ETCD_CLIENT_CERT_AUTH and ETCD_PEER_CLIENT_CERT_AUTH in etcd.conf result in etcd being configured to allow remote users to connect without any authentication if they can access the etcd server bound to the network on the master nodes. An attacker could use this flaw to read and modify all the data about the Openshift cluster in the etcd datastore, potentially adding another compute node, or bringing down the entire cluster. It was found that the REST interface of the pcsd service did not properly remove the pcs debug argument from the /run_pcs query, possibly disclosing sensitive information. A remote attacker with a valid token could use this flaw to elevate their privilege. An information exposure vulnerability has been found in NetworkManager when dnsmasq is used in DNS processing mode. An attacker in control of a DNS server could receive DNS queries even though a Virtual Private Network (VPN) was configured on the vulnerable machine. Incorrect buffer length handling was found in the ncp_read_kernel function in fs/ncpfs/ncplib_kernel.c in the Linux kernel, which could be exploited by malicious NCPFS servers to crash the kernel or possibly execute an arbitrary code. An infinite loop has been discovered in Exempi in the way it handles Extensible Metadata Platform (XMP) data in QuickTime files. An attacker could cause a denial of service via a crafted file. fs/f2fs/segment.c in the Linux kernel allows local users to cause a denial of service (NULL pointer dereference and panic) by using a noflush_merge option that triggers a NULL value for a flush_cmd_control data structure. A buffer overrun flaw was found in the IMAP handler of libcurl. By tricking an unsuspecting user into connecting to a malicious IMAP server, an attacker could exploit this flaw to potentially cause information disclosure or crash the application. A stack based buffer overflow was found in the get_matching_data() function, when reading the principal's certificate during pkinit preauthentication. If the Certifcate Authority's subject line is sufficiently long, an attacker able to have a specially crafted certificate signed could crash the authentication process, such as kinit, or, possibly, run arbitrary code. It was found that fanout_add() in 'net/packet/af_packet.c' in the Linux kernel, before version 4.13.6, allows local users to gain privileges via crafted system calls that trigger mishandling of packet_fanout data structures, because of a race condition (involving fanout_add and packet_do_bind) that leads to a use-after-free bug. It was found that the Hotrod client in Infinispan would unsafely read deserialized data on information from the cache. An authenticated attacker could inject a malicious object into the data cache and attain deserialization on the client, and possibly conduct further attacks. A stack-based buffer overflow when processing chunked, encoded HTTP responses was found in wget. By tricking an unsuspecting user into connecting to a malicious HTTP server, an attacker could exploit this flaw to potentially execute arbitrary code. A heap-based buffer overflow, when processing chunked encoded HTTP responses, was found in wget. By tricking an unsuspecting user into connecting to a malicious HTTP server, an attacker could exploit this flaw to potentially execute arbitrary code. It was discovered that the fix for CVE-2017-12151 was not properly shipped in erratum RHSA-2017:2858 for Red Hat Gluster Storage 3.3 for RHEL 6. It was discovered that the fix for CVE-2017-12150 was not properly shipped in erratum RHSA-2017:2858 for Red Hat Gluster Storage 3.3 for RHEL 6. It was discovered that the fix for CVE-2017-12163 was not properly shipped in erratum RHSA-2017:2858 for Red Hat Gluster Storage 3.3 for RHEL 6. An out-of-bounds array dereference was found in apr_time_exp_get(). An attacker could abuse an unvalidated usage of this function to cause a denial of service or potentially lead to data leak. A deserialization flaw was discovered in the jackson-databind which could allow an unauthenticated user to perform code execution by sending the maliciously crafted input to the readValue method of the ObjectMapper. This issue extends the previous flaw CVE-2017-7525 by blacklisting more classes that could be used maliciously. The KEYS subsystem in the Linux kernel before 4.13.10 does not correctly synchronize the actions of updating versus finding a key in the "negative" state to avoid a race condition, which allows local users to cause a denial of service or possibly have unspecified other impact via crafted system calls. The Linux kernel, before version 4.14.2, is vulnerable to a deadlock caused by fs/ocfs2/file.c:ocfs2_setattr(), as the function does not wait for DIO requests before locking the inode. This can be exploited by local users to cause a subsequent denial of service. It was found that the fix for CVE-2016-4993 was incomplete and Undertow web server is vulnerable to the injection of arbitrary HTTP headers, and also response splitting, due to insufficient sanitization and validation of user input before the input is used as part of an HTTP header value. A flaw was discovered in the Apache XML-RPC (ws-xmlrpc) library that deserializes untrusted data when enabledForExtensions setting is enabled. A remote attacker could use this vulnerability to execute arbitrary code via a crafted serialized Java object in a <ex:serializable> element. By rebuilding an instance using a new image, an authenticated user may be able to circumvent the Filter Scheduler, bypassing imposed filters (for example, the ImagePropertiesFilter or the IsolatedHostsFilter). It was found that vim applies the opened file read permissions to the swap file, overriding the process' umask. An attacker might search for vim swap files that were not deleted properly, in order to retrieve sensible data. It was found that emacs applies the opened file read permissions to the swap file, overriding the process' umask. An attacker might search for vim swap files, that were not deleted properly, in order to retrieve sensible data. Privilege escalation flaws were found in the initialization scripts of PostgreSQL. An attacker with access to the postgres user account could use these flaws to obtain root access on the server machine. Privilege escalation flaws were found in the Red Hat initialization scripts of PostgreSQL. An attacker with access to the postgres user account could use these flaws to obtain root access on the server machine. A denial of service flaw was found in the way the bgpd daemon in Quagga handled the processing of large BGP update messages. A remote, previously trusted attacker could potentially use this flaw to cause bgpd to terminate existing BGP sessions, thereby leading to denial of service. A security-check flaw was found in the way the Heketi server API handled user requests. An authenticated Heketi user could send specially crafted requests to the Heketi server, resulting in remote command execution as the user running Heketi server and possibly privilege escalation. An access flaw was found in heketi, where the heketi.json configuration file was world readable. An attacker having local access to the Heketi server could read plain-text passwords from the heketi.json file. An issue was discovered in newgidmap, in shadow-utils, that allows an unprivileged user to be placed in a user namespace where setgroups is permitted. An attacker could use this flaw to remove himself from a supplementary group, which may allow access to certain filesystem paths, if the administrator has used "group blacklisting" (e.g., chmod g-rwx) to restrict access to paths. An out-of-bounds read flaw was found in the way WavPack handled processing of CAF (Core Audio Format) files. An attacker could potentially use this flaw to crash WavPack by tricking it into processing crafted CAF files. A bug in the 32-bit compatibility layer of the ioctl handling code of the v4l2 video driver in the Linux kernel has been found. A memory protection mechanism ensuring that user-provided buffers always point to a userspace memory were disabled, allowing destination address to be in a kernel space. This flaw could be exploited by an attacker to overwrite a kernel memory from an unprivileged userspace process, leading to privilege escalation. The DPDK vhost-user interface does not check to verify that all the requested guest physical range is mapped and contiguous when performing Guest Physical Addresses to Host Virtual Addresses translations. This may lead to a malicious guest exposing vhost-user backend process memory. A vulnerability was found in Dnsmasq's implementation of DNSSEC. Wildcard synthesized NSEC records could be improperly interpreted to prove the non-existence of hostnames that actually exist. A flaw was found in the way unbound validated wildcard-synthesized NSEC records. An improperly validated wildcard NSEC record could be used to prove the non-existence (NXDOMAIN answer) of an existing wildcard record, or trick unbound into accepting a NODATA proof. The usb_serial_console_disconnect function in drivers/usb/serial/console.c in the Linux kernel, before 4.13.8, allows local users to cause a denial of service (use-after-free and system crash) or possibly have unspecified other impact via a crafted USB device, related to disconnection and failed setup. Firefox proxy settings can be bypassed by using the automount feature with autofs to create a mount point on the local file system. Content can be loaded from this mounted file system directly using a `file:` URI, bypassing configured proxy settings. This issue only affects OS X in default configuration; on Linux systems, autofs must also be installed for the vulnerability to occur. The cdc_parse_cdc_header() function in 'drivers/usb/core/message.c' in the Linux kernel, before 4.13.6, allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. The usb_get_bos_descriptor function in drivers/usb/core/config.c in the Linux kernel can allow a local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. The drivers/media/usb/dvb-usb-v2/lmedm04.c in the Linux kernel, through 4.13.11, allows local users to cause a denial of service (general protection fault and system crash) or possibly have unspecified other impact via a crafted USB device, related to a missing warm-start check and incorrect attach timing (dm04_lme2510_frontend_attach versus dm04_lme2510_tuner). The drivers/uwb/uwbd.c in the Linux kernel, before 4.13.6, allows local users to cause a denial of service (general protection fault and system crash) or possibly have unspecified other impact via a crafted USB device. The sound/usb/mixer.c in the Linux kernel, before 4.13.8, allows local users to cause a denial of service (snd_usb_mixer_interrupt use-after-free and system crash) or possibly have unspecified other impact via a crafted USB device. The sound/core/seq_device.c in the Linux kernel, before 4.13.4, allows local users to cause a denial of service (snd_rawmidi_dev_seq_free use-after-free and system crash) or possibly have unspecified other impact via a crafted USB device. The snd_usb_create_streams function in sound/usb/card.c in the Linux kernel, before 4.13.6, allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. The uas driver in the Linux kernel before 4.13.6 allows local users to cause a denial of service (out-of-bounds read and system crash), or possibly have unspecified other impacts via a crafted USB device, related to drivers/usb/storage/uas-detect.h and drivers/usb/storage/uas.c. The function drivers/usb/core/config.c in the Linux kernel, allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device, related to the USB_DT_INTERFACE_ASSOCIATION descriptor. The usbhid_parse function in drivers/hid/usbhid/hid-core.c in the Linux kernel, before 4.13.8, allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. A vulnerability was found in Nagios 4.2.4, and earlier, which allows local users to gain root privileges via a hard link attack on the Nagios init script file, related to CVE-2016-8641. A vulnerability was found in spring-ldap that allows an attacker to authenticate with an arbitrary password. When spring-ldap connected to some LDAP servers, when no additional attributes are bound, when using LDAP BindAuthenticator with org.springframework.ldap.core.support.DefaultTlsDirContextAuthenticationStrategy as the authentication strategy, and when setting userSearch, authentication is allowed with an arbitrary password when the username is correct. A missing fix for one stack-based buffer overflow in findTable() for CVE-2014-8184 was discovered. An attacker could cause denial of service or potentially allow arbitrary code execution. A vulnerability in Bluetooth pairing potentially allows an attacker with physical proximity (within 30 meters) to gain unauthorized access via an adjacent network, intercept traffic and send forged pairing messages between two vulnerable Bluetooth devices. This may result in information disclosure, elevation of privilege and/or denial of service. It was discovered that keycloak-httpd-client-install uses a predictable log file name in /tmp. A local attacker could create a symbolic link to a sensitive location, possibly causing data corruption or denial of service. In keycloak-http-client-install prior to version 0.8, the admin password could be provided through a command-line argument. This might result in the password being leaked through shell history, or becoming visible to a local attacker at the time the program is running. A use-after-free flaw was found in the way samba servers handled certain SMB1 requests. An unauthenticated attacker could send specially-crafted SMB1 requests to cause the server to crash or execute arbitrary code. A memory disclosure flaw was found in samba. An attacker could retrieve parts of server memory, which could contain potentially sensitive data, by sending specially-crafted requests to the samba server. A flaw was found in dotNET where the CORS attribute is not properly enforced or checked. An attacker could leverage this for possible remote execution. When libvirtd is configured by OSP director (tripleo-heat-templates) to use TLS transport, it defaults to the same certificate authority as all non-libvirtd services. As no additional authentication is configured, this allows these services to connect to libvirtd (which is equivalent to root access). If a vulnerability exists in another service it could, combined with this flaw, be exploited to escalate privileges to gain control over compute nodes. It was found that Apache Camel contains a security vulnerability via camel-castor component. An attacker can utilize this flaw to deserialize a malicious object on the target machine which could lead to Remote Code Execution (RCE). It was found that Apache Camel contains a security vulnerability via camel-hessian component. An attacker can utilize this flaw to deserialize a malicious object on the target machine which could lead to Remote Code Execution (RCE). A vulnerability was found in the Linux kernel when peeling off an association to the socket in another network namespace. All transports in this association are not to be rehashed and keep using the old key in hashtable, thus removing transports from hashtable when closing the socket, all transports are being freed. Later on a use-after-free issue could be caused when looking up an association and dereferencing the transports. A crash due to a NULL pointer dereference was found in Irssi when non-default configuration is used and the number of windows exceeds the available space. A heap-based buffer overflow flaw was found in procmail's formail utility. A remote attacker could send a specially crafted email that, when processed by formail, could cause formail to crash or, possibly, execute arbitrary code as the user running formail. A flaw was found in the Linux kernel's random number generator API. A null pointer dereference in the rngapi_reset function may result in denial of service, crashing the system. An out-of-bounds read flaw was found in the way fig2dev program in Xfig handled the processing of Fig format files. This flaw could potentially be used to crash the fig2dev program by tricking it into processing specially crafted Fig format files. It was found that the tab auto-completion feature of BusyBox did not sanitize filenames, leading to execution of arbitrary escape sequences in the terminal emulator. Exploitation of this flaw by an attacker could potentially result in code execution, arbitrary file writes, or other attacks under highly specific circumstances dependent on the usage of a vulnerable terminal emulator by the user. A flaw was found in the Linux kernel's client-side implementation of the cifs protocol. This flaw allows an attacker controlling the server to kernel panic a client which has the CIFS server mounted. A memory corruption flaw was found in the way MongoDB handled wire protocol compression for intra-cluster communication. A privileged network attacker could potentially use this flaw to crash the MongoDB server under certain circumstances. The parse_hid_report_descriptor function in drivers/input/tablet/gtco.c in the Linux kernel, before 4.13.11, allows local users to cause a denial of service (out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. The ims_pcu_get_cdc_union_desc function in drivers/input/misc/ims-pcu.c in the Linux kernel, through 4.13.11, allows local users to cause a denial of service (ims_pcu_parse_cdc_data out-of-bounds read and system crash) or possibly have unspecified other impact via a crafted USB device. The dvb frontend management subsystem in the Linux kernel contains a use-after-free which can allow a malicious user to write to memory that may be assigned to another kernel structure. This could create memory corruption, panic, or possibly other side affects. A double-free vulnerability was found in the csnmp_read_table function in the SNMP plugin of collectd. A network-based attacker could exploit this by sending malformed data, causing collectd to crash or possibly other impact. A flaw was found in the patches used to fix the 'dirtycow' vulnerability (CVE-2016-5195). An attacker, able to run local code, can exploit a race condition in transparent huge pages to modify usually read-only huge pages. A stack-based buffer overflow vulnerability was found in NBD server implementation in qemu allowing a client to request an export name of size up to 4096 bytes, which in fact should be limited to 256 bytes, allowing causing an out-of-bounds stack write in the qemu process. If NBD server requires TLS, the attacker cannot trigger the buffer overflow without first successfully negotiating TLS. The Network Block Device (NBD) server in Quick Emulator (QEMU), is vulnerable to a denial of service issue. It could occur if a client sent large option requests, making the server waste CPU time on reading up to 4GB per request. A client could use this flaw to keep the NBD server from serving other requests, resulting in DoS. An out of bound read was found in Irssi, version 0.8.7 and later, when dealing with malformed theme strings. An attacker could trigger the vulnerability by using specific nick names that could potentially cause a crash in the application. The Linux kernel is vulerable to a use-after-free flaw when Transformation User configuration interface(CONFIG_XFRM_USER) compile-time configuration were enabled. This vulnerability occurs while closing a xfrm netlink socket in xfrm_dump_policy_done. A user/process could abuse this flaw to potentially escalate their privileges on a system. A NULL pointer dereference flaw was found in RADOS Gateway HTTP request handling when using the Civetweb native webserver. An unauthenticated attacker could crash RADOS Gateway server by sending malicious HTTP requests. The walk_hugetlb_range() function in 'mm/pagewalk.c' file in the Linux kernel from v4.0-rc1 through v4.15-rc1 mishandles holes in hugetlb ranges. This allows local users to obtain sensitive information from uninitialized kernel memory via crafted use of the mincore() system call. A privacy flaw was discovered in Firefox. In Private Browsing mode, a web worker could write persistent data to IndexedDB, which was not cleared when exiting and would persist across multiple sessions. A malicious website could exploit the flaw to bypass private-browsing protections and uniquely fingerprint visitors. The mm_init function in kernel/fork.c in the Linux kernel before 4.12.10 does not clear the ->exe_file member of a new process's mm_struct, allowing a local attacker to achieve a use-after-free condition and to induce a kernel memory corruption on the system, leading to a crash or possibly have unspecified other impact by running a specially crafted program. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we feel it is unlikely. The init_new_context function in arch/x86/include/asm/mmu_context.h in the Linux kernel, before 4.12.10, does not correctly handle errors from LDT table allocation when forking a new process. This could allow a local attacker to achieve a use-after-free or possibly have unspecified other impact by running a specially crafted program. An industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of instructions (a commonly used performance optimization). There are three primary variants of the issue which differ in the way the speculative execution can be exploited. Variant CVE-2017-5753 triggers the speculative execution by performing a bounds-check bypass. It relies on the presence of a precisely-defined instruction sequence in the privileged code as well as the fact that memory accesses may cause allocation into the microprocessor's data cache even for speculatively executed instructions that never actually commit (retire). As a result, an unprivileged attacker could use this flaw to cross the syscall boundary and read privileged memory by conducting targeted cache side-channel attacks. An industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of instructions (a commonly used performance optimization). There are three primary variants of the issue which differ in the way the speculative execution can be exploited. Variant CVE-2017-5715 triggers the speculative execution by utilizing branch target injection. It relies on the presence of a precisely-defined instruction sequence in the privileged code as well as the fact that memory accesses may cause allocation into the microprocessor's data cache even for speculatively executed instructions that never actually commit (retire). As a result, an unprivileged attacker could use this flaw to cross the syscall and guest/host boundaries and read privileged memory by conducting targeted cache side-channel attacks. An industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of instructions (a commonly used performance optimization). There are three primary variants of the issue which differ in the way the speculative execution can be exploited. Variant CVE-2017-5754 relies on the fact that, on impacted microprocessors, during speculative execution of instruction permission faults, exception generation triggered by a faulting access is suppressed until the retirement of the whole instruction block. In a combination with the fact that memory accesses may populate the cache even when the block is being dropped and never committed (executed), an unprivileged local attacker could use this flaw to read privileged (kernel space) memory by conducting targeted cache side-channel attacks. Note: CVE-2017-5754 affects Intel x86-64 microprocessors. AMD x86-64 microprocessors are not affected by this issue. An invalid memory write flaw was found in the way OptiPNG handles processing of GIF files. This flaw could potentially be used to crash the OptiPNG program by tricking it into processing crafted GIF files. An integer overflow flaw leading to heap memory corruption was found in the way OptiPNG handles processing of TIFF files. This flaw could potentially be used to crash the OptiPNG program by tricking it into processing crafted TIFF files. An out-of-bound memory access flaw was found in the way dhclient processed a DHCP response packet. A malicious DHCP server could potentially use this flaw to crash dhclient processes running on DHCP client machines via a crafted DHCP response packet. Linux kernel Virtualization Module (CONFIG_KVM) for the Intel processor family (CONFIG_KVM_INTEL) is vulnerable to a DoS issue. It could occur if a guest was to flood the I/O port 0x80 with write requests. A guest user could use this flaw to crash the host kernel resulting in DoS. An erlang TLS server configured with cipher suites using RSA key exchange, may be vulnerable to an Adaptive Chosen Ciphertext attack (AKA Bleichenbacher attack) against RSA. This may result in plain-text recovery of encrypted messages and/or a man-in-the-middle (MiTM) attack, despite the attacker not having gained access to the server’s private key itself. A use-after-free vulnerability was found in DCCP socket code affecting the Linux kernel since 2.6.16. This vulnerability could allow an attacker to their escalate privileges. A non-privileged user is able to mount a fuse filesystem on RHEL 6 or 7 and crash a system if an application punches a hole in a file that does not end aligned to a page boundary. A NULL pointer dereference was found in Irssi when an "empty" nick joins a channel. A remote attacker, who can control an IRC server, could crash IRC clients by leveraging this vulnerability. A flaw was found in the processing of incoming L2CAP bluetooth commands. Uninitialized stack variables can be sent to an attacker leaking data in kernel address space. It was found that the Bluebooth Network Encapsulation Protocol (BNEP) implementation did not validate the type of second socket passed to the BNEPCONNADD ioctl(), which could lead to memory corruption. A local user with the CAP_NET_ADMIN capability can use this for denial of service (crash or data corruption) or possibly for privilege escalation. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we feel it is unlikely. It was discovered that MariaDB could replicate certain data definition language (DDL) commands to other cluster nodes despite an access control check failure. A user with an SQL access to the server could possibly use this flaw to perform database modification on certain cluster nodes without having privileges to perform such changes. A flaw was found in the way catastrophic backtracking was implemented in python's pop3lib's apop() method. An attacker could use this flaw to cause denial of service. It was found that mercurial was vulnerable to cross repositories modification. A specially crafted mercurial repository could trigger arbitrary commands on a client during commands such as clone or update. Apache Karaf uses the LDAPLoginModule to authenticate users to a directory via LDAP. It does not, however, encode usernames properly and hence is vulnerable to LDAP injection attacks. While it appears that it is not possible to exploit this vulnerability to allow an attacker to gain remote access, it does allow an attacker to insert special characters into the search query step. Therefore, it can potentially be exploited as part of a Denial of Service attack. It was found that the swap file created by vim when opening a file was using the user's primary group instead of the file's group. An attacker belonging to the victim's primary group could use this flaw to read the vim swap file. It was found that volume security can be sidestepped with innocent emptyDir and subpath. This could give an attacker with access to a pod full control over the node host by gaining access to docker socket. It was found that the pack() function in the 32-bit version of the perl interpreter was vulnerable to heap buffer overflow via the packing template. An attacker, able to provide a specially crafted template, could use this flaw to crash the interpreter. The usb_destroy_configuration() function, in 'drivers/usb/core/config.c' in the USB core subsystem, in the Linux kernel through 4.14.5 does not consider the maximum number of configurations and interfaces before attempting to release resources. This allows local users to cause a denial of service, due to out-of-bounds write access, or possibly have unspecified other impact via a crafted USB device. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. VNC server implementation in Quick Emulator (QEMU) was found to be vulnerable to an unbounded memory allocation issue, as it did not throttle the framebuffer updates sent to its client. If the client did not consume these updates, VNC server allocates growing memory to hold onto this data. A malicious remote VNC client could use this flaw to cause DoS to the server host. net/netfilter/xt_osf.c in the Linux kernel through 4.14.4 does not require the CAP_NET_ADMIN capability for add_callback and remove_callback operations. This allows local users to bypass intended access restrictions because the xt_osf_fingers data structure is shared across all network namespaces. The __netlink_deliver_tap_skb function in net/netlink/af_netlink.c in the Linux kernel, through 4.14.4, does not restrict observations of Netlink messages to a single net namespace, when CONFIG_NLMON is enabled. This allows local users to obtain sensitive information by leveraging the CAP_NET_ADMIN capability to sniff an nlmon interface for all Netlink activity on the system. The net/netfilter/nfnetlink_cthelper.c function in the Linux kernel through 4.14.4 does not require the CAP_NET_ADMIN capability for new, get, and del operations. This allows local users to bypass intended access restrictions because the nfnl_cthelper_list data structure is shared across all net namespaces. A flaw was found in the way catastrophic backtracking was implemented in python's difflib.IS_LINE_JUNK method. An attacker could use this flaw to cause denial of service. It was discovered that the Net::FTP module did not properly process filenames in combination with certain operations. A remote attacker could exploit this flaw to execute arbitrary commands by setting up a malicious FTP server and tricking a user or Ruby application into downloading files with specially crafted names using the Net::FTP module. A denial of service flaw was found in the way dhcpd handled reference counting when processing client requests. A malicious DHCP client could use this flaw to trigger a reference count overflow on the server side, potentially causing dhcpd to crash, by sending large amounts of traffic. A NULL pointer dereference flaw was found in the code responsible for saving hashtables of the zsh package. An attacker could use this flaw to cause a denial of service by crashing the user shell. An error in the "_sctp_make_chunk()" function (net/sctp/sm_make_chunk.c) when handling SCTP, packet length can be exploited by a malicious local user to cause a kernel crash and a DoS. A flaw was found in the Linux kernel's handling of fork failure when dealing with event messages in the userfaultfd code. Failure to fork correctly can create a fork event that will be removed from an already freed list of events. A flaw was found in the Linux kernel when freeing pages in hugetlbfs. This could trigger a local denial of service by crashing the kernel. A flaw was found in the Linux kernel where a local user with a shell account can abuse the userfaultfd syscall when using hugetlbfs. A missing size check in hugetlb_mcopy_atomic_pte could create an invalid inode variable, leading to a kernel panic. A flaw was found in the Linux kernel's implementation of raw_sendmsg allowing a local attacker to panic the kernel or possibly leak kernel addresses. A local attacker, with the privilege of creating raw sockets, can abuse a possible race condition when setting the socket option to allow the kernel to automatically create ip header values and thus potentially escalate their privileges. Linux kernel compiled with the KVM virtualization (CONFIG_KVM) support is vulnerable to an out-of-bounds read access issue. It could occur when emulating vmcall instructions invoked by a guest. A guest user/process could use this flaw to disclose kernel memory bytes. A flaw was found in CloudForms in the self-service UI snapshot feature where the name field is not properly sanitized for HTML and JavaScript input. An attacker could use this flaw to execute a stored XSS attack on an application administrator using CloudForms. Please note that CSP (Content Security Policy) prevents exploitation of this XSS however not all browsers support CSP. A command injection flaw was found in the way util-linux implements umount autocompletion in Bash. An attacker with the ability to mount a filesystem with custom mount points may execute arbitrary commands on behalf of the user who triggers the umount autocompletion. It was discovered that the snmp_pdu_parse() mishandles error codes and is vulnerable to a heap corruption within the parsing of the PDU prior to the authentication process. A remote, unauthenticated attacker could use this flaw to crash snmpd or, potentially, execute arbitrary code on the system with the privileges of the user running snmpd. A heap-based out-of-bounds access flaw was found in the way LibRaw processed images. An attacker could potentially use this flaw to crash applications using LibRaw by tricking them into processing crafted images. A stored XSS vulnerability was discovered in ovirt-engine 4.2. Sanitation of HTML elements was not applied correctly to all fields, shows in the management console. An attacker with VM Admin permissions could use this vulnerability to launch XSS attacks against other VM or Cluster administrators. The ovirt-engine web console login form returned different errors for non-existent users and invalid passwords, allowing an attacker to discover the names of valid user accounts. A flaw was found in ovirt-engine. When engine-setup was run and one chooses to provision the database manually or connect to a remote database, the password input was logged in cleartext during the verification step. Sharing the provisioning log might inadvertently leak database passwords. A heap buffer over read flaw was found in the way Perl regular expression engine handled inputs with invalid UTF-8 characters. An attacker able to provide a specially crafted input to be matched against a regular expression could cause Perl interpreter to crash or disclose portion of its memory. The __oom_reap_task_mm function in mm/oom_kill.c in the Linux kernel, before 4.14.4, mishandles gather operations. This allows attackers to cause a denial of service (TLB entry leak or use-after-free) or possibly have unspecified other impact by triggering a copy_to_user call within a certain time window. The "lazy_initialize" function in lib/resolv.rb did not properly process certain filenames. A remote attacker could possibly exploit this flaw to inject and execute arbitrary commands. A flaw was found in the Linux kernel where the swiotlb_print_info() function in lib/swiotlb.c allows local users to obtain some kernel address information by reading the kernel log (dmesg). This address is not useful to commit a further attack. The Salsa20 encryption algorithm in the Linux kernel, before 4.14.8, does not correctly handle zero-length inputs. This allows a local attacker the ability to use the AF_ALG-based skcipher interface to cause a denial of service (uninitialized-memory free and kernel crash) or have an unspecified other impact by executing a crafted sequence of system calls that use the blkcipher_walk API. Both the generic implementation (crypto/salsa20_generic.c) and x86 implementation (arch/x86/crypto/salsa20_glue.c) of Salsa20 are vulnerable. The HMAC implementation (crypto/hmac.c) in the Linux kernel, before 4.14.8, does not validate that the underlying cryptographic hash algorithm is unkeyed. This allows a local attacker, able to use the AF_ALG-based hash interface (CONFIG_CRYPTO_USER_API_HASH) and the SHA-3 hash algorithm (CONFIG_CRYPTO_SHA3), to cause a kernel stack buffer overflow by executing a crafted sequence of system calls that encounter a missing SHA-3 initialization. The KEYS subsystem in the Linux kernel omitted an access-control check when writing a key to the current task's default keyring, allowing a local user to bypass security checks to the keyring. This compromises the validity of the keyring for those who rely on it. An arbitrary memory r/w access issue was found in the Linux kernel compiled with the eBPF bpf(2) system call (CONFIG_BPF_SYSCALL) support. The issue could occur due to calculation errors in the eBPF verifier module, triggered by user supplied malicious BPF program. An unprivileged user could use this flaw to escalate their privileges on a system. Setting parameter "kernel.unprivileged_bpf_disabled=1" prevents such privilege escalation by restricting access to bpf(2) call. An arbitrary memory r/w access issue was found in the Linux kernel compiled with the eBPF bpf(2) system call (CONFIG_BPF_SYSCALL) support. The issue could occur due to calculation errors in the eBPF verifier module, triggered by user supplied malicious BPF program. An unprivileged user could use this flaw to escalate their privileges on a system. Setting parameter "kernel.unprivileged_bpf_disabled=1" prevents such privilege escalation by restricting access to bpf(2) call. A deserialization flaw was discovered in the jackson-databind which could allow an unauthenticated user to perform code execution by sending maliciously crafted input to the readValue method of ObjectMapper. This issue extends upon the previous flaws CVE-2017-7525 and CVE-2017-15095 by blacklisting more classes that could be used maliciously. A buffer overflow flaw was found in the zsh shell symbolic link resolver. A local, unprivileged user can create a specially crafted directory path which leads to a buffer overflow in the context of the user trying to do a symbolic link resolution in the aforementioned path. If the user affected is privileged, this leads to privilege escalation. The __munlock_pagevec function in mm/mlock.c in the Linux kernel, before 4.11.4, allows local users to cause a denial of service (NR_MLOCK accounting corruption) via crafted use of mlockall and munlockall system calls. An issue was discovered in the fd_locked_ioctl function in drivers/block/floppy.c in the Linux kernel. The floppy driver will copy a kernel pointer to user memory in response to the FDGETPRM ioctl. An attacker can send the FDGETPRM ioctl and use the obtained kernel pointer to discover the location of kernel code and data and bypass kernel security protections such as KASLR. A NULL pointer dereference flaw was found in the way LibRaw processed images. An attacker could potentially use this flaw to crash applications using LibRaw by tricking them into processing crafted images. A NULL pointer dereference flaw was found in the way libcurl checks values returned by the openldap ldap_get_attribute_ber() function. A malicious LDAP server could use this flaw to crash a libcurl client application via a specially crafted LDAP reply. The x86/fpu (Floating Point Unit) subsystem in the Linux kernel, when a processor supports the xsave feature but not the xsaves feature, does not correctly handle attempts to set reserved bits in the xstate header via the ptrace() or rt_sigreturn() system call. This allows local users to read the FPU registers of other processes on the system, related to arch/x86/kernel/fpu/regset.c and arch/x86/kernel/fpu/signal.c. The ovirt-engine API and administration web portal exposed Power Management credentials including cleartext passwords to Host Administrators. A Host Administrator could use this flaw to gain access to the power management systems of hosts they control. OpenDaylight Karaf 0.6.1-Carbon fails to clear the cache after a password change allowing the old password to be used until the Karaf cache is manually cleared (e.g. via restart). A vulnerability was found in the way RemoteMessageChannel, introduced in jboss-remoting versions 3.3.10.Final-redhat-1, reads from an empty buffer. An attacker could use this flaw to cause denial of service via high CPU caused by an infinite loop. The tcpmss_mangle_packet function in net/netfilter/xt_TCPMSS.c in the Linux kernel before 4.11, and 4.9.x before 4.9.36, allows remote attackers to cause a denial of service (use-after-free and memory corruption) or possibly have unspecified other impact by leveraging the presence of xt_TCPMSS in an iptables action. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. A use-after-free fault in the Linux kernel's usbtv driver could allow an attacker to cause a denial of service (system crash), or have unspecified other impacts, by triggering failure of audio registration of USB hardware using the usbtv kernel module. A use-after-free vulnerability was found in a network namespaces code affecting the Linux kernel since v4.0-rc1 through v4.15-rc5. The function get_net_ns_by_id() does not check for the net::count value after it has found a peer network in netns_ids idr which could lead to double free and memory corruption. This vulnerability could allow an unprivileged local user to induce kernel memory corruption on the system, leading to a crash. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although it is thought to be unlikely. A denial of service flaw was found in dovecot. An attacker able to generate random SNI server names could exploit TLS SNI configuration lookups, leading to excessive memory usage and the process to restart. It was found that the system umask policy is not being honored when creating XDG user directories (~/Desktop etc) on first login. This could lead to user's files being inadvertently exposed to other local users. Aborting the process of SASL authentication can lead to a memory leak when the same login processes are reused. An attacker could use this flaw to cause a denial of service due to memory exhaustion. A heap buffer write overflow, with control over the bytes written, was found in the way regular expressions employing Unicode rules are compiled. An attacker, with the ability to provide a specially crafted regular expression, could crash the perl interpreter, or possibly execute arbitrary code. An information-exposure flaw was found in the Linux kernel where the pcpu_embed_first_chunk() function in mm/percpu.c allows local users to obtain kernel-object address information by reading the kernel log (dmesg). However, this address is not static and cannot be used to commit a further attack. In the Linux kernel through 4.14.13, the rds_message_alloc_sgs() function does not validate a value that is used during DMA page allocation, leading to a heap-based out-of-bounds write (related to the rds_rdma_extra_size() function in 'net/rds/rdma.c') and thus to a system panic. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. In the Linux kernel through 4.14.13, the rds_cmsg_atomic() function in 'net/rds/rdma.c' mishandles cases where page pinning fails or an invalid address is supplied by a user. This can lead to a NULL pointer dereference in rds_atomic_free_op() and thus to a system panic. A flaw was found in the Linux kernel's handling of loopback devices. An attacker, who has permissions to setup loopback disks, may create a denial of service or other unspecified actions. A NULL pointer dereference flaw was found in the code responsible for the cd builtin command of the zsh package. An attacker could use this flaw to cause a denial of service by crashing the user shell. It was discovered that multiple encryption key classes in the Libraries component of OpenJDK did not properly synchronize access to their internal data. This could possibly cause a multi-threaded Java application to apply weak encryption to data because of the use of a key that was zeroed out. It was discovered that the LDAP component of OpenJDK failed to properly encode special characters in user names when adding them to an LDAP search query. A remote attacker could possibly use this flaw to manipulate LDAP queries performed by the LdapLoginModule class. A stack buffer overflow flaw was found in the way 389-ds-base handled certain LDAP search filters. A remote, unauthenticated attacker could potentially use this flaw to make ns-slapd crash via a specially crafted LDAP request, thus resulting in denial of service. It was discovered that the I18n component of OpenJDK could use an untrusted search path when loading resource bundle classes. A local attacker could possibly use this flaw to execute arbitrary code as another local user by making their Java application load an attacker controlled class file. It was discovered that the DNS client implementation in the JNDI component of OpenJDK did not use random source ports when sending out DNS queries. This could make it easier for a remote attacker to spoof responses to those queries. It was discovered that the Libraries component of OpenJDK failed to sufficiently limit the amount of memory allocated when reading DER encoded input. A remote attacker could possibly use this flaw to make a Java application use an excessive amount of memory if it parsed attacker supplied DER encoded input. It was discovered that the JGSS component of OpenJDK failed to properly handle GSS context in the native GSS library wrapper in certain cases. A remote attacker could possibly make a Java application using JGSS to use a previously freed context. An out-of-bounds read access issue was found in the VGA emulator of QEMU. It could occur in vga_draw_text routine, while updating display area for a vnc client. A privileged user inside a guest could use this flaw to crash the QEMU process resulting in DoS. A race condition was found in systemd. This could result in automount requests not being serviced and processes using them could hang, causing denial of service. It was discovered that the key agreement implementations in the JCE component of OpenJDK did not guarantee sufficient strength of used keys to adequately protect generated shared secret. This could make it easier to break data encryption by attacking key agreement rather than the encryption using the negotiated secret. It was found that the DHCP daemon did not properly clean up closed OMAPI connections in certain cases. A remote attacker able to connect to the OMAPI port could use this flaw to exhaust file descriptors in the DHCP daemon, leading to a denial of service in the OMAPI functionality. A use-after-free flaw leading to denial of service was found in the way BIND internally handled cleanup operations on upstream recursion fetch contexts. A remote attacker could potentially use this flaw to make named, acting as a DNSSEC validating resolver, exit unexpectedly with an assertion failure via a specially crafted DNS request. The JGSS component of OpenJDK ignores the value of the javax.security.auth.useSubjectCredsOnly property when using HTTP/SPNEGO authentication and always uses global credentials. It was discovered that this could cause global credentials to be unexpectedly used by an untrusted Java application. It was discovered that the JMX component of OpenJDK failed to properly set the deserialization filter for the SingleEntryRegistry in certain cases. A remote attacker could possibly use this flaw to bypass intended deserialization restrictions. It was discovered that the LDAPCertStore class in the JNDI component of OpenJDK failed to securely handle LDAP referrals. An attacker could possibly use this flaw to make it fetch attacker controlled certificate data. The tcp_v6_syn_recv_sock function in net/ipv6/tcp_ipv6.c in the Linux kernel, through 4.14.11, allows attackers to cause a denial of service (slab out-of-bounds write) or possibly have unspecified other impact via vectors involving in-kernel TLS implementation. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. A flaw was found in the Linux kernel's skcipher component, which affects the skcipher_recvmsg function. Attackers using a specific input can lead to a privilege escalation. Multiple "expired" flows consume memory resources of CONFIG DS which leads to Controller shutdown. In the Linux kernel versions 4.12, 3.10, 2.6, and possibly earlier, a race condition vulnerability exists in the sound system allowing for a potential deadlock and memory corruption due to use-after-free condition and thus denial of service. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. It was found that 389-ds-base did not always handle internal hash comparison operations correctly during the authentication process. A remote, unauthenticated attacker could potentially use this flaw to bypass the authentication process under very rare and specific circumstances. An out-of-bound access, and a possible memory corruption vulnerability leading to a system crash, was found in the Linux kernel in the Bluetooth subsystem. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although it is unlikely. An unbounded recursion flaw was found in the way Exiv2 handled certain image files. An attacker could potentially use this flaw to crash the exiv2 CLI utility program by tricking it into processing crafted input files. It was found that curl and libcurl might send their Authentication header to a third party HTTP server upon receiving an HTTP REDIRECT reply. This could leak authentication token to external entities. A cross-site scripting (XSS) flaw was found in mailman. An attacker, able to trick the user into visiting a specific URL, can execute arbitrary web scripts on the user's side and force the victim to perform unintended actions. A path traversal vulnerability was discovered in Undertow's org.wildfly.extension.undertow.deployment.ServletResourceManager.getResource method. This could lead to information disclosure of arbitrary local files. A deserialization flaw was discovered in the jackson-databind that could allow an unauthenticated user to perform code execution by sending the maliciously crafted input to the readValue method of the ObjectMapper. This issue extends the previous flaws CVE-2017-7525 and CVE-2017-17485 by blacklisting more classes that could be used maliciously. A denial of service flaw was found in miekg-dns before 1.0.4. A remote attacker could use carefully timed TCP packets to block the DNS server from accepting new connections. A null pointer dereference flaw was found in Samba RPC external printer service. An attacker could use this flaw to cause the printer spooler service to crash. crypto/pcrypt.c in the Linux kernel, before 4.14.13, mishandles freeing instances, allowing a local user able to access the AF_ALG-based AEAD interface (CONFIG_CRYPTO_USER_API_AEAD) and pcrypt (CONFIG_CRYPTO_PCRYPT) to cause a denial of service (kfree of an incorrect pointer) or possibly have unspecified other impact by executing a crafted sequence of system calls. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. A memory disclosure vulnerability in table partitioning was found in postgresql, allowing an authenticated attacker to read arbitrary bytes of server memory via purpose-crafted insert to a partitioned table. pg_upgrade creates file in current working directory containing the output of `pg_dumpall -g` under umask which was in effect when the user invoked pg_upgrade, and not under 0077 which is normally used for other temporary files. This can allow an authenticated attacker to read or modify the file, which may contain encrypted or unencrypted database passwords. The attack is unfeasible if a directory mode blocks the attacker searching the current working directory or if the prevailing umask blocks the attacker opening the file. The acpi_smbus_hc_add function in drivers/acpi/sbshc.c in the Linux kernel, through 4.14.15, allows local users to obtain sensitive address information by reading dmesg data from an SBS HC printk call. A flaw was found in the Linux kernel's implementation of i8042 serial ports. An attacker could cause a kernel panic if they are able to add and remove devices as the module is loaded. An out-of-bounds memory read flaw was found in the way 389-ds-base handled certain LDAP search filters. A remote, unauthenticated attacker could potentially use this flaw to make ns-slapd crash via a specially crafted LDAP request, thus resulting in denial of service. When registering a system with Satellite 6 a hostname must be specified. if an additional system is registered with the same hostname, the original system will stop receiving updates from Satellite 6. An attacker with administrative privileges to add systems to a Satellite 6 server could exploit this to prevent other hosts from getting security updates. In the function sbusfb_ioctl_helper() in drivers/video/fbdev/sbuslib.c in the Linux kernel, up to and including 4.15, an integer signedness error allows arbitrary information leakage for the FBIOPUTCMAP_SPARC and FBIOGETCMAP_SPARC commands. An unaligned memory access bug was found in the way ZZIPlib handled ZIP files. This flaw could potentially be used to crash the application using ZZIPlib by tricking the application into processing specially crafted ZIP files. The "stub_send_ret_submit()" function (drivers/usb/usbip/stub_tx.c) in the Linux kernel can allow an attacker to cause a denial of service (NULL pointer dereference) via a specially crafted USB over IP packet. Improper validation in the bnx2x network card driver of the Linux kernel version 4.15 can allow for denial of service (DoS) attacks via a packet with a gso_size larger than ~9700 bytes. Untrusted guest VMs can exploit this vulnerability in the host machine, causing a crash in the network card. It was found that the Git client printed server-sent ANSI escape codes to the terminal without any sanitization, leading to execution of arbitrary escape sequences in the terminal emulator. Exploitation of this flaw by a MitM attacker could potentially result in code execution, arbitrary file writes, or other attacks under highly specific circumstances dependent on the usage of a vulnerable terminal emulator by the user. The usbip/vhci_sysfs.c:port_show_vhci() in the vhci_hcd driver of the Linux kernel, before version 4.14.8 and 4.4.114, allows local attackers to disclose kernel memory addresses. Successful exploitation requires that a USB device is attached over IP. An out-of-bounds read in drivers/usb/usbip/stub_rx.c:get_pipe() of the Linux Kernel before version 4.14.8, 4.9.71, and 4.4.114 allows attackers to cause a denial of service (out-of-bounds read) via a specially crafted USB over IP packet. Improper input validation in drivers/usb/usbip/stub_rx.c:stub_recv_cmd_submit() in the Linux kernel, when handling CMD_SUBMIT packets, allows attackers to cause a denial of service (arbitrary memory allocation) via a specially crafted USB over IP packet. It was found that flatpak's D-Bus proxy did not properly filter the access to D-Bus during the authentication protocol. A specially crafted flatpak application could use this flaw to bypass all restrictions imposed by flatpak and have full access to the D-BUS interface. A heap corruption bug was found in the way libcdio handled processing of ISO files. An attacker could potentially use this flaw to crash applications using libcdio by tricking them into processing crafted ISO files, thus resulting in local DoS. A buffer overflow flaw was found in the zsh shell file descriptor redirection functionality. An attacker could use this flaw to cause a denial of service by crashing the user shell. GlusterFS and NFS network filesystems rely on File System User ID and Group ID information in order to restrict access to file shares. However, it's possible to overwrite the Openshift restrictions on container UserId and GroupdId as they are not validated before being sent over the Openshift Network. An attacker could use the flaw to read and write any data on the network filesystem. An out-of-bounds read flaw was found in the way LibRaw processed images. An attacker could potentially use this flaw to crash applications using LibRaw by tricking them into processing crafted images. In the Linux kernel, Hisilicon Network Subsystem (HNS) does not consider the ETH_SS_PRIV_FLAGS case when retrieving sset_count data. This allows local users to cause a denial of service (buffer overflow and memory corruption) or possibly have unspecified other impacts. It was found that libcurl did not safely parse FTP URLs when using the CURLOPT_FTP_FILEMETHOD method. An attacker, able to provide a specially crafted FTP URL to an application using libcurl, could write a NULL byte at an arbitrary location, resulting in a crash, or an unspecified behavior. A flaw was found in the way Samba AD DC validated user permissions. An authenticated attacker could use this flaw to change any other users passwords, including administrative users. An improper input validation was found in function __zzip_fetch_disk_trailer of ZZIPlib, up to 0.13.68, that could lead to a crash in __zzip_parse_root_directory function of zzip/zip.c. Remote attackers could leverage this vulnerability to cause a denial of service via a crafted zip file. A heap-based out-of-bounds read flaw was found in the way Sharutils parsed archive files. An attacker could potentially use this flaw to crash Unshar by tricking it into processing crafted archive files. The Linux kernel is vulnerable to a memory leak in the drivers/net/wireless/mac80211_hwsim.c:hwsim_new_radio_nl() function. An attacker could exploit this to cause a potential denial of service. An integer wraparound, leading to a buffer overflow, was found in Exempi in the way it handles Adobe Photoshop Images. An attacker could exploit this to cause a denial of service via a crafted image file. Dogtag PKI, through version 10.6.1, has a vulnerability in AAclAuthz.java that, under certain configurations, causes the application of ACL allow and deny rules to be reversed. If a server is configured to process allow rules before deny rules (authz.evaluateOrder=allow,deny), then allow rules will deny access and deny rules will grant access. This may result in an escalation of privileges or have other unintended consequences. A buffer overflow flaw was found in the zsh shell auto-complete functionality. A local, unprivileged user can create a specially crafted directory path which leads to code execution in the context of the user who tries to use auto-complete to traverse the before mentioned path. If the user affected is privileged, this leads to privilege escalation. An integer overflow leading to an out-of-bound read was found in authenticate_nss_2_3() in Corosync. An attacker could craft a malicious packet that would lead to a denial of service. The Serial Attached SCSI (SAS) implementation in the Linux kernel mishandles a mutex within libsas. This allows local users to cause a denial of service (deadlock) by triggering certain error-handling code. An XML deserialization vulnerability was discovered in slf4j's EventData, which accepts an XML serialized string and can lead to arbitrary code execution. An out-of-bound read flaw has been found in elfutils in the ebl_dynamic_tag_name function of ebldynamictagname.c file. An attacker could exploit this by supplying a crafted ELF file to display wrong data or potentially cause a crash in eu-readelf and eu-elflint binaries. A privilege escalation flaw was found in gluster snapshot scheduler. Any gluster client allowed to mount gluster volumes could also mount shared gluster storage volume and escalate privileges by scheduling malicious cronjob via symlink. It was found that 389-ds-base did not properly handle long search filters with characters needing escapes, possibly leading to buffer overflows. A remote, unauthenticated attacker could potentially use this flaw to make ns-slapd crash via a specially crafted LDAP request, thus resulting in denial of service. In pulp, secrets are passed into override_config when triggering a task and then become readable to all users with read access on the distributor/importer. An attacker with API access can then view these secrets. A stack-based buffer overflow was found in the way librelp parses X.509 certificates. By connecting or accepting connections from a remote peer, an attacker may use a specially crafted X.509 certificate to exploit this flaw and potentially execute arbitrary code. It has been discovered that the mod_session module of Apache HTTP Server (httpd), through version 2.4.29, has an improper input validation flaw in the way it handles HTTP session headers in some configurations. A remote attacker may influence their content by using a "Session" header. A flaw was found in the Linux kernel where a crash can be triggered from unprivileged userspace during core dump on a POWER system with a certain configuration. This is due to a missing processor feature check and an erroneous use of transactional memory (TM) instructions in the core dump path leading to a denial of service. The Linux kernel is vulnerable to a NULL pointer dereference in the ext4/mballoc.c:ext4_process_freed_data() function. An attacker could trick a legitimate user or a privileged attacker could exploit this by mounting a crafted ext4 image to cause a kernel panic. The Linux kernel is vulnerable to an out-of-bounds read in ext4/balloc.c:ext4_valid_block_bitmap() function. An attacker could trick a legitimate user or a privileged attacker could exploit this by mounting a crafted ext4 image to cause a crash. The Linux kernel is vulnerable to a NULL pointer dereference in the ext4/xattr.c:ext4_xattr_inode_hash() function. An attacker could trick a legitimate user or a privileged attacker could exploit this to cause a NULL pointer dereference with a crafted ext4 image. The Linux kernel is vulnerable to an out-of-bound access bug in the fs/posix_acl.c:get_acl() function. An attacker could trick a legitimate user or a privileged attacker could exploit this to cause a system crash or other unspecified impact with a crafted ext4 image. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. The add_free_nid function in fs/f2fs/node.c in the Linux kernel, before 4.12, does not properly track an allocated nid. This allows local users to cause a denial of service (race condition) or possibly have unspecified other impacts via concurrent threads. An input sanitization flaw was found in the id field of the dashboard controller. A user could use this flaw to perform a SQL injection attack on the back-end database. A memory leak vulnerability has been discovered in ImageMagick in the ReadPCDImage function of coders/pcd.c file. An attacker could use this flaw to cause a denial of service via a crafted file. A memory leak vulnerability has been discovered in ImageMagick in the WriteGIFImage function of coders/gif.c file. An attacker could use this flaw to cause a denial of service via a crafted file. BranchScope is a new class of attack which leverages functioning of the Branch Prediction Unit (BPU) of a processor to infer/leak sensitive process information, which is involved in the branch decision making (if (x) { x ^ y; } else {x & y;}). In this, BranchScope side-channel could help to infer 'x', by observing prediction patterns of the Branch Prediction Unit (BPU). It was found that the tmpdir and tempfile modules did not sanitize their file name argument. An attacker with control over the name could create temporary files and directories outside of the dedicated directory. It was found that the UNIXSocket::open and UNIXServer::open ruby methods did not handle the NULL byte properly. An attacker, able to inject NULL bytes in the socket path, could possibly trigger an unspecified behavior of the ruby script. It was found that the methods from the Dir class did not properly handle strings containing the NULL byte. An attacker, able to inject NULL bytes in a path, could possibly trigger an unspecified behavior of the ruby script. It was found that WEBrick could be forced to use an excessive amount of memory during the processing of HTTP requests, leading to a Denial of Service. An attacker could use this flaw to send huge requests to a WEBrick application, resulting in the server running out of memory. It was found that WEBrick did not sanitize headers sent back to clients, resulting in a response-splitting vulnerability. An attacker, able to control the server's headers, could force WEBrick into injecting additional headers to a client. A integer underflow was found in the way String#unpack decodes the unpacking format. An attacker, able to control the unpack format, could use this flaw to disclose arbitrary parts of the application's memory. It was found that when a Node.js script is run in inspector mode, Node.js did not properly validate the Host header, leaving the inspector vulnerable to a DNS rebind attack and bypass same-origin policy. If a developer had an inspector session running, and was visiting a malicious website, the site could carry on a DNS rebind attack, allowing the site to have full access to the debugged script. It was found that the 'path' module from Node.js was vulnerable to a Regular Expression Denial of Service (REDoS) flaw. An attacker able to provide a specially crafted file path to a Node.js script could force it to hang indefinitely. It was found that the http module from Node.js could accept incorrect Content-Length values, containing spaces within the value, in HTTP headers. A specially crafted client could use this flaw to possibly confuse the script, causing unspecified behavior. A vulnerability was found in the Linux kernel's kernel/events/core.c:perf_cpu_time_max_percent_handler() function. Local privileged users could exploit this flaw to cause a denial of service due to integer overflow or possibly have unspecified other impact. A cross-site request forgery flaw has been discovered in etcd. A remote attacker could set up a malicious website that execute POST requests to an etcd server to modify or add a key. It has been discovered that etcd does not correctly restrict access to resources based on hostname. A remote attacker could perform a DNS-rebinding attack and trick the browser into sending requests to an etcd server on an internal network, bypassing the Same-Origin Policy. A buffer overflow flaw was found in the zsh shell check path functionality. A local, unprivileged user can create a specially crafted message file, which, if used to set a custom "you have new mail" message, leads to code execution in the context of the user who receives the message. If the user affected is privileged, this leads to privilege escalation. Ansible Tower, before version 3.2.4, has a flaw in the management of system and organization administrators that allows for privilege escalation. System administrators that are members of organizations can have their passwords reset by organization administrators, allowing organization administrators access to the entire system. A flaw was found in source-to-image function as shipped with Openshift Enterprise 3.x. An improper path validation of tar files in ExtractTarStreamFromTarReader in tar/tar.go leads to privilege escalation. An improper validation of user input flaw was found in the source-to-image component of Openshift. An attacker who could trick a user into using the command to copy files locally, from a pod, could override files outside of the target directory of the command. Use-after-free vulnerability in the snd_pcm_info() function in the ALSA subsystem in the Linux kernel allows attackers to induce a kernel memory corruption and possibly crash or lock up a system. Due to the nature of the flaw, a privilege escalation cannot be fully ruled out, although we believe it is unlikely. It was discovered that an out-of-bounds write vulnerability existed in the Flash-Friendly File System (f2fs) in the Linux kernel. An attacker could construct a malicious file system that, when mounted, could cause a denial of service (system crash) or possibly execute arbitrary code. A flaw was found in the netlink 802.11 configuration interface. A local privileged attacker (CAP_NET_ADMIN) could crash the system or possibly execute arbitrary code. An out-of-bound read has been found in Exiv2 in the way binary bytes are converted to string. An attacker could potentially use this flaw to crash the Exiv2 CLI utility program by tricking it into processing a crafted TIFF image. The Linux kernel was found to be vulnerable to an infinite loop cause by an integer overflow in the fs/f2fs/data.c:__get_data_block() function. A local attacker could exploit this to cause a denial of service. Ansible Tower through version 3.2.3 has a vulnerability that allows users only with access to define variables for a job template to execute arbitrary code on the Tower server. An authentication bypass flaw has been found in PackageKit that allows users without administrator privileges to install signed packages. A local attacker can use this vulnerability to install vulnerable packages to further compromise a system. The OpenShift image import whitelist failed to enforce restrictions correctly when running commands such as "oc tag", for example. This could allow a user with access to OpenShift to run images from registries that should not be allowed. An improper authorization flaw in the atomic-openshift component of Openshift Container Platform 3.7 and earlier allows a user with cluster-reader project viewer permissions to trigger an application build. An attacker could use this flaw to trigger a build of an application when that should be restricted. The code in the drivers/scsi/libsas/sas_scsi_host.c file in the Linux kernel allow a physically proximate attacker to cause a memory leak in the ATA command queue and, thus, denial of service by triggering certain failure conditions. An out-of-bounds read vulnerability has been discovered in IptcData::printStructure in iptc.cpp file of Exiv2 0.26. An attacker could cause a crash or an information leak by providing a crafted image. A flaw was found in the way the Linux kernel's KVM hypervisor handled exceptions delivered after a stack switch operation via Mov SS or Pop SS instructions. During the stack switch operation, the processor did not deliver interrupts and exceptions, rather they are delivered once the first instruction after the stack switch is executed. An unprivileged KVM guest user could use this flaw to crash the guest or, potentially, escalate their privileges in the guest. An industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of Load & Store instructions (a commonly used performance optimization). It relies on the presence of a precisely-defined instruction sequence in the privileged code as well as the fact that memory read from address to which a recent memory write has occurred may see an older value and subsequently cause an update into the microprocessor's data cache even for speculatively executed instructions that never actually commit (retire). As a result, an unprivileged attacker could use this flaw to read privileged memory by conducting targeted cache side-channel attacks. A flaw was found in the way the Linux kernel handled exceptions delivered after a stack switch operation via Mov SS or Pop SS instructions. During the stack switch operation, the processor did not deliver interrupts and exceptions, rather they are delivered once the first instruction after the stack switch is executed. An unprivileged system user could use this flaw to crash the system kernel resulting in the denial of service. An improper validation flaw exists in the kubernetes 'kubectl cp' command. An attacker who could trick a user into using the command to copy files locally, from a pod, could override files outside of the target directory of the command. A weakness was found in the Linux kernel's implementation of random seed data. Programs, early in the boot sequence, could use the data allocated for the seed before it was sufficiently generated. The kernel_wait4 function in kernel/exit.c in the Linux kernel, when an unspecified architecture and compiler is used, might allow local users to cause a denial of service by triggering an attempted use of the -INT_MIN value. The Linux kernel has an undefined behavior when an argument of INT_MIN is passed to the kernel/signal.c:kill_something_info() function. A local attacker may be able to exploit this to cause a denial of service. OpenSSL RSA key generation was found to be vulnerable to cache side-channel attacks. An attacker with sufficient access to mount cache timing attacks during the RSA key generation process could recover parts of the private key. An address corruption flaw was discovered in the Linux kernel built with hardware breakpoint (CONFIG_HAVE_HW_BREAKPOINT) support. While modifying a h/w breakpoint via 'modify_user_hw_breakpoint' routine, an unprivileged user/process could use this flaw to crash the system kernel resulting in DoS OR to potentially escalate privileges on a the system. A flaw was found in the Linux kernel where an out of memory (oom) killing of a process that has large spans of mlocked memory can result in deferencing a NULL pointer, leading to denial of service. A race condition was found in the Linux kernel's sound timer code in the snd_timer_user_read() function in the sound/core/timer.c file. An unprivileged attacker can exploit the race condition to cause an out-of-bound access which may lead to a system crash or other unspecified impact. Due to the nature of the flaw, privilege escalation cannot be fully ruled out. It was discovered that the is-my-json-valid JavaScript library used an inefficient regular expression to validate JSON fields defined to have email format. A specially crafted JSON file could cause it to consume an excessive amount of CPU time when validated. it was found that Squid, when used as a reverse proxy, did not handle ESI responses properly. A malicious web server could use this flaw to crash Squid. The arch_timer_reg_read_stable macro in arch/arm64/include/asm/arch_timer.h in the Linux kernel, before 4.13, allows local users to cause a denial of service (infinite recursion) by writing to a file under /sys/kernel/debug in certain circumstances, as demonstrated by a scenario involving debugfs, ftrace, PREEMPT_TRACER, and FUNCTION_GRAPH_TRACER. A command injection flaw was found in the NetworkManager integration script included in the DHCP client packages in Red Hat Enterprise Linux. A malicious DHCP server, or an attacker on the local network able to spoof DHCP responses, could use this flaw to execute arbitrary commands with root privileges on systems using NetworkManager and configured to obtain network configuration using the DHCP protocol. It was found that fix for CVE-2018-1088 introduced a new vulnerability in the way 'auth.allow' is implemented in glusterfs server. An unauthenticated gluster client could mount gluster storage volumes. A an integer overflow vulnerability was discovered in the Linux kernel, from version 3.4 through 4.15, in the drivers/gpu/drm/udl/udl_fb.c:udl_fb_mmap() function. An attacker with access to the udldrmfb driver could exploit this to obtain full read and write permissions on kernel physical pages, resulting in a code execution in kernel space. Setup in Fedora and Red Hat Enterprise Linux added /sbin/nologin and /usr/sbin/nologin to /etc/shells. This violates security assumptions made by pam_shells and some daemons which allow access based on a user's shell being listed in /etc/shells. Under some circumstances, users which had their shell changed to /sbin/nologin could still access the system. The xfs_dinode_verify function in fs/xfs/libxfs/xfs_inode_buf.c in the Linux kernel can cause a NULL pointer dereference in xfs_ilock_attr_map_shared function. An attacker could trick a legitimate user or a privileged attacker could exploit this by mounting a crafted xfs filesystem image to cause a kernel panic and thus a denial of service. The xfs_bmap_extents_to_btree function in fs/xfs/libxfs/xfs_bmap.c in the Linux kernel can cause a NULL pointer dereference in xfs_bmapi_write function. An attacker could trick a legitimate user or a privileged attacker could exploit this by mounting a crafted xfs filesystem image to cause a kernel panic and thus a denial of service. An infinite loop has been found in the way ImageMagick reads Multiple-image Network Graphics (MNG) data. An attacker could exploit this to cause a denial of service via crafted MNG file. A use-after-free flaw in OpenSLP 1.x and 2.x baselines was discovered in the ProcessSrvRqst function. A failure to update a local pointer may lead to heap corruption. A remote attacker may be able to leverage this flaw to gain remote code execution. An infinite loop vulnerability was discovered in Apache Tika prior to version 1.18. A remote attacker could exploit this to cause a denial of service via crafted file. It was found that URLResource.getLastModified() in Undertow closes the file descriptors only when they are finalized which can cause file descriptors to exhaust. This leads to a file handler leak. An OOB write issue was found in the way Xen hypervisor handled error in the Page Table Isolation (PTI) implementation, used to fix the Meltdown issue. It could occur while processing interrupt 'INT 0x80', when PV guest's vCPU has no handler for it. A malicious guest user/process could use this flaw to crash the hypervisor resulting in denial of service issue. It was found that pg_catalog.pg_logfile_rotate(), from the adminpack extension, did not follow the same ACLs than pg_rorate_logfile. If the adminpack is added to a database, an attacker able to connect to it could use this flaw to force log rotation. A vulnerability was found in Guava where the AtomicDoubleArray and CompoundOrdering classes were found to allocate memory based on size fields sent by the client without validation. A crafted message could cause the server to consume all available memory or crash leading to a denial of service. An out-of-bounds read has been found in PHP when function exif_iif_add_value handles the case of a MakerNote that lacks a final terminator character. A remote attacker could use this vulnerability to cause a crash. An infinite loop vulnerability was found in ext/iconv/iconv.c in PHP due to the iconv stream not rejecting invalid multibyte sequences. A remote attacker could use this vulnerability to hang the php process and consume resources. A heap-based buffer overflow was found in the encoder functionality of the libvorbis library. An attacker could create a malicious file to cause a denial of service, crashing the application containing the library. A stack-based buffer overflow was found in the encoder functionality of the libvorbis library. An attacker could create a malicious file to cause a denial of service, crashing the application containing the library. Due to a missing no_log directive, the 'Add oVirt Provider to ManageIQ/CloudForms' playbook inadvertently disclosed admin passwords in the provisioning log. In an environment where logs are shared with other parties, this could lead to privilege escalation. The Linux kernel does not properly initialize memory in messages passed between virtual guests and the host operating system in the vhost/vhost.c:vhost_new_msg() function. This can allow local privileged users to read some kernel memory contents when reading from the /dev/vhost-net device file. The do_get_mempolicy() function in mm/mempolicy.c in the Linux kernel allows local users to hit a use-after-free bug via crafted system calls and thus cause a denial of service (DoS) or possibly have unspecified other impact. Due to the nature of the flaw, privilege escalation cannot be fully ruled out. A cookie injection flaw was found in wget. An attacker can create a malicious website which, when accessed, overrides cookies belonging to arbitrary domains. By mmap()ing a FUSE-backed file onto a process's memory containing command line arguments (or environment strings), an attacker can cause utilities from psutils or procps (such as ps, w) or any other program which makes a read() call to the /proc/<pid>/cmdline (or /proc/<pid>/environ) files to block indefinitely (denial of service) or for some controlled time (as a synchronization primitive for other attacks). Since the kernel's proc_pid_readdir() returns PID entries in ascending numeric order, a process occupying a high PID can use inotify events to determine when the process list is being scanned, and fork/exec to obtain a lower PID, thus avoiding enumeration. An unprivileged attacker can hide a process from procps-ng's utilities by exploiting a race condition in reading /proc/PID entries. If the HOME environment variable is unset or empty, top will read its configuration file from the current working directory without any security check. If a user runs top with HOME unset in an attacker-controlled directory, the attacker could achieve privilege escalation by exploiting one of several vulnerabilities in the config_file() function. Due to incorrect accounting when decoding and escaping Unicode data in procfs, ps is vulnerable to overflowing an mmap()ed region when formatting the process list for display. Since ps maps a guard page at the end of the buffer, impact is limited to a crash. Multiple integer overflows leading to heap corruption flaws were discovered in file2strvec(). These vulnerabilities can lead to privilege escalation for a local attacker who can create entries in procfs by starting processes, which will lead to crashes or arbitrary code execution in proc utilities run by other users (eg pgrep, pkill, pidof, w). lldptool can print a raw, unsanitized attacker controlled buffer when mngAddr information is displayed. This may allow an attacker to inject shell control characters into the buffer and impact the behavior of the terminal. If an argument longer than INT_MAX bytes is given to pgrep, "int bytes" could wrap around back to a large positive int (rather than approaching zero), leading to a stack buffer overflow via strncat(). A flaw was found where procps-ng provides wrappers for standard C allocators that took `unsigned int` instead of `size_t` parameters. On platforms where these differ (such as x86_64), this could cause integer truncation, leading to undersized regions being returned to callers that could then be overflowed. The only known exploitable vector for this issue is CVE-2018-1124. It was found that cephx authentication protocol did not verify ceph clients correctly and was vulnerable to replay attack. Any attacker having access to the ceph cluster network who is also able to sniff packets on the network can use this vulnerability to authenticate with ceph service and perform actions allowed by ceph service. A flaw was found in the way signature calculation was handled by cephx authentication protocol. An attacker having access to ceph cluster network, who is able to alter the message payload, was able to bypass signature checks done by cephx protocol. A NULL pointer dereference was found in the way the _nc_parse_entry function parses terminfo data for compilation. An attacker able to provide specially crafted terminfo data could use this flaw to crash the application parsing it. A null pointer dereference in dccp_write_xmit() function in net/dccp/output.c in the Linux kernel allows a local user to cause a denial of service by a number of certain crafted system calls. A flaw was found in Opendaylight's SDNInterfaceapp (SDNI). Attackers can SQL inject the component's database (SQLite) without authenticating to the controller or SDNInterfaceapp. An integer overflow has been discovered in libtiff in TIFFSetupStrips:tif_write.c, which could lead to a heap-based buffer overflow in TIFFWriteScanline:tif_write.c. An attacker may use this vulnerability to corrupt memory or cause Denial of Service. A memory leak has been discovered in tools/bmp2tiff.c in libtiff, when the iBitCount header value is not acceptable. An attacker may use this flaw to cause a Denial of Service. A flaw was found in the Linux kernel, before 4.16.6 where the cdrom_ioctl_media_changed function in drivers/cdrom/cdrom.c allows local attackers to use a incorrect bounds check in the CDROM driver CDROM_MEDIA_CHANGED ioctl to read out kernel memory. A flaw was found in the way zone databases were handled by bind. An attacker with permissions to initiate a zone transfer could cause bind to crash. A flaw was found in the "serve-stale" feature as implemented in bind. Problematic interaction between serve-stale feature and NSEC aggressive negative caching could cause denial of service. A NULL pointer dereference flaw was found in H5S_hyper_make_spans in H5Shyper.c in the HDF HDF5 1.10.2 library. This could allow a remote denial of service attack. A division by zero flaw was found in H5D__btree_decode_key in H5Dbtree.c in the HDF HDF5 1.10.2 library. This could allow a remote denial of service attack. A NULL pointer dereference was discovered in HDF5 1.10.2 within the H5O__chunk_deserialize in H5Ocache.c. This could allow a remote denial of service attack. An out-of-bounds read flaw was discovered in H5VM_memcpyvv in H5VM.c in the HDF HDF5 1.10.2 library. This could allow a remote denial of service or information disclosure attack. An out-of-bounds read flaw was discovered in H5O_fill_new_decode and H5O_fill_old_decode in H5Ofill.c in the HDF HDF5 1.10.2 library. This could allow a remote denial of service or information disclosure attack. A division-by-zero flaw was discovered in H5D__chunk_init in H5Dchunk.c in the HDF HDF5 1.10.2 library. This could allow a remote denial of service attack. A divide by zero vulnerability has been discovered in libjpeg-turbo in alloc_sarray function of jmemmgr.c file. An attacker could use this vulnerability to cause a denial of service via a crafted file. An out-of-bound read vulnerability has been discovered in libjpeg-turbo when reading one row of pixels of a PGM file. An attacker could use this flaw to crash the application and cause a denial of service. An out-of-bounds read vulnerability has been discovered in libjpeg-turbo when reading one row of pixels of a PPM file. An attacker could use this flaw to crash the application and cause a denial of service. A missing input sanitization flaw was found in the implementation of LDP database used for the LDAP server. An attacker could use this flaw to cause a denial of service against a samba server, used as a Active Directory Domain Controller. An industry-wide issue was found in the way many modern microprocessor handle speculative access of system registers inaccessible to unprivileged user. It relies on the presence of a precisely-defined instruction sequence in the privileged code which allows speculative load of system registers and that such register value could be subsequently used in speculatively executed instructions that never actually commit (retire). As a result, an unprivileged attacker could use this flaw to read privileged system registers by conducting targeted cache side-channel attacks. A flaw was found in the Linux kernel in the way the etm_setup_aux function in drivers/hwtracing/coresight/coresight-etm-perf.c allows attackers to cause a denial of service by crashing the system, or possibly corrupting memory resources intended for a differently specified CPU. A flaw was found in the Linux kernel in the way a local user could create keyrings for other users via keyctl commands. This may allow an attacker to set unwanted defaults, a denial of service, or possibly leak keyring information between users. A buffer overflow has been discovered in the GNU C Library (aka glibc or libc6) in the __mempcpy_avx512_no_vzeroupper function when particular conditions are met. An attacker could use this vulnerability to cause a denial of service or potentially execute code. An integer overflow issue was found in the NE200 NIC emulation. It could occur while receiving packets from the network, if the size value was greater than INT_MAX. Such overflow would lead to stack buffer overflow issue. A user inside guest could use this flaw to crash the QEMU process, resulting in DoS scenario. A flaw was found in the Linux kernel's implementation of valid_master_desc() in which a memory buffer would be compared to a userspace value with an incorrect size of comparison. By bruteforcing the comparison, an attacker could determine what was in memory after the description and possibly obtain sensitive information from kernel memory. A use-after-free flaw was found in the code responsible for processing packages from Q.931 protocol, in wireshark. An attacker can send specially crafted packages over the network which, when received, would cause an application to crash, or potentially, corrupt information. A heap-based buffer overflow was found in the wireshark module responsible for analyzing the LDSS protocol. An attacker could create a malicious LDSS message to cause a remote denial of service, crashing the application. An integer underflow has been discovered in strongSwan VPN's charon server, which could lead to a buffer overflow and consequent crash. A local attacker, with enough privileges to access the Unix Domain Socket /var/run/charon.ctl, could use this vulnerability to crash the charon server. The Linux kernel is vulnerable to a heap-based buffer overflow in the fs/ext4/xattr.c:ext4_xattr_set_entry() function. An attacker could exploit this by operating on a mounted crafted ext4 image. A flaw was found in glusterfs which can lead to privilege escalation on gluster server nodes. An authenticated gluster client via TLS could use gluster cli with --remote-host command to add it self to trusted storage pool and perform privileged gluster operations like adding other machines to trusted storage pool, start, stop, and delete volumes. The fs/ext4/inline.c:ext4_read_inline_data() function in the Linux kernel performs a memcpy with an untrusted length value in certain circumstances involving a crafted filesystem that stores the system.data extended attribute value in a dedicated inode. The unbound copy can cause memory corruption or possible privilege escalation. A privilege escalation flaw was found in the source-to-image component of Openshift Container Platform which allows the assemble script to run as the root user in a non-privileged container. An attacker can use this flaw to open network connections, and possibly other actions, on the host which are normally only available to a root user. It was found that GnuTLS's implementation of HMAC-SHA-256 was vulnerable to Lucky Thirteen-style attack. A remote attacker could use this flaw to conduct distinguishing attacks and plain text recovery attacks via statistical analysis of timing data using crafted packets. It was found that GnuTLS's implementation of HMAC-SHA-384 was vulnerable to a Lucky Thirteen-style attack. A remote attacker could use this flaw to conduct distinguishing attacks and plain text recovery attacks via statistical analysis of timing data using crafted packets. A cache-based side channel attack was found in the way GnuTLS implements CBC-mode cipher suites. An attacker could use a combination of "Just in Time" Prime+probe and Lucky-13 attacks to recover plain text in a cross-VM attack scenario. The sr_do_ioctl function in drivers/scsi/sr_ioctl.c in the Linux kernel allows local users to cause a denial of service via a stack-based buffer overflow or possibly have unspecified other impact because sense buffers have different sizes at the CDROM layer and the SCSI layer. A flaw was found in the compat_get_timex function in kernel/compat.c in the Linux kernel. A local user could use this flaw to obtain possibly sensitive information from kernel memory via adjtimex system call. When using pre-produced responses from an OCSP responder, Tomcat Native did not correctly validate the status of certificates. This allowed for revoked client certificates to be incorrectly identified. It was therefore possible for users to authenticate with revoked certificates when using mutual TLS. Modern operating systems implement virtualization of physical memory to efficiently use available system resources and provide inter-domain protection through access control and isolation. The L1TF issue was found in the way the x86 microprocessor designs have implemented speculative execution of instructions (a commonly used performance optimization) in combination with handling of page-faults caused by terminated virtual to physical address resolving process. As a result, an unprivileged attacker could use this flaw to read privileged memory of the kernel or other processes and/or cross guest/host boundaries to read host memory by conducting targeted cache side-channel attacks. Ghostscript did not honor the -dSAFER option when executing the "status" instruction, which can be used to retrieve information such as a file's existence and size. A specially crafted postscript document could use this flow to gain information on the targeted system's filesystem content. A heap buffer overflow issue was found in the way SLiRP networking back-end in QEMU processes fragmented packets. It could occur while reassembling the fragmented datagrams of an incoming packet. A privileged user/process inside guest could use this flaw to crash the QEMU process resulting in DoS or potentially leverage it to execute arbitrary code on the host with privileges of the QEMU process. A path traversal vulnerability has been discovered in plexus-archiver when extracting a carefully crafted zip file which holds path traversal file names. A remote attacker could use this vulnerability to write files outside the target directory and overwrite existing files with malicious code or vulnerable configurations. A race condition was found in the way 389-ds-base handles persistent search, resulting in a crash if the server is under load. An anonymous attacker could use this flaw to trigger a denial of service. A vulnerability was found in BouncyCastle. The number of iterations of the Miller-Rabin primality test was incorrectly calculated (according to FIPS 186-4 C.3). Under some circumstances, this could lead to the generation of weak RSA key pairs. A Floating Point Unit (FPU) state information leakage flaw was found in the way the Linux kernel saved and restored the FPU state during task switch. Linux kernels that follow the "Lazy FPU Restore" scheme are vulnerable to the FPU state information leakage issue. An unprivileged local attacker could use this flaw to read FPU state bits by conducting targeted cache side-channel attacks, similar to the Meltdown vulnerability disclosed earlier this year. The mime module is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input. Multiple race condition errors when handling probe, disconnect, and rebind operations can be exploited to trigger a use-after-free condition or a NULL pointer dereference by sending multiple USB over IP packets. Successful exploitation requires USB over IP daemon (usbipd) to be running. It was found that the Archive::Tar module did not properly sanitize symbolic links when extracting tar archives. An attacker, able to provide a specially crafted archive for processing, could use this flaw to write or overwrite arbitrary files in the context of the Perl interpreter. The UNIX pipe which sudo uses to contact SSSD and read the available sudo rules from SSSD utilizes too broad of a set of permissions. Any user who can send a message using the same raw protocol that sudo and SSSD use can read the sudo rules available for any user. A malformed SG_IO ioctl issued for a SCSI device in the Linux kernel leads to a local kernel data leak manifesting in up to approximately 1000 memory pages copied to the userspace. The problem has limited scope as non-privileged users usually have no permissions to access SCSI device files. A data validation flaw was found in the way gnupg processes file names during decryption and signature validation. An attacker may be able to inject messages into gnupg verbose message logging which may have the potential to bypass the integrity of signature authentication mechanisms and could have other unintended consequences if applications take action(s) based on parsed verbose gnupg output. A flaw was found in the way samba allowed the use of weak NTLMv1 authentication even when NTLMv1 was explicitly disabled. A man-in-the-middle attacker could use this flaw to read the credential and other details passed between the samba server and client. A flaw was found in the way Linux kernel KVM hypervisor emulated instructions such as sgdt/sidt/fxsave/fxrstor. It did not check current privilege(CPL) level while emulating unprivileged instructions. An unprivileged guest user/process could use this flaw to potentially escalate privileges inside guest. A vulnerability was found in libssh's server-side state machine. A malicious client could create channels without first performing authentication, resulting in unauthorized access. A memory corruption issue was found in the Linux kernel with a JFS file system. Two setxattr calls to the same file with different extended attribute names would trigger an overflow and a memory corruption. A NULL pointer dereference issue was found in the Linux kernel. If the close() and fchownat() system calls share a socket file descriptor as an argument, then the two calls can race and trigger a NULL pointer dereference leading to a system crash and a denial of service. In the function wmi_set_ie() in the Linux kernel the length validation code does not handle unsigned integer overflow properly. As a result, a large value of the ‘ie_len’ argument can cause a buffer overflow and thus a memory corruption leading to a system crash or other or unspecified impact. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. It was found that the Buffer.fill() and Buffer.alloc() function may hang. An attacker able to control the input of these function could use this flaw to cause a denial of service. Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible. LibRaw is vulnerable to stack-based buffer overflow in internal/dcraw_common.cpp:quicktake_100_load_raw() function when processing specially-crafted RAW data. An attacker could potentially use this flaw to cause an arbitrary code execution or denial of service. A NULL pointer dereference vulnerability in internal/dcraw_common.cpp:leaf_hdr_load_raw() function was found in LibRaw. A user can cause a denial of service when processing specially-crafted RAW data. It has been discovered that podman does not drop capabilities when executing a container as a non-root user. This results in unnecessary privileges being granted to the container. It was found that the Archive::Zip module did not properly sanitize paths while extracting zip files. An attacker able to provide a specially crafted archive for processing could use this flaw to write or overwrite arbitrary files in the context of the perl interpreter. A flaw was found in the way ceph mon handles user requests. Any authenticated ceph user having read access to ceph can delete and corrupt snapshot images It was found that the explode function of the deployment utility in jboss-cli and console that allows extraction of files from an archive does not perform necessary validation for directory traversal. This can lead to remote code execution. The ntpq and ntpdc command-line utilities that are part of ntp package are vulnerable to stack-based buffer overflow via crafted hostname. Applications using these vulnerable utilities with an untrusted input may be potentially exploited, resulting in a crash or arbitrary code execution under privileges of that application. It has been discovered that redhat-certification is not properly configured and it lists all files and directories in the /var/www/rhcert/store/transfer directory through the /rhcert-transfer URL. An unauthorized attacker may use this flaw to gather sensible information. An uncontrolled resource consumption flaw has been discovered in redhat-certification in the way documents are loaded. A remote attacker may provide an existing but invalid XML file which would be opened and never closed, possibly producing a Denial of Service. It has been discovered that redhat-certification does not perform an authorization check and allows an unauthenticated user to call a "restart" RPC method on any host accessible by the system. An attacker could use this flaw to send requests to port 8009 of any host or to keep restarting the RHCertD daemon on a host of another customer. It has been discovered that redhat-certification does not restrict file access in the /update/results page. A remote attacker could use this vulnerability to remove any file accessible by the user which is running httpd. It has been discovered that redhat-certification does not properly limit the number of recursive definitions of entities in XML documents while parsing the status of a host. A remote attacker could use this vulnerability to consume all the memory of the server and cause a Denial of Service. It was discovered that redhat-certification does not properly restrict files that can be download through the /download page. A remote attacker may download any file accessible by the user running httpd. It has been discovered that redhat-certification does not properly sanitize paths in rhcertStore.py:__saveResultsFile. A remote attacker could use this flaw to overwrite any file, potentially gaining remote code execution. The Redis command line tool 'redis-cli' is vulnerable to a buffer overflow through the -h (host) command line parameter. The redis-cli may be used by other services; if these services do not adequately filter the host input it could lead to code execution with the privilege level of that service. Exempi is vulnerable to an issue that may manifest as a NULL pointer dereference or an out-of-bounds access due to not checking if vector is of required size before accessing its elements. An attacker could use this to cause a denial of service. It was discovered that when Apache CXF is configured to use the system property com.sun.net.ssl.internal.www.protocol ,it uses reflection to make the HostnameVerifier work with old com.sun.net.ssl.HostnameVerifier interface. Although the CXF implementation throws an exception, which is caught in the reflection code but it is not properly propagated, this can lead to a man-in-the-middle attack. It was found that Polkit's CheckAuthorization and RegisterAuthenticationAgent D-Bus calls did not validate the client provided UID. A specially crafted program could use this flaw to submit arbitrary UIDs, triggering various denial of service or minor disclosures, such as which authentication is cached in the victim's session. An issue was discovered in the Linux kernel in the filter parsing code in kernel/trace/trace_events_filter.c. The code could be called with no filter when it expected at least one, which allows attackers to cause a slab out-of-bounds write and so a denial of service via crafted perf_event_open and mmap system calls. By default, when the Replica and/or retroChangeLog plugins are enabled, 389-ds-base stores passwords in plaintext format in their respective changelog files. An attacker with sufficiently high privileges, such as root or Directory Manager, can query these files in order to retrieve plaintext passwords. A flaw was found in the way the Linux kernel handled exceptions delivered after a stack switch operation via Mov SS or Pop SS instructions. During the stack switch operation, processor does not deliver interrupts and exceptions, they are delivered once the first instruction after the stack switch is executed. An unprivileged system user could use this flaw to crash the system kernel resulting in DoS. This CVE-2018-10872 was assigned due to regression of CVE-2018-8897 in Red Hat Enterprise Linux 6.10 GA kernel; no other versions are affected by this CVE. A vulnerability was discovered in SPICE where the generated code used for demarshalling messages lacked sufficient bounds checks. A malicious client or server, after authentication, could send specially crafted messages to its peer which would result in a crash or, potentially, other impacts. A cross-site scripting vulnerability (XSS) has been discovered in mailman due to the host_name field not being properly validated. A malicious list owner could use this flaw to create a specially crafted list and inject client-side scripts. It was found that ansible.cfg is being read from the current working directory, which can be made to point to plugin or module paths that are under control of the attacker. This could allow an attacker to execute arbitrary code. A flaw was found in the Linux kernel's ext4 filesystem code. A use-after-free is possible in ext4_ext_remove_space() function when mounting and operating a crafted ext4 image. A flaw was found in the Linux kernel ext4 filesystem. An out-of-bound access is possible in the ext4_ext_drop_refs() function when operating on a crafted ext4 filesystem image. A flaw was found in the Linux kernel's ext4 filesystem. A local user can cause an out-of-bounds write and a denial of service or unspecified other impact is possible by mounting and operating a crafted ext4 filesystem image. A flaw was found in the Linux kernel's ext4 filesystem. A local user can cause a use-after-free in ext4_xattr_set_entry function and a denial of service or unspecified other impact may occur by renaming a file in a crafted ext4 filesystem image. A flaw was found in the Linux kernel's ext4 filesystem code. A stack-out-of-bounds write in ext4_update_inline_data() is possible when mounting and writing to a crafted ext4 image. An attacker could use this to cause a system crash and a denial of service. A flaw was found in the Linux kernel's ext4 filesystem. A local user can cause an out-of-bound access in ext4_get_group_info function, a denial of service, and a system crash by mounting and operating on a crafted ext4 filesystem image. A flaw was found in the Linux kernel's ext4 filesystem. A local user can cause an out-of-bound write in the fs/jbd2/transaction.c code, a denial of service, and a system crash by unmounting a crafted ext4 filesystem image. A flaw was found in the Linux kernel's ext4 filesystem. A local user can cause an out-of-bound write in jbd2_journal_dirty_metadata(), a denial of service, and a system crash by mounting and operating on a crafted ext4 filesystem image. A malicious network-policy configuration can cause Openshift Routing to crash when using ovs-networkpolicy plugin. An attacker can use this flaw to cause a Denial of Service (DoS) attack on an Openshift 3.7 or 3.9 Cluster. A flaw was found in the alarm_timer_nsleep() function in kernel/time/alarmtimer.c in the Linux kernel. The ktime_add_safe() function is not used and an integer overflow can happen causing an alarm not to fire if using a large relative timeout. An issue was discovered in the Linux kernel where an integer overflow in kernel/time/posix-timers.c in the POSIX timer code is caused by the way the overrun accounting works. Depending on interval and expiry time values, the overrun can be larger than INT_MAX, but the accounting is int based. This basically makes the accounting values, which are visible to user space via timer_getoverrun(2) and siginfo::si_overrun, random. An issue was discovered in the XFS filesystem in fs/xfs/xfs_icache.c in the Linux kernel. There is a NULL pointer dereference leading to a system panic in lookup_slow() on a NULL inode->i_ops pointer when doing pathwalks on a corrupted xfs image. This occurs because of a lack of proper validation that cached inodes are free during an allocation. An issue was discovered in the XFS filesystem in fs/xfs/libxfs/xfs_attr_leaf.c in the Linux kernel. A NULL pointer dereference may occur for a corrupted xfs image after xfs_da_shrink_inode() is called with a NULL bp. This can lead to a system crash and a denial of service. An issue was discovered in the XFS filesystem in fs/xfs/libxfs/xfs_inode_buf.c in the Linux kernel. A denial of service due to the NULL pointer dereference can occur for a corrupted xfs image upon encountering an inode that is in extent format, but has more extents than fit in the inode fork. A flaw was discovered in the F2FS filesystem code in fs/f2fs/super.c in the Linux kernel. A denial of service, due to an out-of-bounds memory access, can occur upon encountering an abnormal bitmap size when mounting a crafted f2fs image. A flaw was discovered in the F2FS filesystem code in fs/f2fs/super.c in the Linux kernel. An out-of-bounds read or a divide-by-zero error for an incorrect user_block_count in a corrupted f2fs image can lead to a denial of service. An issue was discovered in the F2FS filesystem code in the Linux kernel in fs/f2fs/inode.c. A denial of service due to a slab out-of-bounds read can occur for a crafted f2fs filesystem image in which FI_EXTRA_ATTR is set in an inode. An issue was discovered in the F2FS filesystem code in fs/f2fs/inline.c in the Linux kernel. A denial of service due to the out-of-bounds memory access can occur for a modified f2fs filesystem image. An issue was discovered in fs/f2fs/super.c in the Linux kernel, which does not properly validate secs_per_zone in a corrupted f2fs image. This may lead to a divide-by-zero error and a system crash. A flaw was found in the Linux kernel, a NULL pointer dereference can happen in hfs_ext_read_extent in hfs.ko which can occur during a mount of a crafted hfs filesystem. This can lead to a system crash and a denial of service. A flaw was found in ntfs_read_locked_inode in the ntfs.ko filesystem driver in the Linux kernel. This allows attackers to trigger a use-after-free read and possibly cause a denial of service via a crafted ntfs filesystem. A flaw was found in ntfs_end_buffer_async_read in the ntfs.ko filesystem driver in the Linux kernel. This allows attackers to trigger a stack-based out-of-bounds write and cause a denial of service or possibly have unspecified other impact via a crafted ntfs filesystem. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. A flaw was found in ntfs_attr_find in the ntfs.ko filesystem driver in the Linux kernel. This allows attackers to trigger a stack-based out-of-bounds write and cause a denial of service or possibly have unspecified other impact via a crafted ntfs filesystem image. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. An out-of-bounds read has been discovered in libsoup when getting cookies from a URI with empty hostname. An attacker may use this flaw to cause a crash in the application. A heap-based buffer overflow has been found in the Curl_smtp_escape_eob() function of curl. An attacker could exploit this by convincing a user to use curl to upload data over SMTP with a reduced buffer to cause a crash or corrupt memory. It has been discovered that an unexpected sign extension in git_delta_apply function in delta.c file may lead to an integer overflow which in turn leads to an out of bound read, allowing to read before the base object. An attacker may use this flaw to leak memory addresses or cause a Denial of Service. A missing check in git_delta_apply function in delta.c file may lead to an out-of-bound read while reading a binary delta file. An attacker may use this flaw to cause a Denial of Service. A memory leak was discovered in ImageMagick in the XMagickCommand function in animate.c file. An array of strings, named filelist, is allocated on the heap but not released in case the function ExpandFilenames returns an error code. The default OCI Linux spec in oci/defaults{_linux}.go in Docker/Moby, from 1.11 to current, does not block /proc/acpi pathnames. The flaw allows an attacker to modify host's hardware like enabling/disabling Bluetooth or turning up/down keyboard brightness. Multiple integer overflow and buffer overflow issues were discovered in spice-client's handling of LZ compressed frames. A malicious server could cause the client to crash or, potentially, execute arbitrary code. A vulnerability was found in the fs/inode.c:inode_init_owner() function logic of the LInux kernel that allows local users to create files with an unintended group ownership and with group execution and SGID permission bits set, in a scenario where a directory is SGID and belongs to a certain group and is writable by a user who is not a member of this group. This can lead to excessive permissions granted in case when they should not. The Linux kernel was found vulnerable to an integer overflow in the drivers/video/fbdev/uvesafb.c:uvesafb_setcmap() function. The vulnerability could result in local attackers being able to crash the kernel or potentially elevate privileges. An industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of instructions past bounds check. The flaw relies on the presence of a precisely-defined instruction sequence in the privileged code and the fact that memory writes occur to an address which depends on the untrusted value. Such writes cause an update into the microprocessor's data cache even for speculatively executed instructions that never actually commit (retire). As a result, an unprivileged attacker could use this flaw to influence speculative execution and/or read privileged memory by conducting targeted cache side-channel attacks. The default cloud-init configuration included "ssh_deletekeys: 0", disabling cloud-init's deletion of ssh host keys. In some environments, this could lead to instances created by cloning a golden master or template system, sharing ssh host keys, and being able to impersonate one another or conduct man-in-the-middle attacks. A directory and symbolic link traversal flaw was found in the way rubyzip gem extracts zip files. An attacker, with access to a privileged application capable of extracting zip files, could use this flaw to write new files to arbitrary paths, accessible by the aforementioned privileged application. A directory traversal issue was found in reposync, a part of yum-utils, where reposync fails to sanitize paths in remote repository configuration files. If an attacker controls a repository, they may be able to copy files outside of the destination directory on the targeted system via path traversal. If reposync is running with heightened privileges on a targeted system, this flaw could potentially result in system compromise via the overwriting of critical system files. An issue was discovered in the __ns_get_path function in fs/nsfs.c in the Linux kernel before 4.11. Due to a race condition when accessing files, a Use After Free condition can occur. A local attacker may be able to leverage this fault to escalate privileges on the system. When deployed using Director using default configuration, Opendaylight in RHOSP13 is configured with easily guessable default credentials. SoundTouch library is vulnerable to reachable assertion in RateTransposer::setChannels() function that can cause denial of service to applications using this library for processing the untrusted file input. A flaw was found in Linux kernel's KVM virtualization subsystem. The VMX code does not restore the GDT.LIMIT to the previous host value, but instead sets it to 64KB. With a corrupted GDT limit a host's userspace code has an ability to place malicious entries in the GDT, particularly to the per-cpu variables. An attacker can use this to escalate their privileges. It was found that the raw midi kernel driver does not protect against concurrent access which leads to a double realloc (double free) in snd_rawmidi_input_params() and snd_rawmidi_output_status() which are part of snd_rawmidi_ioctl() handler in rawmidi.c file. A malicious local attacker could possibly use this for privilege escalation. A flaw was found in python-cryptography versions between >=1.9.0 and <2.3. The finalize_with_tag API did not enforce a minimum tag length. If a user did not validate the input length prior to passing it to finalize_with_tag an attacker could craft an invalid payload with a shortened tag (e.g. 1 byte) such that they would have a 1 in 256 chance of passing the MAC check. GCM tag forgeries can cause key leakage. It was found that IKEv1 (and potentially IKEv2) authentication when using a pre-shared key (PSK) is vulnerable to offline dictionary attacks in Main Mode as well as in Aggressive Mode. A man-in-the-middle attacker who intercepted the handshake of two peers authenticating with a PSK, could apply a brute-force attack to recover the shared secret. It was found that glusterfs server does not properly sanitize file paths in the "trusted.io-stats-dump" extended attribute which is used by the "debug/io-stats" translator. An attacker can use this flaw to create files and execute arbitrary code. To exploit this, the attacker would require sufficient access to modify the extended attributes of files on a gluster volume. A null pointer dereference vulnerability exists in the xpath.c:xmlXPathCompOpEval() function of libxml2 when parsing invalid XPath expression. Applications processing untrusted XSL format inputs with the use of libxml2 library may be vulnerable to denial of service attack due to crash of the application. CloudForms Management Engine has a vulnerability that allows local users to execute arbitrary commands as root. An attacker with SSH access to the system can use the dRuby (DRb) module installed on the system to execute arbitrary shell commands using `instance_eval()`. Non-optimized code for key handling of shared futexes was found in the Linux kernel in the form of unbounded contention time due to the page lock for real-time users. Before the fix, the page lock was an unnecessarily heavy lock for the futex path that protected too much. After the fix, the page lock is only required in a specific corner case. A vulnerability was discovered in fuse. When SELinux is active, fusermount is vulnerable to a restriction bypass. This allows non-root users to mount a FUSE file system with the 'allow_other' mount option regardless of whether 'user_allow_other' is set in the fuse configuration. An attacker may use this flaw to mount a FUSE file system, accessible by other users, and trick them into accessing files on that file system, possibly causing Denial of Service or other unspecified effects. It was found that glusterfs server is vulnerable to mulitple stack based buffer overflows due to functions in server-rpc-fopc.c allocating fixed size buffers using 'alloca(3)'. An authenticated attacker could exploit this by mounting a gluster volume and sending a string longer that the fixed buffer size to cause crash or potential code execution. It was found that vdsm would invoke qemu-img on untrusted inputs without limiting resources. By uploading a specially crafted image, an attacker could cause the qemu-img process to consume unbounded amounts of memory of CPU time, causing a denial of service condition that could potentially impact other users of the host. A flaw was found in Keystone federation. By doing GET /v3/OS-FEDERATION/projects an authenticated user may discover projects they have no authority to access, leaking all projects in the deployment and their attributes. Only Keystone with the /v3/OS-FEDERATION endpoint enabled via policy.json is affected. A bug in Bluez may allow for the Bluetooth Discoverable state being set to on when no Bluetooth agent is registered with the system. This situation could lead to the unauthorized pairing of certain Bluetooth devices without any form of authentication. It was discovered that CUPS allows non-root users to pass environment variables to CUPS backends. Affected backends use attacker-controlled environment variables without proper sanitization. A local attacker, who is part of one of the groups specified in the SystemGroups directive, could use the cupsctl binary to set SetEnv and PassEnv directives and potentially controls the flow of the affected backend, resulting in some cases in arbitrary code execution with root privileges. A Sandbox bypass has been discovered in cups on macOS due to insecure error handling. An attacker that has obtained sandboxed root access can use this flow to escape the sandbox. A Sandbox bypass has been discovered in cups on macOS due to profile misconfiguration. An attacker that has obtained sandboxed root access can use this flow to escape the sandbox. An AppArmor sandbox bypass has been discovered in cups due to the use of hard links which are not covered by the AppArmor profile. An attacker could use the hard link, if it exists, to execute the referenced backend without sandbox restrictions. A flaw was found in dict.c:dict_unserialize function of glusterfs, dic_unserialize function does not handle negative key length values. An attacker could use this flaw to read memory from other locations into the stored dict value. A flaw named SegmentSmack was found in the way the Linux kernel handled specially crafted TCP packets. A remote attacker could use this flaw to trigger time and calculation expensive calls to tcp_collapse_ofo_queue() and tcp_prune_ofo_queue() functions by sending specially modified packets within ongoing TCP sessions which could lead to a CPU saturation and hence a denial of service on the system. Maintaining the denial of service condition requires continuous two-way TCP sessions to a reachable open port, thus the attacks cannot be performed using spoofed IP addresses. Modern operating systems implement virtualization of physical memory to efficiently use available system resources and provide inter-domain protection through access control and isolation. The L1TF issue was found in the way the x86 microprocessor designs have implemented speculative execution of instructions (a commonly used performance optimization) in combination with handling of page-faults caused by terminated virtual to physical address resolving process. As a result, an unprivileged attacker could use this flaw to read privileged memory of the kernel or other processes and/or cross guest/host boundaries to read host memory by conducting targeted cache side-channel attacks. An information disclosure vulnerability was discovered in glusterfs server. An attacker could issue a xattr request via glusterfs FUSE to determine the existence of any file. It was found that an attacker could issue a xattr request via glusterfs FUSE to cause gluster brick process to crash which will result in a remote denial of service. If gluster multiplexing is enabled this will result in a crash of multiple bricks and gluster volumes. When using the django.middleware.common.CommonMiddleware class with the APPEND_SLASH setting enabled, Django projects which accept paths ending in a slash may be vulnerable to an unvalidated HTTP redirect. A flaw named FragmentSmack was found in the way the Linux kernel handled reassembly of fragmented IPv4 and IPv6 packets. A remote attacker could use this flaw to trigger time and calculation expensive fragment reassembly algorithm by sending specially crafted packets which could lead to a CPU saturation and hence a denial of service on the system. A vulnerability was found in libpq, the default PostgreSQL client library where libpq failed to properly reset its internal state between connections. If an affected version of libpq were used with "host" or "hostaddr" connection parameters from untrusted input, attackers could bypass client-side connection security features, obtain access to higher privileged connections or potentially cause other impact through SQL injection, by causing the PQescape() functions to malfunction. An issue was discovered in the btrfs filesystem code in the Linux kernel. An invalid pointer dereference in __del_reloc_root() in fs/btrfs/relocation.c when mounting a crafted btrfs image could lead to a system crash and a denial of service. An issue was discovered in the btrfs filesystem code in the Linux kernel. An out-of-bounds access is possible in write_extent_buffer() when mounting and operating a crafted btrfs image due to a lack of verification at mount time within the btrfs_read_block_groups() in fs/btrfs/extent-tree.c function. This could lead to a system crash and a denial of service. An issue was discovered in the btrfs filesystem code in the Linux kernel. A use-after-free is possible in try_merge_free_space() when mounting a crafted btrfs image due to a lack of chunk type flag checks in btrfs_check_chunk_valid() in the fs/btrfs/volumes.c function. This could lead to a denial of service or other unspecified impact. An issue was discovered in the btrfs filesystem code in the Linux kernel. An invalid NULL pointer dereference in btrfs_root_node() when mounting a crafted btrfs image is due to a lack of chunk block group mapping validation in btrfs_read_block_groups() in the fs/btrfs/extent-tree.c function and a lack of empty-tree checks in check_leaf() in fs/btrfs/tree-checker.c function. This could lead to a system crash and a denial of service. An issue was discovered in the btrfs filesystem code in the Linux kernel. An invalid pointer dereference in io_ctl_map_page() when mounting and operating a crafted btrfs image is due to a lack of block group item validation in check_leaf_item() in fs/btrfs/tree-checker.c function. This could lead to a system crash and a denial of service. An issue was discovered in the Linux kernel's F2FS filesystem code. An out-of-bounds access vulnerability is possible the in __remove_dirty_segment() in fs/f2fs/segment.c function when mounting a crafted f2fs image. An issue was discovered in the Linux kernel's F2FS filesystem code. A buffer overflow in truncate_inline_inode() in the fs/f2fs/inline.c function, when umounting a crafted f2fs image, can occur because a length value may be negative. An issue was discovered in the Linux kernel in the F2FS filesystem code. A NULL pointer dereference in fscrypt_do_page_crypto() in the fs/crypto/crypto.c function can occur when operating on a file on a corrupted f2fs image. An issue was discovered in the Linux kernel. A NULL pointer dereference and panic in hfsplus_lookup() in the fs/hfsplus/dir.c function can occur when opening a file (that is purportedly a hard link) in an hfs+ filesystem that has malformed catalog data, and is mounted read-only without a metadata directory. A heap-based buffer overflow has been discovered in LibRaw, in the way rollei_load_raw() function in internal/dcraw_common.cpp file handles the input image. An attacker could trigger the flaw by providing a specially crafted Rollei RAW Image, which could result in a crash or other unspecified effects. A flaw was found in LibRaw versions before 0.18.9. Another error within the nikon_coolscan_load_raw() function (internal/dcraw_common.cpp) can be exploited to trigger a NULL pointer dereference. It has been discovered that lftp does not properly sanitize remote file names, leading to a loss of integrity on the local system when reverse mirroring is used. A remote attacker may trick a user to use reverse mirroring on an attacker-controlled FTP server, resulting in the removal of all files in the current working directory of the victim's system. A null pointer dereference flaw was found in the way samba checked database outputs from the LDB database layer. An authenticated attacker could use this flaw to crash a samba server in an Active Diretory Domain Controller configuration. The Samba Active Directory LDAP server was vulnerable to an information disclosure flaw because of missing access control checks. An authenticated attacker could use this flaw to extract confidential attribute values using LDAP search expressions. The timer_create syscall implementation in kernel/time/posix-timers.c in the Linux kernel doesn't properly validate the sigevent->sigev_notify field, which leads to out-of-bounds access in the show_timer function. Certain input files may trigger an integer overflow in ttembed input file processing. This overflow could potentially lead to corruption of the input file due to a lack of checking return codes of fgetc/fputc function calls. An input validation flaw exists in ttembed. With a crafted input file, an attacker may be able to trigger a denial of service condition due to ttembed trusting attacker controlled values. It was found that the "mknod" call derived from mknod(2) can create files pointing to devices on a glusterfs server node. An authenticated attacker could use this to create an arbitrary device and read data from any device attached to the glusterfs server node. A flaw was found in the Linux Kernel in the ucma_leave_multicast() function in drivers/infiniband/core/ucma.c which allows access to a certain data structure after freeing it in ucma_process_join(). This allows an attacker to cause a use-after-free bug and to induce kernel memory corruption, leading to a system crash or other unspecified impact. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. It was discovered that fsync(2) system call in glusterfs client code leaks memory. An authenticated attacker could use this flaw to launch a denial of service attack by making gluster clients consume memory of the host machine. SoundStretch command-line utility packaged with SoundTouch library is vulnerable to heap-based buffer overflow in WavFile.cpp:WavInFile::readHeaderBlock() function that can lead to arbitrary code execution when processing untrusted file input. It was discovered that PostgreSQL failed to properly check authorization on certain statements involved with "INSERT ... ON CONFLICT DO UPDATE". An attacker with "CREATE TABLE" privileges could exploit this to read arbitrary bytes server memory. If the attacker also had certain "INSERT" and limited "UPDATE" privileges to a particular table, they could exploit this to update other columns in the same table. A heap-buffer overflow was found in the way samba clients processed extra long filename in a directory listing. A malicious samba server could use this flaw to cause arbitrary code execution on a samba client. A flaw was found in RPC request using gfs3_mknod_req supported by glusterfs server. An authenticated attacker could use this flaw to write files to an arbitrary location via path traversal and execute arbitrary code on a glusterfs server node. A flaw was found in RPC request using gfs3_lookup_req in glusterfs server. An authenticated attacker could use this flaw to leak information and execute remote denial of service by crashing gluster brick process. A flaw was found in RPC request using gfs3_symlink_req in glusterfs server which allows symlink destinations to point to file paths outside of the gluster volume. An authenticated attacker could use this flaw to create arbitrary symlinks pointing anywhere on the server and execute arbitrary code on glusterfs server nodes. A flaw was found in RPC request using gfs2_create_req in glusterfs server. An authenticated attacker could use this flaw to create arbitrary files and execute arbitrary code on glusterfs server nodes. A flaw was found in RPC request using gfs3_rename_req in glusterfs server. An authenticated attacker could use this flaw to write to a destination outside the gluster volume. A flaw in the netback module allowed frontends to control mapping of requests to request queues. An attacker can change this mapping by requesting invalid mapping requests allowing the (usually privileged) backend to access out-of-bounds memory access for reading and writing. An information-leak flaw was found in openstack-cinder deployments using the third-party EMC ScaleIO backend. It was possible for new volumes to contain previous data if they were created from storage pools which had disabled zero-padding. An attacker could exploit this flaw to obtain sensitive information. It was found that the cobbler API did not validate the client's token for all methods. An unauthenticated attacker could use this flaw to call sensitive methods without having to authenticate first. It was found that paravirt_patch_call/jump() functions in the arch/x86/kernel/paravirt.c in the Linux kernel mishandles certain indirect calls, which makes it easier for attackers to conduct Spectre-v2 attacks against paravirtualized guests. A flaw was found in the way NSS responded to an SSLv2-compatible ClientHello with a ServerHello that had an all-zero random. A man-in-the-middle attacker could use this flaw in a passive replay attack. A weakness was found in postgresql-jdbc. It was possible to provide an SSL Factory and not check the host name if a host name verifier was not provided to the driver. This could lead to a condition where a man-in-the-middle attacker could masquerade as a trusted server by providing a certificate for the wrong host, as long as it was signed by a trusted CA. A flaw was found in the Linux kernel present since v4.0-rc1 and through v4.13-rc4. A crafted network packet sent remotely by an attacker may force the kernel to enter an infinite loop in the cipso_v4_optptr() function in net/ipv4/cipso_ipv4.c leading to a denial-of-service. A certain non-default configuration of LSM (Linux Security Module) and NetLabel should be set up on a system before an attacker could leverage this flaw. It was discovered that the type of the LockDistillerParams parameter is not properly verified. An attacker could possibly exploit this to bypass the -dSAFER protection and crash ghostscript or, possibly, execute arbitrary code in the ghostscript context via a specially crafted PostScript document. It was discovered that the ghostscript .tempfile function did not properly handle file permissions. An attacker could possibly exploit this to exploit this to bypass the -dSAFER protection and delete files or disclose their content via a specially crafted PostScript document. It was discovered that the ghostscript .shfill operator did not properly validate certain types. An attacker could possibly exploit this to bypass the -dSAFER protection and crash ghostscript or, possibly, execute arbitrary code in the ghostscript context via a specially crafted PostScript document. A flaw was found in the crypto subsystem that allowed an attacker to crash the system or possibly escalate privileges with a specially crafted program. An uncontrolled recursion flaw was found in libxkbcommon in the way it parses boolean expressions. A specially crafted file provided to xkbcomp could crash the application. A buffer overflow due to a singed-unsigned comparsion was found in hidp_process_report() in the net/bluetooth/hidp/core.c in the Linux kernel. The buffer length is an unsigned int but gets cast to a signed int which in certain conditions can lead to a system panic and a denial-of-service. It was discovered that libX11 does not properly validate input coming from the server, causing XListExtensions() and XGetFontPath() functions to produce an invalid list of elements that in turn make XFreeExtensionsList() and XFreeFontPath() access invalid memory. An attacker who can either configure a malicious X server or modify the data coming from one, could use this flaw to crash the application using libX11, resulting in a denial of service. An out of bounds write, limited to NULL bytes, was discovered in libX11 in functions XListExtensions() and XGetFontPath(). The length field is considered as a signed value, which makes the library access memory before the intended buffer. An attacker who can either configure a malicious X server or modify the data coming from one could use this flaw to make the program crash or have other unspecified effects, caused by the memory corruption. An off-by-one error has been discovered in libX11 in functions XGetFontPath(), XListExtensions(), and XListFonts(). An attacker who can either configure a malicious X server or modify the data coming from one could use this flaw to make the program crash or have other unspecified effects, caused by the memory corruption. A memory leak in the irda_bind function in net/irda/af_irda.c in the Linux kernel, through 4.16, allows local users to cause a denial of service due to a memory consumption by repeatedly binding an AF_IRDA socket. The irda_setsockopt function in net/irda/af_irda.c in the Linux kernel, through 4.16, allows local users to cause a denial of service (due to a use-after-free of the ias_object and a system crash) or possibly have unspecified other impact by leveraging an AF_IRDA socket. An infinite loop vulnerability was found in libtirpc. With the port to using poll rather than select, exhaustion of file descriptors would cause the server to enter an infinite loop, consuming a large amount of CPU time and denying service to other clients until restarted. A null-pointer dereference vulnerability was found in libtirpc. The return value of makefd_xprt() was not checked in all instances, which could lead to a crash when the server exhausted the maximum number of available file descriptors. A remote attacker could cause an rpc-based application to crash by flooding it with new connections. A vulnerability was discovered in 389-ds-base. The lock controlling the error log was not correctly used when re-opening the log file in log__error_emergency(). An attacker could send a flood of modifications to a very large DN, which would cause slapd to crash. An out-of-bounds read was discovered in elfutils in the way it reads DWARF address ranges information. Function dwarf_getaranges() in dwarf_getaranges.c does not properly check whether it reads beyond the limits of the ELF section. An attacker could use this flaw to cause a denial of service via a crafted file. A flaw was found where an attacker may be able to have an uncontrolled read to kernel-memory from within a vm guest. A race condition between connect() and close() function may allow an attacker using the AF_VSOCK protocol to gather a 4 byte information leak or possibly impersonate AF_VSOCK messages destined to other clients or leak kernel memory. An out-of-bounds access issue was discovered in yurex_read() in drivers/usb/misc/yurex.c in the Linux kernel. A local attacker could use user access read/writes with incorrect bounds checking in the yurex USB driver to crash the kernel or potentially escalate privileges. An out of bounds read in H5L_extern_query at H5Lexternal.c was discovered in the HDF HDF5 1.8.20 library. Using a specially crafted file, an attacker could cause a denial of service condition due to inadequate bounds checking. It was discovered that the ghostscript /invalidaccess checks fail under certain conditions. An attacker could possibly exploit this to bypass the -dSAFER protection and, for example, execute arbitrary shell commands via a specially crafted PostScript document. It was discovered that the ghostscript did not properly validate the operands passed to the setcolor function. An attacker could possibly exploit this to bypass the -dSAFER protection and crash ghostscript or, possibly, execute arbitrary code in the ghostscript context via a specially crafted PostScript document. It was discovered that ghostscript did not properly handle certain stack overflow error conditions. An attacker could possibly exploit this to bypass the -dSAFER protection and crash ghostscript or, possibly, execute arbitrary code in the ghostscript context via a specially crafted PostScript document. It was discovered that ghostscript did not properly verify the key used in aesdecode. An attacker could possibly exploit this to bypass the -dSAFER protection and crash ghostscript or, possibly, execute arbitrary code in the ghostscript context via a specially crafted PostScript document. It was discovered that ghostscript did not properly handle certain error conditions related to the SC and CS PDF operators. An attacker could possibly exploit this to bypass the -dSAFER protection and crash ghostscript or, possibly, execute arbitrary code in the ghostscript context via a specially crafted PostScript document. It was discovered that the ghostscript did not properly restrict access to files open prior to enabling the -dSAFER mode. An attacker could possibly exploit this to bypass the -dSAFER protection and disclose the content of affected files via a specially crafted PostScript document. It was discovered that the ghostscript PDF14 compositor did not properly handle the copying of a device. An attacker could possibly exploit this to bypass the -dSAFER protection and crash ghostscript or, possibly, execute arbitrary code in the ghostscript context via a specially crafted PostScript document. It was discovered that the ghostscript device cleanup did not properly handle devices replaced with a null device. An attacker could possibly exploit this to bypass the -dSAFER protection and crash ghostscript or, possibly, execute arbitrary code in the ghostscript context via a specially crafted PostScript document. It was discovered that the ghostscript gssetresolution and gsgetresolution procedures were available, although they have dangerous side effects. An attacker could possibly exploit this to bypass the -dSAFER protection and crash ghostscript or, possibly, execute arbitrary code in the ghostscript context via a specially crafted PostScript document. An out of bounds write can occur when patching an Openshift object using the 'oc patch' functionality in OpenShift Container Platform 3.x. An attacker can use this flaw to cause a denial of service attack on the Openshift master API service which provides cluster management. A security flaw was found in the chap_server_compute_md5() function in the ISCSI target code in the Linux kernel in a way an authentication request from an ISCSI initiator is processed. An unauthenticated remote attacker can cause a stack buffer overflow and smash up to 17 bytes of the stack. The attack requires the iSCSI target to be enabled on the victim host. Depending on how the target's code was built (i.e. depending on a compiler, compile flags and hardware architecture) an attack may lead to a system crash and thus to a denial of service or possibly to a non-authorized access to data exported by an iSCSI target. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is highly unlikely. An integer overflow flaw was found in the Linux kernel's create_elf_tables() function. An unprivileged local user with access to SUID (or otherwise privileged) binary could use this flaw to escalate their privileges on the system. It was discovered that zsh does not properly validate the shebang of input files and it truncates it to the first 64 bytes. A local attacker may use this flaw to make zsh execute a different binary than what is expected, named with a substring of the shebang one. A path traversal vulnerability has been discovered in Okular, in the way it creates temporary files when reading an Okular archive. Paths are read from content.xml and they are not properly sanitized before being used as template file names for the temporary files created when extracting the Okular archive, thus allowing a local attacker to write files outside the target temporary directory. The OpenStack RabbitMQ container image insecurely retrieves the rabbitmq_clusterer component over HTTP, without validation, during the build stage. This could potentially allow an attacker to serve malicious code to the image builder and install in the resultant container image. When using the Linux bridge ml2 driver, non-privileged tenants are able to create and attach ports without specifying an IP address, bypassing IP address validation. A potential denial of service could occur if an IP address, conflicting with existing guests or routers, is then assigned from outside of the allowed allocation pool. Live-migrated instances are briefly able to inspect traffic for other instances on the same hypervisor. This brief window could be extended indefinitely if the instance's port is set administratively down prior to live-migration and kept down after the migration is complete. This is possible due to the Open vSwitch integration bridge being connected to the instance during migration. When connected to the integration bridge, all traffic for instances using the same Open vSwitch instance would potentially be visible to the migrated guest, as the required Open vSwitch VLAN filters are only applied post-migration. An information leak was discovered in the Linux kernel in cdrom_ioctl_drive_status() function in drivers/cdrom/cdrom.c that could be used by local attackers to read kernel memory at certain location. A command injection was discovered in mgetty in the faxrunq script used to send queued faxes. The shell script faxrunq does not properly escape the arguments passed to faxsend before evaluating the command allowing a user, who has permissions to queue faxes in the system, to execute arbitrary command with elevated privileges. A flaw was found in the Linux kernel. A race condition existed in the ARM Advanced Microcontroller Bus Architecture (AMBA) driver that could result in a double free. A local attacker could use this to cause a denial of service. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely. A double-free of a password policy structure was found in the way slapd was handling certain errors during persistent search. A unauthenticated attacker could use this flaw to crash Directory Server. A flaw was found in the way SpamAssassin processes HTML email containing unclosed HTML tags. A carefully crafted mail message could cause SpamAssassin to consume significant resources. If a large number of these messages are sent, a denial of service could occur potentially delaying or preventing the delivery of email. A flaw was found in the way a local user on the SpamAssassin server could inject code in the meta rule syntax. This could cause the arbitrary code execution on the server when these rules are being processed. A security flaw was found in the ip_frag_reasm() function in net/ipv4/ip_fragment.c in the Linux kernel which can cause a later system crash in ip_do_fragment(). With certain non-default, but non-rare, configuration of a victim host, an attacker can trigger this crash remotely, thus leading to a remote denial of service. An authentication bypass flaw was found in the smart_proxy_dynflow component used by Foreman. A malicious attacker can use this flaw to remotely execute arbitrary commands on machines managed by vulnerable Foreman instances, in a highly privileged context. A flaw was discovered in the HPACK decoder of haproxy, before 1.8.14, that is used for HTTP/2. An out-of-bounds read access in hpack_valid_idx() resulted in a remote crash and denial of service. A flaw was found in the Linux kernel in nfc_llcp_build_sdreq_tlv() in net/nfc/llcp_commands.c that lack of size check may lead to an out of bounds write. A flaw was found in the Linux kernel in the hid_debug_events_read() function in the drivers/hid/hid-debug.c file. A lack of the certain checks may result in receiving userspace buffer overflow and an out-of-bounds write or to the infinite loop. A race condition between pppol2tp_session_create() and l2tp_eth_create() in net/l2tp/l2tp_netlink.c was found in the Linux kernel. Calling l2tp_tunnel_find() may result in a new tunnel being created with tunnel id of a previously removed tunnel which wouldn't be protected by the reference counter. The SoundTouch library is vulnerable to a reachable assertion in BPMDetect:::BPMDetect() function that can cause a denial of service to applications using this library for processing the untrusted file input. A security flaw was discovered in the Linux kernel. The vmacache_flush_all() function in mm/vmacache.c mishandles sequence number overflows. An attacker can trigger a use-after-free (and possibly gain privileges) via certain thread creation, map, unmap, invalidation, and dereference operations. It was discovered that the shutil module of python does not properly sanitize input when creating a zip file on Windows. An attacker could use this flaw to cause a denial of service or add unintended files to the generated archive. Python's elementtree C accelerator failed to initialise Expat's hash salt during initialization. This could make it easy to conduct denial of service attacks against Expat by contructing an XML document that would cause pathological hash collisions in Expat's internal data structures, consuming large amounts CPU and RAM. It was found that a specially crafted search query could lead to excessive CPU consumption in the do_search() function. An unauthenticated attacker could use this flaw to provoke a denial of service. It was found that rbd-target-api service provided by ceph-iscsi-cli was running in debug mode. An unauthenticated attacker could use this to remotely execute arbitrary code and escalate privileges. An issue was discovered in the Linux kernel where an incorrect access check in overlayfs mounts could be used by local attackers to modify or truncate files in the underlying filesystem. An issue was discovered in Open vSwitch (OvS), 2.4.x through 2.4.1, 2.5.x through 2.5.5, 2.6.x through 2.6.3, 2.7.x through 2.7.6, 2.8.x through 2.8.4, and2.9.x through 2.9.2, affecting the parse_group_prop_ntr_selection_method in lib/ofp-util.c. On controllers with the OpenFlow 1.5 decoder enabled, a specially crafted group update can cause an assertion failure, potentially leading to a Denial of Service condition. An issue was discovered in Open vSwitch (OvS), 2.7.x through 2.7.6, 2.8.x through 2.8.4, and 2.9.x through 2.9.2, where the ofproto_rule_insert__() function inside ofproto/ofproto.c is affected by an assertion failure under certain circumstances. A specially crafted flow update applied using the bundling feature of Open vSwitch could potentially cause the assertion failure, potentially leading to incorrect flow information being applied, or a denial of service. An issue was discovered in Open vSwitch (OvS) 2.5.x through 2.5.5, 2.6.x through 2.6.3, 2.7.x through 2.7.6, 2.8.x through 2.8.4, and 2.9.x through 2.9.2 where the decode_bundle function inside lib/ofp-actions.c is affected by a buffer over-read issue during BUNDLE action decoding. A specially crafted flow update applied using the bundling feature of Open vSwitch could potentially cause a crash leading to a denial of service. An uncontrolled format string vulnerability has been discovered in udisks when it mounts a filesystem with a malformed label. A local attacker may use this flaw to leak memory, make the udisks service crash, or cause other unspecified effects. It was discovered that sos-collector does not properly set the default permissions of newly created files, making all files created by the tool readable by any local user. A local attacker may use this flaw by waiting for a legit user to run sos-collector and steal the collected data in the /var/tmp directory. It was found that the fix for CVE-2018-10927, CVE-2018-10928, CVE-2018-10929, CVE-2018-10930, and CVE-2018-10926 was incomplete. A remote, authenticated attacker could use one of these flaws to execute arbitrary code, create arbitrary files, or cause denial of service on glusterfs server nodes via symlinks to relative paths. A buffer overflow was found in strncpy of the pl_getxattr() function. An authenticated attacker could remotely overflow the buffer by sending a buffer of larger length than the size of the key resulting in remote denial of service. A buffer overflow on the heap was found in gf_getspec_req RPC request. A remote, authenticated attacker could use this flaw to cause denial of service and read arbitrary files on glusterfs server node. A flaw was found in the way glusterfs server handles client requests. A remote, authenticated attacker could set arbitrary values for the GF_XATTROP_ENTRY_IN_KEY and GF_XATTROP_ENTRY_OUT_KEY during xattrop file operation resulting in creation and deletion of arbitrary files on glusterfs server node. It was discovered that zziplib is vulnerable to a directory traversal flaw in most of its unzip binaries, including unzip-mem, unzzipcat-mem, unzzipcat-big, unzzipcat-mix, and unzzipcat-zip. An attacker may use this flaw to write files outside the intended target directory, overwriting existing files, or creating new ones. A missing address check in the callers of the show_opcodes() in the Linux kernel allows an attacker to dump the kernel memory at an arbitrary kernel address into the dmesg log. A flaw was found in glusterfs server which allowed clients to create io-stats dumps on server node. A remote, authenticated attacker could use this flaw to create io-stats dump on a server without any limitation and utilizing all available inodes resulting in remote denial of service. A flaw was found in glusterfs server which allowed repeated usage of GF_META_LOCK_KEY xattr. A remote, authenticated attacker could use this flaw to create multiple locks for single inode by using setxattr repetitively resulting in memory exhaustion of glusterfs server node. An issue was discovered in the proc_pid_stack function in fs/proc/base.c in the Linux kernel. An attacker with a local account can trick the stack unwinder code to leak stack contents to userspace. The fix allows only root to inspect the kernel stack of an arbitrary task. An option injection flaw has been discovered in git when it recursively clones a repository with sub-modules. A remote attacker may configure a malicious repository and trick a user into recursively cloning it, thus executing arbitrary commands on the victim's machine. An integer overflow issue was found in the RTL8139 NIC emulation in QEMU. It could occur while receiving packets over the network if the size value is greater than INT_MAX. Such overflow would lead to stack buffer overflow issue. A user inside guest could use this flaw to crash the QEMU process, resulting in DoS scenario. An integer overflow issue was found in the AMD PC-Net II NIC emulation in QEMU. It could occur while receiving packets, if the size value was greater than INT_MAX. Such overflow would lead to stack buffer overflow issue. A user inside guest could use this flaw to crash the QEMU process resulting in DoS. A potential integer overflow issue was found in the networking back-end of QEMU. It could occur while receiving packets, because it accepted packets with large size value. Such overflow could lead to OOB buffer access issue. A user inside guest could use this flaw to crash the QEMU process resulting in DoS. It was found that usage of snprintf function in feature/locks translator of glusterfs server was vulnerable to a format string attack. A remote, authenticated attacker could use this flaw to cause remote denial of service. A vulnerability was discovered in the Linux kernel that allows an attacker to escalate privileges with using a 64-bit ARM architecture. A local attacker with permission to create KVM-based virtual machines can both panic the hypervisor by triggering an illegal exception return (resulting in a DoS) and to redirect execution elsewhere within the hypervisor with full register control, instead of causing a return to the guest. A flaw was found in the Linux kernel's handling of complex interactions between netlink, IP, and AH style packets which can enter a state where the used memory will not be freed. This can eventually use all memory and possibly crash userspace programs due to lack of available memory. An incorrect permission check for -modulepath and -logfile options when starting Xorg X server allows unprivileged users with the ability to log in to the system via physical console to escalate their privileges and run arbitrary code under root privileges. A flaw was found in Intel QuickAssist Technology for Linux before version 4.2. An insufficient access control in the driver stack may allow an unprivileged user to potentially disclose information via local access. A security flaw was found in the Linux kernel in the adjust_scalar_min_max_vals() function in kernel/bpf/verifier.c. A faulty computation of numeric bounds in the BPF verifier permits out-of-bounds memory accesses because this function mishandles 32-bit right shifts. This can lead to a system panic and a denial of service or other unspecified impact. It was discovered that systemd-network does not correctly keep track of a buffer size when constructing DHCPv6 packets. This flaw may lead to an integer underflow that can be used to produce an heap-based buffer overflow. A malicious host on the same network segment as the victim's one may advertise itself as a DHCPv6 server and exploit this flaw to cause a Denial of Service or potentially gain code execution on the victim's machine. It was discovered that systemd is vulnerable to a state injection attack when deserializing the state of a service. Properties longer than LINE_MAX are not correctly parsed and an attacker may abuse this flaw in particularly configured services to inject, change, or corrupt the service state. A use-after-free flaw can occur in the Linux kernel due to a race condition between packet_do_bind() and packet_notifier() functions called for an AF_PACKET socket. An unprivileged, local user could use this flaw to induce kernel memory corruption on the system, leading to an unresponsive system or to a crash. Due to the nature of the flaw, privilege escalation cannot be fully ruled out. An out-of-bounds heap buffer r/w access issue was found in the NVM Express Controller emulation in QEMU. It could occur in nvme_cmb_ops routines in a nvme device. A guest user/process could use this flaw to crash the QEMU process resulting in denial of service or, potentially, run arbitrary code with privileges of the QEMU process. The User module in Ansible leaks any data which is passed on as a parameter to ssh-keygen. This could lead to undesirable situations such as passphrase credentials being passed as a parameter for the ssh-keygen executable, showing those credentials in clear text form for every user which have access just to the process list. An information disclosure is possible by manipulating the SSH private key filename of a std.ssh action in OpenStack Mistral before 7.0.1. Using this flaw, it is possible to determine the presence of a file path on the host executing the std.ssh action based on the returned error message. A flaw was found in the Intel processor execution engine sharing on SMT (e.g. Hyper-Threading) architectures. An attacker running a malicious process on the same core of the processor as the victim process can extract certain secret information. The tog-pegasus package is not installed by default on Red Hat Enterprise Linux. tog-pegasus supplied by Red Hat binds only to one port (as plain http is disabled), port 5989. The default firewall installed by Red Hat Enterprise Linux will block remote access to this port. In normal use it's unlikely you'd want to have this port accessible outside of an intranet anyway, and it's likely to be blocked by enterprise border firewalls. However if tog-pegasus has been installed and unblocked through the fireware, the Red Hat Security Response Team believes that it would still be hard to remotely exploit this issue to execute arbitrary code due to the default SELinux targeted policy on Enterprise Linux 4 and 5, and the SELinux memory protections enabled by default on Enterprise Linux 5. Users can lower the impact of this flaw by making sure their privacy settings only allow Pidgin to accept messages from the users on their buddy list. This will prevent exploitation of this flaw by other random MSN users. For users that do not run applications that use SCTP, you can prevent the sctp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist sctp This way, the sctp module cannot be loaded accidentally, which may occur if an application that requires SCTP is started. A reboot is not necessary for this change to take effect. For users that do not run applications that use TIPC, you can prevent the TIPC module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist tipc This way, the TIPC module cannot be loaded accidentally, which may occur if an application that requires TIPC is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep tipc You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound For users that do not run applications that use RDS, you can prevent the rds module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist rds This way, the rds module cannot be loaded accidentally, which may occur if an application that requires RDS is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep rds You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound For users that do not run applications that use RDS, you can prevent the rds module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist rds This way, the rds module cannot be loaded accidentally, which may occur if an application that requires RDS is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep rds You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound mod_autoindex can be configured to ignore request query arguments provided by the client by adding IgnoreClient option to the IndexOptions directive: http://httpd.apache.org/docs/2.2/mod/mod_autoindex.html#indexoptions.ignoreclient For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound Disabling the UserDir directive and also setting AllowOverride None should prevent the processing of perl in user .htaccess files. Instead of --syn use --tcp-flags SYN,RST,ACK SYN in your rulesets in case you want to also match packets with both SYN+FIN flags set. By default, the system wide temporary directory is configured as the repository to use when uploading files. Setting the repository to another location will mitigate this vulnerability. Do not open untrusted filesystem image files on production systems. 'MyspacePolicy' permits tag("form", "action", ONSITE_OR_OFFSITE_URL, "method"); Fix 'MyspacePolicy' by restricting the policy to ONSITE_URL only or perhaps <form> could be banned entirely. Applications running with a security manager that make direct use of classes in these JDK internal packages, need to adjust their security policy to grant access. See Java Security Policy Files documentation. Avoid using HTTP NTLM in your application. If you must use NTLM authentication, ensure that it is the only requested authentication method (use --ntlm specifically, do not use --anyauth or other authentication methods). http://h30499.www3.hp.com/t5/HP-Security-Research-Blog/Protect-your-Struts1-applications/ba-p/6463188#.VCaGk3V53Ua To work-around this issue, disable SSL-bump for clients affected by adding "ssl_bump none" rule(s) at the top of the ssl_bump configuration directives. Alternatively, disable the SSL-bump feature completely by removing the "ssl-bump" option from all http_port and/or https_port configuration directives. add this in the host httpd conf global config, e.g. at the end of /etc/httpd/conf.d/000002_openshift_origin_broker_proxy.conf: RequestHeader unset X-Remote-User Don't allow environment variables 'OPTIND' and 'TRY_BLOCK_ERROR' to be inherited by shells called through zsh. Mitigated by default on Red Hat Enterprise Linux versions 5, 6 and 7, since this is the default configuration on those versions. "A configuration file in the Java library directory (e.g. /jdk1.2/lib) can be used to override the default configuration file with system-wide properties. In addition, a configuration file can be placed in the classpath and will override both the system wide properties and Castor-default configuration." [1] Adding the following content in any of the above mentioned configuration files will act as a viable mitigation against this flaw. > org.exolab.castor.sax.features=\ > http://apache.org/xml/features/disallow-doctype-decl > > org.exolab.castor.sax.features-to-disable=\ > http://xml.org/sax/features/external-general-entities,\ > http://xml.org/sax/features/external-parameter-entities,\ > http://apache.org/xml/features/nonvalidating/load-external-dtd Note that using this configuration after upgrading to a version of Castor containing a fix for this issue might override any future hardening or changes to default behavior. [1] http://castor.codehaus.org/conf-lib.html - Whenever possible, exercise caution when opening documents sent by unknown/untrusted parties. - If "Update Links" dialog is seen, when opening a document, do not send this document to others, since it may be possible that local files got attached to the document. (The exploit only works when the document is sent over to the attacker after opening it on your system using LibreOffice/OpenOffice) When using HornetQ REST in an application, add the following snippet to its web.xml file to disable entity expansion in RESTEasy as used by HornetQ REST endpoints: <context-param> <param-name>resteasy.document.expand.entity.references</param-name> <param-value>false</param-value> </context-param> Note that this <context-param> setting has precedence over <init-param>, and will override a contrary setting in an <init-param> element. For Red Hat Enterprise Linux 6 do -- ]# echo "install pppol2tp /bin/true" > /etc/modprobe.d/pppol2tp.conf For Red Hat Enterprise Linux 7 do -- ]# echo "install l2tp_ppp /bin/true" > /etc/modprobe.d/l2t_pppp.conf Or, alternatively, when pppol2tp/l2tp_ppp module can't be blacklisted and needs to be loaded, you can use the following systemtap script -- 1) On the host, save the following in a file with the ".stp" extension -- probe module("*l2tp*").function("pppol2tp_*etsockopt").call { $level = 273; } 2) Install the "systemtap" package and any required dependencies. Refer to the "2. Using SystemTap" chapter in the Red Hat Enterprise Linux 6 "SystemTap Beginners Guide" document, available from docs.redhat.com, for information on installing the required -debuginfo packages. 3) Run the "stap -g [filename-from-step-1].stp" command as root. If the host is rebooted, the changes will be lost and the script must be run again. Alternatively, build the systemtap script on a development system with "stap -g -p 4 [filename-from-step-1].stp", distribute the resulting kernel module to all affected systems, and run "staprun -L <module>" on those. When using this approach only systemtap-runtime package is required on the affected systems. Please notice that the kernel version must be the same across all systems. As provided at http://www.elasticsearch.org/community/security/, Users should either set "http.cors.enabled" to false, or set "http.cors.allow-origin" to the value of the server that should be allowed access, such as localhost or a server hosting Kibana. Disabling CORS entirely with the former setting is more secure, but may not be suitable for all use cases. For Satellite 6.x and Sam 1.x you can simply firewall elasticsearch to trusted users only (e.g. root, katello, foreman). For instructions on this please see: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html-single/Installation_Guide/index.html#sect-Red_Hat_Satellite-Installation_Guide-Red_Hat_Satellite_Installation-Configuring_Red_Hat_Satellite_Manually Add a polkit rule to disable the org.kde.kcontrol.kcmclock.save action. This rule can be tweaked by configuring file /usr/share/polkit-1/actions/org.kde.kcontrol.kcmclock.policy no = NOT AUTHORIZED for inactive sessions <allow_inactive>no</allow_inactive> auth_admin = Administration Authorization is Required to perform such action. Change this to 'no' <allow_active>no</allow_active> Issue these commands to explicitly generate a strong key and add it to the ntpd configuration: echo trustedkey 65535 >> /etc/ntp.conf printf "65535\tM\t%s\n" $(tr -cd a-zA-Z0-9 < /dev/urandom | head -c 16) >> /etc/ntp/keys The generated key has about 95 bits of entropy. Add these lines (included by default starting with Red Hat Enterprise Linux 5) to the configuration file /etc/ntp.conf: restrict default kod nomodify notrap nopeer noquery restrict -6 default kod nomodify notrap nopeer noquery restrict 127.0.0.1 restrict -6 ::1 This restricts server-type functionality to localhost. If ntpd needs to perform time service for specific hosts and networks, you have to list them with suitable restrict statements. Remove or comment out all configuration directives beginning with the crypto keyword in your ntp.conf file. The UDF filesystem is enabled via loading the UDF kernel module. The kernel module can be prevented from loading via blacklisting see https://access.redhat.com/solutions/41278 for more information. The UDF filesystem is enabled via loading the UDF kernel module. The kernel module can be prevented from loading via blacklisting see https://access.redhat.com/solutions/41278 for more information. The UDF filesystem is enabled via loading the UDF kernel module. The kernel module can be prevented from loading via blacklisting see https://access.redhat.com/solutions/41278 for more information. The UDF filesystem is enabled via loading the UDF kernel module. The kernel module can be prevented from loading via blacklisting see https://access.redhat.com/solutions/41278 for more information. Do not use any applications which call the affected nan* functions. These functions are used only very rarely. On Samba versions 4.0.0 and above, add the line: rpc_server:netlogon=disabled to the [global] section of your smb.conf. For Samba versions 3.6.x and earlier, this workaround is not available. Users should upgrade to Apache Standard Taglibs 1.2.3 or later. This version uses JAXP’s FEATURE_SECURE_PROCESSING to restrict XML processing. Depending on the Java runtime version in use, additional configuration may be required: Java8: External entity access is automatically disabled if a SecurityManager is active. Java7: JAXP properties may need to be used to disable external access. See http://docs.oracle.com/javase/tutorial/jaxp/properties/properties.html Java6 and earlier: A new system property org.apache.taglibs.standard.xml.accessExternalEntity may be used to specify the protocols that can be used to access external entities. This defaults to "all" if no SecurityManager is present and to "" (thereby disabling access) if a SecurityManager is detected. Disabling the cups web interface significantly reduces the impact of this security flaw. Prevent access to URLs containing "../" or "..\" in web server configuration To work around this issue, instead of configuring NTP hosts as peers with the 'peer' directive, use the 'server' directive on both hosts so that the connection uses a regular client/server mode of operation. More information about how to configure NTP can be found at: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Configuring_NTP_Using_ntpd.html Autokey authentication between NTP peers is not sufficient to fully mitigate this issue. Disabling keep-alive (via the "KeepAlive Off" configuration setting, which is used in the default configuration in Red Hat Enterprise Linux 6 and earlier) will prevent httpd from reading multiple requests from a single TCP connection, and should also prevent it from handling any request that was smuggled through the proxy in front of the httpd. As disabling keep-alive may be undesired for performance reasons, an alternative way to mitigate this issue is by rejecting connections with requests using chunked encoding. Unlike chunked encoded HTTP responses, chunked encoded HTTP requests are not believed to be commonly used. The following mod_rewrite rule will reject requests with the "Transfer-Encoding: chunked" HTTP header: RewriteEngine on RewriteCond %{HTTP:Transfer-Encoding} ^chunked$ RewriteRule .* - [R=400] This rule can be used with httpd versions as shipped in Red Hat Enterprise Linux 5 and later. If deployed, administrators should monitor httpd logs for an increase in the number of requests resulting in HTTP error code 400 (Bad Request), which may indicate legitimate clients actually trying to use chunked encoded requests. Please add: create 0600 root root to the /etc/logrotate.d/syslog file, this will ensure the file is created with permissions when logrotate runs. It is also recommended that users manually set the permissions on existing or newly installed log files in order to prevent access by untrusted users. Add pam_warn and pam_deny rules to /etc/pam.d/chfn and /etc/pam.d/chsh to prevent non-root users from using this functionality. With these edits, the files should contain: #%PAM-1.0 auth sufficient pam_rootok.so auth required pam_warn.so auth required pam_deny.so auth include system-auth account include system-auth password include system-auth session include system-auth Afterwards, attempts by unprivileged users to use chfn and chsh (and the respective functionality in the userhelper program) will fail, and will be logged (by default in /var/log/secure). Add pam_warn and pam_deny rules to /etc/pam.d/chfn and /etc/pam.d/chsh to prevent non-root users from using this functionality. With these edits, the files should contain: auth sufficient pam_rootok.so auth required pam_warn.so auth required pam_deny.so auth include system-auth account include system-auth password include system-auth session include system-auth After these changes, attempts by unprivileged users to use chfn and chsh (and the respective functionality in the userhelper program) will fail, and will be logged (by default in /var/log/secure). Apply the following patch on the MethodClosure class (src/main/org/codehaus/groovy/runtime/MethodClosure.java): public class MethodClosure extends Closure { + private Object readResolve() { + throw new UnsupportedOperationException(); + } Alternatively, you should make sure to use a custom security policy file (using the standard Java security manager) or make sure that you do not rely on serialization to communicate remotely. It is recommended to disable abrt via the following command line, till the flaws have been resolved: sysctl -w kern.core_pattern=core Note: This will reset, if abrt is re-started. The permissions on log files can be changed, e.g. using "chmod o-rwx" to prevent anyone but the user and group owner of the file from reading it. Additionally the group permissions can also be removed, e.g. "chmod g-rwx" if only the user owning the file should be able to see it. This issue only affects programs using this program in forms such as: $parser = XML::LibXML->new or $XML_DOC = $parser->load_xml if you use the form: $XML_DOC = XML::LibXML->load_xml this vulnerability will not be exposed. You can check whether ping socket functionality is enabled by examining the net.ipv4.ping_group_range sysctl value: ~]# sysctl net.ipv4.ping_group_range net.ipv4.ping_group_range = 1 0 "1 0" is the default value and disables the ping socket functionality even for root user. Any other value means that the ping socket functionality might be enabled for certain users on the system. To mitigate this vulnerability make sure that you either allow the functionality to trusted local users (groups) only or set the net.ipv4.ping_group_range sysctl to the default and disabled state: ~]# sysctl net.ipv4.ping_group_range="1 0" Please note that this might prevent some programs relying on this functionality from functioning properly. This flaw can be mitigated in wireshark by disabling the WCP protocol dissector. In wireshark GUI application click on Analyze->Enabled Protocols and search for "WCP" and disable in. When using "tshark", the text interface, create a file called "disabled_protos" in the preferences folder (normally .wireshark folder in the home directory of the user running wireshark) and add "WCP" to it. This should disable the WCP protocol. This flaw can be mitigated in wireshark by disabling the X11 protocol dissector. In wireshark GUI application click on Analyze->Enabled Protocols and search for "X11" and disable in. When using "tshark", the text interface, create a file called "disabled_protos" in the preferences folder (normally .wireshark folder in the home directory of the user running wireshark) and add "X11" to it. This should disable the X11 protocol. For Satellite 6.x and Sam 1.x you can simply firewall elasticsearch to trusted users only (e.g. root, katello, foreman). For instructions on this please see: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html-single/Installation_Guide/index.html#sect-Red_Hat_Satellite-Installation_Guide-Red_Hat_Satellite_Installation-Configuring_Red_Hat_Satellite_Manually The UDF filesystem is enabled via loading the UDF kernel module. The kernel module can be prevented from loading via blacklisting see https://access.redhat.com/solutions/41278 for more information. This issue does not affect most systems by default. An administrator would need to have enabled the BPF JIT to be affected. It can be disabled immediately with the command: # echo 0 > /proc/sys/net/core/bpf_jit_enable Or it can be disabled for all subsequent boots of the system by setting a value in /etc/sysctl.d/44-bpf-jit-disable ## start file ## net.core.bpf_jit_enable=0 ## end file ## Add “LimitRequestBody 100000” to the <Location> stanza, like this: <Location "/KdcProxy"> Satisfy Any Order Deny,Allow Allow from all WSGIProcessGroup kdcproxy WSGIApplicationGroup kdcproxy LimitRequestBody 100000 </Location> Disable remote runtime configuration with ntpq or ntpdc. In the default NTP configuration on Red Hat Enterprise Linux, runtime configuration with ntpq or ntpdc is limited to localhost. If you do deploy a JMS publisher, and subscriber, and don't trust the messages sent to you by your clients, you could mitigate this issue by installing a Java agent which restricts the classes which can be deserialized. This is an article with the recommended approach: https://access.redhat.com/solutions/2190911 You could also mitigate this issue using the features of the Java Virtual Machine added in JEP 290: http://openjdk.java.net/jeps/290 For Satellite 6.x and Sam 1.x you can simply firewall elasticsearch to trusted users only (e.g. root, katello, foreman). For instructions on this please see: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html-single/Installation_Guide/index.html#sect-Red_Hat_Satellite-Installation_Guide-Red_Hat_Satellite_Installation-Configuring_Red_Hat_Satellite_Manually This issue can be mitigated by disabling keyboard-interactive authentication method. That can be achieved by setting "ChallengeResponseAuthentication no" in the /etc/ssh/sshd_config configuration file and restarting the sshd service. This flaw can be mitigated in wireshark by disabling the ZigBee protocol dissector. In wireshark GUI application click on Analyze->Enabled Protocols and search for "ZigBee" and disable in. When using "tshark", the text interface, create a file called "disabled_protos" in the preferences folder (normally .wireshark folder in the home directory of the user running wireshark) and add "ZigBee" to it. This should disable the ZigBee protocol. This flaw can be mitigated in wireshark by disabling the waveagent protocol dissector. In wireshark GUI application click on Analyze->Enabled Protocols and search for "waveagent" and disable in. When using "tshark", the text interface, create a file called "disabled_protos" in the preferences folder (normally .wireshark folder in the home directory of the user running wireshark) and add "waveagent" to it. This should disable the waveagent protocol. Avoid recursive cloning or updating of git submodules without checking the submodule URL. Non-recursive cloning is the default in git, so user needs to change this to become vulnerable ("e.g. by specifying --recursive"). Use following code to monkey-patch http_basic_authenticate_with method in ActionController: ~~~ module ActiveSupport module SecurityUtils def secure_compare(a, b) return false unless a.bytesize == b.bytesize l = a.unpack "C#{a.bytesize}" res = 0 b.each_byte { |byte| res |= byte ^ l.shift } res == 0 end module_function :secure_compare def variable_size_secure_compare(a, b) secure_compare(::Digest::SHA256.hexdigest(a), ::Digest::SHA256.hexdigest(b)) end module_function :variable_size_secure_compare end end module ActionController class Base def self.http_basic_authenticate_with(options = {}) before_action(options.except(:name, :password, :realm)) do authenticate_or_request_with_http_basic(options[:realm] || "Application") do |name, password| # This comparison uses & so that it doesn't short circuit and # uses `variable_size_secure_compare` so that length information # isn't leaked. ActiveSupport::SecurityUtils.variable_size_secure_compare(name, options[:name]) & ActiveSupport::SecurityUtils.variable_size_secure_compare(password, options[:password]) end end end end end ~~~ Disable NTP autokey authentication by removing, or commenting out, all configuration directives beginning with the 'crypto' keyword in your ntp.conf file. Disable NTP autokey authentication by removing, or commenting out, all configuration directives beginning with the 'crypto' keyword in your ntp.conf file. Disable NTP autokey authentication by removing, or commenting out, all configuration directives beginning with the 'crypto' keyword in your ntp.conf file. Disable NTP autokey authentication by removing, or commenting out, all configuration directives beginning with the 'crypto' keyword in your ntp.conf file. Disable remote runtime configuration with ntpq or ntpdc. In the default NTP configuration on Red Hat Enterprise Linux, runtime configuration with ntpq or ntpdc is limited to localhost. Do not add the "limited" configuration option to any restrict lines in the ntp.conf file. On systems where the guest kernel is controlled by the host rather than guest administrator, running only kernels which do not make use of multicall functionality will prevent untrusted guest users from exploiting this issue. However untrusted guest administrators can still trigger it unless further steps are taken to prevent them from loading code into the kernel (e.g. by disabling loadable modules etc) or from using other mechanisms which allow them to run code at kernel privilege. The problematic log messages are issued with priority Warning. Therefore they can be rate limited by adding "loglvl=error/warning" to the hypervisor command line or suppressed entirely by adding "loglvl=error". On systems where the guest kernel is controlled by the host rather than guest administrator, running only kernels which do not call these hypercalls will also prevent untrusted guest users from exploiting this issue. However untrusted guest administrators can still trigger it unless further steps are taken to prevent them from loading code into the kernel (e.g. by disabling loadable modules etc) or from using other mechanisms which allow them to run code at kernel privilege. There is no known mitigation. Switching from disaggregated to a non-disaggregated operation does NOT mitigate these vulnerabilities. Rather, it simply recategorises the vulnerability to hostile management code, regarding it "as designed"; thus it merely reclassifies these issues as "not a bug". Users and vendors of disaggregated systems should not change their configuration. Running only HVM guests will avoid this vulnerability. On systems where the guest kernel is controlled by the host rather than guest administrator, running only kernels which do not call these hypercalls will also prevent untrusted guest users from exploiting this issue. However untrusted guest administrators can still trigger it unless further steps are taken to prevent them from loading code into the kernel (e.g. by disabling loadable modules etc) or from using other mechanisms which allow them to run code at kernel privilege. The leak is small. Preventing the creation of large numbers of new domains, and limiting the number of times an existing domain can be rebooted, can reduce the impact of this vulnerability. Switching from disaggregated to a non-disaggregated operation does NOT mitigate the XEN_DOMCTL_max_vcpus vulnerability. Rather, it simply recategorises the vulnerability to hostile management code, regarding it "as designed"; thus it merely reclassifies these issues as "not a bug". Users and vendors of disaggregated systems should not change their configuration. Running only PV guests will avoid this issue. Running HVM guest without enabling Populate-on-Demand mode (so, ensuring that maxmem==memory) will avoid this issue. The problematic log messages are issued with priority Warning. Therefore they can be rate limited by adding "loglvl=error/warning" to the hypervisor command line or suppressed entirely by adding "loglvl=error". On systems where the guest kernel is controlled by the host rather than guest administrator, running only kernels which do not call these hypercalls will also prevent untrusted guest users from exploiting this issue. However untrusted guest administrators can still trigger it unless further steps are taken to prevent them from loading code into the kernel (e.g. by disabling loadable modules etc) or from using other mechanisms which allow them to run code at kernel privilege. Reducing the guest's memory target, after guest startup, can cause the guest's ballon driver to eliminate the PoD discrepancy. If the guest successfully balloons down, it will no longer be vulnerable. Do not use NTP's broadcast mode by not configuring the "broadcast" directive in the ntp.conf file. Use the 'restrict default nomodify' directive in ntp.conf to disable modification of ntp.conf via the ntpq command. Keep the number of restriction list entries in ntp.conf lower than 500. Keep the number of restriction list entries in ntp.conf lower than 500. Do not use NTP's broadcast mode by not configuring the "broadcast" directive in the ntp.conf file. https://jenkins-ci.org/content/mitigating-unauthenticated-remote-code-execution-0-day-jenkins-cli This issue can be mitigated by one of the following methods: adding the noquery option to all restrict entries in ntp.conf, configuring ntpd to get time from multiple sources, or using a restriction list in your ntp.conf to limit who is allowed to issue ntpq and ntpdc queries. Note that ntpdc queries are disabled by default. This issue can be mitigated by one of the following methods: disabling ntpq in ntp.conf, configuring ntpd to get time from multiple sources, or using a restriction list in your ntp.conf to limit who is allowed to issue ntpq queries. The vulnerability can be avoided if the guest kernel is controlled by the host rather than guest administrator, provided that further steps are taken to prevent the guest administrator from loading code into the kernel (e.g. by disabling loadable modules etc) or from using other mechanisms which allow them to run code at kernel privilege. In Xen HVM, controlling the guest's kernel would involve locking down the bootloader. The vulnerability can be avoided if the guest kernel is controlled by the host rather than guest administrator, provided that further steps are taken to prevent the guest administrator from loading code into the kernel (e.g. by disabling loadable modules etc) or from using other mechanisms which allow them to run code at kernel privilege. In Xen HVM, controlling the guest's kernel would involve locking down the bootloader. Disable debug logging in named. Check time values before they are passed to strftime, or call strftime only with struct tm values computed by gmtime or localtime. The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation. Do not use any applications which call hcreate or hcreate_r with a large size argument. These functions are used only rarely, and most callers supply a constant argument. Other applications calculate the size argument in such a way that the error condition cannot be triggered. Do not use applications which call catopen with unbounded strings. The catopen function is rarely used. Typical application usage involves passing a short, constant string to catopen, so most applications are not affect even if they call catopen. Do not use untrusted magic files. A possible mitigation is to only remove CPU's while the system is shut down. This will prevent local attackers from being able to abuse this flaw. Use following code to monkey-patch mime types cache and disable caching. ``` require 'action_dispatch/http/mime_type' Mime.const_set :LOOKUP, Hash.new { |h,k| Mime::Type.new(k) unless k.blank? } ``` Alternatively perform filtering of mime types in the Accept header to allow only known types. Avoid passing untrusted input to render method, or verify the input using whitelist before passing it to the render method: ``` def index render verify_template(params[:id]) end private def verify_template(name) # add verification logic particular to your application here end ``` Do not allow arbitrary attributes to be passed to models. In Rails with Strong Parameters, make sure to not call permit! method, which bypasses strong parameters protections. Outside of rails, use whitelisting to filter only allowed attributes before passing them to models. 1. The vulnerable roaming code can be permanently disabled by adding the undocumented option "UseRoaming no" to the system-wide configuration file (usually /etc/ssh/ssh_config), or per-user configuration file (~/.ssh/config), or command-line (-o "UseRoaming no"). 2. If an OpenSSH client is disconnected from an SSH server that offers roaming, it prints "[connection suspended, press return to resume]" on stderr, and waits for '\n' or '\r' on stdin (and not on the controlling terminal) before it reconnects to the server; advanced users may become suspicious and press Control-C or Control-Z instead, thus avoiding the information leak. However, SSH commands that use the local stdin to transfer data to the remote server are bound to trigger this reconnection automatically (upon reading a '\n' or '\r' from stdin). Moreover, these non-interactive SSH commands (for example, backup scripts and cron jobs) commonly employ public-key authentication and are therefore perfect targets for this information leak. This flaw, and others like it, are mitigated by enabling hardlink and symlink protections. These protections are enabled by default in Red Hat Enterprise Linux 7 and this vulnerability will only be exploitable if disabled. Ensure the following protections are enabled: sysctl -w fs.protected_hardlinks=1 sysctl -w fs.protected_symlinks=1 This issue can be mitigated by configuring Redis to require clients to authenticate with password. Password authentication can be enabled using the 'requirepass' directive in the redis.conf configuration file. The following examples will remove '.' from the module path : RHEL6 and above : Create a file /usr/local/share/perl5/sitecustomize.pl containing the line "pop @INC if $INC[-1] eq '.';" RHEL5: Create a perl module with the same code in a BEGIN block, and use the 'PERL5OPT=-m<module-name>' environment variable to load it before execution of a perl program. Disabling modeline support in .vimrc by adding "set nomodeline" will prevent exploitation of this flaw. By default, modeline is enabled for ordinary users but disabled for root. This problem is only exposed when the user uses server-side prepared statement support (mysql_server_prepare=1), which is NOT default behavior and was turned off back for all drivers per MySQL AB decision in 2006 due to issues with server-side prepared statements in the server. Use the default driver setting which uses emulated prepared statements. Restrict access to the control channel (by using the "controls" configuration statement in named.conf) to allow connection only from trusted systems. Note that if no "controls" statement is present, named defaults to allowing control channel connections only from localhost (127.0.0.1 and ::1) if and only if the file rndc.key exists in the configuration directory and contains valid key syntax. If rndc.key is not present and no "controls" statement is present in named.conf, named will not accept commands on the control channel. Assure only trusted hosts have access to the trustedkey. The following mitigation is suggested by upstream. The samba-tool command and the AD DC mode honours the undocumented "gensec_gssapi:delegation=no" option in the [global] section of the smb.conf file. Controlling Kerberos forwarding =============================== In the Active Directory world it's possible for administrators to limit the delegation. User and computer objects can both act as Kerberos users and also as Kerberos services. Both types of objects have an attribute called 'userAccountControl' which is a bitmask that controls the behavior of the account. The following three values have impact on possible delegation: 0x00100000: UF_NOT_DELEGATED: The UF_NOT_DELEGATED can be used to disable the ability to get forwardable TGT for the account. It means the KDC will respond with an error if the client asks for the forwardable ticket. The client typically gives up and removes the GSS_C_DELEG_FLAG flag and continues without passing delegated credentials. Administrators can use this to disable possible delegation for the most privileged accounts (e.g. administrator accounts). 0x00080000: UF_TRUSTED_FOR_DELEGATION If the UF_TRUSTED_FOR_DELEGATION is set on an account a KDC will include the OK_AS_DELEGATE flag in a granted service ticket. If the client application uses just GSS_C_DELEG_POLICY_FLAG (instead of GSS_C_DELEG_FLAG) gssapi/Kerberos libraries typically only include delegated credentials when the service ticket includes the OK_AS_DELEGATE flag. Administrators can use this to control which services will get delegated credentials, for example if the service runs in a trusted environment and actually requires the presence of delegated credentials. 0x01000000: UF_TRUSTED_TO_AUTHENTICATE_FOR_DELEGATION The UF_TRUSTED_TO_AUTHENTICATE_FOR_DELEGATION is not really relevant for this CVE and just listed here for completeness. This flag is relevant for the S4U2Proxy feature, where a service can ask the KDC for a proxied service ticket which can impersonate users to other services. Please refer to https://access.redhat.com/articles/2360521 for more information. 1.SSL/TLS configurations should prefer AES over DES. Versions of OpenSSL shipped with Red Hat Enterprise Linux 6 and 7 already do so. In the version of OpenSSL shipped with Red Hat Enterprise Linux 5, 3DES is listed below the AES-256 cipher and above the AES-128 cipher, therefore AES-256 based ciphersuite should not be disabled on the server. 2. Servers using OpenSSL, should not disable AES-128 and AES-256 ciphersuites. Versions of Apache shipped with Red Hat Enterprise Linux use the default cipher string, in which AES is preferred over DES/3DES based ciphersuites. For JBoss Middleware, and Java mitigations, please review this knowledge base article: https://access.redhat.com/articles/2598471 Disable remote configuration of NTP, or restrict this ability to trusted users. Do not use NSS to parse untrusted certificates. Users are advised to use other FTP and HTTP based file servers for transferring blob messages. Fileserver web application SHOULD NOT be used in older version of the broker and it should be disabled (it has been disabled by default since 5.12.0). This can be done by removing (commenting out) the following lines from conf\jetty.xml file <bean class="org.eclipse.jetty.webapp.WebAppContext"> <property name="contextPath" value="/fileserver" /> <property name="resourceBase" value="${activemq.home}/webapps/fileserver" /> <property name="logUrlOnStart" value="true" /> <property name="parentLoaderPriority" value="true" /> </bean> Set X11Forwarding=no in sshd_config. For authorized_keys that specify a "command" restriction, this issue can be mitigated by also setting the "no-X11-forwarding" restriction. In OpenSSH 7.2 and later, the "restrict" restriction can be used instead, which includes the "no-X11-forwarding" restriction. The PooledInvokerServlet is no longer required and can be removed by following the details in this knowledgebase solution: https://access.redhat.com/solutions/178393 Details can be found under the resolve tab at https://access.redhat.com/security/vulnerabilities/2296071 Red Hat Enterprise Linux 6 and 7 ================================ As a workaround the /etc/ImageMagick/policy.xml file can be edited to disable processing of MVG, HTTPS, HTTP, URL, FTP, EPHEMERAL, MSL, LABEL, TEXT, SHOW, WIN and PLT commands within image files, simply add the following lines: <policy domain="coder" rights="none" pattern="EPHEMERAL" /> <policy domain="coder" rights="none" pattern="HTTPS" /> <policy domain="coder" rights="none" pattern="HTTP" /> <policy domain="coder" rights="none" pattern="URL" /> <policy domain="coder" rights="none" pattern="FTP" /> <policy domain="coder" rights="none" pattern="MVG" /> <policy domain="coder" rights="none" pattern="MSL" /> <policy domain="coder" rights="none" pattern="TEXT" /> <policy domain="coder" rights="none" pattern="LABEL" /> <policy domain="coder" rights="none" pattern="SHOW" /> <policy domain="coder" rights="none" pattern="WIN" /> <policy domain="coder" rights="none" pattern="PLT" /> <policy domain="path" rights="none" pattern="@*" /> within the policy map stanza: <policymap> ... </policymap> Red Hat Enterprise Linux 5 ========================== In the following folders: /usr/lib64/ImageMagick-6.2.8/modules-Q16/coders/ (64bit package) or /usr/lib/ImageMagick-6.2.8/modules-Q16/coders/ (32bit package) Rename the following files: * mvg.so to mvg.so.bak * msl.so to msl.so.bak * label.so to label.so.bak Details can be found under the resolve tab at https://access.redhat.com/security/vulnerabilities/2296071 Red Hat Enterprise Linux 6 and 7 ================================ As a workaround the /etc/ImageMagick/policy.xml file can be edited to disable processing of MVG, HTTPS, HTTP, URL, FTP, EPHEMERAL, MSL, LABEL, TEXT, SHOW, WIN and PLT commands within image files, simply add the following lines: <policy domain="coder" rights="none" pattern="EPHEMERAL" /> <policy domain="coder" rights="none" pattern="HTTPS" /> <policy domain="coder" rights="none" pattern="HTTP" /> <policy domain="coder" rights="none" pattern="URL" /> <policy domain="coder" rights="none" pattern="FTP" /> <policy domain="coder" rights="none" pattern="MVG" /> <policy domain="coder" rights="none" pattern="MSL" /> <policy domain="coder" rights="none" pattern="TEXT" /> <policy domain="coder" rights="none" pattern="LABEL" /> <policy domain="coder" rights="none" pattern="SHOW" /> <policy domain="coder" rights="none" pattern="WIN" /> <policy domain="coder" rights="none" pattern="PLT" /> <policy domain="path" rights="none" pattern="@*" /> within the policy map stanza: <policymap> ... </policymap> Red Hat Enterprise Linux 5 ========================== In the following folders: /usr/lib64/ImageMagick-6.2.8/modules-Q16/coders/ (64bit package) or /usr/lib/ImageMagick-6.2.8/modules-Q16/coders/ (32bit package) Rename the following files: * mvg.so to mvg.so.bak * msl.so to msl.so.bak * label.so to label.so.bak Details can be found under the resolve tab at https://access.redhat.com/security/vulnerabilities/2296071 Red Hat Enterprise Linux 6 and 7 ================================ As a workaround the /etc/ImageMagick/policy.xml file can be edited to disable processing of MVG, HTTPS, HTTP, URL, FTP, EPHEMERAL, MSL, LABEL, TEXT, SHOW, WIN and PLT commands within image files, simply add the following lines: <policy domain="coder" rights="none" pattern="EPHEMERAL" /> <policy domain="coder" rights="none" pattern="HTTPS" /> <policy domain="coder" rights="none" pattern="HTTP" /> <policy domain="coder" rights="none" pattern="URL" /> <policy domain="coder" rights="none" pattern="FTP" /> <policy domain="coder" rights="none" pattern="MVG" /> <policy domain="coder" rights="none" pattern="MSL" /> <policy domain="coder" rights="none" pattern="TEXT" /> <policy domain="coder" rights="none" pattern="LABEL" /> <policy domain="coder" rights="none" pattern="SHOW" /> <policy domain="coder" rights="none" pattern="WIN" /> <policy domain="coder" rights="none" pattern="PLT" /> <policy domain="path" rights="none" pattern="@*" /> within the policy map stanza: <policymap> ... </policymap> Red Hat Enterprise Linux 5 ========================== In the following folders: /usr/lib64/ImageMagick-6.2.8/modules-Q16/coders/ (64bit package) or /usr/lib/ImageMagick-6.2.8/modules-Q16/coders/ (32bit package) Rename the following files: * mvg.so to mvg.so.bak * msl.so to msl.so.bak * label.so to label.so.bak Details can be found under the resolve tab at https://access.redhat.com/security/vulnerabilities/2296071 Red Hat Enterprise Linux 6 and 7 ================================ As a workaround the /etc/ImageMagick/policy.xml file can be edited to disable processing of MVG, HTTPS, HTTP, URL, FTP, EPHEMERAL, MSL, LABEL, TEXT, SHOW, WIN and PLT commands within image files, simply add the following lines: <policy domain="coder" rights="none" pattern="EPHEMERAL" /> <policy domain="coder" rights="none" pattern="HTTPS" /> <policy domain="coder" rights="none" pattern="HTTP" /> <policy domain="coder" rights="none" pattern="URL" /> <policy domain="coder" rights="none" pattern="FTP" /> <policy domain="coder" rights="none" pattern="MVG" /> <policy domain="coder" rights="none" pattern="MSL" /> <policy domain="coder" rights="none" pattern="TEXT" /> <policy domain="coder" rights="none" pattern="LABEL" /> <policy domain="coder" rights="none" pattern="SHOW" /> <policy domain="coder" rights="none" pattern="WIN" /> <policy domain="coder" rights="none" pattern="PLT" /> <policy domain="path" rights="none" pattern="@*" /> within the policy map stanza: <policymap> ... </policymap> Red Hat Enterprise Linux 5 ========================== In the following folders: /usr/lib64/ImageMagick-6.2.8/modules-Q16/coders/ (64bit package) or /usr/lib/ImageMagick-6.2.8/modules-Q16/coders/ (32bit package) Rename the following files: * mvg.so to mvg.so.bak * msl.so to msl.so.bak * label.so to label.so.bak Details can be found under the resolve tab at https://access.redhat.com/security/vulnerabilities/2296071 Red Hat Enterprise Linux 6 and 7 ================================ As a workaround the /etc/ImageMagick/policy.xml file can be edited to disable processing of MVG, HTTPS, HTTP, URL, FTP, EPHEMERAL, MSL, LABEL, TEXT, SHOW, WIN and PLT commands within image files, simply add the following lines: <policy domain="coder" rights="none" pattern="EPHEMERAL" /> <policy domain="coder" rights="none" pattern="HTTPS" /> <policy domain="coder" rights="none" pattern="HTTP" /> <policy domain="coder" rights="none" pattern="URL" /> <policy domain="coder" rights="none" pattern="FTP" /> <policy domain="coder" rights="none" pattern="MVG" /> <policy domain="coder" rights="none" pattern="MSL" /> <policy domain="coder" rights="none" pattern="TEXT" /> <policy domain="coder" rights="none" pattern="LABEL" /> <policy domain="coder" rights="none" pattern="SHOW" /> <policy domain="coder" rights="none" pattern="WIN" /> <policy domain="coder" rights="none" pattern="PLT" /> <policy domain="path" rights="none" pattern="@*" /> within the policy map stanza: <policymap> ... </policymap> Red Hat Enterprise Linux 5 ========================== In the following folders: /usr/lib64/ImageMagick-6.2.8/modules-Q16/coders/ (64bit package) or /usr/lib/ImageMagick-6.2.8/modules-Q16/coders/ (32bit package) Rename the following files: * mvg.so to mvg.so.bak * msl.so to msl.so.bak * label.so to label.so.bak Apply the configuration changes described in the documentation here: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.3/html/Admin_and_Config/JBoss_ON_and_SSL-Authentication.html For more information, refer to https://access.redhat.com/articles/2570101. Do not enable exceptions when using the SNMP object. For this flaw to be exploited, both non-admin image upload must be permitted and records of deleted IDs must have been purged from the openstack-glance 'images' database table. To prevent flaw exploitation: * Do not allow non-admin users to upload images, or * If you do permit normal users to upload images, do not purge the 'images' table. Note: It is safe to delete rows from `image_properties`, `image_tags`, `image_members`, and `image_locations` tables. If upgrading is not possible, the vulnerability can be mitigated using an ACL file containing "ACCESS VIRTUALHOST" clauses that white-lists user access to all virtualhosts. If AMQP 0-8, 0-9, 0-91, and 0-10 support is not required, the vulnerability can also be mitigated by turning off these protocols at the Port level. Versions of dracut package shipped with Red Hat Enterprise Linux 6 and 7 support kernel command line options which allow a shell to be presented when it is not able to mount the root device. (As in case of a failed root partition decryption attempt by cryptsetup, when wrong password is entered multiple times). In Red Hat Enterprise Linux 6, this is enabled by "rdshell" option on the kernel command line. However default installs do not enable this option. Hence when several attempts to decrypt the root partition fails, it will cause a kernel panic. In Red Hat Enterprise Linux 7, this is enabled by the "rd.shell" option. Default behavior here is to drop to a shell when root device mount fails, which can be disabled by adding "rd.shell=0" to the kernel command line. In either of the cases, a user having access to the grub console, can edit the kernel command line and re-enable his access. Red Hat Product Security Team strongly advocates enabling grub passwords as well BIOS passwords to protect against this. Disable autokey authentication. Instead, configure ntp to use symmetric key authentication, or no authentication at all (if not required). To configure ntp with symmetric key authentication, follow the steps at https://access.redhat.com/solutions/393663 Do not use NTP's broadcast mode in the clients by not configuring the "broadcastclient" directive in the ntp.conf file. Use wget with "-O" option to explicitly specify the output filename. Setting enabledForExtensions is false by default, thus <ex:serializable> elements are not automatically deserialized. However, if you have it enabled and you don't need any of the provided functions (https://ws.apache.org/xmlrpc/extensions.html) we suggest you disable it. Please see bug 1384344 comment #13 (https://bugzilla.redhat.com/show_bug.cgi?id=1384344#c13) for details on how to mitigate this issue. This issue can be mitigated by disallowing zone transfers and dynamic updates from potentially malicious sources. For more information, see the "Workarounds" section on https://kb.isc.org/article/AA-01390 page. You can add a filter in the JBoss CLI that sets the host header to the 'myvirtualhost.com' if the host header is not present. eg: /subsystem=undertow/configuration=filter/expression-filter=hostname:add(expression="header(header=Host, value=myvirtualhost.com)") /subsystem=undertow/server=default-server/host=default-host/filter-ref=hostname:add(predicate="not exists(%{i,Host})") Use the "star" utility provided by the "star" package to process archives from untrusted sources. Apply the configuration changes described in the documentation here: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.3/html/Admin_and_Config/JBoss_ON_and_SSL-Authentication.html For more information, refer to https://access.redhat.com/articles/2570101. Don't enable Async Jobs Service as details in the section, "2.10. RESTEASY ASYNCHRONOUS JOB SERVICE" of JBoss EAP 7 Developing Web Services Applications documentation: https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/paged/developing-web-services-applications/chapter-2-developing-jax-rs-web-services - Ensure all MySQL / MariaDB configuration files are not writeable to the mysql user. This is the default configuration in Red Hat products. - Ensure that non-administrative database users are not granted FILE privilege. Applications accessing data in MySQL / MariaDB databases, including web application potentially vulnerable to SQL injections, should use database accounts with the lowest privileges required. - If FILE permission needs to be granted to some non-administrative database users, use secure_file_priv setting to limit where files can be written to or read from. Disable third-party cookies in the browser. https://support.mozilla.org/en-US/kb/disable-third-party-cookies (Firefox) https://support.google.com/chrome/answer/95647?hl=en (Google Chrome) Disable third-party cookies in the browser. https://support.mozilla.org/en-US/kb/disable-third-party-cookies (Firefox) https://support.google.com/chrome/answer/95647?hl=en (Google Chrome) If you choose to use restrict default limited ..., be sure to use restrict source ... (without limited) to avoid this attack. Only use broadcast mode on trusted networks. If you are going to configure your OS to disable source address checks, also configure your firewall configuration to control what interfaces can receive packets from what networks. A possible workaround to this flaw is, when using aes-256-gcm mode, always set the key first and then the iv. For example when setting random keys and iv use the following code segment: key = cipher.random_key iv = cipher.random_iv When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. In order to exploit this issue you need to have credentials of a user with the 'admin' role. Therefore a good mitigation against this attack is to set a strong password for any user with the 'admin' role in the 'etc/users.properties' file of the Red Hat JBoss Fuse 6, or Red Hat JBoss AM-Q 6. This flaw is in the memcached binary protocol. If you client programs only use the ASCII protocol when communicating with memcached, you can disable the binary protocol and protect against this flaw by adding "-B ascii" to OPTIONS in /etc/sysconfig/memcached. This flaw is in the memcached binary protocol. If your client programs only use the ASCII protocol when communicating with memcached, you can disable the binary protocol and protect against this flaw by adding "-B ascii" to OPTIONS in /etc/sysconfig/memcached. This flaw requires memcached to be running with SASL authentication enabled, which is not the default setting. If your memcached instances are running without the "-S" command-line option, they are not vulnerable. Only Apache+Subversion servers that have the "DontDoThatConfigFile" configuration option present are affected by this flaw. This option is not enabled in default httpd or mod_dav_svn configuration as shipped with Red Hat Enterprise Linux. As a temporary workaround - HTTP/2 can be disabled by changing the configuration by removing h2 and h2c from the Protocols line(s) in the configuration file. The resulting line should read: Protocols http/1.1 Implement BCP-38. Configure enough servers/peers that an attacker cannot target all of your time sources. Properly monitor your ntpd instances, and auto-restart ntpd (without -g) if it stops running. https://github.com/jenkinsci-cert/SECURITY-218 Use "restrict default noquery ..." in your ntp.conf file. Use "restrict default noquery ..." in your ntp.conf file. Only allow mode 6 queries from trusted networks and hosts. Application parsing untrusted input with libxml2 should be careful to NOT use entity expansion (enabled by XML_PARSE_NOENT) or DTD validation (XML_PARSE_DTDLOAD, XML_PARSE_DTDVALID) on such input. This mitigation is only required if vulnerable gstreamer-plugins-bad-free and/or gstreamer1-plugins-bad-free packages are installed. For RHEL 7, sudo rm /usr/lib*/gstreamer-1.0/libgstvmnc.so sudo rm /usr/lib*/gstreamer-0.10/libgstvmnc.so For RHEL 6, sudo rm /usr/lib*/gstreamer-0.10/libgstvmnc.so Please note that this mitigation deletes the vulnerable VMware NC decoder, which removes the functionality to play VMware movie files. sudo rm /usr/lib*/gstreamer-0.10/libgstnsf.so Please note that this mitigation deletes the vulnerable NSF codec file, which removes the functionality to play Nintendo NSF music files. #!/bin/bash mv /usr/share/nagios/html/includes/rss /usr/share/nagios/html/includes/rss.disarmed mv /usr/share/nagios/html/rss-corefeed.php /usr/share/nagios/html/rss-corefeed.php.disarmed mv /usr/share/nagios/html/rss-newsfeed.php /usr/share/nagios/html/rss-newsfeed.php.disarmed This should disable rss from nagios installation and stop affected php code from being executed. Only downside to this would be news widget wont fetch any data from nagios.org rss feeds. You should not expose Remote JMX on EAP 5, or SOA-P 5. To do that remove this system property from bin/run.conf, or bin/run.conf.bat: com.sun.management.jmxremote.port=<portNum> Add authentication and authorization to any Resteasy endpoint which doesn't define a mime type, or defines a multipart mime type. This mitigation is only required if vulnerable gstreamer-plugins-good and/or gstreamer1-plugins-good packages are installed. For RHEL 7, sudo rm /usr/lib*/gstreamer-1.0/libgstflxdec.so sudo rm /usr/lib*/gstreamer-0.10/libgstflxdec.so For RHEL 5 and RHEL 6, sudo rm /usr/lib*/gstreamer-0.10/libgstflxdec.so Please note that this mitigation deletes the vulnerable FLI/FLC/FLX animation demuxer file(s), which removes the functionality to play FLI/FLC/FLX animation files. This mitigation is only required if vulnerable gstreamer-plugins-good and/or gstreamer1-plugins-good packages are installed. For RHEL 7, sudo rm /usr/lib*/gstreamer-1.0/libgstflxdec.so sudo rm /usr/lib*/gstreamer-0.10/libgstflxdec.so For RHEL 5 and RHEL 6, sudo rm /usr/lib*/gstreamer-0.10/libgstflxdec.so Please note that this mitigation deletes the vulnerable FLI/FLC/FLX animation demuxer file(s), which removes the functionality to play FLI/FLC/FLX animation files. This mitigation is only required if vulnerable gstreamer-plugins-good and/or gstreamer1-plugins-good packages are installed. For RHEL 7, sudo rm /usr/lib*/gstreamer-1.0/libgstflxdec.so sudo rm /usr/lib*/gstreamer-0.10/libgstflxdec.so For RHEL 5 and RHEL 6, sudo rm /usr/lib*/gstreamer-0.10/libgstflxdec.so Please note that this mitigation deletes the vulnerable FLI/FLC/FLX animation demuxer file(s), which removes the functionality to play FLI/FLC/FLX animation files. This mitigation is only required if vulnerable gstreamer-plugins-good and/or gstreamer1-plugins-good packages are installed. For RHEL 7, sudo rm /usr/lib*/gstreamer-1.0/libgstflxdec.so sudo rm /usr/lib*/gstreamer-0.10/libgstflxdec.so For RHEL 5 and RHEL 6, sudo rm /usr/lib*/gstreamer-0.10/libgstflxdec.so Please note that this mitigation deletes the vulnerable FLI/FLC/FLX animation demuxer file(s), which removes the functionality to play FLI/FLC/FLX animation files. Use a Servlet container known not to include path parameters in the return values for getServletPath() and getPathInfo() Do not click on deep phpMyAdmin links on third party sites. Affected versions: All 4.6.x versions (prior to 4.6.6), 4.4.x versions (prior to 4.4.15.10), and 4.0.x versions (prior to 4.0.10.19) are affected. Upstream patches: https://github.com/phpmyadmin/phpmyadmin/commit/3d230b6 https://github.com/phpmyadmin/phpmyadmin/commit/38f9223 https://github.com/phpmyadmin/phpmyadmin/commit/a134a01 Properly configured server which sets PHP_SELF is not affected by this. Affected versions: All 4.6.x versions (prior to 4.6.6) are affected Upstream patches: https://github.com/phpmyadmin/phpmyadmin https://github.com/phpmyadmin/phpmyadmin/commit/3b6ed1f The vulnerability is exposed only to MySQL superusers. Affected versions: All 4.6.x versions (prior to 4.6.6), 4.4.x versions (prior to 4.4.15.10), and 4.0.x versions (prior to 4.0.10.19) are affected. Upstream patches: https://github.com/phpmyadmin/phpmyadmin/commit/f8ad5bd https://github.com/phpmyadmin/phpmyadmin/commit/ca8edbc https://github.com/phpmyadmin/phpmyadmin/commit/695a488 - Disabling evince-thumbnailer to render icons will reduce the attack surface (removing /usr/share/thumbnailers/evince.thumbnailer). - SELinux in enforcing mode partially restricts evince-thumbnailer By setting vm.legacy_va_layout to 1 we can effectively disable the exploitation of this issue by switching to the legacy mmap layout. The mmap allocations start much lower in the process address space and follow the bottom-up allocation model. As such, the initial PIE executable mapping is far from the reserved stack area and cannot interfere with the stack. 64-bit processes on Red Hat Enterprise Linux 5 are forced to use the legacy virtual address space layout regardless of the vm.legacy_va_layout value. Note: Applications that have demands for a large linear address space (such as certain databases) may be unable to handle the legacy memory layout proposed using this mitigation. We recommend to test your systems and applications before deploying this mitigation on production systems. Edit the /etc/sysctl.conf file as root, and add or amend: vm.legacy_va_layout = 1 To apply this setting, run the /sbin/sysctl -p command as the root user to reload the settings from /etc/sysctl.conf. Verify that vm.legacy_va_layout is now set to defined value: $ /sbin/sysctl vm.legacy_va_layout vm.legacy_va_layout = 1 Switch off IMAP in `CURLOPT_PROTOCOLS` Disabling the use of zero page: It is possible to prevent the zero page from being mapped as a huge page, by modifying a configuration tunable in the /sys directory as shown below. This prevents the flaw from being exercised in this method. # echo 0 > /sys/kernel/mm/transparent_hugepage/use_zero_page Disabling huge pages: It is possible to mitigate this flaw by disabling hugepages on a system. Some user applications may require hugepages to be performant, and may suffer a performance penalty when running without hugepages. Red Hat has existing solutions created instructing how to disable transparent How to disable transparent hugepages (THP) on Red Hat Enterprise Linux 7 https://access.redhat.com/solutions/1320153 If your application may require transparent huge pages, please consult your software vendor to confirm. Where the HVM guest is explicitly configured to use shadow paging (eg via the `hap=0' xl domain configuration file parameter), changing to HAP (eg by setting `hap=1') will avoid exposing the vulnerability to those guests. HAP is the default (in upstream Xen), where the hardware supports it; so this mitigation is only applicable if HAP has been disabled by configuration. (This mitigation is not applicable to PV guests.) On x86, specifying "hap_1gb=0 hap_2mb=0" on the hypervisor command line will avoid the vulnerability. Alternatively, running all x86 HVM guests in shadow mode will also avoid this vulnerability. (For example, by specifying "hap=0" in the xl domain configuration file.) There is no known mitigation on ARM systems. On systems where the guest kernel is controlled by the host rather than guest administrator, running only kernels which do not disable SGI and PPI (i.e IRQ < 32) will prevent untrusted guest users from exploiting this issue. However untrusted guest administrators can still trigger it unless further steps are taken to prevent them from loading code into the kernel (e.g by disabling loadable modules etc) or from using other mechanisms which allow them to run code at kernel privilege. Running only HVM guests will avoid this vulnerability. Running only HVM guests will avoid this vulnerability. Running only HVM guests will avoid this vulnerability. On systems where the guest kernel is controlled by the host rather than guest administrator, running only kernels which only send sane IPIs (i.e. targeting valid CPUs) will prevent untrusted guest users from exploiting this issue. However untrusted guest administrators can still trigger it unless further steps are taken to prevent them from loading code into the kernel (e.g by disabling loadable modules etc) or from using other mechanisms which allow them to run code at kernel privilege. Secure the access to the entire http-invoker contexts by adding <url-pattern>/*</url-pattern> to the security-constraints in the web.xml file of the http-invoker.sar.The users who do not wish to use the http-invoker.sar can remove it. The missing implied signing for 'smb2mount -e', 'smbcacls -e' and 'smbcquotas -e' can be enforced by explicitly using '--signing=required' on the commandline or "client signing = required" in smb.conf. Keep the default of "client max protocol = NT1". To mitigate the flaw, use an overcloud post-deploy script[1] to do the following on all overcloud nodes: key=/etc/ceph/ceph.client.openstack.keyring chown root:root $key chmod 600 $key setfacl -m u:glance:r $key setfacl -m u:cinder:r $key setfacl -m u:nova:r $key setfacl -m u: gnocchi:r $key If not using Red Hat OpenStack Platform director, then run the commands above manually on each overcloud node, Warning: Only running 'chmod 600 $key' alone (without an ACL) will prevent OpenStack from reading the key. [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html-single/advanced_overcloud_customization/#sect-Customizing_Overcloud_PostConfiguration_All As this is an SMB1-only vulnerability, it can be avoided by setting the server to only use SMB2 via adding: server min protocol = SMB2_02 to the [global] section of your smb.conf and restarting smbd. It is possible to disable manually credential caching : * Stop the sssd service * Delete the cache (rm -f /var/lib/sss/db/* /var/log/sssd/*) or manually remove the hashes for the database * In the sssd configuration file, change cache_credentials to False for each domains * start the sssd service again However, tools such as realmd & ipa-client-install might enable credential caching, and should be used with care. Ensure that readonly is set to true (the default) for the DefaultServlet, WebDAV servlet or application context. Block HTTP methods that permit resource modification for untrusted users. Ensure that readonly is set to true (the default) for the DefaultServlet, WebDAV servlet or application context. Block HTTP methods that permit resource modification for untrusted users. Applications should strongly consider blocking remote entity resolution and/or outright disabling of DTD processing in light of the continued identification of bugs in this area of the library. Until fixes are available, all Solr users are advised to restart their Solr instances with the system parameter `-Ddisable.configEdit=true`. This will disallow any changes to be made to configurations via the Config API. This is a key factor in this vulnerability, since it allows GET requests to add the RunExecutableListener to the config. This is sufficient to protect from this type of attack, but means you cannot use the edit capabilities of the Config API until further fixes are in place. The ISDN kernel module is automatically loaded when the system boots and the ISDN service is present and enabled. The kernel modules can be prevented from being loaded by using system-wide modprobe rules. Run the following commands to blacklist the ISDN module, thus preventing them from loading: ```# echo "install isdn /bin/true">> /etc/modprobe.d/disable-isdn.conf``` On RHEL 6 execute the following commands as root to check if any isdn-related services are present: ```# chkconfig --list | grep isdn``` and disable them if they are: ```# chkconfig isdn off``` (or use a name of another isdn-related service) A systemtap script intercepting v4l2_compat_ioctl32() function of the [videodev] module and making it to return -ENOIOCTLCMD error value would work just fine, except breaking all 32bit video capturing software, but not 64bit ones. Alternatively, blacklisting [videodev] module will work too, but it will break all video capturing software. This issue can be mitigated by adding the following lines to the Emacs init file (for example ~/.emacs, ~/emacs.d/init.el, site-start.el) and avoiding options that would bypass normal initialization, like 'emacs -Q': ;; Mitigate CVE-2017-14482 in Emacs 25.2 and earlier (require 'enriched) (defun enriched-decode-display-prop (start end &optional param) (list start end)) Prevent SMB1 access to the server by setting the parameter: "server min protocol = SMB2" to the [global] section of your smb.conf and restart smbd. This prevents and SMB1 access to the server. Note this could cause older clients to be unable to connect to the server. In case you do not rely on the commands offered by the "-cvs" subpackage (for example "git cvsserver" or "git cvsimport") on RHEL or RHSCL, you can uninstall the git "-cvs" subpackage. Mitigation to this problem is to not trigger polymorphic desrialization globally by using: objectMapper.enableDefaultTyping() and rather use @JsonTypeInfo on the class property to explicitly define the type information. For more information on this issue please refer to https://www.github.com/mbechler/marshalsec/blob/master/marshalsec.pdf?raw=true This issue can be mitigated on vulnerable systems by limiting the login process to a single request per process, which is also the default value. Don't use webhook tokens to trigger builds. Alternatively don't rely on project viewer, or cluster-reader permissions from preventing those users from running builds. This flaw only affects Red Hat OpenStack Platform deployments which use the third-party EMC ScaleIO driver plugin. To mitigate this flaw, ensure all volumes use zero-padding by updating the ScaleIO storage-pool policy. Note: Only an empty pool's policy can be changed. ~~~ scli --modify_zero_padding_policy (((--protection_domain_id <ID> | --protection_domain_name <NAME>) --storage_pool_name <NAME>) | --storage_pool_id <ID>) (--enable_zero_padding | --disable_zero_padding) Example: scli --modify_zero_padding_policy --protection_domain_name pd10 --storage_pool_name scale1 --enable_zero_padding ~~~ It is possible to prevent the affected code from being loaded by blacklisting the kernel module snd_seq. Instructions relating to how to blacklist a kernel module are shown here: https://access.redhat.com/solutions/41278 Alternatively a custom permission set can be created by udev, the correct permissions will depend on your use case. Please contact Red Hat customer support for creating a rule set that can minimize flaw exposure. 1. Use "scala -nocompdaemon MyScript.scala" rather than "scala MyScript.scala" to disable the implicit startup and use of the daemon. 2. Avoid explicitly starting fsc. This text is borrowed from the upstream security advisory. To protect against this vulnerability, users need to ensure the interconnect route endpoints are protected by authentication. Please refer to official documentation on how to secure the endpoints: https://access.redhat.com/documentation/en-us/red_hat_jboss_amq/7.0/html-single/using_amq_interconnect/#security-1 if you are running Exim 4.88 or newer, then in the main section of your Exim configuration, set: chunking_advertise_hosts = This disables advertising the ESMTP CHUNKING extension, making the BDAT verb unavailable and avoids letting an attacker apply the logic. Disable sub-repositories The easiest way to mitigate this vulnerability is not to use HTML emails. If you really need to use them ensure that MUA clients disable external links embedded in HTML emails. For example in thunderbird email client, Edit->Preferences->Privacy->Disable "Allow remote content in messages". The easiest way to mitigate this vulnerability is not to use HTML emails. If you really need to use them ensure that MUA clients disable external links embedded in HTML emails. For example in thunderbird email client, Edit->Preferences->Privacy->Disable "Allow remote content in messages". The server can manually sanitize possibly untrusted headers prior to inserting them in the reply. This flaw, and many others like it, is mitigated by enabling hardlink and symlink protections. These protections are enabled by default in Red Hat Enterprise Linux and this vulnerability will only be exploitable if disabled. To ensure your system is protected, check that `fs.protected_hardlinks` is enabled as in the following example: # sysctl fs.protected_hardlinks fs.protected_hardlinks = 1 Set a password for all users. Affected versions: Version 4.0 prior to 4.0.10.20 Version 4.4 (no longer supported) Version 4.6 (no longer supported) Version 4.7.0-beta1 and 4.7.0-rc1 Upstream patches: https://github.com/phpmyadmin/phpmyadmin https://github.com/phpmyadmin/phpmyadmin/commit/b6ca92cc75c8a16001425be7881e73430bcc35b8 https://github.com/phpmyadmin/phpmyadmin/commit/7232271a379396ca1d4b083af051262057003c41 Attached to this bugzilla is a systemtap script that will prevent opening (and therefore reading) the /proc/<process>/timers file which is used to leak information. The SystemTap script is relatively small and efficient, broken into 3 distinct sections as follows: -------- probe kernel.function("proc_timers_open@fs/proc/base.c").return { // this is -EACCES $return = -13; message = sprintf("CVE-2017-18344 mitigation denied access to %s to %s(%d)", file_name , execname(), pid()); // print a warning message at KERN_INFO debug level printk(6, message); } probe begin { printk(6, "Mitigation for CVE-2017-18344 loaded.\n"); } probe end { printk(6, "Mitigation for CVE-2017-18344 unloaded.\n"); } --------- First, the script places a probe at the return of the kernel function “proc_timers_open” when called. This modifies the return value to be EACCES which would return this value to userspace preventing this file from being opened. When the /proc/<pid>/timer file is attempted to be opened, a message will be logged to the kernel log subsystem showing the process and pid of the application attempting to access the timer file. This file is not in widespread use at this time, although some applications may read from it to debug or understand their own timers that are set. This mitigation will not be useful in this context. Finally, the “probe begin” and “probe end” code blocks tell systemtap to add the supplied text to the kernel log buffer via the printk function. This creates an audit trail by registering in the system logs exactly when the mitigation is loaded and unloaded. This will need to be compiled with guru mode (-g parameter) to compile. This will need to be loaded at each boot to remain effective. Red Hat Product security recommends updating to a patched kernel when it is available. Red Hat always seeks to provide both mitigations to disable attacks as well as the actual patches to treat the flaw. To learn more about SystemTap, and how it can be used in your management of your Red Hat systems, please refer to Using SystemTap[1] or one of our videos about it within our Customer Portal[2]. 1 - https://access.redhat.com/articles/17839 2 - https://access.redhat.com/search/#/?q=systemtap Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both. This issue is partially mitigated on RHEL Atomic Host, where default certificate pinning ensures provenance. The n_hdlc kernel module will be automatically loaded when an application attempts to use the HDLC line discipline from userspace. This module can be prevented from being loaded by using the system-wide modprobe rules. The following command, run as root, will prevent accidental or intentional loading of the module. Red Hat Product Security believe this method is a robust method to prevent accidental loading of the module, even by privileged users. ​# echo "install n_hdlc /bin/true" >> /etc/modprobe.d/disable-n_hdlc.conf The system will need to be restarted if the n_hdlc modules are already loaded. In most circumstances, the n_hdlc kernel modules will be unable to be unloaded if in use and while any current process using this line discipline is required. Exploiting this flaw does not require Microgate or SyncLink hardware to be in use. If further assistance is needed, see this KCS article ( https://access.redhat.com/solutions/41278 ) or contact Red Hat Global Support Services. A KCS article with more details on this flaw is available at: https://access.redhat.com/solutions/3022771 ~]# chmod 600 /etc/skyring/skyring.conf While it is possible to avoid the condition by removing either DNS64 or RPZ from the configuration, or by carefully restricting the contents of the policy zone, for an affected configuration the most practical and safest course of action is to upgrade to a version of BIND without this vulnerability. Servers which have configurations which require DNS64 and "break-dnssec yes;" should upgrade. Servers which are not using these features in conjunction are not at risk from this defect. The effects of this vulnerability can be mitigated by using Access Control Lists (ACLs) that require both address range validation and use of TSIG authentication in parallel. For information on how to configure this type of compound authentication control, please see: https://kb.isc.org/article/AA-00723/0/Using-Access-Control-Lists-ACLs-with-both-addresses-and-keys.html The effects of this vulnerability can be mitigated by using Access Control Lists (ACLs) that require both address range validation and use of TSIG authentication in parallel. For information on how to configure this type of compound authentication control, please see: https://kb.isc.org/article/AA-00723/0/Using-Access-Control-Lists-ACLs-with-both-addresses-and-keys.html Disable salt-api for mitigation. Disable salt-api for mitigation. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. When invoked with the "-w" option, to write raw packets to a pcap file (for forensic purposes or offline examination), tcpdump does not use the protocol decoding subsystem and is not affected by these flaws. Red Hat Product Security recommends that any unattended uses of tcpdump use this option to ensure uninterrupted packet capture. This vulnerability only allows files in the current directory to be overwritten, so using `pear download` in a temporary directory effectively mitigates the risk of a dangerous file overwrite occurring. The AJP connector does not support the sendfile capability. A server configured to only use the AJP connector (disable HTTP Connector) is not affected by this vulnerability. Disable the sendfile capability by setting useSendfile="false" in the HTTP connector configuration. Note: Disabling sendfile, may impact performance on large files. If it is necessary to have the DefaultServlet property readonly=false, use a jsp error page, for example Error404.jsp rather than a static html error page. Alternatively do not specify an error-page in the Deployment Descriptor and use a custom ErrorReportValve. Recent versions of the SELinux policy can mitigate this flaw. The steps below will work with SELinux enabled or disabled. As the DCCP module will be auto-loaded when required, its use can be disabled by preventing the module from loading with the following instructions: # echo "install dccp /bin/true" >> /etc/modprobe.d/disable-dccp.conf The system will need to be restarted if the DCCP modules are loaded. In most circumstances, the DCCP kernel modules will be unable to be unloaded while any network interfaces are active and the protocol is in use. If you need further assistance, see KCS article https://access.redhat.com/solutions/41278 or contact Red Hat Global Support Services. Properly monitor your ntpd instances, and auto-restart ntpd (without -g) if it stops running. Implement BCP-38. If you don't want to upgrade, then don't setvar variable names longer than 200-512 bytes in your ntp.conf file. Properly monitor your ntpd instances, and auto-restart ntpd (without -g) if it stops running. Properly monitor your ntpd instances, and auto-restart ntpd (without -g) if it stops running. Properly monitor your ntpd instances, and auto-restart ntpd (without -g) if it stops running. Properly monitor your ntpd instances, and auto-restart ntpd (without -g) if it stops running. Ensure UDP port 5353 is blocked at the firewall. Enable the security features of the DocumentBuilderFactory or SaxParserFactory as described by OWASP: https://www.owasp.org/index.php/XML_External_Entity_(XXE)_Prevention_Cheat_Sheet#JAXP_DocumentBuilderFactory.2C_SAXParserFactory_and_DOM4J Doing a transform in JAXP requires the use of a 'javax.xml.transform.TransformerFactory'. If the FEATURE_SECURE_PROCESSING feature is set to 'true', it mitigates this vulnerability. Eg: TransformerFactory factory = TransformerFactory.newInstance(); factory.setFeature(javax.xml.XMLConstants.FEATURE_SECURE_PROCESSING, true); Red Hat recommends blacklisting the kernel module to prevent its use. This will prevent accidental version loading by administration and also mitigate the flaw if a kernel with the affected module is booted. As the macsec module will be auto-loaded when required, its use can be disabled by preventing the module from loading with the following instructions: Raw # echo "install macsec /bin/true" >> /etc/modprobe.d/disable-macsec.conf If macsec functionality is in use as a functional part of the system a kernel upgrade is required. Use PGSSLMODE=require instead of PGREQUIRESSL=1 Possible workaround (with side-effects): authconfig --enablesysnetauth --update Any of the following: 1. SELinux is enabled by default and our default policy prevents loading of modules from outside of samba's module directories and therefore blocks the exploit 2. Mount the filesystem which is used by samba for its writable share using "noexec" option. 3. Add the parameter: nt pipe support = no to the [global] section of your smb.conf and restart smbd. This prevents clients from accessing any named pipe endpoints. Note this can disable some expected functionality for Windows clients. Alternative filesystems may be used in place of ext4 in case of sensitive data leak. Alternatively, don't hard reset the system. This issue affects processing of XML content from an untrusted source using a javax.xml.transform.TransformerFactory. The only safe way to process untrusted XML content with a TransformerFactory is to use the StAX API. StAX is a safe implementation on EAP 7.0.x because the XML content is not read in it's entirety in order to parse it. As a developer using StAX, you decide which XML stream events you want to react to, so XXE control constructs won't be processed automatically by the parser. Mitigation to this problem is to not trigger polymorphic desrialization globally by using: objectMapper.enableDefaultTyping() and rather use @JsonTypeInfo on the class property to explicitly define the type information. For more information on this issue please refer to https://www.github.com/mbechler/marshalsec/blob/master/marshalsec.pdf?raw=true rpcbind should be protected by iptables so that only trusted hosts that require access can reach it (eg, nfs clients). Applying per-IP rate limits in iptables will also significantly limit the impact of this attack. The default iptables rules in the system-config-firewall or firewalld package deny all remote access to rpcbind. If you elect to run your system with overcommit turned off, daemons should have memory limits enforced by the init system to ensure stability. With systemd, use directives such as LimitAS in unit files. With upstart, place ulimit commands in /etc/sysconfig/$daemon. Forcefully disable the RLE decoder from being used, for example by renaming ImageMagick's rle.so library: RHEL6 mitigation: 32bit: mv /usr/lib/ImageMagick-6.7.2/modules-Q16/coders/rle.so /usr/lib/ImageMagick-6.7.2/modules-Q16/coders/rle.so.CVE-2017-9098 64bit: mv /usr/lib64/ImageMagick-6.7.2/modules-Q16/coders/rle.so /usr/lib64/ImageMagick-6.7.2/modules-Q16/coders/rle.so.CVE-2017-9098 RHEL7 mitigation: 32bit: mv /usr/lib/ImageMagick-6.7.8/modules-Q16/coders/rle.so /usr/lib/ImageMagick-6.7.8/modules-Q16/coders/rle.so.CVE-2017-9098 64bit: mv /usr/lib64/ImageMagick-6.7.8/modules-Q16/coders/rle.so /usr/lib64/ImageMagick-6.7.8/modules-Q16/coders/rle.so.CVE-2017-9098 If you are using the glibc heap implementation (default), it may also be possible to set the "MALLOC_PERTURB_" environment variable to a non-zero value before launching the process using ImageMagick. This should forcefully initialize the memory, but may reduce performance. Ensure proper testing before using these methods. Disable TLS session caching in FreeRADIUS by setting "enable = no" in the cache subsection of EAP module settings, which are in /etc/raddb/mods-available/eap file. Do not parse untrusted arbitrary XML data using the expat package. If you do not use digest authentication, do not load the "auth_digest_module". For example, on RHEL 7, this can be done by commenting out or removing the "LoadModule auth_digest_module modules/mod_auth_digest.so" line within the /etc/httpd/conf.modules.d/00-base.conf configuration file and restarting the service. You can then use the "httpd -t -D DUMP_MODULES" command to verify that the module is no longer loaded. This issue can be mitigated by configuring httpd to disallow the use of the "Limit" configuration directive in .htaccess files. The set of directives that can be used in .htaccess files is configured using the "AllowOverride" directive. Refer to Red Hat Bugzilla bug 1490344 for further details: https://bugzilla.redhat.com/show_bug.cgi?id=1490344#c18 There are various methods available to mitigate this issue. For further information, please refer to the Subversion advisory available at: https://subversion.apache.org/security/CVE-2017-9800-advisory.txt This flaw is in the memcached binary protocol. If your client programs only use the ASCII protocol when communicating with memcached, you can disable the binary protocol and protect against this flaw by adding "-B ascii" to OPTIONS in /etc/sysconfig/memcached. By default, curl and libcurl will not follow redirect requests. This flaw happens only when curl or libcurl are explicitly requested to follow redirects (option --location in curl, and CURLOPT_FOLLOWLOCATION in libcurl). To mitigate this, it is possible to prevent the automated following of redirects, replacing it by manual redirects (and remove the authentication header), for example. A workaround for this issue is to not use the internal ESI parser, which can be achieved by adding either the "esi_parser expat" or "esi_parser libxml2" configuration directive to the squid configuration file (for example /etc/squid/squid.conf). A workaround for this issue is to set the "log_uses_indirect_client off" configuration directive in the squid configuration file (for example /etc/squid/squid.conf). Please refer to the Red Hat Knowledgebase article 3369081 for instructions on how to properly secure memcached installations to prevent them from being used in an attack. https://access.redhat.com/solutions/3369081 Preventing application from using non-default CURLOPT_FTP_FILEMETHOD will avoid triggering the vulnerable code. We suggest to keep the default `dns=default` in the NetworkManager configuration file to prevent DNS queries leaks to possibly hostile DNS servers. Users are strongly advised not to expose their logging RELP services to a public network. Enable TLS in OpenFlow plugin. Upstream documentation is a useful resource. https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:_TLS_Support To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko Check Okular archives with `unzip -l <archive-name>.okular` before opening them. Do not open them with Okular if they contain files with "../". Ensure the paramter: rpc_server:spoolss = external is not set in the [global] section of your smb.conf. If the YamlProvider is enabled it's recommended to add authentication, and authorization to the endpoint expecting Yaml content to prevent exploitation of this vulnerability. Revoke the change passwords right for everyone from all user objects (including computers) in the directory. Note that this will prevent users from being able to change their own expired passwords, so the maximum password age should be set to a value that prevents user passwords from expiring while the workaround is in place. For more information please refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1553553#c3 Upstream suggests the following mitigation can be used to protect against this security flaw: https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:_Protect_Your_Search_Path Remove any symbolic links from /tmp and /var/tmp directories before relabeling the file system. If exposing shares with NFS or GlusterFS to Openshift Nodes use EgressNetworkPolicy, [1] to redirect outbound storage network traffic via an egress router. Alternatively if you're on AWS, EgressNetworkPolicy is not supported, you can use a Static IP, [2], for projects to force projects which need storage to connect from a NIC with a unique IP Address. Once traffic is coming from a known IP address, not the Node IP, you can protect the NFS, or GlusterFS storage node with a firewall, or exports which only allows access from the Egress router, or from the Static IP. An egress policy such as the one in the redirect-mode, [3], is an example of egress policy which would mitigate this vulnerability. An administrator would need to deploy one of these to the project using storage, as they need to run in privileged mode. This forces all traffic to the storage device through the egress router, which is a distinct IP. You can then configure the storage device to only access traffic from that source IP. Be aware that during a docker build, the build container is not subject to EgressNetworkPolicy rules in versions prior to 3.7. Also the Static IP feature is only available as a Tech Preview from version 3.7. An alternative mitigation if you're using Red Hat Gluster Storage is outlined here: https://github.com/gluster/gluster-kubernetes/blob/master/docs/design/tls-security.md A semi-automatic namespace wide egress-IP is due to be released in OCP 3.11 which will make management of the EgressNetworkPolicy easier. It will only work for the multitenant and networkpolicy plugins. [1] https://docs.openshift.com/container-platform/3.7/admin_guide/managing_networking.html#admin-guide-controlling-egress-traffic [2] https://docs.openshift.com/container-platform/3.7/admin_guide/managing_networking.html#enabling-static-ips-for-external-project-traffic [3] https://docs.openshift.org/latest/admin_guide/managing_networking.html#admin-guide-deploying-an-egress-router-pod On master nodes where etcd has been installed using the container method: 0. Verify you can connect to etcd without providing TLS authentication credentials. On any master node, check the ETCD_LISTEN_CLIENT_URLS in /etc/etcd/etcd.conf, and use one of the client urls to connect without providing a certificate, eg: curl -4 curl https://10.0.1.1:2379/version -k 0a. If vulnerable output will show something like this: {"etcdserver":"3.2.15","etcdcluster":"3.2.0"} 0b. If not affected the connection will fail with: curl: (58) NSS: client certificate not found (nickname not specified) 1. update /etc/etcd/etcd.conf on the master nodes to remove quotes from these fields: ETCD_PEER_CLIENT_CERT_AUTH="true" ETCD_CLIENT_CERT_AUTH="true" eg. ETCD_PEER_CLIENT_CERT_AUTH=true ETCD_CLIENT_CERT_AUTH=true 2. Restart the etcd container service: sudo systemctl restart etcd_container 3. Test if client authentication is now required using the steps from 0. above. Use mon_allow_pool_delete = false in ceph.conf to disable deletion of pools ~]$ for p in `rados lspools` do ceph osd pool set $p nodelete true done caveat: This mitigation does not protect against attacker from corrupting snapshot images If SELinux is enabled, it will restrict the number of files accessible by the httpd process. If SELinux is enabled it further restricts the set of files that can be downloaded through this flaw. If SELinux is enabled it further restricts the set of files an attacker may write to. This prevents some basic attacks that would allow to gain remote code execution, though it is not excluded other means are possible. On 389-ds-base 1.3.1 and above: 1- Deactivate clear password storing by default, to prevent new passwords to be logged. -> in cn=config, set nsslapd-unhashed-pw-switch attribute to 'off' or 'nolog' 2- Trim changelog to ensure currently stored passwords are removed. For Replication: -> in cn=changelog5,cn=config, reduce nsslapd-changelogmaxentries, nsslapd-changelogtrim-interval and nsslapd-changelogmaxage -> force a replication & wait for the changelogtrim-interval time -> restore previous values For RetroChangelog: -> deactivate the plugin -> restart directory server -> reactivate the plugin -> restart directory server To limit exposure of gluster server nodes : 1. gluster server should be on LAN and not reachable from public networks. 2. Use gluster auth.allow and auth.reject. 3. Use TLS certificates between gluster server nodes and clients. Caveat: This would only mitigate attacks from unauthorized malicious clients. gluster clients allowed by auth.allow or having signed TLS client certificates would still be able to trigger this attack. Use an alternative plugin such as ovs-subnet, or ovs-multitentant if delivering a multitentant service. To limit exposure of gluster server nodes : 1. gluster server should be on LAN and not reachable from public networks. 2. Use gluster auth.allow and auth.reject. 3. Use TLS certificates to authenticate gluster clients. caveat: This does not protect from attacks against authenticated gluster clients. Administrators of the CloudForms appliance can filter local packages going to the port where MIQ Server is listening, by using the following iptables command: # iptables -I OUTPUT 1 -o lo -d localhost/32 -p tcp -m tcp --dport <MIQ Server port> -m owner '!' --uid-owner root -j DROP Where the MIQ Server port can be found using netstat command: # netstat -nl --tcp -p | grep -i "miq server" To limit exposure of gluster server nodes : 1. gluster server should be on LAN and not reachable from public networks. 2. Use gluster auth.allow and auth.reject. 3. Use TLS certificates to authenticate gluster clients. caveat: This does not protect from attacks by authenticated gluster clients. Disable Bluetooth. SELinux mitigates this issue on Red Hat Gluster Storage 3. SELinux should be in enforcing mode only as permissive mode does not block attacks. SELinux mitigates this issue on Red Hat Gluster Storage 3. SELinux should be in enforcing mode only as permissive mode does not block attacks. To limit exposure of gluster server nodes : 1. gluster server should be on LAN and not reachable from public networks. 2. Use gluster auth.allow and auth.reject. 3. Use TLS certificates to authenticate gluster clients. caveat: This does not protect from attacks by authenticated gluster clients. To limit exposure of gluster server nodes : 1. gluster server should be on LAN and not reachable from public networks. 2. Use gluster auth.allow and auth.reject. 3. Use TLS certificates to authenticate gluster clients. caveat: This does not protect from attacks by authenticated gluster clients. To limit exposure of gluster server nodes : 1. gluster server should be on LAN and not reachable from public networks. 2. Use gluster auth.allow and auth.reject. 3. Use TLS certificates to authenticate gluster clients. caveat: This does not protect from attacks by authenticated gluster clients. To limit exposure of gluster server nodes : 1. gluster server should be on LAN and not reachable from public networks. 2. Use gluster auth.allow and auth.reject. 3. Use TLS certificates to authenticate gluster clients. caveat: This does not protect from attacks by authenticated gluster clients. To limit exposure of gluster server nodes : 1. gluster server should be on LAN and not reachable from public networks. 2. Use gluster auth.allow and auth.reject. 3. Use TLS certificates to authenticate gluster clients. caveat: This does not protect from attacks by authenticated gluster clients. To limit exposure of gluster server nodes : 1. gluster server should be on LAN and not reachable from public networks. 2. Use gluster auth.allow and auth.reject. 3. Use TLS certificates to authenticate gluster clients. caveat: This does not protect from attacks by authenticated gluster clients. If SELinux is enabled, it might prevent some locations from accepting uploaded files from the attacker. This prevents some basic attacks allowing remote code execution, although it would not exclude all other possibilities. Applications using postgresql-jdbc should have their SSL configuration reviewed to ensure that host name verification is not disabled and only trusted CAs are accepted. Configure and enable authentication on the etcd server. Configure and enable authentication on the etcd server or secure your client connection via HTTPS. Customers can turn off the source-to-image (S2I) build strategy to prevent access to the exploitable function. Information about how to disable the source-to-image build strategy is in the product documentation. * Disabling S2I in OpenShift Enterprise 3.0 - https://docs.openshift.com/enterprise/3.0/admin_guide/securing_builds.html#disabling-a-build-strategy-globally * Disabling S2I in OpenShift Enterprise 3.1 - https://docs.openshift.com/enterprise/3.1/admin_guide/securing_builds.html#disabling-a-build-strategy-globally * Disabling S2I in OpenShift Enterprise 3.2 - https://docs.openshift.com/enterprise/3.2/admin_guide/securing_builds.html#disabling-a-build-strategy-globally * Disabling S2I in OpenShift Enterprise 3.3 - https://access.redhat.com/documentation/en-us/openshift_container_platform/3.3/html/cluster_administration/admin-guide-securing-builds * Disabling S2I in OpenShift Enterprise 3.4 - https://access.redhat.com/documentation/en-us/openshift_container_platform/3.4/html/cluster_administration/admin-guide-securing-builds * Disabling S2I in OpenShift Enterprise 3.5 - https://access.redhat.com/documentation/en-us/openshift_container_platform/3.5/html/cluster_administration/admin-guide-securing-builds * Disabling S2I in OpenShift Enterprise 3.6 - https://access.redhat.com/documentation/en-us/openshift_container_platform/3.6/html/cluster_administration/admin-guide-securing-builds * Disabling S2I in OpenShift Enterprise 3.7 - https://access.redhat.com/documentation/en-us/openshift_container_platform/3.7/html/cluster_administration/admin-guide-securing-builds * OpenShift Enterprise 3.8 is not a production version (only for upgrades). * Disabling S2I in OpenShift Enterprise 3.9 - https://access.redhat.com/documentation/en-us/openshift_container_platform/3.9/html/cluster_administration/admin-guide-securing-builds Please access https://access.redhat.com/security/vulnerabilities/3442151 for information on how to mitigate this issue. 1. Use TLS Authentication to authenticate gluster clients to limit access to gluster storage volumes 2. The gluster server should be on LAN, firewalled to trusted systems, and not reachable from public networks. Don't create OCP source-to-image applications from source code repositories hosted by untrusted parties. Github is blocking users from pushing repositories with malicious submodules so it's less likely you can pull a malicious repository from there which triggers this vulnerability. PPP instances must be configured for EAP-TLS authentication to expose this vulnerability. For ppp servers, the file `/etc/ppp/eaptls-server' must exist. For clients, either `/etc/ppp/eaptls-client` must exist or command-line options `ca`, `cert` and `key` must be provided. As a general precaution, users are encouraged to separate public and private resources. For example, separating static resources and mapping them to /resources/public/** and /resources/private/** is preferred to having one common root with mixed public and private resource content underneath. This flaw can be mitigated by appending the --no-verbose command line flag. On Openshift Container Platform 3.x you can override the container image used on the Jenkins Slave by specifying the JENKINS_SLAVE_IMAGE environment variable in your jenkins deployment configuration. Ref: https://github.com/openshift/jenkins/blob/8e1ab16fb5f44d6570018c5dfa3407692fdba6e5/2/contrib/jenkins/kube-slave-common.sh#L27-L33 To mitigate against this flaw, examine user profile directories for the presence of both `key3.db` and `key4.db` files. If both are present, `key3.db` should be deleted. Information disclosure occurs when java.nio.file.InvalidPathException occurs and is handled by the default Jetty error handler. To protect against this, a custom error handler can be configured for that particular error or for a larger set of errors according to the documentation link below. Red Hat Product Security advises that production deployments on Jetty use custom error handlers to limit the information disclosed and to ensure effective logging of error conditions. http://www.eclipse.org/jetty/documentation/current/custom-error-pages.html If the HFS+ filesystem is not in use, this module can be blacklisted and prevented from being loaded. See https://access.redhat.com/solutions/41278 for instructions on how to blacklist the 'hfsplus.ko' kernel module. To mitigate the issue: Enable and install kernel-debuginfo packages as per https://access.redhat.com/solutions/666123 1) On the host, save the following in a file with the ".stp" extension: // CVE-2018-14634 // // Theory of operations: adjust the thread's # rlimit-in-effect around // calls to the vulnerable get_arg_page() function so as to encompass // the newly required _STK_LIM / 4 * 3 maximum. // Complication: the rlimit is stored in a current-> structure that // is shared across the threads of the process. They may concurrently // invoke this operation. function clamp_stack_rlim_cur:long () %{ struct rlimit *rlim = current->signal->rlim; unsigned long rlim_cur = READ_ONCE(rlim[RLIMIT_STACK].rlim_cur); unsigned long limit = _STK_LIM / 4 * 3; limit *= 4; // multiply it back up, to the scale used by rlim_cur if (rlim_cur > limit) { WRITE_ONCE(rlim[RLIMIT_STACK].rlim_cur, limit); STAP_RETURN(limit); } else STAP_RETURN(0); %} probe kernel.function("copy_strings").call { l = clamp_stack_rlim_cur() if (l) printf("lowered process %s(%d) STACK rlim_cur to %p\n", execname(), pid(), l) } probe begin { printf("CVE-2018-14634 mitigation loaded\n") } probe end { printf("CVE-2018-14634 mitigation unloaded\n") } 2) Install the "systemtap" package and any required dependencies. Refer to the "2. Using SystemTap" chapter in the Red Hat Enterprise Linux "SystemTap Beginners Guide" document, available from docs.redhat.com, for information on installing the required -debuginfo and matching kernel-devel packages 3) Run the "stap -g [filename-from-step-1].stp" command as root. If the host is rebooted, the changes will be lost and the script must be run again. Alternatively, build the systemtap script on a development system with "stap -g -p 4 [filename-from-step-1].stp", distribute the resulting kernel module to all affected systems, and run "staprun -L <module>" on those. When using this approach only systemtap-runtime package is required on the affected systems. Please notice that the kernel version must be the same across all systems. This may not be a suitable workaround if your application uses massive amounts of stack space. Please consider this if there are any adverse affects when running this mitigation. Disable Smart Proxy Dynflow by setting the :enabled: option to false in the /etc/foreman-proxy/settings.d/dynflow.yml file. HTTP/2 support is disabled by default on OpenShift Container Platform 3.11. To mitigate this vulnerability keep it disabled. You can verify it HTTP/2 support is enabled by following the instructions in the upstream pull request, [1]. [1] https://github.com/openshift/origin/pull/19968 To stop werkzeug debug mode started by rbd-target-api which is provided by ceph-iscsi-cli: 1. ~]# systemctl stop rbd-target-api 2. ~]# vi /usr/bin/rbd-target-api # Start the API server ... 737 app.run(host='0.0.0.0', 738 port=settings.config.api_port, 739 debug=True, <==== change this to debug=False use_evalex=False, <=== add this line to disable debugger code execution 740 use_reloader=False, 741 ssl_context=context) ... after changes it should be # Start the API server ... 737 app.run(host='0.0.0.0', 738 port=settings.config.api_port, 739 debug=False, use_evalex=False, 740 use_reloader=False, 741 ssl_context=context) ... 3. ~]# systemctl start rbd-target-api 4. Limit exposure of port 5000/tcp: This port should be opened to trusted hosts which require to run 'gwcli'. Configuring your firewall to limit the origin and/or rate of incoming ssh connections (using the netfilter xt_recent module) will limit the impact of this attack, as it requires a new TCP connection for each username tested. This configuration also provides some protection against brute-force attacks on SSH passwords or keys. Administrators can mitigate this issue by setting reasonable limits on size of processed image, consumed memory, time limit, etc. For example, disallowing the processing of large images (e.g. having either width or height larger than 10240 pixels) which consumes a lot of CPU time can be done by adding the following XML child elements under <policymap> element in /etc/ImageMagick/policy.xml: ``` <policy domain="resource" name="width" value="10KP"/> <policy domain="resource" name="height" value="10KP"/> ``` As per upstream (https://grafana.com/blog/2018/08/29/grafana-5.2.3-and-4.6.4-released-with-important-security-fix) * Switch to authentication mechanism other than LDAP or OAuth * Grafana should be isolated from public networks Please see https://bugzilla.redhat.com/show_bug.cgi?id=1619748#c3 Please see https://bugzilla.redhat.com/show_bug.cgi?id=1619748#c3 ImageMagick relies on ghostscript when processing certain files formats. Thus, ImageMagick can be used as an attack vector. In order to prevent ImageMagick from processing those files on Red Hat Enterprise Linux 6 and 7, you can disable the use of ghostscript and the processing of PS, EPS, PDF, and XPS file formats in ImageMagick's security policy by opening /etc/ImageMagick/policy.xml and adding the following lines to the "<policymap>" section of the file: <policy domain="coder" rights="none" pattern="PS" /> <policy domain="coder" rights="none" pattern="EPS" /> <policy domain="coder" rights="none" pattern="PDF" /> <policy domain="coder" rights="none" pattern="XPS" /> <policy domain="delegate" rights="none" pattern="gs" /> Additionally, this issue can be triggered when processing files in order to generate thumbnails, for example when browsing a folder containing a malicious PostScript file in Nautilus. To prevent this, remove or rename the "/usr/bin/evince-thumbnailer" executable. Please see https://bugzilla.redhat.com/show_bug.cgi?id=1619748#c3 Please see https://bugzilla.redhat.com/show_bug.cgi?id=1619748#c3 Allow only trusted users to run the faxq-helper binary, by correctly setting the /etc/mgetty+sendfax/fax.allow configuration file. Make sure the `notify` option in /etc/mgetty+sendfax/mgetty.config does not contain characters that can be possibly interpreted by the shell and that the file is readable and writable only by root. Make sure the `notify` option in /etc/mgetty+sendfax/mgetty.config does not contain more than 150 characters and that the file is readable and writable only by root. RHEL-7 will automatically default to (safe) “eager” floating point register restore on Sandy Bridge and newer Intel processors. AMD processors are not affected. You can mitigate this issue on older processors by booting the kernel with the 'eagerfpu=on' parameter to enable eager FPU restore mode. In this mode FPU state is saved and restored for every task/context switch regardless of whether the current process invokes FPU instructions or not. The parameter does not affect performance negatively, and can be applied with no adverse effects to processors that are not affected. Ensure config.assets.compile = false in production.rb. Do not add untrusted users to sys and root groups. On Red Hat Enterprise Linux 7 only root has access to /var/run/charon.ctl so you need to be already root to exploit the vulnerability. One may change the default 4MB and 3MB values of net.ipv4.ipfrag_high_thresh and net.ipv4.ipfrag_low_thresh (and their ipv6 counterparts net.ipv6.ipfrag_high_thresh and net.ipv6.ipfrag_low_thresh) to 256 kB and 192 kB (respectively) or below. Tests show some to significant CPU saturation drop during an attack, depending on a hardware, configuration and environment. There can be some impact on performance though, due to ipfrag_high_thresh of 262144 bytes, as only two 64K fragments can fit in the reassembly queue at the same time. For example, there is a risk of breaking applications that rely on large UDP packets. See the Mitigation section in the https://access.redhat.com/articles/3553061 article for the script to quickly change to/from default and lower settings. Disable SMT/Hyper-Threading. Disabling the "deny-answer-aliases" configuration option should prevent exploitation. Advice on how to remain safe while using JAX-RS webservices on JBoss EAP 7.x is available here: https://access.redhat.com/solutions/3279231 https://github.com/FasterXML/jackson-docs/wiki/JacksonPolymorphicDeserialization Vulnerable code when String#unpack's argument is attacker controlled. In the unpack format string argemument, manual sanitization can be done by preventing the number following '@' to overflow to a negative number. See https://dev.to/sqreenio/an-in-depth-look-at-cve-2018-8878-or-why-integer-overflows-are-still-a-thing-1n01 for mitigation details. It is possible to test for presence of the NULL byte manually prior to call the affected methods. It is possible to test for presence of the NULL byte manually prior to call a Dir method with an untrusted string. This is a hardware processor issue, not a Linux kernel flaw. The flaw specifically targets software which uses sensitive information in branching expressions. A software mitigation could be for the target software to avoid the use of sensitive data bits in (if..else) branching decisions or to avoid (if..else) branching altogether.