Microsoft Releases Out-of-Band Advisory for all Versions of Internet Explorer, (Tue, Sep 17th)

 SANS Internet Storm Center, Security Alerts  Comments Off on Microsoft Releases Out-of-Band Advisory for all Versions of Internet Explorer, (Tue, Sep 17th)
Sep 172013
 

Microsoft just released an advisory on an Internet Explorer vulnerability that would allow for remote execution.  The report references public availability of details of his vulnerability.  The long story short, a targetted attack that gets a user to view a malicious webpage (or malicious content on an otherwise safe webpage) could lead to memory corruption that could execute arbitrary code with the permissions of the logged in user.  Two suggested actions are provided by Microsoft, apply the FixIt provided by Microsoft or deploy EMET 3.0/4.0 which provides generalized protection of memory (and probably not a bad idea to deploy anyway).  Note, the FixIt ONLY applies to 32-bit versions of Internet Explorer.

This post will be updated with more details as the situation warrants.


John Bambenek
bambenek \at\ gmail /dot/ com
Bambenek Consulting

(c) SANS Internet Storm Center. http://isc.sans.edu Creative Commons Attribution-Noncommercial 3.0 United States License.

Microsoft September 2013 Black Tuesday Overview, (Tue, Sep 10th)

 SANS Internet Storm Center, Security Alerts  Comments Off on Microsoft September 2013 Black Tuesday Overview, (Tue, Sep 10th)
Sep 102013
 

Overview of the September 2013 Microsoft patches and their status.

# Affected Contra Indications – KB Known Exploits Microsoft rating(**) ISC rating(*)
clients servers
MS13-067 A multitude of vulnerabilities in sharepoint (Office Server) have been fixed. It could lead to a Denial of Service over privilege escalation  to random code execution with the rights of the W3WP service account.
CVE-2013-1315 is also mentioned in MS13-073.
CVE-2013-3847, CVE-2013-3848, CVE-2013-3849, CVE-2013-3857 and CVE-2013-3858 are also mentioned in MS13-072.
Also contains functional changes for Visio Services.
Sharepoint

CVE-2013-0081
CVE-2013-1315
CVE-2013-1330
CVE-2013-3179
CVE-2013-3180
CVE-2013-3847
CVE-2013-3848
CVE-2013-3849
CVE-2013-3857
CVE-2013-3858

KB 2834052 CVE-2013-3180 was publicly disclosed. Severity:Critical
Exploitability:1
NA Critical
MS13-068 A input validation error dealign with S/MIME messages leads to random code execution with the rights of the logged on user. The vulnerability can be triggered by merely viewing or previewing a message.
Outlook

CVE-2013-3870

KB 2756473 No publicly known exploits Severity:Critical
Exploitability:2
Critical Important
MS13-069 A set of 10 new memory corruption vulnerabilities in this monthly instance of the cumulative MSIE patch. They lead to random code execution withthe rights of the logged on user.
MSIE

CVE-2013-3201
CVE-2013-3202
CVE-2013-3203
CVE-2013-3204
CVE-2013-3205
CVE-2013-3206
CVE-2013-3207
CVE-2013-3208
CVE-2013-3209
CVE-2013-3245

KB 2870699 No publicly known exploits Severity:Critical
Exploitability:1
Critical Important
MS13-070 A memory handling error in OLE allows for random code execution with the rights of the logged on user.
OLE

CVE-2013-3863

KB 2876217 No publicly known exploits Severity:Critical
Exploitability:1
Critical Important
MS13-071

A vulnerability in handling the theme files allows for random code execution with the rights of the logged on user.

Theme

CVE-2013-0810

KB 2864063 No publicly known exploits Severity:Important
Exploitability:1
Critical Important
MS13-072 Multiple vulnerabilities allow information leaks and random code execution with the rights of the logged on user.
CVE-2013-3847, CVE-2013-3848, CVE-2013-3849, CVE-2013-3857 and CVE-2013-3858 are also mentioned in MS13-067.
Office

CVE-2013-3160
CVE-2013-3847
CVE-2013-3848
CVE-2013-3849
CVE-2013-3850
CVE-2013-3851
CVE-2013-3852
CVE-2013-3853
CVE-2013-3854
CVE-2013-3855
CVE-2013-3856
CVE-2013-3857
CVE-2013-3858

KB 2845537 No publicly known exploits Severity:Important
Exploitability:1
Critical Important
MS13-073 Multiple vulnerabilities in Excel allow for information leak and random code execution with the rights of the logged on user.
CVE-2013-1315 is also mentioned in MS13-067.
Excel 

CVE-2013-1315
CVE-2013-3158
CVE-2013-3159

KB 2858300 No publicly known exploits Severity:Important
Exploitability:3
Critical Important
MS13-074 Multiple vulnerabilities allow random code execution with the rights of the logged on user.
Access

CVE-2013-3155
CVE-2013-3156
CVE-2013-3157

KB 2848637 No publicly known exploits Severity:Important
Exploitability:1
Critical Important
MS13-075 Pinyn Input Method Editor (IME) for Simplified Chinese allows for a privilege escalation by the user to local system. 
Office IME (Chinese)

CVE-2013-3859

KB 2878687 No publicly known exploits Severity:Important
Exploitability:1
Important Less urgent
MS13-076 Multiple memory corruption vulnerabilities allow privilege escalation. 
Kernel Mode Drivers

CVE-2013-1341
CVE-2013-1342
CVE-2013-1343
CVE-2013-1344
CVE-2013-3864
CVE-2013-3865
CVE-2013-3866

KB 2876315 No publicly known exploits Severity:Important
Exploitability:1
Important Less urgent
MS13-077 A double free vulnerability in the Service Control manager (SCM) allows privilege escalation.
Service Control Manager

CVE-2013-3862

KB 2872339 No publicly known exploits Severity:Important
Exploitability:2
Important Less Urgent
MS13-078

An information leak vulnerability in Frontpage while handling the DTD of an XML file.

Frontpage

CVE-2013-3137

KB 2825621 No publicly known exploits Severity:Important
Exploitability:3
Important Less Urgent
MS13-079 A Denial of Service vulnerability in Active Directory by a query to the LDAP service. Lasts till an administroator restarts the service.
Active Directory

CVE-2013-3868

KB 2853587 No publicly known exploits Severity:Important
Exploitability:3
NA Important
We will update issues on this page for about a week or so as they evolve.
We appreciate updates
US based customers can call Microsoft for free patch related support on 1-866-PCSAFETY
(*): ISC rating

  • 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.


Swa Frantzen

(c) SANS Internet Storm Center. http://isc.sans.edu Creative Commons Attribution-Noncommercial 3.0 United States License.

Microsoft July 2013 Black Tuesday Overview, (Tue, Jul 9th)

 SANS Internet Storm Center, Security Alerts  Comments Off on Microsoft July 2013 Black Tuesday Overview, (Tue, Jul 9th)
Jul 092013
 

Overview of the July 2013 Microsoft patches and their status.

# Affected Contra Indications – KB Known Exploits Microsoft rating(**) ISC rating(*)
clients servers
MS13-052 Multiple vulnerabilities allow privilege escalation and/or remote code execution. 
.NET & silverlight

CVE-2013-3129
CVE-2013-3131
CVE-2013-3132
CVE-2013-3133
CVE-2013-3134
CVE-2013-3171
CVE-2013-3178

KB 2861561 Microsoft claims CVE-2013-3131 and CVE-2013-3134 have been publicly disclosed. Severity:Critical
Exploitability:1
Critical Important
MS13-053 Multiple vulnerabilities allow privelege escalation and/or remote code execution.
kernel mode drivers (KMD)

CVE-2013-1300
CVE-2013-1340
CVE-2013-1345
CVE-2013-3129
CVE-2013-3167
CVE-2013-3172
CVE-2013-3173
CVE-2013-3660

KB 2850851 Microsoft claims CVE-2013-3172 and CVE-2013-3660 have been publicly disclosed. Moreover they claim to be aware of "targeted" attacks exploiting CVE-2013-3660. Severity:Critical
Exploitability:1
PATCH NOW Important
MS13-054 A truetype font parsing issue in the GDI+ library allows remote code execution. This affects a wide selection of sofware and extra care should be given to make sure to patch all instances.
GDI+

CVE-2013-3129

KB 2848295 No publicly known exploits. Severity:Critical
Exploitability:1
Critical Important
MS13-055 A multitude of vulnerabilities are fixed in this month's IE cumulative patch, you want this one. All but one are memory corruption vulnerabilities.
MSIE

CVE-2013-3115
CVE-2013-3143
CVE-2013-3144
CVE-2013-3145
CVE-2013-3146
CVE-2013-3147
CVE-2013-3148
CVE-2013-3149
CVE-2013-3150
CVE-2013-3151
CVE-2013-3152
CVE-2013-3153
CVE-2013-3161
CVE-2013-3162
CVE-2013-3163
CVE-2013-3164
CVE-2013-3166

KB 2846071 No publicly known exploits Severity:Critical
Exploitability:1
Critical Important
MS13-056 An input validation problem in how directShow handles GIF file allows random code execution.
DirectShow

CVE-2013-3174

KB 2845187 No publicly known exploits Severity:Critical
Exploitability:1
Critical Important
MS13-057 An input validation problem in windows media format (WMV – windows media player, not to be confused with the infamous WMF format) allows random code execution.
Media Player

CVE-2013-3127

KB 2847883 No publicly known exploits Severity:Critical
Exploitability:2
Critical Important
MS13-058 An unquoted path vulnerability (see more on what this is in Mark Bagget's excellent diary on the unquoted path issues) in windows defender allows privilege esclation to the localsystem account.
Windows defender

CVE-2013-3154

KB 2847927 No publicly known exploits Severity:Important
Exploitability:1
Important Important
We will update issues on this page for about a week or so as they evolve.
We appreciate updates
US based customers can call Microsoft for free patch related support on 1-866-PCSAFETY
(*): ISC rating

  • 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.


Swa Frantzen

(c) SANS Internet Storm Center. http://isc.sans.edu Creative Commons Attribution-Noncommercial 3.0 United States License.

Microsoft Internet Explorer CVE-2013-3147 Memory Corruption Vulnerability

 Security Alerts  Comments Off on Microsoft Internet Explorer CVE-2013-3147 Memory Corruption Vulnerability
Jul 082013
 

Type: Vulnerability. Microsoft Internet Explorer is prone to a memory-corruption vulnerability; fixes are available.

Microsoft June 2013 Black Tuesday Overview, (Tue, Jun 11th)

 SANS Internet Storm Center, Security Alerts  Comments Off on Microsoft June 2013 Black Tuesday Overview, (Tue, Jun 11th)
Jun 112013
 

Overview of the June 2013 Microsoft patches and their status.

# Affected Contra Indications – KB Known Exploits Microsoft rating(**) ISC rating(*)
clients servers
MS13-047 The usual monthly MSIE cumulative patch, adding fixes for a bunch more vulnerabilities. All but one are memory corruption vulnerabilities. The odd one is an information leak.
MSIE

CVE-2013-3110
CVE-2013-3111
CVE-2013-3112
CVE-2013-3113
CVE-2013-3114
CVE-2013-3116
CVE-2013-3117
CVE-2013-3118
CVE-2013-3119
CVE-2013-3120
CVE-2013-3121
CVE-2013-3122
CVE-2013-3123
CVE-2013-3124
CVE-2013-3125
CVE-2013-3139
CVE-2013-3141
CVE-2013-3142

KB 2838727 No publicly known exploits Severity:Critical
Exploitability:1
Critical Important
MS13-048 A kernel memory information leak vulnerability.
kernel

CVE-2013-3136

KB 2839229 No publicly known exploits Severity:Important
Exploitability:3
Important Less urgent
MS13-049 A vulnerability in the implementation of TCP/IP allows for a TCP connection to cause the system to stop responding.
TCP/IP

CVE-2013-3138

KB 2845690 No publicly known exploits. Severity:Important
Exploitability:3
Important Critical
MS13-050 Privilege excalation vulnerability when deleting a printer connection.
Print spooler

CVE-2013-3139

KB 2839894 No publicly known exploits Severity:Important
Exploitability:1
Important Important
MS13-051 A memory corruption vulnerability allows random code execution in the context of the current user due to failure to properly handle PNG images.
Note it also affects Office for Mac 2011.
Office

CVE-2013-1331

KB 2839571 Microsoft claim this is being exploited in "targeted attacks". Severity:Important
Exploitability:1
Critical Important
We will update issues on this page for about a week or so as they evolve.
We appreciate updates
US based customers can call Microsoft for free patch related support on 1-866-PCSAFETY
(*): ISC rating

  • 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.


Swa Frantzen — Section 66

(c) SANS Internet Storm Center. http://isc.sans.edu Creative Commons Attribution-Noncommercial 3.0 United States License.

%d bloggers like this: