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: Wed, 5 Nov 2003 17:39:53 -0500
From: "Steve Hillier" <>
To: "'Thor Larholm'" <>,
	"'Liu Die Yu'" <>,
Subject: RE: Six Step IE Remote Compromise Cache Attack

I see this more as a method to bring attention to the fact that even
though the individual flaws seem trivial, they can be combined to
perform a malicious act.

Vendors often do not act on an individual flaw as quickly if they feel
the exploit is trivial. This however shows that the individual flaws
pose a greater risk when combined, and that a 'trivial' flaw shouldn't
be ignored simply because it seems 'harmless'.

Why have these flaws not been patched even after almost two years of
knowing that they exist?

Steve Hillier, B.Sc.
Manager of Information Services
Mastermind Educational 

> -----Original Message-----
> From: Thor Larholm [] 
> Sent: Wednesday, November 05, 2003 5:23 p
> To: Liu Die Yu;
> Subject: RE: Six Step IE Remote Compromise Cache Attack
> This post raises an interesting question. Is our goal to find 
> new vulnerabilities and attack vectors to help secure users 
> and critical infrastructures, or is our goal to ease 
> exploitation of existing vulnerabilities?
> There are no new vulnerabilities or techniques highlighted in 
> this attack (which is what it is), just a combination of 
> several already known vulnerabilities. This is not a 
> proof-of-concept designed to highlight how a particular 
> vulnerability works, but an exploit designed specifically to 
> compromise your machine. All a malicious viruswriter has to 
> do is exchange the EXE file.
> Believe me, I am all in for full disclosure and detailing 
> every aspect of a vulnerability to prevent future occurances 
> of similar threats, but I don't particularly think that we 
> should actively be trying to help malicious persons.
> Regards
> Thor Larholm
> Senior Security Researcher
> PivX Solutions, LLC
> Get our research, join our mailinglist -
> -----Original Message-----
> From: Liu Die Yu [] 
> Sent: Wednesday, November 05, 2003 2:35 AM
> To:
> Subject: Six Step IE Remote Compromise Cache Attack
> Snip 

Powered by blists - more mailing lists