|
| |
| |
|
|
|
|
| |
- TCP/IP
Out of band data bug - May
16, 1997 (05/16/1997)
- The bug sends Out Of Band
data to any TCP/IP port listening for a
connection most web servers listen for
connections on port 80. While this bug
can cause Win NT and Win 95 machines (at
worst case) to crash, it will not make
the system's data available to hackers.
There is a Unix program called Winnuke
and a Windows program called Bitchslap
that can be used to generate these types
of errors.
- Microsoft Corp. posted a fix
for Windows NT to
replace the TCP/IP services (Service Pack
3 is 18mg for Intel and 25mg for Alpha ):
- ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP2/oob-fix
|
| Guest Account -
The presents a security threat
and according to Microsoft ( KB Article ID:
Q101232) should
be disabled in order to enhance security (major). |
Windows NT "RedButton"
Issue
 | Microsoft
Info |
| NT
Security.com - RedButton
Bug
General Synopsis - An account created
by NT is called Everyone.
This has the potential of the following:
1. Any
Default Installation of Windows NT
Workstation (v 3.51, 4.0) is vulnerable:
- the flaw allows the creation of a new
entry in the registry which describes a
new drive share with access granted to
Everyone.
- a potential intruder can then wait for
the system to reboot
- after reboot the new share is published
on the network to Everyone. By sharing
system drive one can obtain a copy of a
password file updated by rdisk -s from
the %SYSTEMROOT%\Repair directory, etc.
2. Any
Default Installation of Windows NT Server
or Workstation (v 4.0) is vulnerable:
- the flaw allows the creation of a new
entry in the registry which describes a
reference to a Trojan horse program
located on the intruder's computer e.g.
\\xxx.xxx.xxx.xxx\Share\Smth.exe
- potential intruder can then wait for an
interactive logon
- after the user logs on to the server
the Trojan horse program is executed.
Obviously, the Trojan horse program could
do about anything if the logged user is
an Administrator. The Trojan can create a
share (see above) if the logged user has
guest or ordinary user privileges.
General
Solution - Remove the account Everyone
from your system. This includes any
access rights granted and recorded within
the system registry. You must also insure
that the Permissions are changed and
propagated to all your NT computers.
|
|
|
|
|
NT 4.0 (by country) - ftp.microsoft.com/bussys/
winnt/winnt-public/fixes/.
|
| |
|
| |
|
| |
|
| |
|
| MS Windows 95 |
|
|
      
Password Bug in Windows
for Workgroups & Win 95
Service Packs
OEM Service
Release 2 (OSR 2)
These updates are intended to provide support for
new and emerging hardware. Because most of the new
functionality in OSR 2 is applicable only to new
hardware devices, OSR 2 is only available on new PCs.
However, here are the OSR 2 components available for
download from the Internet today!
Internet Connection Wizard
Microsoft Internet Explorer 3.0
Personal Web Server
Internet Mail and News
NetMeeting
DirectX 2.0 (including Direct3Dä)
ActiveMovie
ISDN Accelerator Pack 1.1
Unimodem V (Support for Voice Modems
MSN 1.3
Wang Imaging for Windows 95
Fixes/Updates
Power Toys - www.microsoft.com/windows/software/PowerToy.htm
.
|
| |
E.27. How to kill Windows' dubious "password
caching feature"?
Date: Fri, 29 Dec 1995 21:00:00 -0800
From: Rich Graves <win95netbugs-owner@lists.stanford.edu>
By default, Windows stores all network and dialup
passwords in world-readable .PWL files. Even if Microsoft
successfully resolves the serious .PWL
encryption bugs that make password storage totally
insecure (which they have promised to do for Win95, but
not for Windows for Workgroups), this default
"password caching" behavior is inappropriate
for many sites.
To turn it off for Windows for Workgroups, add the
following to SYSTEM.INI [Credit Jim Carlson]:
[NETWORK]
passwordcaching=no
To turn it off for Win95, you can use Policy Editor,
or edit the following Registry entry directly:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\
Network\DisablePwdCaching
This gets a binary value of 1 [Credit Malcolm G.
Miles].
Here's a simple RegEdit script to accomplish the
above. Save it as NOCACHE.REG and run it from either DOS
(in a network login script, for example) or Windows.
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Network]
"DisablePwdCaching"=dword:00000001
Note that there are *three* nonblank lines. The second
nonblank line ends with the right bracket and the third
starts with the double quote; what you're seeing is *not*
a line broken at column 80.
|
| |
|
| |
|
| |
|
Disclaimer: We do not hold any responsibility or creative control over
the contents of the web sites and documents referenced by our links. They solely express the
opinions of their respective authors and not Ugenie PCS. Items and information are
provided as links because they appear to have relevant content to topics presented on our
web site(s). Ugenie PCS does not continually verify the truthfulness or locations
of their contents. Ugenie PCS does not endorse, recommend, or guarantee any particular software.
Software and other items on these pages are provided as a service only and maybe copyrighted by their respective owners. Requests for
additions to, or removal from, this or other pages should be sent to Content
Management@CezWright.com.
Additionally
Last Edit: 2002-10-24 10:54 AM -0400
Auto Update: Saturday, August 20, 2005 12:29 PM -0400
|
|
