How solve Brute Force through IIS NTLM authentication scheme

Williams Padilla 41 Reputation points
2021-01-17T00:42:05.403+00:00

Hi everyone

Someone know how Can I solve this vulnerability?

It's associate with the CVE 2002-0419

My OS is windows server 2016 Datacenter

Thanks

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,374 questions
Windows Server Infrastructure
Windows Server Infrastructure
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Infrastructure: A Microsoft solution area focused on providing organizations with a cloud solution that supports their real-world needs and meets evolving regulatory requirements.
515 questions
{count} votes

3 answers

Sort by: Most helpful
  1. MotoX80 31,656 Reputation points
    2021-01-18T01:38:12.597+00:00

    This looks like an old vulnerability. https://nvd.nist.gov/vuln/detail/CVE-2002-0419
    https://www.cvedetails.com/cve/CVE-2002-0419/

    WS 2016 should not be running IIS 4 or 5.1.

    Did someone scan your system and detect this vulnerability?


  2. Gloria Gu 3,891 Reputation points
    2021-01-20T08:38:56.373+00:00

    Hi,

    Thank you for posting in Q&A!

    May I ask what's your IIS version? According to my research, IIS 6 and 7 are susceptible to this particular vulnerability:
    https://answers.microsoft.com/en-us/protect/forum/protect_other-protect_scanning-windows_other/account-brute-force-possible-through-iis-ntlm/e7f42505-f871-4dd7-a67d-3245f959e61e?auth=1

    And there's a workaroud posted by some user has the same problem, maybe you can try it:

    disable NTLM authentication for your Web server. This can be done by unchecking "Integrated Windows Authentication" within "Authentication Method" under "Directory Security" in "Default Web Site Properties".

    Hope you have a nice day : )
    Gloria

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
    https://learn.microsoft.com/en-us/answers/articles/67444/email-notifications.html


  3. MotoX80 31,656 Reputation points
    2021-01-22T15:34:26.487+00:00

    Yes the security team detected it with scan , the software is qualys

    I am not familiar with Qualys. My experience with having my servers scanned, was that the vulnerability report typically provided a link to "Here's how to fix this vulnerability" where I could go research what I needed to change.

    On the US government web site.... https://nvd.nist.gov/vuln/detail/CVE-2002-0419

    it says: NOTE: this entry originally contained a vector (1) in which the server reveals whether it supports Basic or NTLM authentication through 401 Access Denied error messages. CVE has REJECTED this vector; it is not a vulnerability because the information is already available through legitimate use, since authentication cannot proceed without specifying a scheme that is supported by both the client and the server.

    In the section "References to Advisories, Solutions, and Tools", I don't see a solution. There are 3 links to other sites, and https://www.securityfocus.com/bid/4235/solution says "Currently the SecurityFocus staff are not aware of any vendor-supplied patches for this issue".

    https://marc.info/?l=bugtraq&m=101535399100534&w=2 says: "Microsoft was informed of this but didn't consider it to be a problem."

    So..... for whatever web site you have on the server, how does it authenticate users? Does it even require authentication? In the IIS manager, disable any authentication scheme that is not used.

    59635-capture.jpg

    If that doesn't satisfy your security team, send them an email that says "Thank you for pointing out this vulnerability. Please provide instructions as to how I fix the issue. My research has not found a solution.."