未加星标

Mitigating Buffer Overflow Attacks in Linux/Unix

字体大小 | |
[系统(linux) 所属分类 系统(linux) | 发布者 店小二05 | 时间 2018 | 作者 红领巾 ] 0人收藏点击收藏

A buffer overflow is the most common and the most serious threat to linux/Unix operating systems. Buffer overflows occur when code running in unprotected memory in a buffer overwrites memory in an adjacent location. For example, a string of information, say 20 bytes, is sent to a 16-byte buffer, which can’t accommodate that string. Linux/Unix is written in C and there are memory-safety issues to consider, it could occur as a result of programming errors if memory boundary checking is inefficient or if boundary checking in a process isn’t present.

Buffer overflow becomes a security issue when an attacker manages to maliciously insert code into the memory of a running process, the attacker may then be able to acquire the privileges of that process. Generally buffer overflow is stack based where malicious code placed on a stack changes the return pointer and consequentially program flow, and heap based where overflowing buffers on lower parts of the heap result in unpredictable effects on the rest of the heap.

When trying to prevent buffer overflow, there are few preventative measures you can take. Of course, careful programming should ensure that attackers aren’t made aware of where privilege processes are running from. So analysis of source code for potential vulnerabilities is highly recommended. However, given that programmers are human, buffer overflows are always going to be a problem.

It’s important to disable stack execution and randomize stack location because this will make it more difficult for attackers to locate overflows and inject malicious code. When possible, if you are writing programs, use languages that have memory protection features, for example, Java or C#.

In C and C++, there are no automatic bounds checking on the buffer, which means a user can write past a buffer. For example:

int main () {

int buffer[10]; buffer[20] = 10;

}

The above C program is a valid program, and every compiler can compile it without any errors. However, the program attempts to write beyond the allocated memory for the buffer, which might result in unexpected behavior.

It’s always a good idea to perform runtime checking to ensure that buffer overflow isn’t occurring. In certain operating systems, you can enforce stack protection. With stack protection, you can modify your kernel to ensure that code only executes from areas of memory that you have cordoned off and locked. If a malicious user attempts to insert code into the stack-protected memory of a running process, the process will abort. Service will be denied, but the system won’t be compromised. The methods vary depending on the distribution of Linux/Unix or Linux that you are using.

本文系统(linux)相关术语:linux系统 鸟哥的linux私房菜 linux命令大全 linux操作系统

代码区博客精选文章
分页:12
转载请注明
本文标题:Mitigating Buffer Overflow Attacks in Linux/Unix
本站链接:https://www.codesec.net/view/611148.html


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 系统(linux) | 评论(0) | 阅读(69)