CVE-2018-8059: High severity suse Portus vulnerability
The Djelibeybi configuration examples for use of NGINX in SUSE Portus 2.3, when applied to certain configurations involving Docker Compose, have a Missing SSL Certificate Validation issue because no proxyssl directives are used.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Update the NGINX configuration derived from the Djelibeybi examples to add the appropriate proxy_ssl_* directives so the upstream SSL certificate is validated (the issue occurs because no proxy_ssl_* directives are used).
NGINX (used with SUSE Portus 2.3 example configuration) proxy_ssl_* directives = Include required proxy_ssl_certificate / proxy_ssl_verify (and related proxy_ssl_* directives as applicable) to ensure SSL certificate validation when proxying to Docker Compose services
Event History
Frequently Asked Questions
What is the severity of CVE-2018-8059?
CVE-2018-8059 is classified as a medium severity vulnerability that could lead to potential security risks in specific configurations.
How do I fix CVE-2018-8059?
To fix CVE-2018-8059, ensure that proxy_ssl_* directives are correctly implemented in your NGINX configuration for SUSE Portus 2.3.
What is the impact of CVE-2018-8059?
The impact of CVE-2018-8059 is that it allows for potential man-in-the-middle attacks due to missing SSL certificate validation.
Which versions are affected by CVE-2018-8059?
CVE-2018-8059 affects SUSE Portus version 2.3.0 when using certain Docker Compose configurations.
Is CVE-2018-8059 a client-side or server-side vulnerability?
CVE-2018-8059 is primarily a server-side vulnerability that affects the configuration of the NGINX proxy server.