• About Us
  • Search
  • Compatibility
  • Forums
  • Archive
  • Channels
  • Home
To take full advantage of all features you need to login or register. Registration is completely free and takes only a few seconds.
Warp2Search.net » News » January 2002 » Internet Explorer Security Flaw Revisited!

Internet Explorer Security Flaw Revisited!

Posted by: [PM] on: 01/02/2002 01:26 PM [ Print | 2 comment(s) ] · 574 views

Security consultant Georg Guninski has uncovered a new variant of an Active Scripting flaw which may lead to IE reading local files due to a bug in GetObject(). It is advised to read more.



Georgi Guninski security advisory #52, 2001 IE GetObject() problems Systems affected:
Patched IE 6.0, somewhat patched 5.5 Win2K Risk: High
Date: 1 January 2002 Legal Notice:
This Advisory is Copyright (c) 2001 Georgi Guninski.
You may distribute it unmodified.
You may not modify it and distribute it or distribute parts
of it without the author's written permission. Disclaimer:
The information in this advisory is believed to be true based on
experiments though it may be false.
The opinions expressed in this advisory and program are my own and
not of any company. The usual standard disclaimer applies,
especially the fact that Georgi Guninski is not liable for any damages
caused by direct or  indirect use of the information or functionality
provided by this advisory or program. Georgi Guninski bears no
responsibility for content or misuse of this advisory or program or
any derivatives thereof. Description: IE allows reading local files due to a bug in GetObject().
Reading local files may lead to executing arbitrary programs. Details: GetObject() has a bad security record - 
check http://www.guninski.com/browsers.html
The new bug is quite similar to:
http://www.guninski.com/getobject1-desc.html
the difference being:
----------------------
a=GetObject("http://"+location.host+"/../../../../../../test.txt","htmlfile");
----------------------
It is funny that directory traversal on a http: URL leads to reading local files. Workaround/Solution: Disable Active Scripting and never turn it on.
Better, do not use IE in hostile environments such as the internet.  Vendor status: Microsoft was notified on 11 December 2001.
They had 3 weeks to produce a patch but didn't. Regards,
Georgi Guninski
Guninski.com

Digg it! Del.icio.us Technorati Furl Google Bookmarks

« New ECS BIOSes Out! · Internet Explorer Security Flaw Revisited! · ItweakU v4.03! »

Comment

unknown
Junior Member


Posts: 2
Joined: 2002-11-11

#34873 Posted on: 01/02/2002 03:50 PM
IE 6 Service Pack 1 doesnt seem to be affected by it

Comment

unknown
Junior Member


Posts: 2
Joined: 2002-11-11

#34876 Posted on: 01/02/2002 06:47 PM
You will likely see less and less patches for anything other than IE6. After all, you don't hear about security patches for Win95 (oh please we all know they are still there, but not even anti-MSers are beating the drum on those) anymore.

They are pushing for upgrade, and speaking personally, I'd rather run IE6 on XP than IE3 on Win95.

Warp2Search.net » News » January 2002 » Internet Explorer Security Flaw Revisited!

Latest News

· PQI Cool Drive U350H Review
· Tagan Icy Box IB-285StU-B USB 2 1/2 Review
· AMD's Phenom X4 9350e Review
· Razer Lycosa Gaming Keyboard Review
· How To Install Django On Debian Etch (Apache2/mod_python)
· MSI Wind - upgrading memory voids the warranty
· IBM - Hitachi Drive Fitness Test 4.14
· Wise Registry Cleaner 3.6.3
· Avast! Home Edition 4.8.1229
· Windows SBS 2008 Release Candidate 0
· Microsoft Office Outlook Connector 12.1 Beta
· Intel EP80579 Integrated Processor Preview
· Asus Trinity Tri-GPU Graphics Prototype Benched
· Sapphire HD 4870 Review
· Palit HD 4870 512MB Video Card Reviewed
· GeForce 9800 GTX+ SLI tested
· Mighty Mouse 5 Waterproof Mouse Review
· Rosewill RX630-S-B Xtreme 630W PSU Review
· GNOME 2.23.5 Released
· iPhone Gaming Article

Nodes To Friends





Online Users

There are currently 726 user(s) online

© 2007-2008 Esselbach Internet Solutions
All products mentioned are registered trademarks or trademarks of their respective owners.
Read our disclaimer over here and our Privacy Policy over here
Managed with Contentteller