Skip to content

Issuer validation regression in Spring Cloud SSO Connector

High severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Mar 4, 2024

Package

maven io.pivotal.spring.cloud:spring-cloud-sso-connector (Maven)

Affected versions

= 2.1.2.RELEASE

Patched versions

2.1.3.RELEASE

Description

Spring Cloud SSO Connector, version 2.1.2, contains a regression which disables issuer validation in resource servers that are not bound to the SSO service. In PCF deployments with multiple SSO service plans, a remote attacker can authenticate to unbound resource servers which use this version of the SSO Connector with tokens generated from another service plan.

Mitigation

Users of affected versions should apply the following mitigation:

  • Releases that have fixed this issue include:

    • Spring Cloud SSO Connector: 2.1.3
  • Alternatively, you can perform one of the following workarounds:

    • Bind your resource server to the SSO service plan via a service instance binding
    • Set “sso.connector.cloud.available=true” within your Spring application properties

References

Published by the National Vulnerability Database May 7, 2018
Published to the GitHub Advisory Database May 13, 2022
Reviewed Jan 8, 2024
Last updated Mar 4, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(63rd percentile)

Weaknesses

No CWEs

CVE ID

CVE-2018-1256

GHSA ID

GHSA-q4q2-93pw-qwgf

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.