ProxyDisclosureScanRule reporting is confusing for cases where servers freely offer X-Forwarded-*
text
#8556
Labels
add-on
backlog
Issues that the Core Team think are higher priority and would like to work on given time
FalsePositive
Describe the bug
I have a server which will freely respond with
x-forwarded
headers: https://api.test.glaypen.garnercorp.com/say-what-you-wantWhen the ProxyDisclosureScanRule rule runs, it will generate this report item:
There are a number of problems with this text...
is grammatically broken and otherwise muddled.
Removing words might help a bit...
Removing one word probably yields the opposite of the intended meaning:
at this point, changing
detected
,prevented
, andmitigated
to other things could enable the sentence to make sense in context, maybe.So, nothing has actually been identified, which is very confusing/misleading/unhelpful. It took reading the code and hunting around to figure out what the component was actually thinking.
This turned out to be an incredibly large red-herring -- nothing about what was discovered had anything to do with
TRACE
,OPTIONS
,Max-Forwards
orTRACK
.Steps to reproduce the behavior
Expected behavior
As the logic has not identified anything relating to
TRACE
,OPTIONS
orTRACK
, and as the logic has not (successfully) relied onMax-Forwards
, the message should clearly indicate what is actually bothering the rule (which is apparently the presence of one or moreX-Forwarded-
headers).Software versions
macOS Sonoma 14.5
ZAP 2.15.0
I can't tell if ProxyDisclosureScanRule is a built-in -- the add-ons manager isn't showing it to me...
Screenshots
Errors from the zap.log file
The log has lots of errors (including hilarious errors from 2022), but nothing particularly relevant.
Additional context
https://github.com/zaproxy/zap-extensions/blob/2708148f2fae6b8e75ea45d5a89d16ccc3c2e756/addOns/ascanrulesBeta/src/main/java/org/zaproxy/zap/extension/ascanrulesBeta/ProxyDisclosureScanRule.java#L101-L120
Would you like to help fix this issue?
The text was updated successfully, but these errors were encountered: