-
Notifications
You must be signed in to change notification settings - Fork 12
fix: Dockerfile entrypoint #96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
6f2c96a
trigger always ci
Lodek dc97060
remove pipe in entrypoint
Lodek ec436fb
fix entrypoint
Lodek ac899cd
Merge branch 'dev' into fix/df-perms
Lodek e86ac62
Update docker-publish.yml
Lodek fb99ab9
Update docker-publish.yml
Lodek bcab643
test: improve docker tests to use testcontainers
Lodek a5bca5b
Merge remote-tracking branch 'origin/dev' into fix/df-perms
Lodek File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
What is the latest version of google.golang.org/grpc and which versions fix the authorization bypass vulnerability GHSA-p77j-4mvh-x3m3?💡 Result:
The latest version of google.golang.org/grpc is v1.79.3 (released 2026-03-17). This version fixes the authorization bypass vulnerability GHSA-p77j-4mvh-x3m3. Affected versions are those below v1.79.3; upgrade to v1.79.3 or newer.
Citations:
Upgrade
google.golang.org/grpcto v1.79.3 or later to fix authorization bypass vulnerability.The current version v1.76.0 contains GHSA-p77j-4mvh-x3m3 (CVE GO-2026-4762), a critical authorization bypass vulnerability in the
:pathheader validation. Upgrade to v1.79.3 or newer to resolve this issue.🧰 Tools
🪛 OSV Scanner (2.3.5)
[CRITICAL] 61-61: google.golang.org/grpc 1.76.0: Authorization bypass in gRPC-Go via missing leading slash in :path in google.golang.org/grpc
(GO-2026-4762)
[CRITICAL] 61-61: google.golang.org/grpc 1.76.0: gRPC-Go has an authorization bypass via missing leading slash in :path
(GHSA-p77j-4mvh-x3m3)
🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this suggestion is valid
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@iverc, confirmed. This is an Authorization Bypass (CWE-285) resulting from Improper Input Validation of the HTTP/2:pathpseudo-header — the gRPC-Go server accepted requests where:pathomitted the mandatory leading slash (e.g.,Service/Methodinstead of/Service/Method). While the server successfully routed these requests to the correct handler, authorization interceptors evaluated the raw, non-canonical path string, causing "deny" rules defined using canonical paths to fail to match, allowing requests to bypass the policy if a fallback "allow" rule was present.The advisory has a CVSS score of 9.1 (Critical). All versions of
google.golang.org/grpcbelow v1.79.3 are affected, and v1.79.3 is the patched release.Here's the fix for
go.mod:Then run: