Property
Language
Severity
CWE	CWE-300: Channel Accessible by Non-Endpoint
OWASP	A07:2021 - Identification and Authentication Failures
Confidence Level	High
Impact Level	Low
Likelihood Level	Low

Description

The gRPC server is being started without SSL/TLS credentials, which means connections to it are not encrypted. This allows clients to connect over an insecure channel, making sensitive data visible in transit.

Impact

Without encryption, attackers could intercept, read, or modify gRPC messages between clients and the server. This could expose confidential information, allow message tampering, or open the server to various network-based attacks, potentially compromising application integrity and user data.

Property
Language
Severity
Service	gke
Provider	Google
Vulnerability Type	omission

Description

GKE node pools are configured to use the default Compute Engine service account instead of a minimally privileged, custom service account. This setup grants nodes broader permissions than necessary, increasing exposure to potential misuse.

Impact

If compromised, nodes with overly permissive service accounts could allow attackers to access or manipulate other Google Cloud resources, leading to data breaches, privilege escalation, or unauthorized resource usage across the environment.

Property
Language	apex
Severity
CWE	CWE-319: Cleartext Transmission of Sensitive Information
Confidence Level	Medium
Impact Level	Medium
Likelihood Level	Low

Description

The software transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.

Property
Language
Severity
CWE	CWE-319: Cleartext Transmission of Sensitive Information
OWASP	A03:2017 - Sensitive Data Exposure
Confidence Level	Medium
Impact Level	Medium
Likelihood Level	Medium

Description

TLS certificate verification is disabled for this service, meaning it will trust any server certificate, even if it’s invalid or fake. This makes HTTPS connections vulnerable to interception and tampering.

Impact

Attackers could perform man-in-the-middle attacks to intercept or alter sensitive data sent between your service and the server. This compromises data confidentiality and integrity, potentially exposing credentials or allowing unauthorized access.

Property
Language
Severity
CWE	CWE-319: Cleartext Transmission of Sensitive Information
OWASP	A03:2017 - Sensitive Data Exposure
Confidence Level	Medium
Impact Level	Medium
Likelihood Level	Medium

Description

The configuration disables TLS certificate verification when connecting to a Kubernetes cluster, making HTTPS connections vulnerable to impersonation and interception. This exposes sensitive data exchanged between clients and the server.

Impact

Attackers could perform man-in-the-middle attacks to intercept or alter traffic, steal credentials, or inject malicious commands. This compromises the confidentiality and integrity of data and could lead to unauthorized access or control over your Kubernetes environment.

Property
Language
Severity
CWE	CWE-319: Cleartext Transmission of Sensitive Information
OWASP	A03:2017 - Sensitive Data Exposure
Confidence Level	Low
Impact Level	Low
Likelihood Level	Low

Description

The Redis cache is configured to allow non-SSL (unencrypted) connections, which means data sent between clients and the cache can be intercepted and read in plain text. This exposes sensitive information to potential attackers.

Impact

If exploited, attackers on the network could eavesdrop on credentials, session data, or other sensitive information transmitted to and from the Redis cache. This can lead to data breaches, unauthorized access, and compromise of confidential data.

Property
Language
Severity
CWE	CWE-319: Cleartext Transmission of Sensitive Information
OWASP	A03:2017 - Sensitive Data Exposure
Confidence Level	Medium
Impact Level	Medium
Likelihood Level	Medium

Description

The App Service is configured to accept both HTTP and HTTPS connections, rather than enforcing HTTPS only. This allows unencrypted (HTTP) traffic, exposing sensitive data to interception.

Impact

If exploited, attackers could intercept or tamper with data transmitted over insecure HTTP connections, potentially stealing credentials or other sensitive information. This undermines data confidentiality and may lead to compliance violations or user trust issues.

Property
Language
Severity
CWE	CWE-319: Cleartext Transmission of Sensitive Information
OWASP	A03:2017 - Sensitive Data Exposure
Confidence Level	Medium
Impact Level	Medium
Likelihood Level	Low

Description

The web app is not configured to enforce HTTPS, allowing users to access it over unencrypted HTTP. This can expose sensitive data in transit to interception or tampering.

Impact

If exploited, attackers could intercept or modify data sent between users and the app, potentially stealing credentials, session tokens, or other confidential information. This puts user privacy and application security at risk, and may violate compliance requirements.

Property
Language
Severity
CWE	CWE-319: Cleartext Transmission of Sensitive Information
OWASP	A03:2017 - Sensitive Data Exposure
Confidence Level	Medium
Impact Level	Medium
Likelihood Level	Low

Description

The storage account is not configured to enforce HTTPS-only traffic, which allows data to be accessed over unencrypted HTTP connections. This exposes sensitive information to potential interception during transmission.

Impact

Without HTTPS-only enforcement, attackers could intercept or tamper with data sent to and from the storage account over unsecured networks. This can lead to data breaches, unauthorized access, and compromise of confidential information.

Property
Language	regex
Severity
CWE	CWE-319: Cleartext Transmission of Sensitive Information
OWASP	A03:2017 - Sensitive Data Exposure
Confidence Level	Low
Impact Level	Medium
Likelihood Level	Low

Description

The code is establishing WebSocket connections using the insecure ‘ws://’ protocol instead of ‘wss://’. This means data sent over the connection is not encrypted and can be intercepted by attackers.

Impact

If exploited, sensitive information transmitted via these WebSockets can be read or tampered with by attackers on the network. This could lead to data breaches, session hijacking, or unauthorized access to user data, putting both users and the organization at risk.