Y2K

[magicvsmagick]

I would like to inform, with deep regret to members of this newsgroup
about the Y2K bug. I call it the Y2K bug but I'm not talking about
your system clock. I'm talking about buffer overflows.

The problem needs to be corrected at the source, and not patched as
weak vulnerabilities become uncovered. When I write C++ code I build
protection around every memory space, but this is time consuming when
code is done professionally.

I wrote a simple html webpage tonight bored out of my mind that crashed
microsoft word with a buffer overflow, when I opened it. This problem
needs to be fixed because I am not a hacker.

All I did was write a series of open <img tags with a closed image tag
inside of them. That image tag contained alternate text to be used if
the image wasn't displayed that had even more <img tags inside of it.

Something as simple as that should not crash microsoft word! I am upset
that Y2k is such a huge problem, and if hackers take advantage of it
they could put malicious code into memory where the buffer overflows.

I talked with microsoft word technical support but they refused to help
me. Who can I talk to about fixing the Y2K bug?

 

[Shenan Stanley]

I would like to inform, with deep regret to members of this
newsgroup about the Y2K bug. I call it the Y2K bug but I'm not
talking about your system clock. I'm talking about buffer
overflows.

The problem needs to be corrected at the source, and not patched as
weak vulnerabilities become uncovered. When I write C++ code I
build protection around every memory space, but this is time
consuming when code is done professionally.

I wrote a simple html webpage tonight bored out of my mind that
crashed microsoft word with a buffer overflow, when I opened it.
This problem needs to be fixed because I am not a hacker.

All I did was write a series of open <img tags with a closed image
tag inside of them. That image tag contained alternate text to be
used if the image wasn't displayed that had even more <img tags
inside of it.

Something as simple as that should not crash microsoft word! I am
upset that Y2k is such a huge problem, and if hackers take
advantage of it they could put malicious code into memory where the
buffer overflows.

I talked with microsoft word technical support but they refused to
help me. Who can I talk to about fixing the Y2K bug?

Word what?
Internet Explorer what?
OS?
Patched to what level?
What other applications installed?
Are those other applications updated?
etc.. etc.. etc..

 

[Bob I]

So you're nesting HTML <img tags till it till it crashes Word? I wonder
why they couldn't be bothered.

 

[magicvsmagick]

Word what?
Internet Explorer what?
OS?
Patched to what level?
What other applications installed?
Are those other applications updated?
etc.. etc.. etc..

I'm using Word Word 2003, IE 6, Windows XP.
They are all installed fresh out of the box, and came with this
computer that I just purchased. I patched everything up to date as
soon as I turned it on.

The only other applications I run are AOL, and graphics software that I
bought and paid for.

I have noticed strange problems when IE opens the offending file as
well.

Please try and help resolve this issue, because this seems like a
serious threat to me, and I'm not a hacker. The vulnerability is so
simple that I am sure hackers must already be aware of it and know how
to take advantage of systems like mine.

Thanks