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
The "IP address has changed" functionality is dodgy. Worse, when allow_reverse_proxy is used, the X-Forwarded-For header is trusted implicitly without validation.
BeEF::Core::Logger.instance.register('Zombie',"IP address has changed from #{hooked_browser.ip} to #{request.env['HTTP_X_FORWARDED_FOR']}",hooked_browser.id.to_s)
The "IP address has changed" functionality is dodgy. Worse, when
allow_reverse_proxy
is used, theX-Forwarded-For
header is trusted implicitly without validation.beef/core/main/handlers/hookedbrowsers.rb
Lines 93 to 102 in 943a6fd
Here's an example someone provided, showing that the stored IP address contains two IP addresses separated by
,
.It may also result in many "IP address has changed" events in load balanced environments. Although I'm not sure that this is avoidable.
The text was updated successfully, but these errors were encountered: