bugtraq - Re: openMosix userspace library stack-based buffer overflow

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20080410150118.14830.qmail@securityfocus.com>
Date: 10 Apr 2008 15:01:18 -0000
From: nixpanic@...rs.sourceforge.net
To: bugtraq@...urityfocus.com
Subject: Re: openMosix userspace library stack-based buffer overflow

This vulnerability does not seem to be valid. The example given in the API can not be abused by any (correctly) working application using this libary. The 'const char *item' argument only has limited valid values. If an invalid value is used, the application won't be able to gather the requested information. None of the possible valid values can be used to create a buffer overflow.

As stated in the openMosix-API: 'item' can be e.g. load, speed, cpus, util, status, mem, rmem, tmem)
This refers to the files available in the /proc/hpc-directorystructure. None of these files have a filename longer than the allocated buffer.