Recent Posts

Showing posts with label Microsoft. Show all posts
Showing posts with label Microsoft. Show all posts

26 Windows, Office holes patched in 13 bulletins

Microsoft fixed 26 vulnerabilities in 13 security bulletins as part of its Patch Tuesday, including critical ones for Windows that could be exploited to take control of a computer and one that has resided in the 32-bit Windows kernel since its release 17 years ago.
The top priorities for deployment are bulletins plugging holes in the SMB (Server Message Block) Protocol, Windows Shell Handler, ActiveX via Internet Explorer, DirectShow, and the 32-bit version of Windows, Jerry Bryant, a lead senior security communications manager at Microsoft, wrote in a blog post.
The DirectShow bulletin should be at the top of the list, according to Bryant. It is critical for all supported versions of Windows except Itanium-based server products. To exploit the hole, an attacker could host a malicious AVI (Audio Video Interleave) file on a Web site, and lure a user to visit the site or send the file via e-mail so the user could open it.
In the SMB bulletin, critical for all versions of Windows except Vista and Server 2008, an attacker would need to host a malicious server and convince a client system to connect to it, or an attacker could try to perform a man-in-the-middle attack by responding to SMB requests from clients, Bryant said.
In the critical Windows Shell Handler vulnerability, which affects Windows 2000, XP, and Server 2003, an attack could come via a specially crafted link that appears to be valid to the ShellExecute API (application programming interface).
The cumulative update for ActiveX Killbits is critical, but a Killbit does not address the underlying vulnerability. It is a registry setting that keeps the vulnerable ActiveX control from running in IE.
The vulnerability affecting the 32-bit Windows kernel, which Microsoft announced last month, after Google engineer Tavis Ormandy disclosed it on a security e-mail list, could allow an attacker to elevate privileges to full system access, once the attacker is already in the system.
Much has been made of the fact that the hole is 17 years old, but Ormandy said he informed Microsoft about it in June 2009. "You can criticize them for taking a long time to fix a bug", but not if they didn't know about it, said Pedram Amini, who runs the Zero Day Initiative.
Microsoft is aware of publicly available proof-of-concept code for that issue, but is not aware of any active attacks at this time, Bryant wrote.
The most important bug for IT security teams is the one affecting DirectShow, said Andrew Storm, director of security compliance at security firm nCircle. "The nature of the exploit lends itself to drive-by attacks that leave unsuspecting victims infected," he said. "Since media is what excites people most on the Internet today, an exploit of this bug would make it extremely easy to entice users to watch videos that are actually gateways to malware."
Meanwhile, the Shell Handler vulnerability has the potential for an unlimited amount of damage, which should make potential attackers take notice, he said.
This month's "sleeper update" is probably a hole in Windows TCP/IP (Transmission Control Protocol-Internet Protocol) that could allow remote code execution if specially crafted packets were sent to a computer with IPv6 enabled, said HD Moore, chief security officer of Rapid7. "While it has an exploitability rating of 2 based on the requirement for an attacker to be on-link to the target host, Wi-Fi access points provide link level connectivity to target systems" he said. "Customers should not confuse the exploitability index with exposure severity--the priority of this patch should be raised where mobile users are prevalent."
Two bulletins, both rated "important", affect older versions of Microsoft Office and could allow an attacker to remotely execute code on the computer via a hole in PowerPoint or via a specially crafted Office file.
The bulletins affect Windows 2000, XP, Vista, and Windows 7, as well as Server 2003 and 2008, Office XP, Office 2003, and Office 2004 for Mac, according to the advisory.
Microsoft also issued a security advisory to provide a work-around for a publicly known hole in the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.
And Microsoft updated its Malicious Software Removal Tool to include the Win32/Pushbot, a worm that spreads via MSN Messenger and AIM, and opens a backdoor so an attacker can take complete control of the machine.
Microsoft is still working on patches for a hole disclosed last week in Internet Explorer that could lead to data leakage and an SMB hole that was disclosed in November.
"The [SMB] issue cannot be used to allow an attacker to take control of a system remotely, but instead can result in a system becoming unresponsive due to resource consumption," Microsoft said in a statement. "At this time, Microsoft is not aware of any attacks using this vulnerability."
READ MORE - 26 Windows, Office holes patched in 13 bulletins

Microsoft Windows 7 Review, System Requirements, Free Upgrades and more…


Microsoft Windows 7 is being launched today worldwide in keeping with their promise. It is a pleasant surprise for many of use to see Microsoft keeping their promise, considering their previous records and that their road was not always smooth. Windows 7 has already been launched in India, though availability in retail stores will be delayed due to customs / Income tax issues. Lenovo has rolled out PC's with Windows 7 today.
Today we will provide you with comprehensive list of articles on Windows 7:
  • Microsoft Windows 7 Review
  • Windows 7 System Requirements
  • Windows 7 Free Upgrade
  • Windows 7 Alternatives: MacOS X, Linux
  • Windows 7: To upgrade or not to upgrade
  • Windows 7 Hacks, Tips & Tricks

Microsoft Windows 7 reviews

Windows 7 Free Upgrade

Microsoft Windows 7 Alternatives

Windows 7: To upgrade or not to upgrade

So you want to upgrade to Windows 7? Here is a brief guide to upgrading to Windows 7.
However if you are not sure then here are top 10 reasons not to upgrade to Windows 7. Here is another article on why Windows 7 is good for new PC's but upgrading to Windows 7 for old computers may not make much sense.
On the other hand, Windows 7 with Intel processors may increase your laptop battery life by 50%.

Windows 7 Hacks, Secrets, Tips & Tricks

Miscellaneous Windows 7 articles

READ MORE - Microsoft Windows 7 Review, System Requirements, Free Upgrades and more…

No More Second Chances?

If cats have nine lives, Microsoft's Exam Retake offer has a feline nature as it's been revived countless times in the past. But that may change. Right now, the Microsoft Learning folks continue to remind us that those chances are running out soon. Microsoft's Exam Retake offer, need we remind you, concludes at the end of June. What this means to you right now is this:
  1. You must be registered into the program before May 31 if you're planning on taking an exam and then taking Microsoft up on their offer to retake (if you fail the first time, of course).
  2. If you have an exam retake voucher that you've yet to use, schedule that exam quick! All is lost after June 30.
  3. Your local testing center may be booked up, due to overwhelming demand. It happens and remember that it's your fault for waiting, not the testing center's problem. (I got your back, Prometric.)
Here's the kicker, though: Just because Microsoft has run this campaign in the past doesn't necessarily mean they'll do it again. Microsoft is feeling the economic pinch, so they're scrutinizing all internal decisions. Who knows if Exam Retake might finally get put to sleep forever? Really, it's anyone's guess.
If you need a subtle reminder to schedule your exam, watch this video. But let me warn you -- you may need some eye bleach. (I won't mention names, but thanks to the mysterious kr for the link.)
READ MORE - No More Second Chances?

Tools to monitor memory usage in Windows 7

Over the years, Microsoft has vastly improved the primitive Resource Meter and increasingly made it easier to see what is going on with the OS's use of memory.

Ever since I discovered how to use the Windows 9x's Resource Meter to keep track of system resources and prevent system crashes caused by depleting system resources when running more than one application at a time, I've made good use of Windows monitoring tools.
Over the years Microsoft has vastly improved the primitive Resource Meter and increasingly made it easier to see what is going on with the operating system's use of memory.
With Windows 7, I've discovered some slight, but notable, changes in the way that memory usage is reported on the Performance tab of the Task Manager. I have also noticed a very nice chart in the new Resource Monitor that provides very detailed information on physical memory usage at a glance.
In this issue of the Windows Vista and Windows 7 Report, I'll take a closer look at the changes on Task Manager's Performance tab and investigate the Physical Memory usage chart.
Note: Keep in mind that this is a Beta version and that the look and features of Windows 7 that I will discuss here may very well change between now and the time the operating system is actually released.
Taking a look back
To help you to appreciate the memory usage information in Windows 7 and to put the evolution of Windows resource monitoring into perspective, I thought I would begin by taking a quick look back at Windows 9x's Resource Meter. Once you have Resource Meter up and running, you can hover the mouse pointer over the icon and you will see a pop-up display that breaks down the amount of available system resources into its three categories: System, User, and GDI, as shown in Figure A.
Figure A

Hovering the mouse pointer over the Resource Meter icon produces a display of the currently available system resources in three categories.
If you double-click the icon, you will see the Resource Meter dialog box, shown in Figure B. As you can see, this display used three gas gauge-like monitors to show you the amount of available system resources in each category.
Figure B

The Resource Meter's display uses three gas gauge-like monitors to show you the amount of available system resources in each category.
Because resource management was horrible in the Windows 9x days, system crashes were inevitable. If you kept your eye on the Resource Meter icon, you could literally watch the amount of system resources depleted as you worked. As you can see in Figure C, the green bars would move down and change to yellow and then to red right before the system crashed.
Fiure C

This is the evolution of a system cgrash caused by the depletion of system resources.
The Task Manager Performance tab
When you compare the Performance tab in Windows 7's Task Manager to the one in Vista, as shown in Figure D, you'll notice a few changes in the statistics sections.
First, in the Physical Memory section, you'll see that there is now a measurement showing the amount of available memory. While in Vista you can easily deduce the amount of available memory by subtracting the Total value from the Cached value. It is nice to be able to tell at a glance just how much physical memory is currently available to the system.
Figure D

Comparing Vista's and 7's Performance tab reveals a few slight, but noteworthy, changes.
Of course, the Total entry shows the amount of RAM installed in the system. The Cached entry indicates the amount of physical memory used recently for system resources. (This memory will remain in the cache in case the system resources are needed again, but it's available should other operations need it.) The new Available entry indicates the amount of physical memory that is currently not being used. The Free entry indicates the amount of memory being used in the cache that does not contain useful information.
The Kernel Memory section now shows only the amount of Paged and Nonpaged memory. The Paged and Nonpaged entries break down the total amount of memory being used by the kernel and show you how much is coming from virtual memory and how much is coming from physical memory, respectively. The Total entry, which was essentially useless here, has been removed.
In the System section, you'll find the same measurements found in Vista; however, the Page File item has been renamed to Commit. (Windows XP called this same measurement the Commit Charge and dedicated an entire section to it.) This measurement still shows Page File usage. Here, the first number indicates the total amount of physical and virtual memory currently in use, while the second number indicates the total amount of physical and virtual memory available on your computer.
The Handles and Threads entries are rather obscure and are actually sub-objects of processes. The Handles entry shows the number of object identifiers, or handles, that are currently in use by all the running processes. The Threads entry actually refers to the number of subprocesses running inside larger processes. The Processes entry, of course, represents the number of currently running processes. As you know, you can see each of the currently running processes by selecting the Processes tab.
The Up Time entry is still a nice piece of information that shows the amount of time that has passed since the computer has been restarted.
The Resource Monitor Memory tab
To access the Resource Monitor, just click the button on the Performance tab in Windows 7's Task Manager. Then, select the Memory tab in the Resource Monitor. When you do, you'll see the newly revamped interface, shown in Figure E. While the three graphs on the side are a nice new feature and show regularly updated graphs, the Physical Memory usage chart is stunning in that it provides an extremely intuitive picture of memory usage.
Figure E

The Physical Memory usage chart provides a very easy to understand picture of memory usage.
If you do the math, you can see the chart accounts for every bit of memory installed in the system. Table A identifies each section of the chart. If you subtract the amount reserved for hardware, you get the Total. If you add the Standby and Free, you get the Available to Programs total.
Table A

Hardware Reserved Memory that is reserved for use by the BIOS and some drivers for other peripherals.
In Use Memory used by process working sets, drivers, nonpaged pools, and operating system functions.
Modified Memory whose contents must be to disk before it can be used for another purpose.
Standby Memory that contains cached data and code that is not actively in use.
Free Memory that does not contain any valuable data and that will be used first when processes or the operating system needs more memory.
Greg Shultz is a Documentation Specialist for MediaBank. Previously, he worked as technical journalist in the computer publishing industry.
READ MORE - Tools to monitor memory usage in Windows 7