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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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 pinpoints whether GHSA-q4q2-93pw-qwgf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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 72th 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.

GHSA-q4q2-93pw-qwgf: Issuer validation regression in Spring Clo…

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk72th percentile+1.28%

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.

Blast Radius

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

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 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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 pinpoints whether GHSA-q4q2-93pw-qwgf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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 detects GHSA-q4q2-93pw-qwgf across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-q4q2-93pw-qwgf