jtgh
Fri Feb 04 16:41:21 CST 2005
window File Protector ( what it does and what it does not do )
also see : System File Checker sfc.exe (boot scan)
I assembeled this group to understand WFP.
WFP
the horses mouth (arce?):
http://support.microsoft.com/default.aspx?scid=kb;en-us;222193
Note the M$ fails to note other means of attack, the kernal itself and
WFP , can
be attacked , not to mention the Update.exe, dllhost.exe, can be
attacked.
Or any virus that can run the regedit code and turn off WFP will be
successful.
Cmd.exe ?
or WINLOGON.EXE or W32TM.EXE
Why is it that M$ always understates the issues, ignorance, EGO, or are
they just
keeping the Hackers , ignorant. I just wonder.
known successful attacks: ( direct or indirect) , just to name a few.
Nachi Worm attacks the following file:
C:\WINNT\system32\wins\dllhost.exe
and
virus <WORM.MSBLAST
Win32.Wqk.C
VBS.LOVELETTER Worm
W32.Pinfi
W32.Valla.2048
Code Red worm
TROJAN EXPLORER.EXE
[First, the trojan program adds the value SFCDisable=0xFFFFFF9D
to HKLM\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogin.
This registry setting completely disables the Windows File
Protection (WFP) mechanism. WFP prevents the replacement of
certain monitored system files. See the following for more info:
http://support.microsoft.com/support/kb/articles/Q222/1/93.ASP]
Links:
http://groups-beta.google.com/group/microsoft.public.windowsxp.setup_deployment/b
rowse_frm/thread/452843f86a37bcbc/fd4210a02427445f?q=WPF+++Windows+XP&_done=%2Fgr
oups%3Fhl%3Den%26q%3DWPF+++Windows+XP%26qt_s%3DSearch+Groups%26&_doneTitle=Back+t
o+Search&&d#fd4210a02427445f
One known weakness:
WFP will pop up an alert if you try to delete/rename a dllcache'd file
on
Windows 2000 Professional. ( under admin only)
A workaround (my favorite) that I found posted somewhere was to do
something
like this:
copy c:\winnt\system32\dllcache\notepad.exe
c:\winnt\system32\dllcache\wscript.exe
copy c:\winnt\system32\dllcache\notepad.exe
c:\winnt\system32\dllcache\cscript.exe
copy c:\winnt\system32\dllcache\notepad.exe
c:\winnt\system32\wscript.exe
copy c:\winnt\system32\dllcache\notepad.exe
c:\winnt\system32\cscript.exe
WFP is not intelligent enough to know when one protected file is
overwritten
with a copy of another. ( note a service pack may have cured this bug)
Weakness 2:
I just now have confirmed that WFP does not appear to check the
checksum (crc, not checksum) of the file in the dllcache folder to see
whether it
has been altered by a local or remote attacker or a virus or worm, so
this would
appear to be a security issue.] ( a weakness and it WILL be our death)
(reviewers note: checksum is useless technology, CRC ! ok?)
food for thought:
After reading a 1000 documents on Best Practices and the Doing them.
Then why are you not using LINUX?
that is the real question ( is it only fear of the unknown)?
Links:
http://groups-beta.google.com/group/microsoft.public.windowsxp.setup_deployment/b
rowse_frm/thread/452843f86a37bcbc/fd4210a02427445f?q=WPF+++Windows+XP&_done=%2Fgr
oups%3Fhl%3Den%26q%3DWPF+++Windows+XP%26qt_s%3DSearch+Groups%26&_doneTitle=Back+t
o+Search&&d#fd4210a02427445f
http://www.systemexperts.com/tutors/HardenW2K101.pdf
http://securityadmin.info/faq.htm#harden
http://www.nsa.gov/ < look for security templates.
conclusion:
Windows is doomed to its present design and as such , the WFP is the
only hope.
so , how can we make WFP bullet proof. ?
Now that will be worth spending some time on.