what you don't know can hurt you
Home Files News &[SERVICES_TAB]About Contact Add New

ms02-064

ms02-064
Posted Oct 31, 2002

Microsoft Security Advisory MS02-064 - On Windows 2000, the default permissions provide the Everyone group with Full access on the system root folder (typically, C:\). In most cases, the system root is not in the search path. However, under certain conditions - for instance, during logon or when applications are invoked directly from the Windows desktop via Start | Run - it can be, allowing users to make trojans that other users execute.

tags | root, trojan
systems | windows
SHA-256 | 1216c825445c9a208c39bc93c9c94e146553beb71516ba0e00744b827f2d5645

ms02-064

Change Mirror Download
-----BEGIN PGP SIGNED MESSAGE-----

- ----------------------------------------------------------------------
Title: Windows 2000 Default Permissions Could Allow Trojan Horse
Program (Q327522)
Date: 30 October 2002
Software: Windows 2000
Impact: Trojan Horse program execution
Max Risk: Moderate
Bulletin: MS02-064

Microsoft encourages customers to review the Security Bulletin at:
http://www.microsoft.com/technet/security/bulletin/MS02-064.asp.
- ----------------------------------------------------------------------

Issue:
======
On Windows 2000, the default permissions provide the Everyone group
with Full access (Everyone:F) on the system root folder
(typically, C:\). In most cases, the system root is not in the search
path. However, under certain conditions - for instance, during logon
or when applications are invoked directly from the Windows desktop
via Start | Run - it can be.

This situation gives rise to a scenario that could enable an attacker
to mount a Trojan horse attack against other users of the same
system, by creating a program in the system root with the same name
as some commonly used program, then waiting for another user to
subsequently log onto the system and invoke the program. The Trojan
horse program would execute with the user's own privileges, thereby
enabling it to take any action that the user could take.

The simplest attack scenario would be one in which the attacker knew
that a particular system program was invoked by a logon script. In
that case, the attacker could create a Trojan horse with the same
name as the system program, which would then be executed by the
logon script the next time someone logged onto the system. Other
scenarios almost certainly would require significantly greater user
interaction - for instance, convincing a user to start a particular
program via Start | Run - and would necessitate the use of social
engineering.

The systems primarily at risk from this vulnerability would be
workstations that are shared between multiple users, and local
terminal server sessions. Other systems would be at significantly
less risk:

- Workstations that are not shared between users would be at no
risk, because the attacker would require the ability to log onto
the system in order to place the Trojan horse.

- Servers would be at no risk, if standard best practices have
been followed that advocate only allowing trusted users to log
onto them.

- Remote Terminal server sessions would be at little risk,
because each user's environment is isolated. That is, the system
root is never the current folder - instead, the user's Documents
and Settings folder is, but the permissions on this folder would
not enable an attacker to place a Trojan horse there.

Mitigating Factors:
====================
- An attacker would require the ability to log onto the system
interactively in order to place the Trojan horse program. It
could not be placed remotely

- As discussed above, dedicated workstations, servers and remote
terminal server sessions would be at less risk (or, in some cases,
none at all) from the vulnerability.

Risk Rating:
============
- Internet systems: Low
- Intranet systems: Low
- Client systems: Moderate

Patch Availability:
===================
- This vulnerability requires an administrative procedure rather
than a patch. The needed changes are discussed in the FAQ.
Please read the Security Bulletin at
http://www.microsoft.com/technet/security/bulletin/ms02-064.asp
for information on obtaining this patch.

Acknowledgment:
===============
- Jason Miller of Security Focus (http://www.securityfocus.com)

- ---------------------------------------------------------------------

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED
"AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL
WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT
SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY
DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.1

iQEVAwUBPcBlpY0ZSRQxA/UrAQG6NQf/XSZD58pgMpXoZsbu2axijUERbFI3Npq8
YF4gVOf8QTc5/OzZUobaYnTmGjpP2epfL+tNZ/Tj9H2pCD0f/JOE8GNfo03PPI6a
JcA1tbuifpTcf2IQc8NVm/7/Nvh+mSia32Q/LKMyPl/wOqwMHLc0vhlqKGAh+HRa
mfQH9MGBos6JrgZSj7pjvHN4+aD++jfo6Jg/v8jCqLHYL7iarNjwLygnyMfPx8Vs
agEMYDcNG7nk9WnY1vDnQtlWgBFYcgrWxNlnzRf7cadLCYnlrvJBEspROq1EF2Tx
LS4KbcoAUj/Eruf5/c/BMIt/YI536wTqaNWOy77SThcmnps8llmn0w==
=LepM
-----END PGP SIGNATURE-----

Login or Register to add favorites

File Archive:

March 2024

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Mar 1st
    16 Files
  • 2
    Mar 2nd
    0 Files
  • 3
    Mar 3rd
    0 Files
  • 4
    Mar 4th
    32 Files
  • 5
    Mar 5th
    28 Files
  • 6
    Mar 6th
    42 Files
  • 7
    Mar 7th
    17 Files
  • 8
    Mar 8th
    13 Files
  • 9
    Mar 9th
    0 Files
  • 10
    Mar 10th
    0 Files
  • 11
    Mar 11th
    15 Files
  • 12
    Mar 12th
    19 Files
  • 13
    Mar 13th
    21 Files
  • 14
    Mar 14th
    38 Files
  • 15
    Mar 15th
    15 Files
  • 16
    Mar 16th
    0 Files
  • 17
    Mar 17th
    0 Files
  • 18
    Mar 18th
    10 Files
  • 19
    Mar 19th
    32 Files
  • 20
    Mar 20th
    46 Files
  • 21
    Mar 21st
    16 Files
  • 22
    Mar 22nd
    13 Files
  • 23
    Mar 23rd
    0 Files
  • 24
    Mar 24th
    0 Files
  • 25
    Mar 25th
    12 Files
  • 26
    Mar 26th
    31 Files
  • 27
    Mar 27th
    19 Files
  • 28
    Mar 28th
    42 Files
  • 29
    Mar 29th
    0 Files
  • 30
    Mar 30th
    0 Files
  • 31
    Mar 31st
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2022 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close