what you don't know can hurt you
Home Files News &[SERVICES_TAB]About Contact Add New

ms.smtp.DoS.txt

ms.smtp.DoS.txt
Posted Aug 17, 1999

Microsoft's SMTP service (v5.5.1877.977.9) launches Denial of Service attacks. No, this is not a joke, either. Read it. You can download consolation patches at Macroshaft

tags | exploit, denial of service
SHA-256 | afa8c84873e58b0ecc4bf80424693dc11975593de4616394a389bd2808e06d4d

ms.smtp.DoS.txt

Change Mirror Download
Date: Sun, 14 Mar 1999 20:49:30 -0600
From: Chris Adams <cadams@RO.COM>
To: BUGTRAQ@netspace.org
Subject: Microsoft's SMTP service broken/stupid

Our mail servers came to a screeching halt today thanks to Microsoft.
Our servers are still running sendmail 8.8 (we've got custom stuff and
are working on upgrading to 8.9, but it has been slow), so any kind of
DNS error (like invalid reverse DNS) returns a 4xx error - temporary
problem. When we get a message like this, the sending site will requeue
the message and try again in 30 minutes to an hour. After a bit, they
stop trying. It is not a perfect solution, but it is all that is
available under sendmail 8.8 (sendmail 8.9 differentiates between
temporary and permanent DNS errors).

Well, that has been fine, but now Microsoft's SMTP service comes along.
When it gets that temporary error (for invalid reverse DNS), it tries
again. Fast. Like, right away, with no delay. This bogs down our
servers a bit, especially the extra logging load, but eventually they go
away.

Yesterday, we got hit by four different servers running Microsoft's
software. One attempted delivery nearly 200,000 times, and the other
three attempted to 30,000-40,000 times each. This on a server that
usually sees ~40,000 messages a day. This filled up our logs, bogged
everything down, and basically killed us.

This is not a configuration issue AFAIK. In the past, I've worked
through it with one person, and he said he bumped up his retry time to 3
hours and his server was still attempting multiple deliveries per
second.

This basically amounts to a denial of service attack by Microsoft's SMTP
service. Here is the connect string from several of the servers that
hit us (I've changed the hostname):

220-example.com Microsoft SMTP MAIL ready at Sun, 14 Mar 1999 21:44:02 -0500 Version: 5.5.1877.977.9

I was able to connect to several of the SMTP servers that hit us and
they are all running this version. Several of them don't accept
incoming connections (gee thanks - send me junk and don't accept any
back).

I haven't been able to find anything at Microsoft about this. I would
think that attempting several outgoing connections per second would tend
to bog down the NT server as well, so I figured they might have
mentioned it. Has anybody else seen this?
--
Chris Adams - cadams@ro.com
System Administrator - Renaissance Internet Services
I don't speak for anybody but myself - that's enough trouble.

-------------------------------------------------------------------------------

Date: Wed, 17 Mar 1999 14:58:43 -0800
From: "David Lemson (Exchange)" <dlemson@EXCHANGE.MICROSOFT.COM>
To: BUGTRAQ@netspace.org
Subject: Re: Microsoft's SMTP service broken/stupid

We have confirmed this as a problem with the Microsoft SMTP Service, as
shipped in Windows NT 4 Service Pack 4. We are working on a fix and will
have it tested shortly. We will have a Knowledge Base article created as
soon as the fix is ready so that people can find the fix when they run into
the problem. Any Microsoft customer who is hitting this problem (such as
the people whose servers are connecting to you over and over) may e-mail me
directly to get set up with the right people to get the fix. The service is
erroneously not treating the 4xx error as a reason to defer the delivery
until the next queue run. Instead, it treats it as a very transient error
and retries immediately.

In your case, there is another (easier) solution for the servers that are
connecting to you over and over: it sounds like if they were to fix their
inverse DNS entries, so you didn't give them a temporary error code, the
mail would succeed. This is not to say that what the SMTP Service is doing
is right, but there may be another way to solve this particular problem.

Another solution, which you allude to, is for your server to issue a
permanent (5xx) code to a problem that will not get corrected on its own
(such as an invalid inverse DNS record).

David Lemson
Microsoft SMTP Service Program Manager
dlemson@microsoft.com

-------------------------------------------------------------------------------

Date: Wed, 17 Mar 1999 19:47:52 +1300
From: Alan Brown <alan@MANAWATU.GEN.NZ>
To: BUGTRAQ@netspace.org
Subject: Re: Microsoft's SMTP service broken/stupid

On Sun, 14 Mar 1999, Chris Adams wrote:

> Well, that has been fine, but now Microsoft's SMTP service comes along.
> When it gets that temporary error (for invalid reverse DNS), it tries
> again. Fast. Like, right away, with no delay. This bogs down our
> servers a bit, especially the extra logging load, but eventually they go
> away.
>
> Yesterday, we got hit by four different servers running Microsoft's
> software. One attempted delivery nearly 200,000 times, and the other
> three attempted to 30,000-40,000 times each. This on a server that
> usually sees ~40,000 messages a day. This filled up our logs, bogged
> everything down, and basically killed us.

What's needed is judicious tuning of these configuration items:

# load average at which we just queue messages
O QueueLA=8

# load average at which we refuse connections
O RefuseLA=12

The above two default to 8 and 12

# maximum number of children we allow at one time
O MaxDaemonChildren=12

# maximum number of new connections per second
O ConnectionRateThrottle=3

If the above two aren't defined, there are no limits.

Also useful for load control are these two items:

# deliver each queued job in a separate process?
#O ForkEachJob

# single thread deliveries (requires HostStatusDirectory)?
#O SingleThreadDelivery

AB

-------------------------------------------------------------------------------

Date: Wed, 17 Mar 1999 17:49:57 -0700
From: Bob Beck <beck@BOFH.UCS.UALBERTA.CA>
To: BUGTRAQ@netspace.org
Subject: Re: Microsoft's SMTP service broken/stupid

"David Lemson (Exchange)" <dlemson@EXCHANGE.MICROSOFT.COM> writes:


> connecting to you over and over: it sounds like if they were to fix their
> inverse DNS entries, so you didn't give them a temporary error code, the
> mail would succeed. This is not to say that what the SMTP Service is doing
> is right, but there may be another way to solve this particular problem.
>
> Another solution, which you allude to, is for your server to issue a
> permanent (5xx) code to a problem that will not get corrected on its own
> (such as an invalid inverse DNS record).

You miss the point - this could simply be that their DNS is
down or unreachable in a timely manner so the lookup fails. When this
produces an nonexistent entry it actually *does* often correct itself
"on it's own" once the DNS server is reachable again. Similarly the
invalid entry may in fact be corrected before the usual timeout and
allow the mail to proceed. That's the whole point of returning 4XX.

The only way your "solution" is a solution is to return 5XX
errors for *ALL* situations that currently return a 4XX, otherwise we
risk being DOS'ed by a poorly written server that doesn't treat SMTP
errors right. And this isn't a solution - You lose mail that you
shouldn't. So now I should lose mail on a transient DNS failure
because microsoft distrbutes code that doesn't play SMTP nicely? I
don't think so.

The only solution is to fix the buggy code. and/or block access
>from sites running buggy code.

-Bob

-------------------------------------------------------------------------------

Date: Wed, 17 Mar 1999 17:39:16 -0800
From: "David Lemson (Exchange)" <dlemson@EXCHANGE.MICROSOFT.COM>
To: BUGTRAQ@netspace.org
Subject: Re: Microsoft's SMTP service broken/stupid

I have gotten a few queries and I realized that I was not completely clear.
This bug does not, to our knowledge, affect any version of Microsoft
Exchange's Internet Mail Service. It is solely with the SMTP Service
component of Internet Information Service (IIS) v4.0.

Login or Register to add favorites

File Archive:

March 2024

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Mar 1st
    16 Files
  • 2
    Mar 2nd
    0 Files
  • 3
    Mar 3rd
    0 Files
  • 4
    Mar 4th
    32 Files
  • 5
    Mar 5th
    28 Files
  • 6
    Mar 6th
    42 Files
  • 7
    Mar 7th
    17 Files
  • 8
    Mar 8th
    13 Files
  • 9
    Mar 9th
    0 Files
  • 10
    Mar 10th
    0 Files
  • 11
    Mar 11th
    15 Files
  • 12
    Mar 12th
    19 Files
  • 13
    Mar 13th
    21 Files
  • 14
    Mar 14th
    38 Files
  • 15
    Mar 15th
    15 Files
  • 16
    Mar 16th
    0 Files
  • 17
    Mar 17th
    0 Files
  • 18
    Mar 18th
    10 Files
  • 19
    Mar 19th
    32 Files
  • 20
    Mar 20th
    46 Files
  • 21
    Mar 21st
    16 Files
  • 22
    Mar 22nd
    13 Files
  • 23
    Mar 23rd
    0 Files
  • 24
    Mar 24th
    0 Files
  • 25
    Mar 25th
    12 Files
  • 26
    Mar 26th
    31 Files
  • 27
    Mar 27th
    19 Files
  • 28
    Mar 28th
    42 Files
  • 29
    Mar 29th
    0 Files
  • 30
    Mar 30th
    0 Files
  • 31
    Mar 31st
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2022 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close