bugtraq - Jamming communication [COM] ports in windows...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20030923114030.172D9E4BE@sitemail.everyone.net>
Date: Tue, 23 Sep 2003 04:40:29 -0700 (PDT)
From: Bipin Gautam <door_hUNT3R@...ckcodemail.com>
To: full-disclosure@...ts.netsys.com
Cc: bugtraq@...urityfocus.com
Subject: Jamming communication [COM] ports in windows...

---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