If the user reads a sysctl entry which is of string type
by sysctl syscall, this call probably corrupts the user data
right after the old value buffer, the issue lies in sysctl_string
seting 0 to oldval[len], len is the available buffer size
specified by the user, obviously, this will write to the first
byte of the user memory place immediate after the old value buffer
, the correct way is that sysctl_string doesn't set 0, the user
should do it by self in the program.
Re: [PATCH] Fix user data corrupted by old value return of sysctl ... by sysctl syscall, this call probably corrupts the user data right after the old value buffer, the issue lies in sysctl_string seting 0 to oldval, len is the available buffer size specified by the user, obviously, this will write to the first byte of the user memory place immediate after the old value buffer, the correct way is that sysctl_string doesn't set 0, the user should do it by self in the program. ...int sysctl{struct __sysctl_args args ...int target;... Current host name: ... (Linux-Kernel)
Re: Two macros for resource management ... > PUSH(fclose(source)) ... > PUSH(fclose(target))... > PUSH(free(buffer))...{int result = EXIT_FAILURE; ... (comp.lang.c)
[EXPL] XFree86 XLOCALEDIR Exploit Code ... A vulnerability in XFree86's XLOCALEDIR string handling allows a local ... ** Demonstration - here we use xlock as the target...int LEN;...local root exploit ---\n" ... (Securiteam)
Re: SQL Server 2000 BUG? ... I think using subselects will generate the same query plan as using ... pk int not null primary key, ...UPDATE target... (microsoft.public.sqlserver.programming)