BugTraq
[HV-HIGH] Microsoft Jet DB engine vulnerabilities Mar 31 2005 09:53PM
vuln hexview com (1 replies)
Re: [HV-HIGH] Microsoft Jet DB engine vulnerabilities Apr 01 2005 12:53AM
Thor (Hammer of God) (thor hammerofgod com) (1 replies)
Re: [HV-HIGH] Microsoft Jet DB engine vulnerabilities Apr 02 2005 08:59AM
Denis Jedig (seclists syneticon de) (2 replies)
Re: [HV-HIGH] Microsoft Jet DB engine vulnerabilities Apr 03 2005 09:12PM
Thor (Hammer of God) (thor hammerofgod com)
Re: [HV-HIGH] Microsoft Jet DB engine vulnerabilities Apr 03 2005 05:13PM
Steve Shockley (steve shockley shockley net) (1 replies)
Re: [HV-HIGH] Microsoft Jet DB engine vulnerabilities Apr 04 2005 06:23PM
Son SonOfLilit (sonoflilit gmail com)
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 (at) shockley (dot) net [email concealed]> 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.
>

[ reply ]


 

Privacy Statement
Copyright 2010, SecurityFocus