• Follow us on Twitter @buckeyeplanet and @bp_recruiting, like us on Facebook! Enjoy a post or article, recommend it to others! BP is only as strong as its community, and we only promote by word of mouth, so share away!
  • Consider registering! Fewer and higher quality ads, no emails you don't want, access to all the forums, download game torrents, private messages, polls, Sportsbook, etc. Even if you just want to lurk, there are a lot of good reasons to register!

gregorylee

I'd rather be napping!!
If you haven't already installed this one, you might want to hold off. It is currently in the process of blowing up some of our SAP applications.

In some cases it throws "memory write" errors, others it gives generic "Internet Explorer has encountered a problem" errors, and sometimes it just closes IE without warning, but in all cases with or without the errors it closes the IE session in which you are trying to work. I hate IE almost as much as I hate SAP. (Fucking Krauts).

I will add, that it only seems to be screwing up the older XPSP1 boxes. All the server 2003 sp1 and XPSP2 boxes seem to be fine. We are unfortunately still in process of upgrading the client systems...
 
The only things that it really seems to have affected for us (so far) have been some of the SAP functions, which are unfortunately key to our functional staff performing thier jobs. That is probably why our patch (WSUS) test group didn't show any problems with it. Unfortunately, it consists of technical people, hopefully after this we can get a few of the functionals out on the floor into the group as well so this might not happen again.
 
Upvote 0
Just as an FYI...

http://support.microsoft.com/default.aspx/kb/923762/en-us

Internet Explorer 6 Service Pack 1 unexpectedly exits after you install the 918899 update


and talk about an every sixth Tuesday of the month bunch of things that have to happen to break shit...

SYMPTOMS
Consider the following scenario. You run Microsoft Internet Explorer 6 Service Pack 1 (SP1) on a computer that is running Microsoft Windows XP with Service Pack (SP1) or Microsoft Windows 2000 with Service Pack 4 (SP4). You install the Internet Explorer cumulative security update that is documented in Microsoft Knowledge Base article 918899. In this scenario, Internet Explorer unexpectedly exits when you view a Web site that uses the HTTP 1.1 protocol and compression.


I know for a fact that the SAP site I was talking about did meet each criteria except "compression"... I guess now I know it meets that one too.
 
Upvote 0
IE Patch Intros New Exploitable Vulnerability
August 23, 2006

By Ryan Naraine, eWEEK

On the same day Microsoft is expected to re-release an Internet Explorer security update, a private security research outfit is warning that the original patch actually introduced an exploitable vulnerability.

The new warning comes less than a week after Microsoft offered a private hotfix for the browser because of a glitch that caused unexpected crashes.

However, according to an advisory from eEye Digital Security, the browser crash could cause a "high risk" buffer overflow that could lead to code execution attacks.

"After investigating and confirming that indeed this is an exploitable condition, we are alerting people to the true severity of these 'crashing' problems that people are experiencing, so that they can take the appropriate mitigation steps as need be," said Marc Maiffret, chief hacking officer at eEye, in Aliso Viejo, Calif.

Microsoft confirmed eEye's new discovery and said the updated IE patch would be delayed indefinitely.

"Due to an issue discovered in final testing that impacts a customer's ability to broadly deploy the update, Microsoft will not be re-releasing MS06-042 today [Aug. 22]," a company spokesperson said in a statement sent to eWEEK.

Microsoft also posted a security advisory that pinpointed the issue as "long URLs to sites using HTTP 1.1 and compression."

The company also chided eEye for going public with its findings before a comprehensive fix could be made available.

However, Maiffret noted that his company's warning never included any details that could point to the cause of the bug.

Instead, he noted that Microsoft's advisory mentions "long URLs" as the cause.

"We never mentioned 'long URLs' publicly anywhere because we did not want to release any details," Maiffret said, pointing out that Microsoft has released more information on the bug than anyone else.

Maiffret said the exploitable flaw affects Windows 2000 with IE6 SP1 and MS06-042 hotfix installed; and Windows XP SP1 with IE6 SP1 and MS06-042 hotfix installed.

The original patches were shipped as part of the MS06-042 cumulative security update for Internet Explorer, but immediately after the release of the patch on Aug. 8, IE users complained that the browser was crashing when viewing certain Web sites.

On Aug. 11, Microsoft acknowledged the browser crash issues with a knowledge base article and said it was only happening on Web sites using the HTTP 1.1 protocol and compression.

A hotfix was offered to businesses through Microsoft's PSS (Product Support Services), and the company said it would re-release the full IE update on Aug. 22.

According to eEye's Maiffret, the new exploitable issue is already known in research circles and exploit writers.

"[It] is important that IT administrators understand the true threat of this problem, that this is not simply a crashing bug as Microsoft has been incorrectly misrepresenting it, but in fact that it is an exploitable security bug," he said.

"Researchers and exploit developers know this, therefore it is extremely important that IT administrators are told what really is going on," he added.

Maiffret recommends that affected IE users disable HTTP 1.1 functionality in the browser.

He also suggested that Windows users upgrade to Windows XP SP2 (Service Pack 2) to protect against the vulnerability.

Public support for Windows XP SP1 ends in October 2006.



:slappy:
 
Upvote 0
Back
Top