One Article Review
| Source |  Network World |
|---|---|
| Identifiant | 1175012 |
| Date de publication | 2019-06-26 08:08:00 (vue: 2019-06-26 18:01:08) |
| Titre | Tracking down library injections on Linux |
| Texte | While not nearly commonly seen on Linux systems, library (shared object files on Linux) injections are still a serious threat. On interviewing Jaime Blasco from AT&T's Alien Labs, I've become more aware of how easily some of these attacks are conducted.In this post, I'll cover one method of attack and some ways that it can be detected. I'll also provide some links that will provide more details on both attack methods and detection tools. First, a little background. [ Two-Minute Linux Tips: Learn how to master a host of Linux commands in these 2-minute video tutorials ] Shared library vulnerability Both DLL and .so files are shared library files that allow code (and sometimes data) to be shared by various processes. Commonly used code might be put into one of these files so that it can be reused rather than rewritten many times over for each process that requires it. This also facilitates management of commonly used code. |
| Envoyé | Oui |
| Condensat | alien allow also are article at&t attack attacks aware background become blasco both can click code commands commonly conducted cover data details detected detection dll down each easily facilitates files first from full here host how injections interviewing jaime labs learn library links linux little management many master method methods might minute more nearly not object one over please post process processes provide put rather read requires reused rewritten seen serious shared some sometimes systems than these threat times tips: tools tracking tutorials two used various video vulnerability ways will |
| Tags | |
| Stories | |
| Notes | |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.