Openshift 4.9 does not use HTTP Strict Transport Security (HSTS) which may allow man-in-the-middle (MITM) attacks.
Weakness
The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Openshift |
Redhat |
4.9 (including) |
4.9 (including) |
| Red Hat OpenShift Container Platform 4.12 |
RedHat |
openshift-0:4.12.0-202301042257.p0.g77bec7a.assembly.stream.el9 |
* |
| Red Hat OpenShift Container Platform 4.13 |
RedHat |
openshift-0:4.13.0-202304211155.p0.gb404935.assembly.stream.el8 |
* |
Potential Mitigations
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- For example, in Java, if the programmer does not explicitly initialize a variable, then the code could produce a compile-time error (if the variable is local) or automatically initialize the variable to the default value for the variable’s type. In Perl, if explicit initialization is not performed, then a default value of undef is assigned, which is interpreted as 0, false, or an equivalent value depending on the context in which the variable is accessed.
References