Vulnerability Assessment & Network Security Forums
If through a vulnerability assessment, a network security issue is detected for the vulnerability below, applying the appropriate security patches in a timely matter is very important. If you have detected that your system has already been compromised, following CERT's Network Security recovery document will assist with recommended steps for system recovery.
Vulnerability Assessment Details
Check for the version of the kernel package
Detailed Explanation for this Vulnerability Assessment
The remote host is missing the patch for the advisory FEDORA-2006-421 (kernel).
The kernel package contains the Linux kernel (vmlinuz), the core of any
Linux operating system. The kernel handles the basic functions
of the operating system: memory allocation, process allocation, device
input and output, etc.
This update includes a number of security issues that have been
fixed upstream over the last week or so.
i386/x86-64: Fix x87 information leak between processes
ip_route_input panic fix (CVE-2006-1525)
fix MADV_REMOVE vulnerability (CVE-2006-1524)
shmat: stop mprotect from giving write permission to a
readonly attachment (CVE-2006-1524)
Fix MPBL0010 driver insecure sysfs permissions
x86_64: When user could have changed RIP always force IRET
Fix RCU signal handling
Keys: Fix oops when adding key to non-keyring (CVE-2006-1522)
sysfs: zero terminate sysfs write buffers (CVE-2006-1055)
It also includes various other fixes from the -stable tree.
Full changelogs are available from:
Solution : Get the newest Fedora Updates
Network Security Threat Level: High
Networks Security ID:
Vulnerability Assessment Copyright: This script is Copyright (C) 2006 Tenable Network Security
|Intel Xeon E5-2680 V2 SR1A6 OEM 2.8GHz 10Core 115W 20T 25M LGA2011 Processor
|Apple Mac Pro A1289|2009| Xeon QC@2.66GHz| 8GB| 2x1TB/640GB/160GB HDDs (H574018)
|Apple Mac Pro A1289| 2010| Xeon QC@2.8GHz| 8GB RAM| 1TB HDD| OS Lion (H573968)
|Apple Mac Pro A1289| 2009| Xeon QC@2.67GHz| 8GB| 2x 1TB & 640GB| Lion (H574156)
No Discussions have been posted on this vulnerability.