Difference between revisions of "Libsafe"
(Created page with "{{Entry |Name=libsafe |Short description=Detects and handles buffer overflow attacks |Full description=The exploitation of buffer overflow and format string vulnerabilities in pr...") |
(Added Debian link) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 3: | Line 3: | ||
|Short description=Detects and handles buffer overflow attacks | |Short description=Detects and handles buffer overflow attacks | ||
|Full description=The exploitation of buffer overflow and format string vulnerabilities in process stacks are a significant portion of security attacks. 'libsafe' is based on a middleware software layer that intercepts all function calls made to library functions known to be vulnerable. A substitute version of the corresponding function implements the original function in a way that ensures that any buffer overflows are contained within the current stack frame, which prevents attackers from overwriting the return address and hijacking the control flow of a running program. The true benefit of using libsafe is protection against future attacks on programs not yet known to be vulnerable. The performance overhead of libsafe is negligible, it does not require changes to the OS, it works with existing binary programs, and it does not need access to the source code of defective programs, or recompilation or off-line processing of binaries. | |Full description=The exploitation of buffer overflow and format string vulnerabilities in process stacks are a significant portion of security attacks. 'libsafe' is based on a middleware software layer that intercepts all function calls made to library functions known to be vulnerable. A substitute version of the corresponding function implements the original function in a way that ensures that any buffer overflows are contained within the current stack frame, which prevents attackers from overwriting the return address and hijacking the control flow of a running program. The true benefit of using libsafe is protection against future attacks on programs not yet known to be vulnerable. The performance overhead of libsafe is negligible, it does not require changes to the OS, it works with existing binary programs, and it does not need access to the source code of defective programs, or recompilation or off-line processing of binaries. | ||
| + | |Homepage URL=https://github.com/tagatac/libsafe-CVE-2005-1125 | ||
|User level=none | |User level=none | ||
| − | |||
| − | |||
| − | |||
| − | |||
|Computer languages=C | |Computer languages=C | ||
| − | | | + | |Accepts cryptocurrency donations=No |
| − | |||
| − | |||
| − | |||
| − | |||
|Related projects=GMM,Mbuffer | |Related projects=GMM,Mbuffer | ||
|Keywords=security,Internet,buffer,overflow,buffer overflow,libsafe | |Keywords=security,Internet,buffer,overflow,buffer overflow,libsafe | ||
| − | | | + | |Version identifier=2.0-16 |
| − | | | + | |Version date=2002/05/21 |
| − | | | + | |Version status=historical |
| − | | | + | |Version download=https://github.com/tagatac/libsafe-CVE-2005-1125/blob/master/libsafe-2.0-16.tgz |
| + | |Last review by=Bendikker | ||
| + | |Last review date=2018/02/21 | ||
|Submitted date=2011-04-01 | |Submitted date=2011-04-01 | ||
| − | | | + | |Is GNU=No |
| − | | | + | |License verified date=2001-07-11 |
| − | | | + | }} |
| − | | | + | {{Project license |
| + | |License=LGPL | ||
| + | |License verified by=Janet Casey | ||
|License verified date=2001-07-11 | |License verified date=2001-07-11 | ||
| − | |||
}} | }} | ||
{{Person | {{Person | ||
|Role=Maintainer | |Role=Maintainer | ||
| − | + | }} | |
| − | | | + | {{Resource |
| − | |Resource URL= | + | |Resource audience=Debian (Ref) |
| + | |Resource URL=https://tracker.debian.org/pkg/libsafe | ||
}} | }} | ||
{{Resource | {{Resource | ||
| Line 44: | Line 41: | ||
|Use=security | |Use=security | ||
}} | }} | ||
| − | {{ | + | {{Featured}} |
| − | |||
| − | |||
| − | |||
| − | }} | ||
Latest revision as of 13:03, 21 February 2018
libsafe
https://github.com/tagatac/libsafe-CVE-2005-1125
Detects and handles buffer overflow attacks
The exploitation of buffer overflow and format string vulnerabilities in process stacks are a significant portion of security attacks. 'libsafe' is based on a middleware software layer that intercepts all function calls made to library functions known to be vulnerable. A substitute version of the corresponding function implements the original function in a way that ensures that any buffer overflows are contained within the current stack frame, which prevents attackers from overwriting the return address and hijacking the control flow of a running program. The true benefit of using libsafe is protection against future attacks on programs not yet known to be vulnerable. The performance overhead of libsafe is negligible, it does not require changes to the OS, it works with existing binary programs, and it does not need access to the source code of defective programs, or recompilation or off-line processing of binaries.
Licensing
License
Verified by
Verified on
Notes
Leaders and contributors
| Contact(s) | Role |
|---|---|
| Maintainer |
Resources and communication
| Audience | Resource type | URI |
|---|---|---|
| Debian (Ref) | https://tracker.debian.org/pkg/libsafe | |
| Developer,Support | mailto:libsafe@research.avayalabs.com |
Software prerequisites
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.