Introduction to Memory Analysis with Mandiant Redline
In a previous diary I talked about memory acqusition with Dumpit .in this diary I will talk about how to use Mandiant Redline to analysis the memory dump.[1]
Mandiant Redline:
“Redline, Mandiant’s premier free tool, provides host investigative capabilities to users to find signs of malicious activity through memory and file analysis, and the development of a threat assessment profile”.[2]
Installation:
1-Download Mandiant Redline from https://www.mandiant.com/resources/download/redline
2-Double click on Redline-1.11.msi
3-follow up the steps, then click close
Redline Usage:
To analysis a memory image :
1-Select From a Saved Memory File under Analyze Data on the home screen
2-Click Browse under Location of Saved Memory Image (for this diary I will not use an Indicators of Comporomise)
3-Click Next then OK
Depending on the size of the image and the speed of your PC, Mandiant Redline will take time to process the memory image.
4-For this example I am going to choose “I am reviewing A Full Live Response or Memory Image”
Now our Image is ready for Review:.jpg)
From the left hand side you can choose which type of Data you would like to analysis in this view it’s the “Processes”
Here you can find all the process which was running on the system when the memory image was acquired . It shows the full details about the process such as the Process ID,Path ,Arguemnts ,User name ,SID …etc .
If you would like to view the open ports on the System while the image was acquired , To view ports, click Ports under Processes on the Analysis Data window’s Host tab.
Microsoft Patch Tuesday March 2014
Overview of the March 2014 Microsoft patches and their status.
| # | Affected | Contra Indications - KB | Known Exploits | Microsoft rating(**) | ISC rating(*) | |
|---|---|---|---|---|---|---|
| clients | servers | |||||
| MS14-012 |
Cummulative Security Update for Internet Explorer (ReplacesMS14-010 ) |
|||||
|
Internet Explorer CVE-2014-0297 CVE-2014-0298 CVE-2014-0299 CVE-2014-0302 CVE-2014-0303 CVE-2014-0304 CVE-2014-0305 CVE-2014-0306 CVE-2014-0307 CVE-2014-0308 CVE-2014-0309 CVE-2014-0311 CVE-2014-0312 CVE-2014-0313 CVE-2014-0314 CVE-2014-0321 CVE-2014-0322 CVE-2014-0324 |
KB 2925418 | Yes! |
Severity:Critical Exploitability: 1 |
PATCH NOW! | Critical | |
| MS14-013 |
Remote Code Execution Vulnerability in Microsoft Direct Show (ReplacesMS13-056 ) |
|||||
|
Direct Show JPEG Library CVE-2014-0301 |
KB 2929961 | No. |
Severity:Critical Exploitability: 1 |
Critical | Important | |
| MS14-014 |
Vulnerability in Silverlight Could Allow Security Feature Bypass (ReplacesMS13-087 ) |
|||||
|
Silverlight CVE-2014-0319 |
KB 2932677 | No. |
Severity:Important Exploitability: 1 |
Important | Important | |
| MS14-015 |
Privilege Escalation Vulnerability in Windows Kernel-Mode Driver (ReplacesMS13-101 ) |
|||||
|
Windows Kernel-Mode Driver CVE-2014-0300 CVE-2014-0323 |
KB 2930275 | Yes. CVE-2014-0323 was public. |
Severity:Important Exploitability: 1 |
Important | Important | |
| MS14-016 |
Security Bypass Vulnerabilty in Security Account Manager Remote (SAMR) (ReplacesMS11-095 MS13-032 ) |
|||||
|
Security Account Manager Remote CVE-2014-0317 |
KB 2930275 | No. |
Severity:Important Exploitability: 1 |
Important | Important | |
We appreciate updates
US based customers can call Microsoft for free patch related support on 1-866-PCSAFETY
-
We use 4 levels:
- PATCH NOW: Typically used where we see immediate danger of exploitation. Typical environments will want to deploy these patches ASAP. Workarounds are typically not accepted by users or are not possible. This rating is often used when typical deployments make it vulnerable and exploits are being used or easy to obtain or make.
- Critical: Anything that needs little to become "interesting" for the dark side. Best approach is to test and deploy ASAP. Workarounds can give more time to test.
- Important: Things where more testing and other measures can help.
- Less Urgent: Typically we expect the impact if left unpatched to be not that big a deal in the short term. Do not forget them however.
- The difference between the client and server rating is based on how you use the affected machine. We take into account the typical client and server deployment in the usage of the machine and the common measures people typically have in place already. Measures we presume are simple best practices for servers such as not using outlook, MSIE, word etc. to do traditional office or leisure work.
- The rating is not a risk analysis as such. It is a rating of importance of the vulnerability and the perceived or even predicted threat for affected systems. The rating does not account for the number of affected systems there are. It is for an affected system in a typical worst-case role.
- Only the organization itself is in a position to do a full risk analysis involving the presence (or lack of) affected systems, the actually implemented measures, the impact on their operation and the value of the assets involved.
- All patches released by a vendor are important enough to have a close look if you use the affected systems. There is little incentive for vendors to publicize patches that do not have some form of risk to them.
(**): The exploitability rating we show is the worst of them all due to the too large number of ratings Microsoft assigns to some of the patches.
------
Johannes B. Ullrich, Ph.D.
SANS Technology Institute
Twitter
Adobe Updates: Flash Player
Adobe released a new version of Flash Player as part of today's patch Tuesday. No details are available yet. We will update this diary once the details become available. Note that this will also affect browsers like Chrome that include an embeded version of Flash.
------
Johannes B. Ullrich, Ph.D.
SANS Technology Institute
Twitter
Comments