Data Portal @ linkeddatafragments.org

Matches in DBpedia 2014 for { <http://dbpedia.org/resource/Return-to-libc_attack> ?p ?o. }

• Return-to-libc_attack abstract "A return-to-libc attack is a computer security attack usually starting with a buffer overflow in which the return address on the call stack is replaced by the address of a function that is already loaded in the binary or via shared library. This allows attackers to defeat the Non-eXecutable stack protection - i.e. a page cannot be marked as write and executable at the same time. In fact, in this way the attacker simply calls preexisting functions without the need to inject malicious code into a program.The shared library called "libc" provides the C runtime on UNIX style systems. Although the attacker could make the code return anywhere, libc is the most likely target, as it is always linked to the program, and it provides useful calls for an attacker (such as the system call to execute an arbitrary program, which needs only one argument). This is why the exploit is called "return-to-libc" even when the return address may point to a completely different location.".
• Return-to-libc_attack wikiPageExternalLink return-to-libc.pdf.
• Return-to-libc_attack wikiPageID "846717".
• Return-to-libc_attack wikiPageRevisionID "606746611".
• Return-to-libc_attack hasPhotoCollection Return-to-libc_attack.
• Return-to-libc_attack subject Category:C_standard_library.
• Return-to-libc_attack subject Category:Computer_security_exploits.
• Return-to-libc_attack type Abstraction100002137.
• Return-to-libc_attack type Accomplishment100035189.
• Return-to-libc_attack type Act100030358.
• Return-to-libc_attack type Action100037396.
• Return-to-libc_attack type ComputerSecurityExploits.
• Return-to-libc_attack type Event100029378.
• Return-to-libc_attack type Feat100036762.
• Return-to-libc_attack type PsychologicalFeature100023100.
• Return-to-libc_attack type YagoPermanentlyLocatedEntity.
• Return-to-libc_attack comment "A return-to-libc attack is a computer security attack usually starting with a buffer overflow in which the return address on the call stack is replaced by the address of a function that is already loaded in the binary or via shared library. This allows attackers to defeat the Non-eXecutable stack protection - i.e. a page cannot be marked as write and executable at the same time.".
• Return-to-libc_attack label "Return into libc".
• Return-to-libc_attack label "Return-to-libc attack".
• Return-to-libc_attack label "Return-to-libc attack".
• Return-to-libc_attack label "Return-to-libc attack".
• Return-to-libc_attack label "Return-to-libc attack".
• Return-to-libc_attack label "Return-to-libc 攻击".
• Return-to-libc_attack label "Return-to-libc攻撃".
• Return-to-libc_attack label "Атака возврата в библиотеку".
• Return-to-libc_attack sameAs Return_into_libc.
• Return-to-libc_attack sameAs Return-to-libc_attack.
• Return-to-libc_attack sameAs Return-to-libc攻撃.
• Return-to-libc_attack sameAs Return-to-libc_attack.
• Return-to-libc_attack sameAs Return-to-libc_attack.
• Return-to-libc_attack sameAs m.03gmxj.
• Return-to-libc_attack sameAs Q13427559.
• Return-to-libc_attack sameAs Q13427559.
• Return-to-libc_attack sameAs Return-to-libc_attack.
• Return-to-libc_attack wasDerivedFrom Return-to-libc_attack?oldid=606746611.
• Return-to-libc_attack isPrimaryTopicOf Return-to-libc_attack.