Where results make sense

About us   |   Why use us?   |   Reviews   |   PR   |   Contact us

Topic: Stack-smashing protection

    Note: these results are not from the primary (high quality) database.

Stack-smashing protection - Wikipedia, the free encyclopedia Typically, stack-smashing protection modifies the organization of data in the stack frame of a function call to include a "canary" value which, when destroyed, shows that a buffer preceding it in memory has been overflowed. As such, it is possible for the protection to alter the structure of the data on the stack frame. A stack frame is built from the end of memory to the beginning; and each stack frame is placed on the top of the stack, closest to the beginning of memory. en.wikipedia.org /wiki/Stack_smashing   (1697 words)

Debian SbD: Stack Smash Protection Protecting from Stack Smashing Attacks is an article written by the creator(s) of ProPolice about Stack Smash Protection. Stack Smash Protection, or ProPolice, is a patch to gcc which allows the -fstack-protector switch to be used to protect stack-based buffers. In this scenario, the -fno-stack-protector switch must be used to build a source file without SSP. d-sbd.alioth.debian.org /www?page=ssp   (708 words)

Return-to-libc attack - Wikipedia, the free encyclopedia Stack-smashing protection can prevent or obstruct exploitation, as it can detect the corruption of the stack. A non-executable stack can prevent some buffer overflows, but not a return-to-libc attack: only existing, executable code is used. A return-to-libc attack is a computer security attack usually starting with a buffer overflow, in which the return address on the stack is replaced by the address of another function in the program. en.wikipedia.org /wiki/Return-to-libc_attack   (163 words)

.:[ packet storm ]:. - http://packetstormsecurity.org/ Stack smashing attacks are the most common form of security vulnerability. StackGuard is a compiler approach for defending programs and systems against "stack smashing" attacks, the most common form of security vulnerability. StackGuard is a compiler approach for defending programs and systems against "stack smashing" attacks. packetstormsecurity.nl /UNIX/utilities/stackguard   (335 words)

Gentoo Linux Documentation -- Introduction to Hardened Gentoo SSP is entirely implemented in userland and protects against stack smashing attacks without the assistance of the kernel. SSP protects against stack smashing by allocating an area outside of buffers and putting a random, cryptographic canary (or marker) in it. This allows SSP to check whether the canary was overwritten after any write to the buffer and allows it to kill the app if it was overwritten. www.gentoo.org /proj/en/hardened/primer.xml   (1238 words)

Buffer overflow - Stack-smashing protection is used to detect the most common buffer overflows by checking that the stack has not been altered when a function returns. C and C++ provide no protection against accessing or overwriting data in any part of memory through invalid pointers; more specifically, they do not check that data written to an array (the implementation of a buffer) is within the assumed boundaries of that array. For example the stack memory region, where data can be temporarily "pushed" onto the "top" of the stack, and later "popped" to read the value of the variable. psychcentral.com /psypsych/Buffer_overflow   (2140 words)

GCC extension for protecting applications from stack-smashing attacks SSP Transforms a program to meet the "ideal stack layout" as much as possible. The protection is realized by buffer overflow detection and the variable reordering feature to avoid the corruption of pointers. Applications written in C will be protected by the method that automatically inserts protection code into an application at compilation time. www.trl.ibm.com /projects/security/ssp   (342 words)

11th Annual USENIX Security Symposium — Technical Paper Techniques for stack smashing protection by keeping copies of the actual return addresses in an area inaccessible to the application are also proposed in StackGhost [14] and in the compiler patch StackShield [26]. This protection comes at the low cost of two extra instructions per function call, but its additional value is hard to determine due to the already limited applicability of this kind of exploit. Rather than attempt to stop a multitude of attack paths, where the protection is only as powerful as the weakest link, our approach is to prevent the execution of malicious code. www.usenix.org /publications/library/proceedings/sec02/full_papers/kiriansky/kiriansky_html   (8375 words)

Stack Shield Stack Shield is a tool for adding protection to programs from this kind of attacks at compile time whitout changing a line of code. The "stack smashing" technique is the most common way used in exploits to break the security of programs. Stack Shield is designed to support the GCC under a Linux Intel 386 class platform. www.angelfire.com /sk/stackshield   (137 words)

Dr. Dobb's Memory Matters December 15, 2005 The textbook heap and stack implementation puts the two at opposite ends of a common storage block with the heap growing up from the lowest address, and the stack growing down from the highest. Stack segments became a specialized data segment, with the ability to grow downward rather than upward. The lesson to be drawn from all this resembles the lessons found in copy protection, digital-rights management, and Trusted Computing: The attackers are at least as smart as you are, they have better tools, and they will find a way around whatever technological measures you put in place. www.ddj.com /dept/64bit/184406443   (2811 words)

Securiteam: [NEWS] Multiple Vulnerabilities in Stack Smashing Protection Technologies stack based buffer overflows on stack protected programs is presented. protections, the first one is an extension of that described in the "Stack shielding" software has been developed on the promise of preventing www.derkeiler.com /Mailing-Lists/Securiteam/2002-04/0115.html   (2014 words)

OpenBSD - LearnThis.Info Enclyclopedia As of version 3.3, ProPolice has been enabled by default in GCC, providing additional protection against stack smashing attacks. W^X (pronounced: "W xor X") is a fine-grained memory management scheme ensuring that memory is either writable, or executable, but never both, providing yet another layer of protection against buffer overflows. Systrace can now be used to protect the system while building ports. encyclopedia.learnthis.info /o/op/openbsd.html   (592 words)

Building FreeBSD 5.4 or 6.0 with Propolice An executable is protected when you see __stack_smash_handler with strings. NOTE: The executables will only be protected when compiled with a propolice-gcc so dont use precompiled packages/distributions. SSP gives the program a kill SIGABORT (signal 6). www.paranoid.nl /~eilander/freebsd/propolice   (264 words)

Stack-Protector.txt These are -fstack-protector to enable the stack protection, and -fno-stack-protector (default behavior) to explicitly disable the protection. ProPolice is a GCC extension for protecting from stack-smashing attacks. If glibc 2.3.1 is built with stack protection, portage's sandbox will break, and you will no longer be able to emerge packages. www.d-axel.dk /pub/mydesk/Stack-Protector.txt   (1068 words)

Re: machine independent protection from stack-smashing attack Prev by thread: machine independent protection from stack-smashing attack Subject: Re: machine independent protection from stack-smashing attack Nonetheless, we don't think this is such a horrible way to break the standard, given the protection it affords and the rarity of programs that rely on this behavior. cert.uni-stuttgart.de /archive/bugtraq/2000/08/msg00176.html   (740 words)

Debian Developer : Steve Kemp [skx] ~ ProPolice / SSP Packages One of my recent interests has been inproving the security of packages contained in the Debian distribution by rebuilding them with a compiler which includes built in stack smashing protection. There are several different versions of bound-checking and stack protection available for the GNU Compiler Collection, but the SSP patches seem to be combine simplicity, portablity and reliability. It's worth noting that the future of the SSP patches seems to be a little uncertain, as the upstream developers of GCC seem to be moving towards using a different type of bounds-checking called mudflap in their next releases. people.debian.org /~skx/ssp.html   (223 words)

ISS X-Force Database: stack-protection-frame-pointers(8982): Multiple "stack protection" programs fail to protect frame pointers Multiple "stack protection" programs fail to protect frame pointers, which could allow a remote attacker to execute arbitrary code on the system. StackGuard's "terminator canary" is a protection mechanism that prevents an attacker from overwriting the return address. ISS X-Force Database: stack-protection-frame-pointers(8982): Multiple "stack protection" programs fail to protect frame pointers xforce.iss.net /xforce/xfdb/8982   (319 words)

OpenBSD: Stack-Smashing Protection It is now simply referred to as the "stack-smashing protector", being a highly portable GCC extension that 1) reorders variables to prevent pointer corruption, and 2) inserts protection code into an application at compilation time to detect buffer overflows, preventing such bugs from being exploited. The buffer overflow protection portion of Hiroaki's GCC extension is based on StackGuard. And it goes further: we've got stack smash protected install floppies! kerneltrap.org /node/516   (1367 words)

Stack Shield A "stack smashing" technique protection tool for Linux The system configuration required to compile and run Stack Shield is an Intel 386 or highter CPU and the Linux operating system with the Gnu C Compiler (GCC). Added options to exit on attacks and to disable protection system when too much calls are executed. www.angelfire.com /sk/stackshield/download.html   (84 words)

Server attacks Some of the buffer overflows were found on static variables, which are not protected by stack protection mechanisms. Stackguard is a gcc variant which can protect programs from stack-smashing attacks, programs compiled using Stackguard dies without executing the stack code. Libsafe implements a 'middleware' layer which sits between the OS and the daemon process and protects against buffer overflows. users.ev1.net /~starfan/howto/proftpd/x293.html   (274 words)

Debian Administration :: Adding stack smashing protection to GCC v3.4 One of the most tested and widely used is a patch from IBM which is known as SSP, (for "Stack Smashing Protection"). When it comes to buffer overflow protection there are a couple of different implementations which are available. The best way to see this working is to use it to compile something with and without the protection, and see how they compare. www.debian-administration.org /articles/76   (1334 words)

Re: gcc 4.1 with stack smashing protection in etch? Previous by thread: gcc 4.1 with stack smashing protection in etch? Let's see what SSP breaks in terms of old code _first_ :) > It seems that Redhat will release RHEL 5 in the end of > 2006 with a gcc 4.1 compiler. Let's see it first :) There is currently a transition going on to get GCC 4.0x as the default compiler across all architectures that Debian supports. lists.debian.org /debian-gcc/2005/10/msg00307.html   (370 words)

smashing - OneLook Dictionary Search Phrases that include smashing: stack smashing, plate smashing, stack smashing protection, stack smashing protector, the smashing pumkins Words similar to smashing: bang-up, bully, cool, corking, cracking, dandy, great, groovy, keen, neat, nifty, peachy, shattering, slap-up, smash, smashingly, swell, not bad, more... Smashing : Online Plain Text English Dictionary [home, info] www.onelook.com /?w=smashing   (237 words)

OSGalaxy Right now I simply disable the stack protection on the whole libc, that is non optimal. I’ll be also rebuilding it with hardened compiler, as I want to test stack protection and hardened that box a bit. The implementation is still lousy, SSP is disabled for the whole libc, and the canary is not random, but I’ll focus on that more tomorrow. osgalaxy.com /v2/index.php/tag/gentooenglishgentoofreebsdsspgcc   (537 words)

bugtraq: Re: CORE-20020409: Multiple vulnerabilities in stack s Maybe in reply to: Iván Arce: "CORE-20020409: Multiple vulnerabilities in stack smashing protection technologies" Re: CORE-20020409: Multiple vulnerabilities in stack smashing protection technologies The MS /GS switch has an equally fatal flaw in its stack www.dataguard.no /bugtraq/2002_1/1520.html   (229 words)

Richard Henderson - [rfc] reimplementation of ibm stack-smashing protector The following is a functional re-implementation of the IBM stack smashing protection patch described here: http://www.research.ibm.com/trl/projects/security/ssp/ This version is *much* less intrusive than the IBM version: Makefile.in Instead I layout all variables up front (easy with tree-ssa) and require that new stack slots be placed at lower addresses. Which does mean that FRAME_GROWS_DOWNWARD must be defined by the target in order for this pass to be enabled. gcc.gnu.org /ml/gcc-patches/2005-05/msg01193.html   (363 words)

2CPU.com - The one stop source for everything SMP! Presumably then this exploit wouldn't be an issue on _any_ operating system built with stack-smashing protection, such as Gentoo Linux? Well I just meant that you wouldn't be able to execute arbitrary code if your stack wasn't executable in the first place, which is what I understand the x86+NX version of windows does by default, which is why a whole bunch of programs break. That is, regardless of whether or not the NX bit is in use, XP SP2 does not suffer any problems. www.2cpu.com /story.php?id=3270   (1146 words)

Stack protection bypass in multiple systems - information security, vulnerabilities, bugs, PoCs and IT security news CORE, CORE-20020409: Multiple vulnerabilities in stack smashing protection technologies (25.04.2002) Stack protection bypass in multiple systems - information security, vulnerabilities, bugs, PoCs and IT security news Article describes multiple exploitation techniques for different protection methods. www.security.nnov.ru /news1967.html   (58 words)

GCC extensions - GNU Project - Free Software Foundation (FSF) ProPolice automatically inserts stack-smashing protection code into an application at compile time to detect buffer overflow and corruption of pointers. In this section you will find extensions which do not (directly) apply to current GCC sources but are of historical interest or may be helpful to consult for future development. Here is a compilation and execution of an example program. www.gnu.org /software/gcc/extensions.html   (351 words)

Try your search on: Qwika (all wikis)

About us   |   Why use us?   |   Reviews   |   Press   |   Contact us   Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.