Insecure authentication method - NTLM

Description

The application uses the Legacy NTLM authentication protocol which can be vulnerable to several security flaws, including Relay attacks, Man in the Middle and brute force to obtain valid challenge results.

Impact

Obtain valid challenges to impersonate application users.

Recommendation

Avoid and restrict the use of NTLM as authentication mechanism, in favor of more recent and secure alternatives such as Kerberos, Smart Cards, OAuth, Bearer Authentication, forms, JWT, among others.

Threat

Anonymous attacker from adjacent network performing a MitM.

Expected Remediation Time

⌚ minutes.

Score

Default score using CVSS 3.1. It may change depending on the context of the src.

Base

• Attack vector: A
• Attack complexity: H
• Privileges required: N
• User interaction: R
• Scope: U
• Confidentiality: L
• Integrity: L
• Availability: N

Temporal

• Exploit code madurity: P
• Remediation level: O
• Report confidence: C

Result

• Vector string: CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N/E:P/RL:O/RC:C
• Score:
  • Base: 3.7
  • Temporal: 3.4
• Severity:
  • Base: Low
  • Temporal: Low

Requirements

• 228.Authenticate using standard protocols
• 319.Make authentication options equally secure

Fixes

• Scala
• Python
• Ruby
• Go
• Java
• C-Sharp
• TypeScript

free trial

Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.