[GHSA-5hjh-c26m-xw8w] github.com/hoppscotch/proxyscotch: patched version 1.0.0 does not exist on the registry; the fix is in 0.1.0 - #9386
Open
zyl71 wants to merge 1 commit into
Conversation
…ion 1.0.0 does not exist on the registry; the fix is in 0.1.0
github-actions
Bot
changed the base branch from
main
to
zyl71/advisory-improvement-9386
September 7, 2026 04:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
Comments
Current record: Go:github.com/hoppscotch/proxyscotch: introduced=0 fixed=1.0.0
Proposed: Go:github.com/hoppscotch/proxyscotch: introduced=0 fixed=0.1.0
The record's fixed version 1.0.0 does not exist. There is no v1.0.0 tag in the repository, proxy.golang.org returns "unknown revision v1.0.0" for .info, .mod and .zip, and pkg.go.dev lists only v0.1.0, v0.1.1, v0.1.3 and v0.1.4. A stale sum.golang.org entry (record #10425204, older than v0.1.0's #11309308) shows a v1.0.0 tag was published once and later removed. Because every published version sorts below 1.0.0, the current range flags every real release, including the latest 0.1.4, as vulnerable.
The referenced fix commit de67380f ("ability to have a blacklist of target urls for proxy to make calls to", 2022-01-24) is an ancestor of v0.1.0 (compare v0.1.0...de67380f = behind, ahead_by 0) and is not in v0.0.1 (ahead, ahead_by 45). The v0.1.0 module zip contains isAllowedDest and the -banned-dests flag; the v0.0.1 zip contains neither. v0.0.1 (2020-06-09) is the only release before v0.1.0 (2022-06-03), so 0 -> 0.1.0 covers every affected version. Snyk records the same range ("<0.1.0", "Upgrade to version 0.1.0 or higher"). The v0.1.0 release notes mention only Apple Silicon/arm64 builds and Go 1.18, not the SSRF fix.
Evidence:
Happy to adjust if the maintainers intend otherwise.