Unencrypted Client-Server Traffic

The client communicates with its server without encryption, exposing credentials and data to anyone able to observe or intercept the traffic.

SeverityMedium
CVSS 3.15.9 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N Open in the calculator
CVSS 4.06 CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-319: Cleartext Transmission of Sensitive Information
OWASP Top 10A04:2025 Cryptographic Failures
MITRE ATT&CKT1040 Network Sniffing, T1557 Adversary-in-the-Middle
CategoryCryptographic Failures

Description

The thick client sends and receives data over the network without encryption. Common forms are web services called over HTTP rather than HTTPS, database connections where encryption is not required, for example to SQL Server or MySQL, and proprietary TCP protocols that send data in cleartext or under a simple encoding. Some clients use TLS but accept any certificate, which leaves the same exposure to an attacker who can intercept the connection. Because thick clients are often deployed on internal networks, cleartext protocols tend to be accepted on the assumption that the internal network is trusted.

The traffic typically includes users' credentials or session tokens, the application's business data, and the requests that drive server-side actions. An attacker with a position on the network path, for example on the same network segment using ARP spoofing, or with control of a network device, can read the credentials and data as they pass, and in many cases alter requests and responses to change what the client or server does. The attacker needs that network position first, which limits the rating, but on flat internal networks and shared wireless networks it is often easy to obtain.

The weakness is identified by capturing the application's traffic with Wireshark, or routing it through an intercepting proxy, and reviewing what is visible. Where the traffic is not HTTP, tools that intercept arbitrary TCP connections show whether requests can also be altered in transit.

Remediation

Encrypt and authenticate every connection between the client and its servers:

  • Use TLS 1.2 or later for all client-server communication, with the client validating the server certificate's chain and host name. For web services, use HTTPS only and disable cleartext endpoints on the server.
  • For direct database connections, configure the server to require encryption and the client to require it too, without trusting any certificate presented. For SQL Server this means setting Encrypt=True and TrustServerCertificate=False in the connection string, with a valid certificate installed on the server.
  • Replace custom encoding in proprietary protocols with TLS, or carry the protocol inside a TLS connection.
  • Where the server needs to know which clients are genuine, add mutual TLS.

As an interim measure, restrict the client-server traffic to a dedicated network segment or an IPsec-protected path. Confirm the fix by capturing the traffic again and confirming that it is encrypted, and that an intercepting proxy presenting an untrusted certificate is rejected.

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 trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Thick Clients Findings

Every Thick Clients finding