Re: [Full-Disclosure] Jamming communication [COM] ports in windows...

[S G Masood <sgmasood@xxxxxxxxx>]

Hi Bipin,

This is a long known issue. AFAIK, not only "edit
com*", but any operation involving device names as
file names will cause the same issue

Best Regards,

--
S.G.Masood.
Hyderabad,
India.


--- Bipin Gautam <door_hUNT3R@xxxxxxxxxxxxxxxxx>
wrote:
> ---Description---
> In windows filenames like CON, AUX, PRN, CLOCK$
> ,COM* , LPT* [ "*" stands for 1, 2, 3, 4 etc... ]
> can't be created cauz it's reserved for "System
> Device Driver" NAMES by OS itself.
> 
> ---Exploit---
> 
> Well, using simple command "say"
> 
> edit COM*                  [ "*" stands for 1, 2, 3,
> 4 etc... ]
> 
> ---<Example>---
> 
> c:\> edit COM8         < Here COM8 was actually
> reserved by my MODEM in my computer >
> 
> type it in CMD prompt or "RUN" etc... Using this
> Any/EVERY available communication port's in WINDOWS
> could be JAMMMED! By using JUST the privileges of a
> "GUEST" account.
> 
> ---Summery---
> The exploits have been successfully tried in Windows
> xp pro. and windows 98. I assume! It works in all
> versions of windows. While trying the exploit THE
> COM* should not be in use.
> 
> ---[Background Information]---
> These bug's were originally discovered by hUNT3R,
> [myself] a member of 01 Security Submission. The
> vendor was notified via email.
> http://www.ysgnet.com/hn
> 
>
_____________________________________________________________
> Secure mail ---> http://www.blackcode.com
> 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter:
http://lists.netsys.com/full-disclosure-charter.html


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html