A configuration vulnerability in VMware Spring Cloud Gateway allows for unintended SSL settings to be applied, potentially degrading security transport controls.

The application fails to properly apply the spring.ssl.bundle configuration property, causing the system to ignore custom SSL configurations and revert to default settings. The vulnerability is exploitable by an unauthenticated remote attacker who can influence the environment where the default SSL configuration may be insufficient or insecure.

The failure to honor custom SSL configurations may lead to the use of weaker encryption parameters or misconfigured trust stores, potentially exposing sensitive data in transit to interception or man-in-the-middle attacks. While the CVSS score of 7.5 indicates a high severity based on integrity impact, the primary risk is the silent degradation of security posture for encrypted communications.

Immediate Action: Upgrade to version 4.2.1 or migrate to the supported open source releases 5.0.2 or 5.1.1.

Proactive Monitoring: Review application logs and SSL/TLS handshake configurations to ensure that the intended security bundles are being correctly loaded and utilized by the gateway.

Compensating Controls: Ensure that network traffic is inspected by robust perimeter security controls that enforce strict TLS requirements, effectively mitigating risks posed by potential SSL configuration downgrades.

Public Exploit Available: No — exploit_available (unknown).

Given the silent nature of this configuration failure, organizations must verify their SSL/TLS implementations immediately. It is highly recommended to upgrade to the provided patched versions or transition to a supported release branch to ensure that security configurations are properly enforced and maintained.