Threat Level: green Handler on Duty: Manuel Pelaez

SANS ISC InfoSec Handlers Diary Blog


Sign Up for Free!   Forgot Password?
Log In or Sign Up for Free!

Microsoft black Tuesday patches - April 2007

Published: 2007-04-10
Last Updated: 2007-04-11 11:14:05 UTC
by Swa Frantzen (Version: 2)
0 comment(s)

Overview of the April 2007 Microsoft patches and their status.


Note there was an out of cycle patch for the ANI vulnerability that we reported on earlier and that same patch is included here once again for completeness.

# Affected Contra Indications Known Exploits Microsoft rating ISC rating(*)
clients servers
MS07-017

rerun
-
out of cycle
Multiple vulnerabilities, leading to privilege escalation, DoS and remote code execution.
Replaces MS06-001 and MS05-053 and MS05-002 on windows 2003
Windows GDI.

CVE-2006-5758
CVE-2007-1211
CVE-2007-1212
CVE-2006-5586
CVE-2007-0038
CVE-2007-1215
CVE-2007-1213
KB 925902

Realtek HD audio control panel and more
Actively exploited

SA 935423
Critical PATCH NOW Important
MS07-018 Remote code execution and XSS scripting
MCMS (Microsoft Content Management Server)

CVE-2007-0938
CVE-2007-0939
KB 925939
No known exploits Critical Important Critical
MS07-019 Memory corruption leading to remote code execution
UPnP (Universal Plug and Play)

CVE-2007-1204
KB 931261
PoC available in for pay program
Critical Critical Critical(**)
MS07-020 URL parsing error leads to remote code execution
Microsoft Agent

CVE-2007-1205
KB 932168
No known exploits Critical Critical Important
MS07-021 Multiple vulnerabilities leading to remote Code execution, privilege escalation and DoS
CSRSS (Windows Client/Server Run-time Subsystem)

CVE-2006-6696
CVE-2007-1209
CVE-2006-6797
KB 930178
Known exploits since Dec 15th, 2006.

MSRC blog
Critical PATCH NOW Critical
MS07-022 Race conditions leading to privilege escalation
Windows Kernel

CVE-2007-1206
KB 931784
Details discussed publicly
Important Important Important

We will update issues on this page 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.
(**)Further clarification from the more generic text above: Windows XP is used in a server role (like it or not), just as Windows 2003 server is used on laptops. The difference between client and server is not how the OS is marketed, not even what it is best suited for, but how its users are using it.

--
Swa Frantzen -- NET2S

Keywords:
0 comment(s)

Mailbag

Published: 2007-04-10
Last Updated: 2007-04-10 22:54:58 UTC
by Swa Frantzen (Version: 1)
0 comment(s)
AOL's IM clients are getting attention from the security researchers: following ".." while deposing a file and/or not displaying the same filename as the actually used filename.
  • ICQ: should have updated itself by now, if not, make sure it did.
  • AIM: make sure to upgrade to the latest greatest
Several readers reported that Sun Java 6 update 1 is being released through automatic updates.

--
Swa Frantzen -- NET2S
Keywords:
0 comment(s)

Pump and Dump reporting

Published: 2007-04-10
Last Updated: 2007-04-10 20:35:07 UTC
by Swa Frantzen (Version: 1)
0 comment(s)
Pump and Dump spams are part of a financial fraud scheme. . Aside of the usual spam reporting one can also report the practice to the appropriate official contacts.

Due to the global nature of this spam one needs to have a list of which address to report to.

USA: SEC:
  • SEC wants your stock related spam
  • Forward the spam to enforcement(AT)sec.gov
  • You get a standardized reply for every report, typically during the next business day
Germany: Bafin
  • poststelle-ffm(AT)bafin.de
Australia: ASIC (oversight) and ASX (stock exchange)
  • ASIC has a form, way too impractical for dealing with individual spam messages
  • info(AT)asx.com.au

If you have confirmed and working responsive addresses for other stock exchanges, please let us know.

Links:
http://en.wikipedia.org/wiki/Pump_and_dump
http://www.sec.gov/complaint.shtml

Thanks to our readers Axel and more for reporting in on this.
--
Swa Frantzen -- NET2S
Keywords:
0 comment(s)
Diary Archives