full-disclosure - Re: [AppSecInc Advisory MYSQL05-V0002] Buffer Overflow in MySQL User Defined Functions

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <03fc01c59c7a$b38506b0$2100a8c0@ngssoftware.com>
Date: Tue Aug  9 02:54:16 2005
From: davidl at ngssoftware.com (David Litchfield)
Subject: Re: [AppSecInc Advisory MYSQL05-V0002] Buffer
	Overflow in MySQL User Defined Functions

> Buffer Overflow in MySQL User Defined Functions
> Risk level: LOW
> Credits: This vulnerability was discovered and researched by Reid
> Borsuk of Application Security Inc.

How can this even be marked as low risk? If you're loading a library into 
mysql's address space then you're already executing "arbitrary code". It's 
important that we, as security researchers, don't desensitize the readership 
with pointless "vulnerability" posts otherwise people begin to turn off. 
Sure - you've found some sloppy code in mysql - get it looked at by all 
means but please don't try to create a risk, whether low or not, where there 
really is none.

Cheers,
David "got out of the wrong side of bed this morning" Litchfield