Credentials Transmitted Over an Unencrypted Channel
Usernames, passwords or authentication tokens are sent without encryption, so anyone able to observe the traffic can capture them.
| Severity | Medium |
| CVSS 3.1 | 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N Open in the calculator |
| CVSS 4.0 | 6 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-523: Unprotected Transport of Credentials |
| OWASP Top 10 | A04:2025 Cryptographic Failures |
| MITRE ATT&CK | T1040 Network Sniffing, T1557 Adversary-in-the-Middle |
| Category | Cryptographic Failures |
Description
The application sends authentication credentials across the network without transport encryption. Typical cases are a login form served or submitted over plain HTTP; HTTP Basic authentication over HTTP, which only encodes the username and password with base64 and so offers no protection; an API that accepts passwords, API keys or bearer tokens over HTTP; and a login page delivered over HTTP that posts to an HTTPS address, which still lets an attacker who can modify the page send the submission elsewhere. Thick clients, mobile applications and integrations that send credentials over unencrypted protocols have the same weakness.
An attacker who can observe the network path between users and the application, for example on shared or public Wi-Fi, through a compromised network device or from within an internal network, can capture credentials and session tokens as users sign in, and reuse them to access their accounts; captured passwords may also work on other systems where users have reused them. The attack requires a position on the network path, which limits it to attackers on the same network or with access to intermediate infrastructure.
The finding is confirmed by intercepting the authentication exchange, with an intercepting proxy or a packet capture, and showing the credentials or token in readable form, or by showing that an HTTPS login endpoint also accepts submissions over HTTP. Scanners commonly report the issue as cleartext submission of a password, or as a password field served or submitted over HTTP.
Remediation
- Serve the login page, the credential submission and all authenticated pages and API endpoints over HTTPS only, using TLS 1.2 or 1.3.
- Redirect plain HTTP requests to HTTPS before any credentials are entered, and stop accepting credentials or tokens on HTTP endpoints altogether, so that a mistaken HTTP request fails rather than succeeding in clear text.
- Send the
Strict-Transport-Securityheader so that browsers use HTTPS for every later request, and consider HSTS preloading for public sites. - Set the
Secureattribute on session cookies so that they are never sent over HTTP. - Replace unencrypted protocols used by clients and integrations with their encrypted equivalents, and enforce encryption on the server rather than leaving it optional.
Users whose credentials may have been exposed should be asked to change their passwords. Confirm the fix by attempting to sign in and to call authenticated endpoints over plain HTTP, and confirming that no credentials are accepted or sent unencrypted.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.