Search Results for "buffer overflow attack"
Sort By:
Showing 6 open source projects for "buffer overflow attack"
View related business solutions-
Create stunning, professional email signatures in minutesCreate, assign and manage all your employees’ email signatures and add targeted marketing banners. Stop getting worked up about your signatures! Leverage a centralized interface to easily create and manage the email signatures of all your employees. Take advantage of each email to broadcast and amplify your brand. Letsignit helps you regain control over your digital identity. Harmonize 100% of your employee’s email signatures in just a few clicks! 121 professional emails are received and 40 are sent every day by an employee. With Letsignit, turn every email into a powerful communication opportunity: send the right message to the right person at the right time! Innovative more than tech, inspiring more than following. Authentic more than overrated, close more than "think big", trustworthy more than doubtful. Hands-on more than complex, available but yet premium, fun but yet expert.
-
Windocks - Docker Oracle and SQL Server ContainersWindocks is a leader in cloud native database DevOps, recognized by Gartner as a Cool Vendor, and as an innovator by Bloor research in Test Data Management. Novartis, DriveTime, American Family Insurance, and other enterprises rely on Windocks for on-demand database environments for development, testing, and DevOps. Windocks software is easily downloaded for evaluation on standard Linux and Windows servers, for use on-premises or cloud, and for data delivery of SQL Server, Oracle, PostgreSQL, and MySQL to Docker containers or conventional database instances.
-
1
HackSys Extreme Vulnerable Driver
HackSys Extreme Vulnerable Driver (HEVD) - Windows & Linux
The HackSys Extreme Vulnerable Driver (HEVD) is a Windows Kernel driver that is intentionally vulnerable. It has been developed for security researchers and enthusiasts to improve their skills in kernel-level exploitation. HEVD offers a range of vulnerabilities, from simple stack buffer overflows to more complex issues such as use-after-free, pool buffer overflows, and race conditions. This allows researchers to explore exploitation techniques for each implemented vulnerability. -
2
test-tlb
Stupid memory latency and TLB tester
test-tlb is a tiny C microbenchmark that explores the performance characteristics of memory access patterns with respect to the CPU’s Translation Lookaside Buffer (TLB) and caches. It walks arrays using different strides and working-set sizes so you can observe when access patterns overflow cache or TLB capacity. By timing tight loops and varying parameters, the program reveals step-changes in latency that map to cache lines, page sizes, and TLB coverage. It is intentionally minimal so you can modify page sizes, strides, or pointer-chasing strategies to run experiments on different machines and kernels. ... -
3
String object manipulation library for C language - Objet de gestion de chaînes de caractères pour le langage C
-
4
An alternative to the string library for C and C++ which is more functional and does not have buffer overflow problems.
-
Queue Management System for Busy Service Providers | WaitWellThe queue management system that perfectly adapts to your workflows. Improve operational efficiency in weeks with the most configurable enterprise queue system.
-
5
boef
Buffer Overflow Exploitation Framework
-
6
Hardware Memory Checker
Hardware Memory Checker
...It uses the memory paging system to allocate a guard page after each page of memory to provide a hardware boundary that can detect memory overflows. This allows for immediate detection of buffer overflow error conditions. There are many other memory checker programs in existence - why do we need another? This Hardware Memory Checker provides a combination of features not found in other memory checkers. - it uses the hardware paging system for immediate error detection (most other memory checkers look for modified memory in no mans land) - it is very fast compared to other hardware memory checkers because it makes fewer changes to the paging tables - it can track the original release location when debugging duplicate free problems - it is designed for large scale integration with the ability to call user defined fail functions
- Previous
- You're on page 1
- Next
