OWASP / OWASP/TCASVS

Missing Server Authentication Verification Requirement on TASVS-NETWORK-2

Open
#16 0 comments 0 reactions 1 assignee View on GitHub

@JeffreyShran is already working on this.

Since Apr 7, 2025.

enhancement
Dominant language
TeX
Stars
30
Forks
5
PR merge metrics
No merged PRs in 30d

Description

I suspect there's a potential gap in the TASVS-NETWORK-2 section (Licensing & Authentication Servers). While the standard covers many aspects of client authentication to servers, there's no explicit requirement for verifying server authenticity to prevent server spoofing and man-in-the-middle attacks.

I recently found an issue with a thick client that I did a security test on. This client uses ldap as authentication therefore its sending ldap request to the server. Since no verification done on the server, I was able to spoof it using fake ldap server that i generated using a docker container.

Security Implications
Without proper server authentication verification:

  • Clients may connect to malicious servers posing as legitimate authentication endpoints
  • Man-in-the-middle attacks may be possible even with TLS encryption in place (TASVS-NETWORK-1.2)
  • Attackers could steal credentials, hijack sessions, or inject malicious responses

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.