A Windows Vista forum. Vista Banter

Welcome to Vista Banter.

You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

If you have any problems with the registration process or your account login, please contact contact support.

Go Back   Home » Vista Banter forum » Microsoft Windows Vista » Security and Windows Vista
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Security and Windows Vista A forum for discussion on security issues with Windows Vista. (microsoft.public.windows.vista.security)

Doesn't this example violate Mandatory Integrity Control?



 
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old September 27th 06, 12:04 AM posted to microsoft.public.windows.vista.security
Walter Porter
external usenet poster
 
Posts: 12
Default Doesn't this example violate Mandatory Integrity Control?

Hello:

Scenario:
1) Launch notepad.exe with High MIC label, create file, close file.
2) Launch notepad.exe with Medium MIC label, edit that same file, save the
changes successfully.

Isn't this a violation of the purpose of mandatory integrity control? A
process with a lower label (Medium) is successfully editing a file created
and saved by another process with a higher label (High)?

I'm not certain, but I swear this wasn't possible with earlier builds of
Vista... :-\

Any insight will be greatly appreciated!

Thanks!



  #2 (permalink)  
Old October 4th 06, 12:43 PM posted to microsoft.public.windows.vista.security
Jimmy Brush
external usenet poster
 
Posts: 827
Default Doesn't this example violate Mandatory Integrity Control?

Hello,

I may be wrong on this, but I think the object integrity value is controlled
thru the object permissions heirarchy. When a process is running, it can
only write to objects/containers that have an equal or lesser integrity
value than what it is assigned, but when it creates an object I believe that
object inherits the MIC value from the container, unless explicitly set.

This would explain the behavior in your example, as the file you created
most likely would have been set to the NORMAL integrity value, which is
writable from both admin and non-admin processes.

--
- JB

Windows Vista Support Faq
http://www.jimmah.com/vista/

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 05:28 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.Search Engine Optimization by vBSEO 3.0.0 RC6
Copyright ©2004-2012 Vista Banter.
The comments are property of their posters.