{"answers":{"affected":"3 open source packages ship an affected version, including github.com/octo-sts/app.","exploited":"There is no known exploitation of CVE-2025-52477 in the wild and no public exploit code.","fix":"Upgrade github.com/octo-sts/app to 0.5.3 or later.","what":"CVE-2025-52477 is a high-severity server-side request forgery vulnerability in octo-sts app, published on 26 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-52477 and fix it if it is affected.\n\nWhat it is: CVE-2025-52477 is a high-severity server-side request forgery vulnerability in octo-sts app, published on 26 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-52477 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/octo-sts/app (Go): affected all versions; fixed in 0.5.3\n- github.com/octo-sts/app (Go): affected all versions; fixed in 0.5.3\n- github.com/octo-sts/app (Go): affected all versions; fixed in 0.5.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-52477/ (Markdown: https://insights.sbomify.com/CVE-2025-52477/index.md)","id":"CVE-2025-52477","markdown":"https://insights.sbomify.com/CVE-2025-52477/index.md","name":"CVE-2025-52477","record":{"aliases":["GHSA-h3qp-hwvr-9xcq","GO-2025-3779"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub App STS","requires_auth":"none","summary":"Unauthenticated attackers can trigger SSRF via OIDC tokens to access internal networks and leak sensitive information from error logs.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Octo-STS is a GitHub App that acts like a Security Token Service (STS) for the GitHub API. 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. Upgrade to v0.5.3 to resolve this issue. This version includes patch sets to sanitize input and redact logging.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Octo-STS Vulnerable to Unauthenticated SSRF with HTTP Response Reflection in OIDC Flow","id":"CVE-2025-52477","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":3,"n_references":4,"next":{"headline":"Stored XSS in n8n Form Trigger allows Account Takeover via injected iframe and video/source","id":"CVE-2025-52478"},"packages":[{"ecosystem":"Go","fixed":["0.5.3"],"introduced":["0"],"last_affected":[],"package":"github.com/octo-sts/app","purl":null,"source":"GHSA-h3qp-hwvr-9xcq"},{"ecosystem":"Go","fixed":["0.5.3"],"introduced":["0"],"last_affected":[],"package":"github.com/octo-sts/app","purl":"pkg:golang/github.com/octo-sts/app","source":"GHSA-h3qp-hwvr-9xcq"},{"ecosystem":"Go","fixed":["0.5.3"],"introduced":["0"],"last_affected":[],"package":"github.com/octo-sts/app","purl":"pkg:golang/github.com/octo-sts/app","source":"GO-2025-3779"}],"prev":{"headline":"Chamilo: Reflected XSS via keyword_active parameter","id":"CVE-2025-52476"},"products":["app"],"published":"2025-06-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-27","vendors":["octo-sts"]},"summary":"Unauthenticated attackers can trigger SSRF via OIDC tokens to access internal networks and leak sensitive information from error logs.","url":"https://insights.sbomify.com/CVE-2025-52477/"}