Bug 177311 - CVE-2005-4618 sysctl overflow
Summary: CVE-2005-4618 sysctl overflow
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Alexander Viro
QA Contact: Brian Brock
Whiteboard: reported=20051231,source=lkml,impact=...
Depends On:
TreeView+ depends on / blocked
Reported: 2006-01-09 15:50 UTC by Mark J. Cox
Modified: 2012-06-20 13:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-06-20 13:33:10 UTC

Attachments (Terms of Use)

Description Mark J. Cox 2006-01-09 15:50:50 UTC
CVE defines CVE-2005-4618 as:
"Buffer overflow in sysctl in the Linux Kernel 2.6 before 2.6.15 allows local
users to cause a denial of service and possibly execute arbitrary code via a
long string, which causes sysctl to write a zero byte outside the buffer."

This is fixed by

I can't see a useful attack vector here, writing a character to one spot after a
userland buffer seems to me likely at the worst to crash your userland program,
and not cause a DoS or privilege escalation.  So we have marked this severity
low but this could equally be severity none (kernel maintainers please let us
know what you think after analysis)

Comment 1 Jason Baron 2006-01-09 22:36:46 UTC
agreed. the bug here is that a NULL character can be written 1 byte off the end
of   a user supplied buffer, which is a potential data corruption. I don't see
any DoS issue here, if the extra byte is not mapped, then the kernel will return
cleanly. A single byte corruption of userspace is fairly serious though, imo.

Comment 2 Jiri Pallich 2012-06-20 13:33:10 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

Note You need to log in before you can comment on or make changes to this bug.