How can I upgrade this against C.O.W. on Owls with kernel version 2.6.18-194.11.3.el5.028stab071.5.owl1
"Alan Williams" <[email protected]> Thu, 17 Nov 2016 17:02:59 +1100
| Newsgroups | gmane.linux.openwall.user |
|---|---|
| Message-ID | <[email protected]> |
This is a multipart message in MIME format.
------=_NextPart_000_4086_01D240F4.7395F110
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
I have found a number of owl installs in the infrastructure I now manage and
I am wondering how to deal with them in respect of the dirty c.o.w.
vulnerability, given that they are all quite old.
The four machines list the following two kernel versions:
2.6.18-194.11.3.el5.028stab071.5.owl1 #1 SMP Sat Sep 25 02:43:36 MSD 2010
x86_64 GNU/Linux
2.6.18-348.3.1.el5.028stab106.2.owl1 #1 SMP Mon Apr 8 03:39:13 MSK 2013
x86_64 GNU/Linux
Many thank
Alan
------=_NextPart_000_4086_01D240F4.7395F110
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-AU =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal>I have found a number of owl installs in the =
infrastructure I now manage and I am wondering how to deal with them in =
respect of the dirty c.o.w. vulnerability, given that they are all =
quite old.<o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><p =
class=3DMsoNormal>The four machines list the following two kernel =
versions:<o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><p =
class=3DMsoNormal>2.6.18-194.11.3.el5.028stab071.5.owl1 #1 SMP Sat Sep =
25 02:43:36 MSD 2010 x86_64 GNU/Linux<o:p></o:p></p><p =
class=3DMsoNormal>2.6.18-348.3.1.el5.028stab106.2.owl1 #1 SMP Mon Apr 8 =
03:39:13 MSK 2013 x86_64 GNU/Linux<o:p></o:p></p><p =
class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal>Many =
thank<o:p></o:p></p><p class=3DMsoNormal>Alan<o:p></o:p></p><p =
class=3DMsoNormal><o:p> </o:p></p></div></body></html>
------=_NextPart_000_4086_01D240F4.7395F110--