From: "Rich"
This is a multi-part message in MIME format.
------=_NextPart_000_0020_01C2BF1B.87850860
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_0021_01C2BF1B.87850860"
------=_NextPart_001_0021_01C2BF1B.87850860
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Because the thread started with new features =3D=3D new =
vulnerabilities and branched from a thread discussing a less feature = rich
player like WMP 6.x. Media playback is constant across the board = and
would not support a claim of new vulnerabilities being due to new = WMP9
features.
Rich
"Randy H" wrote in message =
news:3e29f939{at}w3.nls.net...
Why the exclusion of new features related to media playback?=20
"Rich" wrote in message news:3e29aacb{at}w3.nls.net...
Yep along with whether they are due to new features, specificly =
those not related to media playback.
Rich
"Randy H" wrote in message =
news:3e29747e{at}w3.nls.net...
We'll just have to wait and see what vulnerabilities do surface =
with WMP9. =20
"Rich" wrote in message news:3e279d79{at}w3.nls.net...
If you were to look at these you would find that the more =
recent more feature rich players have fewer issues than older players =
pretty much refuting the insinuation that more features =3D=3D more =
vulnerabilities. WMP 8.0 for Windows XP has two or if you stretch three =
issues. Of those two, one was common to all players and one was an old =
feature retained for compatility and the vulnerability was not with WMP =
but an issue of WMP exposing something that could be used against =
something else.
I suspect if you look at other media players you would likely =
find the same. Not that Real Player has had a great track record lately =
but I suspect newer versions are better than old ones.
Rich
"Randy H" wrote in message =
news:3e2768da{at}w3.nls.net...
Some of these look old, but I'm not at all surpised.=20
"Geo." wrote in message =
news:3e2762a0{at}w3.nls.net...
"Randy H" wrote
in message =
news:3e2756fa{at}w3.nls.net...
> What I'd like to know is how many new vulnerability =
vectors these
> new features have added.
2002-10-18: Windows Media Player For Solaris Default =
World Writeable Permissions Vulnerability=20
2002-08-22: Microsoft Windows Media Player File =
Attachment Script Execution Vulnerability=20
2002-07-30: Microsoft Windows Media Player =
Filename Buffer Overflow Vulnerability=20
2002-07-25: Windows Media Player IE Cache Path =
Disclosure Vulnerability=20
2002-06-27: Windows Media Player Playlist HTML =
Script Execution Vulnerability=20
2002-06-27: Windows Media Player WMDM Privilege =
Escalation Vulnerability=20
2001-11-20: Windows Media Player Internet =
Shortcut Execution Vulnerability=20
2001-11-20: Microsoft Windows Media Player .NSC =
File Buffer Overflow Vulnerability=20
2001-11-20: Microsoft Windows Media Player .ASF =
Marker Buffer Overflow Vulnerability=20
2001-08-13: Windows Media Player .ASX 'Version' =
Buffer Overflow Vulnerability=20
2001-05-26: Microsoft Windows Media Player .ASX =
Buffer Overflow Vulnerability=20
2001-05-02: Windows Media Player .ASX Buffer =
Overflow Vulnerability=20
2001-02-14: Microsoft Windows Media Player .WMZ =
Arbitrary Java Applet Vulnerability=20
2001-01-01: Microsoft Windows Media Player =
Javascript URL Vulnerability=20
2000-11-22: Microsoft Windows Media Player .WMS =
Arbitrary Script Vulnerability=20
2000-09-26: Microsoft Windows Media Player 7 =
Embedded OCX Control Vulnerability=20
=20
=20
------=_NextPart_001_0021_01C2BF1B.87850860
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Because
the thread started =
with new=20
features =3D=3D new vulnerabilities and branched from a thread = discussing a less=20
feature rich player like WMP 6.x. Media playback is constant =
across the=20
board and would not support a claim of new vulnerabilities being due to = new WMP9=20
features.
Rich