For anyone who cares, this problem has now been assigned CVE-2006-0482 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-0482 (That link isn't active yet, but hopefully it will be soon) -- Horms