adplus-dvertising
frame-decoration

Question

Which operating systems support nonexecutable memory?

a.

Windows XP Service Pack 1 and above

b.

Solaris 2.5 and above

c.

Linux kernel without any patches

d.

Windows XP Service Pack 2 and above, Solaris 2.6 and above, and several patches implemented for the Linux kernel

Posted under Reverse Engineering

Answer: (d).Windows XP Service Pack 2 and above, Solaris 2.6 and above, and several patches implemented for the Linux kernel Explanation:Windows XP Service Pack 2 and above, Solaris 2.6 and above, and several patches implemented for the Linux kernel support nonexecutable memory.

Engage with the Community - Add Your Comment

Confused About the Answer? Ask for Details Here.

Know the Explanation? Add it Here.

Q. Which operating systems support nonexecutable memory?

Similar Questions

Discover Related MCQs

Q. Does nonexecutable memory completely eliminate the problem of buffer overflow attacks?

Q. What is the most popular strategy for attackers to overcome the hurdles imposed by nonexecutable memory systems?

Q. Which option is used for returning values to the caller in functions?

Q. Which type of vulnerability is required for an attacker to exploit the buffer overflow bug?

Q. What is the purpose of stack-checking mechanisms embedded into programs?

Q. What is a heap overflow?

Q. How does a heap overflow attack work?

Q. How are heaps arranged?

Q. What causes the program to crash in a heap overflow attack?

Q. How can attackers take advantage of the heap's linked-list structure?

Q. Why are heap overflows less common than stack overflows?

Q. What is the most common example of overflow attacks?

Q. What is the risk of using the strcpy function?

Q. What are heap overflows and why are they less common than stack overflows?

Q. What is the most common example of string-related overflow attacks?

Q. What happens if an attacker's string is internally converted into Unicode before it reaches the vulnerable function?

Q. What are integer overflows?

Q. What is the risk associated with adding a constant value to a user-supplied buffer length?

Q. What happens if the addition performed on the buffer length parameter overflows?

Q. Why do stack variables always have a fixed size?