Tool to scan/verify the TLS connection parameters and the certificates usage on the target server ports. The tool does not inject a proxy/sidecar to do this scanning.
Our primary reason to work on this tool was to handle 5G Security Control checks that mandates use of TLS within 5G Control Plane. Since then, this tool has been used in the context of general k8s clusters to understand the security risk posture of exposed k8s service endpoints.
- 🔒 Check if the server port is TLS enabled or not.
- 📃 Check TLS version, Ciphersuite, Hash, and Signature for the connection. Are these TLS parameters per the TLS best practices guide?
- Certificate Verification
- 💥 Is the certificate expired or revoked?
- ✍️ Is it a self-signed certificate?
- ⛓️ Is there a self-signed certificate in the full certificate chain?
- Verification of TLS enabled communication and validation of TLS parameters are key to most compliance frameworks. For e.g.,
- Under PCI-DSS 3.2., compliant servers must drop support for TLS 1.0 and “migrate to a minimum of TLS 1.1, Preferably TLS 1.2.”
- HIPAA mandates use of TLS but technically allows use of all versions of TLS.
- 5G Security: 3GPP TS 33.501, Security architecture and procedures for 5G system mandates TLS across all control plane connections.
- Operates in k8s, containerized, and non-containerized environments
- 🚀 Scans control + data plane services in k8s in full auto pilot mode. No user-inputs needed.
- ♾️ Integrate this in CI/CD pipeline to identify use of insecure ports early. Json report option is available.
- 🎯 No proxy or no sidecar implies no impact on runtime performance.
- Scan for Terrapin-SSH vulnerability
- Deploy the k8tls job
kubectl apply -f https://raw.githubusercontent.com/kubearmor/k8tls/main/k8s/job.yaml
- Get the report (once the job is Completed)
kubectl logs -n k8tls $(kubectl get pod -n k8tls -l job-name=k8tls -o name) -f
| Name | Address | Status | Version | Ciphersuite | Hash | Signature | Verification |
| ---------------------------------------------------------------- | -------------------- | ---------- | ------- | ---------------------- | ------ | --------- | -------------------------------------------- |
| accuknox-agents/agents-operator[health-check] | 10.100.17.218:9090 | PLAIN_TEXT | | | | | |
| accuknox-agents/agents-operator[spire-agent] | 10.100.17.218:9091 | PLAIN_TEXT | | | | | |
| accuknox-agents/discovery-engine | 10.100.16.51:9089 | PLAIN_TEXT | | | | | |
| default/kubernetes[https] | 10.100.0.1:443 | TLS | TLSv1.3 | TLS_AES_128_GCM_SHA256 | SHA256 | RSA-PSS | unable to verify the first certificate |
| kube-system/kube-dns[dns-tcp] | 10.100.0.10:53 | PLAIN_TEXT | | | | | |
| kube-system/kubearmor | 10.100.212.208:32767 | PLAIN_TEXT | | | | | |
| kube-system/kubearmor-annotation-manager-metrics-service[https] | 10.100.162.219:443 | TLS | TLSv1.3 | TLS_AES_128_GCM_SHA256 | SHA256 | RSA-PSS | unable to verify the first certificate |
| kube-system/kubearmor-host-policy-manager-metrics-service[https] | 10.100.35.162:8443 | TLS | TLSv1.3 | TLS_AES_128_GCM_SHA256 | SHA256 | RSA-PSS | self-signed certificate in certificate chain |
| kube-system/kubearmor-policy-manager-metrics-service[https] | 10.100.145.145:8443 | TLS | TLSv1.3 | TLS_AES_128_GCM_SHA256 | SHA256 | RSA-PSS | self-signed certificate in certificate chain |
| vault/vault[http] | 10.100.85.110:8200 | PLAIN_TEXT | | | | | |
| vault/vault[https-internal] | 10.100.85.110:8201 | PLAIN_TEXT | | | | | |
| vault/vault-agent-injector-svc[https] | 10.100.198.112:443 | TLS | TLSv1.3 | TLS_AES_128_GCM_SHA256 | SHA256 | ECDSA | unable to verify the first certificate |
| wordpress-mysql/mysql | 10.100.212.210:3306 | PLAIN_TEXT | | | | | |
| wordpress-mysql/wordpress | 10.100.189.9:80 | PLAIN_TEXT | | | | | |
Summary:
| Status | Count |
| ----------------------- | ----- |
| self-signed certificate | 2 |
| insecure port | 9 |
docker run --rm -v $PWD/config:/home/k8tls/config kubearmor/k8tls --infile config/addr.list --csv config/out.csv
| Name | Address | Status | Version | Ciphersuite | Hash | Signature | Verification |
| ------------------------------ | ----------------------------- | -------- | ------- | --------------------------- | ------ | --------- | -------------------------------------------- |
| Google | google.com:443 | TLS | TLSv1.3 | TLS_AES_256_GCM_SHA384 | SHA256 | ECDSA | OK |
| Accuknox | accuknox.com:443 | TLS | TLSv1.3 | TLS_AES_256_GCM_SHA384 | SHA256 | RSA-PSS | OK |
| BadSSL | expired.badssl.com:443 | TLS | TLSv1.2 | ECDHE-RSA-AES128-GCM-SHA256 | SHA512 | RSA | certificate has expired |
| BadSSL | wrong.host.badssl.com:443 | TLS | TLSv1.2 | ECDHE-RSA-AES128-GCM-SHA256 | SHA512 | RSA | OK |
| BadSSL | self-signed.badssl.com:443 | TLS | TLSv1.2 | ECDHE-RSA-AES128-GCM-SHA256 | SHA512 | RSA | self-signed certificate |
| BadSSL | untrusted-root.badssl.com:443 | TLS | TLSv1.2 | ECDHE-RSA-AES128-GCM-SHA256 | SHA512 | RSA | self-signed certificate in certificate chain |
| BadSSL | revoked.badssl.com:443 | TLS | TLSv1.2 | ECDHE-RSA-AES128-GCM-SHA256 | SHA512 | RSA | certificate has expired |
| BadSSL | pinning-test.badssl.com:443 | TLS | TLSv1.2 | ECDHE-RSA-AES128-GCM-SHA256 | SHA512 | RSA | OK |
| BadSSL | dh480.badssl.com:443 | CONNFAIL | | | | | |
| LocalTest | isunknownaddress.com:12345 | CONNFAIL | | | | | |
| localhost:1234 | localhost:1234 | CONNFAIL | | | | | |
| namespace:deployment/wordpress | localhost:22 | CONNFAIL | | | | | |
Note: The command assumes that the current folder contains
addr.listfile containing the list of addresses to scan.
Pre-requisite:
apt-get install jq
- Prepare the
ssh.listfile ref containing the list of ssh ports to scan. - Execute the k8tls tool with ssh.list as the input
docker run --rm -v $PWD:/home/k8tls/data kubearmor/k8tls --infile data/ssh.list --json data/ssh.json
- Print the json report
cat ssh.json | jq .
Sample config/ssh.json report output
{
"app": {
"version": "v0.1"
},
"endpoints": [
{
"svc": "open-horizon-edge-vm",
"host": "172.174.240.192",
"port": "22",
"finding": [
{
"plugin": "terrapin-ssh",
"title": "terrapin ssh server attack",
"description": "The exploit can allow an attacker to downgrade the connection security by truncating the extension negotiation message (RFC8308) from the transcript. The truncation can lead to using less secure client authentication algorithms and deactivating specific countermeasures against keystroke timing attacks.",
"link": "https://terrapin-attack.com/",
"banner": "SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.5",
"supportsChaCha20": "true",
"supportsCbcEtm": "false",
"supportsStrictKex": "true",
"severity": "high",
"remediationEstEffort": "medium",
"solution": "Both SSH client and server needs to be patched to fix the exploit.",
"status": "OK"
}
]
},
{
"svc": "jfrog-registry-vm",
"host": "4.242.4.41",
"port": "22",
"finding": [
{
"plugin": "terrapin-ssh",
"title": "terrapin ssh server attack",
"description": "The exploit can allow an attacker to downgrade the connection security by truncating the extension negotiation message (RFC8308) from the transcript. The truncation can lead to using less secure client authentication algorithms and deactivating specific countermeasures against keystroke timing attacks.",
"link": "https://terrapin-attack.com/",
"banner": "SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.7+esm2",
"supportsChaCha20": "true",
"supportsCbcEtm": "false",
"supportsStrictKex": "false",
"severity": "high",
"remediationEstEffort": "medium",
"solution": "Both SSH client and server needs to be patched to fix the exploit.",
"status": "FAIL"
}
]
},
{
"svc": "jumphost",
"host": "172.208.81.244",
"port": "22",
"finding": [
{
"plugin": "terrapin-ssh",
"title": "terrapin ssh server attack",
"description": "The exploit can allow an attacker to downgrade the connection security by truncating the extension negotiation message (RFC8308) from the transcript. The truncation can lead to using less secure client authentication algorithms and deactivating specific countermeasures against keystroke timing attacks.",
"link": "https://terrapin-attack.com/",
"banner": "SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.5",
"supportsChaCha20": "true",
"supportsCbcEtm": "false",
"supportsStrictKex": "true",
"severity": "high",
"remediationEstEffort": "medium",
"solution": "Both SSH client and server needs to be patched to fix the exploit.",
"status": "OK"
}
]
},
{
"svc": "nessus-vm",
"host": "20.124.83.23",
"port": "22",
"finding": [
{
"plugin": "terrapin-ssh",
"title": "terrapin ssh server attack",
"description": "The exploit can allow an attacker to downgrade the connection security by truncating the extension negotiation message (RFC8308) from the transcript. The truncation can lead to using less secure client authentication algorithms and deactivating specific countermeasures against keystroke timing attacks.",
"link": "https://terrapin-attack.com/",
"banner": "SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.10",
"supportsChaCha20": "true",
"supportsCbcEtm": "false",
"supportsStrictKex": "true",
"severity": "high",
"remediationEstEffort": "medium",
"solution": "Both SSH client and server needs to be patched to fix the exploit.",
"status": "OK"
}
]
},
{
"svc": "ai-team-vm",
"host": "74.249.73.76",
"port": "22",
"finding": [
{
"plugin": "terrapin-ssh",
"title": "terrapin ssh server attack",
"description": "The exploit can allow an attacker to downgrade the connection security by truncating the extension negotiation message (RFC8308) from the transcript. The truncation can lead to using less secure client authentication algorithms and deactivating specific countermeasures against keystroke timing attacks.",
"link": "https://terrapin-attack.com/",
"banner": "SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.5",
"supportsChaCha20": "true",
"supportsCbcEtm": "false",
"supportsStrictKex": "true",
"severity": "high",
"remediationEstEffort": "medium",
"solution": "Both SSH client and server needs to be patched to fix the exploit.",
"status": "OK"
}
]
},
{
"svc": "performance-test-vm",
"host": "172.208.76.73",
"port": "22",
"finding": [
{
"plugin": "terrapin-ssh",
"title": "terrapin ssh server attack",
"description": "The exploit can allow an attacker to downgrade the connection security by truncating the extension negotiation message (RFC8308) from the transcript. The truncation can lead to using less secure client authentication algorithms and deactivating specific countermeasures against keystroke timing attacks.",
"link": "https://terrapin-attack.com/",
"banner": "SSH-2.0-OpenSSH_8.7",
"supportsChaCha20": "true",
"supportsCbcEtm": "false",
"supportsStrictKex": "false",
"severity": "high",
"remediationEstEffort": "medium",
"solution": "Both SSH client and server needs to be patched to fix the exploit.",
"status": "FAIL"
}
]
},
{
"svc": "devops-vm",
"host": "20.109.50.235",
"port": "22",
"finding": [
{
"plugin": "terrapin-ssh",
"title": "terrapin ssh server attack",
"description": "The exploit can allow an attacker to downgrade the connection security by truncating the extension negotiation message (RFC8308) from the transcript. The truncation can lead to using less secure client authentication algorithms and deactivating specific countermeasures against keystroke timing attacks.",
"link": "https://terrapin-attack.com/",
"banner": "SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.5",
"supportsChaCha20": "true",
"supportsCbcEtm": "false",
"supportsStrictKex": "true",
"severity": "high",
"remediationEstEffort": "medium",
"solution": "Both SSH client and server needs to be patched to fix the exploit.",
"status": "OK"
}
]
},
{
"svc": "harbor-accuknox",
"host": "172.190.166.169",
"port": "22",
"finding": [
{
"plugin": "terrapin-ssh",
"title": "terrapin ssh server attack",
"description": "The exploit can allow an attacker to downgrade the connection security by truncating the extension negotiation message (RFC8308) from the transcript. The truncation can lead to using less secure client authentication algorithms and deactivating specific countermeasures against keystroke timing attacks.",
"link": "https://terrapin-attack.com/",
"banner": "SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.10",
"supportsChaCha20": "true",
"supportsCbcEtm": "false",
"supportsStrictKex": "true",
"severity": "high",
"remediationEstEffort": "medium",
"solution": "Both SSH client and server needs to be patched to fix the exploit.",
"status": "OK"
}
]
}
]
}- Validate based on SSL/TLS best practices.
- Check if the key size is ok
- Add support for DTLS scanning
- In detailed mode, enlist all possible TLS versions, Ciphersuites, Hash/Signature algorithms supported.
- Verify if algorithms supporting PFS (Pure Forward Secrecy) are used.
- Check for presence of HTTP Strict Transport Security (HSTS)
- Check for HTTP Public Key Pinning (HPKP)
- TLS compression checks
- Check for use of TLS Fallback SCSV to Prevent Protocol Downgrade Attacks
- Check if Secure Renegotiation is enabled. (Secure renegotiation is a feature of the SSL/TLS protocols that allows the client or server to request a new TLS handshake in the middle of a session. This can be useful for a variety of reasons, such as refreshing encryption keys or changing the level of encryption.)
- Add service scanning for e.g., mysql, cassandra, ssh etc