You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In an effort to standardize defaults loading when upgrading our Rails monolith, we ended up moving the code that calls load_defaults into a separate class and file that gets required and used in config/application.rb. It seems like Brakeman is unable to determine the defaults and overrides in this case e.g. we see cross-site forgery warnings despite config.action_controller.default_protect_from_forgery evaluating to true.
Describe the solution you'd like
An option to provide a list of additional config files to check alongside config/application.rb, config/environments/production.rb etc.:
Is your feature request related to a problem? Please describe.
In an effort to standardize defaults loading when upgrading our Rails monolith, we ended up moving the code that calls
load_defaults
into a separate class and file that gets required and used inconfig/application.rb
. It seems like Brakeman is unable to determine the defaults and overrides in this case e.g. we see cross-site forgery warnings despiteconfig.action_controller.default_protect_from_forgery
evaluating totrue
.Describe the solution you'd like
An option to provide a list of additional config files to check alongside
config/application.rb
,config/environments/production.rb
etc.:brakeman/lib/brakeman/scanner.rb
Lines 171 to 200 in 88994b8
Describe alternatives you've considered
No workaround as far as I can tell.
Additional context
Brakeman version: 6.2.1
Rails version: 7.0.8.4 loading 6.1 defaults
Ruby version: 3.3.6
The text was updated successfully, but these errors were encountered: