GHSA-q347-cg56-pcq4: SSRF in repository migration
Noroxi assessment
Priority: Monitor (action score 20/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: gogs.io/gogs (Go) 0.12.5.
Low priority for now. Upgrade to gogs.io/gogs (Go) 0.12.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
### Impact The malicious user is able to discover services in the internal network through repository migration functionality. All installations accepting public traffic are affected. ### Patches Internal network CIDRs are prohibited to be used as repository migration targets. Users should upgrade to 0.12.5 or the latest 0.13.0+dev. ### Workarounds Run Gogs in its own private network. ### References https://www.huntr.dev/bounties/327797d7-ae41-498f-9bff-cc0bf98cf531/ ### For more information If you have any questions or comments about this advisory, please post on #6754.
- Published
- Mar 14, 2022
- Updated
- Aug 21, 2024
- EPSS
- —
- CWE
- CWE-918
Report tools
Action score
20
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Go | gogs.io/gogs | pkg:golang/gogs.io/gogs |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | gogs.io/gogs | before 0.12.5 | 0.12.5 |
Same product
Go: all recordsOther highest-scoring records for the same primary product.
- GHSA-26gq-grmh-6xm6Gogs vulnerable to Stored XSS via Mermaid diagrams29Monitor
- GO-2026-5193Gogs: XSS in .ipynb files renderer due to outdated notebookjs in gogs.io/gogs0Monitor
- GHSA-6vxv-wg6j-5qwpGogs: XSS in .ipynb files renderer due to outdated notebookjs0Monitor
Published before and after this one in the same product
- Later →GHSA-pj96-4jhv-v792Jun 2, 2022 · Cross site scripting via cookies in gogs0Monitor
- Later →GO-2022-0377Aug 21, 2024 · SSRF in repository migration in gogs.io/gogs0Monitor
- Later →GO-2022-0473Aug 21, 2024 · Cross site scripting via cookies in gogs in gogs.io/gogs0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:gogs.io/gogs | 0.12.5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.