Windows Vista Forums
Vista Forums Home Join Vista Forums Donate Vista Tutorials Tags

Welcome to Vista Forums we are your forum to discuss Windows Vista x64 and x86 systems. Whether you need help or just want to post an idea you have on Vista, this is the forum for you.
Register at Vista forums...the world biggest Windows Vista resource Join Vista Forums Now

Go Back   Vista Forums > Vista Newsgroups > Vista security

Doesn't this example violate Mandatory Integrity Control?

Closed Thread
 
Thread Tools Display Modes
Old 09-26-2006   #1 (permalink)
Walter Porter
Guest


 

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!



Old 10-04-2006   #2 (permalink)
Jimmy Brush
Guest


 

Re: 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/

Old 10-04-2006   #3 (permalink)
Jimmy Brush
Guest


 

Re: 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/

Closed Thread

Thread Tools
Display Modes


Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: Booting Vista from external drive violate MS EULA? Mark Conrad Vista General 2 4 Days Ago 03:36 PM
RE: Booting Vista from external drive violate MS EULA? Mick Murphy Vista General 2 2 Weeks Ago 08:22 AM
Code Integrity Errors Blackjaw System Security 1 03-16-2008 10:43 AM
How to elevate integrity level of a process Darshan Tilak Vista security 4 12-05-2007 03:43 AM
Mandatory Integrity Control (MIC) tools? Biba tools? Sharon2323 Vista security 1 08-04-2006 01:13 PM








Vistax64.com is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows Vista", the Start Orb, and related materials are trademarks of Microsoft Corp.
© Designer Media 2005-2008

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50