String Based Filtering: Follow on for #10038 #10050
DryRun Security
Details
Authn/Authz Analyzer Findings: 16 detected
⚠️ Potential Authn/Authz Function Used or Modified dojo/endpoint/views.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code contains the function get_authorized_endpoints() , which suggests that it is responsible for determining the list of endpoints that the user is authorized to access. This function is likely part of the authentication or authorization mechanism of the application. |
Filename | dojo/endpoint/views.py |
CodeLink | django-DefectDojo/dojo/endpoint/views.py Lines 42 to 54 in 9d12461 |
⚠️ Potential Authn/Authz Function Used or Modified dojo/endpoint/views.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code includes the user_is_authorized decorator from the dojo.authorization.authorization_decorators module, which suggests that the code contains functions related to authorization. Additionally, the Permissions class from the dojo.authorization.roles_permissions module is imported, which also indicates the presence of authorization-related functionality. |
Filename | dojo/endpoint/views.py |
CodeLink | django-DefectDojo/dojo/endpoint/views.py Lines 12 to 23 in 9d12461 |
⚠️ Potential Authn/Authz Function Used or Modified dojo/engagement/views.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code includes the following functions that are commonly associated with authentication or authorization in web applications: PermissionDenied and HttpResponseRedirect . The PermissionDenied exception is typically raised when a user tries to access a resource they are not authorized to access, and HttpResponseRedirect is often used to redirect users to a login page or other authentication-related page. |
Filename | dojo/engagement/views.py |
CodeLink | django-DefectDojo/dojo/engagement/views.py Lines 15 to 21 in 9d12461 |
⚠️ Potential Authn/Authz Function Used or Modified dojo/filters.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code contains functions related to authentication and authorization, such as get_authorized_products() and get_authorized_users() , which are used to filter the queryset based on user permissions. These functions indicate that the code is handling access control and user authorization. |
Filename | dojo/filters.py |
CodeLink | django-DefectDojo/dojo/filters.py Lines 865 to 922 in 9d12461 |
⚠️ Potential Authn/Authz Function Used or Modified dojo/filters.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code contains two functions that appear to be related to authentication or authorization: get_authorized_users() and Permissions.Product_Type_View . The get_authorized_users() function seems to be used to filter the queryset of users based on their permissions, which suggests that it is related to authorization. The Permissions.Product_Type_View variable also suggests the existence of a permissions system, which is typically used for authorization. |
Filename | dojo/filters.py |
CodeLink | django-DefectDojo/dojo/filters.py Lines 1055 to 1098 in 9d12461 |
⚠️ Potential Authn/Authz Function Used or Modified dojo/filters.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code contains a ProductFilter class that has an __init__ method that takes a user parameter. This suggests that the user parameter is used for authentication or authorization purposes, potentially to restrict the available product types that the user can view. Additionally, the get_authorized_product_types function is called in the __init__ method, which further indicates that the code is handling authentication or authorization logic. |
Filename | dojo/filters.py |
CodeLink | django-DefectDojo/dojo/filters.py Lines 1174 to 1234 in 9d12461 |
⚠️ Potential Authn/Authz Function Used or Modified dojo/filters.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code contains functions related to authentication and authorization, such as get_authorized_engagements() and get_authorized_product_types() . These functions likely perform checks to ensure the user has the necessary permissions to access the requested resources. |
Filename | dojo/filters.py |
CodeLink | django-DefectDojo/dojo/filters.py Lines 2118 to 2222 in 9d12461 |
⚠️ Potential Authn/Authz Function Used or Modified dojo/filters.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code contains a reporter and reviewers field in the FindingFilter class, which suggests that these fields are used to filter findings based on the user who reported or reviewed them. This indicates that the code may contain functions related to authentication or authorization, as the Dojo_User model is likely used to represent users who can report or review findings. |
Filename | dojo/filters.py |
CodeLink | django-DefectDojo/dojo/filters.py Lines 1694 to 1700 in 9d12461 |
⚠️ Potential Authn/Authz Function Used or Modified dojo/filters.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code contains a function called get_authorized_endpoints that appears to be related to authorization. This function is used in the qs property of the EndpointFilterWithoutObjectLookups class, which suggests that it is used to filter the queryset based on the user's permissions. Additionally, the user attribute is set in the __init__ method of the class, which indicates that the user's information is being used in the filtering process. |
Filename | dojo/filters.py |
CodeLink | django-DefectDojo/dojo/filters.py Lines 2514 to 2537 in 9d12461 |
⚠️ Potential Authn/Authz Function Used or Modified dojo/metrics/views.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code includes the import statement for Dojo_User , which suggests the presence of user-related functionality, potentially including authentication and authorization mechanisms. |
Filename | dojo/metrics/views.py |
CodeLink | django-DefectDojo/dojo/metrics/views.py Lines 20 to 32 in 9d12461 |
⚠️ Potential Authn/Authz Function Used or Modified dojo/metrics/views.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code contains the function 'get_authorized_endpoint_status' which is likely related to authorization. This function appears to be checking the permissions of the user to view the endpoints based on the 'Permissions.Endpoint_View' permission. This suggests that the code is handling authentication and authorization mechanisms. |
Filename | dojo/metrics/views.py |
CodeLink | django-DefectDojo/dojo/metrics/views.py Lines 228 to 237 in 9d12461 |
⚠️ Potential Authn/Authz Function Used or Modified dojo/product/views.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code contains a reference to request.user , which is likely used for authentication or authorization purposes. The ProductFilterWithoutObjectLookups and ProductFilter classes may also contain functions related to authentication or authorization, as they are used to filter the product queryset based on the current user. |
Filename | dojo/product/views.py |
CodeLink | django-DefectDojo/dojo/product/views.py Lines 78 to 86 in 9d12461 |
⚠️ Potential Authn/Authz Function Used or Modified dojo/reports/views.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code imports the Dojo_User model, which is likely related to authentication and authorization functionality in the web application. The Dojo_User model is likely used to represent user accounts and manage user-related operations, such as authentication and authorization. |
Filename | dojo/reports/views.py |
CodeLink | django-DefectDojo/dojo/reports/views.py Lines 17 to 23 in 9d12461 |
⚠️ Potential Authn/Authz Function Used or Modified dojo/product/views.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code contains the @user_is_authorized decorator, which is likely used to check if the user is authorized to access the view_engagements function. This function is related to authentication and authorization, as it involves handling user access control for the product engagements view. |
Filename | dojo/product/views.py |
CodeLink | django-DefectDojo/dojo/product/views.py Lines 654 to 689 in 9d12461 |
⚠️ Potential Authn/Authz Function Used or Modified dojo/reports/views.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code contains a reference to request.user , which suggests that it is handling user-specific information and may involve authentication or authorization functions. The EndpointFilter and EndpointFilterWithoutObjectLookups classes also suggest that the code is dealing with access control and authorization of users to access certain endpoints or resources. |
Filename | dojo/reports/views.py |
CodeLink | django-DefectDojo/dojo/reports/views.py Lines 63 to 71 in 9d12461 |
⚠️ Potential Authn/Authz Function Used or Modified dojo/reports/widgets.py (click for details)
Type | Potential Authn/Authz Function Used or Modified |
Description | The code contains the user parameter and the request.user object, which are typically used for authentication and authorization purposes in web applications. The EndpointFilter and EndpointFilterWithoutObjectLookups classes may also be involved in the authorization process, as they are used to filter the Endpoint objects based on the user's permissions or access control settings. |
Filename | dojo/reports/widgets.py |
CodeLink | django-DefectDojo/dojo/reports/widgets.py Lines 407 to 415 in 9d12461 |