Skip to content

Octo STS Unauthenticated SSRF by abusing fields in OpenID Connect tokens

High severity GitHub Reviewed Published Jun 26, 2025 in octo-sts/app • Updated Jun 26, 2025

Package

gomod github.com/octo-sts/app (Go)

Affected versions

<= 0.5.2

Patched versions

0.5.3

Description

Summary

Octo-STS versions before v0.5.3 are vulnerable to unauthenticated SSRF by abusing fields in OpenID Connect tokens. Malicious tokens were shown to trigger internal network requests which could reflect error logs with sensitive information.

Please upgrade to v0.5.3 to resolve this issue. This version includes patch sets to sanitize input and redact logging.

Many thanks to @vicevirus for reporting this issue and for assisting with remediation review.

References

References

@cpanato cpanato published to octo-sts/app Jun 26, 2025
Published by the National Vulnerability Database Jun 26, 2025
Published to the GitHub Advisory Database Jun 26, 2025
Reviewed Jun 26, 2025
Last updated Jun 26, 2025

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
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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:L/PR:N/UI:N/S:C/C:H/I:N/A:N

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.
(7th percentile)

Weaknesses

CVE ID

CVE-2025-52477

GHSA ID

GHSA-h3qp-hwvr-9xcq

Source code

Credits

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