How severe is GHSA-q4q2-93pw-qwgf?

GHSA-q4q2-93pw-qwgf has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-q4q2-93pw-qwgf?

GHSA-q4q2-93pw-qwgf affects the following packages: io.pivotal.spring.cloud:spring-cloud-sso-connector (Maven). Ecosystems affected: Maven.

How do I fix GHSA-q4q2-93pw-qwgf?

Update io.pivotal.spring.cloud:spring-cloud-sso-connector to 2.1.3.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q4q2-93pw-qwgf is resolved across your whole dependency graph.

How do I detect GHSA-q4q2-93pw-qwgf in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.pivotal.spring.cloud:spring-cloud-sso-connector, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-q4q2-93pw-qwgf if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-q4q2-93pw-qwgf?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-q4q2-93pw-qwgf can be triaged on real exposure rather than presence alone.

Is GHSA-q4q2-93pw-qwgf actively exploited in the wild?

No public exploit code has been indexed for GHSA-q4q2-93pw-qwgf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-q4q2-93pw-qwgf?

GHSA-q4q2-93pw-qwgf has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 75th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-q4q2-93pw-qwgf published, and has it been updated?

GHSA-q4q2-93pw-qwgf was published on May 13, 2022 and was last updated on March 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

GHSA-q4q2-93pw-qwgf — spring-cloud-sso-connector

HIGHFix: pivotal-cf/spring-cloud-sso-connector@ef647a2

GHSA-q4q2-93pw-qwgf is a high-severity (CVSS 8.1) vulnerability in io.pivotal.spring.cloud:spring-cloud-sso-connector. A fix is available for io.pivotal.spring.cloud:spring-cloud-sso-connector — see the affected versions and patch details below.

Issuer validation regression in Spring Cloud SSO Connector

Also known asCVE-2018-1256

Published

May 13, 2022

Updated

Mar 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-q4q2-93pw-qwgf plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected

☕io.pivotal.spring.cloud:spring-cloud-sso-connector

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Mitigation

Users of affected versions should apply the following mitigation:

Releases that have fixed this issue include:<ul><li>Spring Cloud SSO Connector: 2.1.3</li></ul>
Alternatively, you can perform one of the following workarounds:<ul><li>Bind your resource server to the SSO service plan via a service instance binding</li><li>Set “sso.connector.cloud.available=true” within your Spring application properties</li></ul>

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.pivotal.spring.cloud:spring-cloud-sso-connector`	≥ 2.1.2.RELEASE&&< 2.1.3.RELEASE	2.1.3.RELEASE`io.pivotal.spring.cloud:spring-cloud-sso-connector:2.1.3.RELEASE`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.pivotal.spring.cloud:spring-cloud-sso-connector, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.pivotal.spring.cloud:spring-cloud-sso-connector to 2.1.3.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q4q2-93pw-qwgf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-q4q2-93pw-qwgf can be triaged on real exposure rather than presence alone.

Tailored to GHSA-q4q2-93pw-qwgf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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:<ul><li>Spring Cloud SSO Connector: 2.1.3</li></ul> * Alternatively, you can perform one of the

O3 Security · Impact-Aware SCA

Is GHSA-q4q2-93pw-qwgf in your dependencies?

O3 Security finds GHSA-q4q2-93pw-qwgf across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works