assembly - Does each process has its own portion of utopia in the memory? -



assembly - Does each process has its own portion of utopia in the memory? -

by doing cat /proc/*some pid*/maps on multiple processes on machine, notice have same starting point in regards memory address, beingness 0x8048000. mean every process has "it's own memory space, including stack, heap etc." @ runtime?

and if so, how can attackers instance distinguish between memory address of 1 process another?

so if machine has 2gb of ram, , few processes running simultaneously - how can know memory address targeting? or getting wrong, , attack starts looking @ process , advancing there?

pardon beginner's question, getting assembly , reading 5 tutorials simultaneously , having bit of hard-time grasping level of understanding.

please note question set here , not in security since refer assembly side of things.

each process has own "virtual memory", stores own stack, heap, instructions, etc. each process can utilize entire 32/64-bit address space independently of other process. kernel manages mapping between each processes virtual memory , machine's physical ram. wikipedia covers in more detail.

most attacks target memory in 1 particular process. attackers utilize addresses address space of process targeting. observed, many executables load @ standard virtual addresses, making easier attackers predict memory layout of process.

memory assembly stack-overflow buffer-overflow

Comments

Popular posts from this blog

web services - java.lang.NoClassDefFoundError: Could not initialize class net.sf.cglib.proxy.Enhancer -

Accessing MATLAB's unicode strings from C -

javascript - mongodb won't find my schema method in nested container -