ID CVE-2001-1399
Summary Certain operations in Linux kernel before 2.2.19 on the x86 architecture copy the wrong number of bytes, which might allow attackers to modify memory, aka "User access asm bug on x86."
References
Vulnerable Configurations
  • Linux Kernel 2.2.19
    cpe:2.3:o:linux:linux_kernel:2.2.19
CVSS
Base: 2.1 (as of 01-01-2004 - 00:00)
Impact:
Exploitability:
Access
VectorComplexityAuthentication
LOCAL LOW NONE
Impact
ConfidentialityIntegrityAvailability
NONE PARTIAL NONE
nessus via4
  • NASL family Mandriva Local Security Checks
    NASL id MANDRAKE_MDKSA-2001-037.NASL
    description A number of security problems have been found in the Linux kernels prior to the latest 2.2.19 kernel. Following is a list of problems based on the 2.2.19 release notes as found on http://www.linux.org.uk/ - binfmt_misc used user pages directly - the CPIA driver had an off-by-one error in the buffer code which made it possible for users to write into kernel memory - the CPUID and MSR drivers had a problem in the module unloading code which could cause a system a crash if they were set to automatically load and unload - there was a possible hang in the classifier code - the getsockopt and setsockopt system calls did not handle sign bits correctly which made a local DoS and other attacks possible - the sysctl system call did not handle sign bits correctly which allowed a user to write in kernel memory - ptrace/exec races that could give a local user extra privileges - possible abuse of a boundary case in the sockfilter code - SYSV shared memory code could overwrite recently freed memory which might cause problems - the packet lengh checks in the masquerading code were a bit lax (probably not exploitable) - some x86 assembly bugs caused the wrong number of bytes to be copied - a local user could deadlock the kernel due to bugs in the UDP port allocation. All of these problems are corrected in the 2.2.19 kernel and it is highly recommended that all Linux-Mandrake users upgrade their systems to this kernel. It is also recommended that you download the necessary RPMs and upgrade manually by following these steps : - type: rpm -ivh kernel-2.2.19-4.1mdk.i586.rpm - type: mv kernel-2.2.19-4.1mdk.i586.rpm /tmp - type: rpm -Fvh *.rpm - type: mkinitrd -f --ifneeded /boot/initrd-2.2.19-4.1mdk 2.2.19-4.1mdk - type: ln -sf /boot/initrd-2.2.19-4.1mdk /boot/initrd.img - edit /etc/lilo.conf and double-check the options - type: /sbin/lilo -v Replace the kernel revision noted in the above instructions with those from the packages you downloaded. You will then be able to reboot and use the new kernel and remove the older kernel when you are comfortable using the upgraded one.
    last seen 2019-02-21
    modified 2018-07-19
    plugin id 61910
    published 2012-09-06
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=61910
    title Mandrake Linux Security Advisory : kernel (MDKSA-2001:037)
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-047.NASL
    description The kernels used in Debian GNU/Linux 2.2 have been found to have multiple security problems. This is a list of problems based on the 2.2.19 release notes as found on http://www.linux.org.uk/ : - binfmt_misc used user pages directly - the CPIA driver had an off-by-one error in the buffer code which made it possible for users to write into kernel memory - the CPUID and MSR drivers had a problem in the module unloading code which could cause a system crash if they were set to automatically load and unload (please note that Debian does not automatically unload kernel modules) - There was a possible hang in the classifier code - The getsockopt and setsockopt system calls did not handle sign bits correctly which made a local DoS and other attacks possible - The sysctl system call did not handle sign bits correctly which allowed a user to write in kernel memory - ptrace/exec races that could give a local user extra privileges - possible abuse of a boundary case in the sockfilter code - SYSV shared memory code could overwrite recently freed memory which might cause problems - The packet length checks in the masquerading code were a bit lax (probably not exploitable) - Some x86 assembly bugs caused the wrong number of bytes to be copied. - A local user could deadlock the kernel due to bugs in the UDP port allocation.
    last seen 2019-02-21
    modified 2018-07-20
    plugin id 38953
    published 2004-09-29
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=38953
    title Debian DSA-047-1 : kernel
redhat via4
advisories
rhsa
id RHSA-2001:047
refmap via4
bugtraq
  • 20010405 Trustix Security Advisory #2001-0003 - kernel
  • 20010409 PROGENY-SA-2001-01: execve()/ptrace() exploit in Linux kernels
caldera CSSA-2001-012.0
conectiva CLA-2001:394
confirm http://www.linux.org.uk/VERSION/relnotes.2219.html
debian DSA-047
immunix IMNX-2001-70-010-01
mandrake MDKSA-2001:037
suse SuSE-SA:2001:018
Last major update 07-12-2016 - 21:59
Published 17-04-2001 - 00:00
Back to Top