Scope location and endpoint reference writes to authorized products#15300
Open
svader0 wants to merge 1 commit into
Open
Scope location and endpoint reference writes to authorized products#15300svader0 wants to merge 1 commit into
svader0 wants to merge 1 commit into
Conversation
svader0
force-pushed
the
harden-location-reference-authz
branch
2 times, most recently
from
July 21, 2026 07:26
88d6aff to
0a9d535
Compare
svader0
marked this pull request as ready for review
July 21, 2026 07:34
|
This pull request contains a critical finding where a sensitive codepath file,
🔴 Configured Sensitive Codepath Modified by Non-Allowed Author in
|
| Vulnerability | Configured Sensitive Codepath Modified by Non-Allowed Author |
|---|---|
| Description | File 'dojo/api_v2/serializers.py' matches configured sensitive codepath pattern 'dojo/api_v2/*.py' and was modified by 'svader0' (commit b435880) who is not in the allowed authors list. |
We've notified @mtesauro.
Comment to provide feedback on these findings.
Report false positive: @dryrunsecurity fp [FINDING ID] [FEEDBACK]
Report low-impact: @dryrunsecurity nit [FINDING ID] [FEEDBACK]
Example: @dryrunsecurity fp drs_90eda195 This code is not user-facing
All finding details can be found in the DryRun Security Dashboard.
Hardening to object-level authorization on several API and UI write paths that associate locations and endpoints with findings and products. These paths now restrict the selectable references to the objects the requesting user is authorized for, matching the scoping the UI forms and dedicated viewsets already apply. Adds regression tests. No functional change for correctly-permissioned users.
svader0
force-pushed
the
harden-location-reference-authz
branch
from
July 21, 2026 15:46
0a9d535 to
b435880
Compare
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.
Hardening and consistency improvement to object-level authorization on several API and UI write paths that associate locations and endpoints with findings and products.
These paths now restrict the selectable references to objects the requesting user is authorized for, matching the scoping the UI forms and dedicated viewsets already apply. No functional change for correctly-permissioned users.
Adds regression tests covering same-product (allowed) and cross-product (rejected) writes.