Findings

Insecure auth scheme

Updated: June 19, 2025

Description

An endpoint has an insecure authentication scheme set. There are many [HTTP authorization schemes](https://www.iana.org/assignments/http-authschemes/) but some of them are now considered insecure, such as negotiating authentication using specifications like NTLM or OAuth v1. You should also consider that basic authentication credentials transported over networks are more susceptible to interception than other forms of authentication, and as they are not encrypted it means passwords and tokens are more easily leaked.

Remediation

Improve the security of the endpoint by choosing a secure authentication schema.

Security Frameworks

Authentication mechanisms are often implemented incorrectly, allowing attackers to compromise authentication tokens or to exploit implementation flaws to assume other user's identities temporarily or permanently. Compromising a system's ability to identify the client/user, compromises API security overall.

Authentication mechanisms are often implemented incorrectly, allowing attackers to compromise authentication tokens or to exploit implementation flaws to assume other user's identities temporarily or permanently. Compromising the system's ability to identify the client or user, compromises API security overall.

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

Need help?

Contact FireTail support

Previous (Findings - Design based findings)
Index creation failed
Next (Findings - Design based findings)
Insecure host (OAS2)