bugtraq - Re: [HV-HIGH] Microsoft Jet DB engine vulnerabilities

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]

Date: Mon, 4 Apr 2005 20:23:29 +0200
From: Son SonOfLilit <sonoflilit@...il.com>
To: Steve Shockley <steve.shockley@...ckley.net>
Cc: "bugtraq-securityfocus.com" <bugtraq@...urityfocus.com>
Subject: Re: [HV-HIGH] Microsoft Jet DB engine vulnerabilities

Or perhaps you have some macros running on every file (WordXP throws
me a warning every time I open a DOC since I installed MathType, which
extends Office through VBA scripts. Guess WordXP has some kind of
".login" / "autoexec.bat" file - a "initialization" script, that
MathType hooks up through... Never bothered to research into it)

(Sorry for the empty mail I mistakenly sent earlier)

On Apr 3, 2005 7:13 PM, Steve Shockley <steve.shockley@...ckley.net> wrote:
> Denis Jedig wrote:
> > Newer Access versions throw a security warning if the VBA code is not
> > signed and let the user disable VBA execution. The issue highlighted by
> > hexview is able to circumvent this security-related feature.
> 
> Access 2003 on WinXP SP2 throws a security warning when I open any
> Access file, even one without VBA.  I believe that's new with WinXP SP2.
>