Issuer validation regression in Spring Cloud SSO Connector

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2018-1256: 1.58% estimated exploitation activity in the next 30 days; percentile 75.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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:</p<ul<liSpring Cloud SSO Connector: 2.1.3</li</ul Alternatively, you can perform <uone</u of the following workarounds:</p<ul<liBind your resource server to the SSO service plan via a service instance binding</li<liSet “sso.connector.cloud.available=true” within your Spring application properties</li</ul

Published by the source

13 May 2022, 01:07 UTC

Last modified by the source

4 Mar 2024, 20:49 UTC

Source last checked

26 Oct 2026, 16:26 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q4q2-93pw-qwgf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2018-1256

Advisory: Issuer validation regression in Spring Cloud SSO Connector
IDs: CVE-2018-1256, GHSA-q4q2-93pw-qwgf
Record: https://patchnext.com/advisories/cve-2018-1256 (revision 1, source checked 26 Oct 2026, 16:26 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.pivotal.spring.cloud:spring-cloud-sso-connector 2.1.3.RELEASE. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.pivotal.spring.cloud:spring-cloud-sso-connector: affected >= 2.1.2.RELEASE, <= 2.1.2.RELEASE; fixed in 2.1.3.RELEASE

## Suggested inspection (read-only)
- Maven io.pivotal.spring.cloud:spring-cloud-sso-connector: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.pivotal.spring.cloud:spring-cloud-sso-connector.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-q4q2-93pw-qwgf (GitHub-reviewed advisory GHSA-q4q2-93pw-qwgf lists affected ranges: Maven io.pivotal.spring.cloud:spring-cloud-sso-connector >=2.1.2.RELEASE <=2.1.2.RELEASE)

Commands are suggestions: review each one before running it.