bugtraq - Re: Publishing exploit code

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

Date: Fri, 1 Jul 2005 15:07:47 +0900 (JST)
From: Curt Sampson <cjs@...ic.net>
To: Aviram Jenik <aviram@...ondsecurity.com>
Cc: full-disclosure@...ts.grok.org.uk, bugtraq@...urityfocus.com
Subject: Re: Publishing exploit code - what is it good for

Interesting, becuase this just hit me the other day.

Wearing my sysadmin hat, I woke up one morning to find that the NetBSD
package converters/xlreader had a vulnerability. Nobody seemed to have
a patch for it, but looking at it, even with my rather limited level of
C coding skill, I reckoned I could fix it. (Standard buffer overflow:
replace sprintf with snprintf kinda thing.) So I did.

Or at least, I think I did. I can't get my hands on a working exploit,
so I don't feel truly comfortable that I did indeed fix the problem. Maybe
to someone more familiar with C it would be proved fixed by inspection,
but I don't feel that comfortable with it myself.

I didn't really used to think that exploits were so useful until this.

cjs
-- 
Curt Sampson  <cjs@...ic.net>   +81 90 7737 2974   http://www.NetBSD.org
      Make up enjoying your city life...produced by BIC CAMERA
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/