Skip to content

Conversation

@prateekrana-getastra
Copy link

The Alert Description states about leaking version information via the http header. The previous version for the script only checks for the header without considering whether even the version is leaked or not. Added checks for looking up numeric versions information available in the http header.

@thc202 thc202 changed the title Added Functional checks to match the script to the alert description. Check for the version in Server Header Disclosure  Jun 29, 2022
@thc202
Copy link
Member

thc202 commented Jul 3, 2022

The changelog should be updated.

@lgtm-com
Copy link

lgtm-com bot commented Jul 4, 2022

This pull request introduces 1 alert when merging b11a4b9 into d4d4b92 - view on LGTM.com

new alerts:

  • 1 for Unreachable statement

@prateekrana-getastra
Copy link
Author

The changelog should be updated.

Changes to be added under Unreleased?

@kingthorin
Copy link
Member

Yes, for this one: Under Unreleased, in the ### Changed section.

@prateekrana-getastra
Copy link
Author

Anything else to update?

@kingthorin kingthorin force-pushed the version-leak-found branch 2 times, most recently from 6dd9465 to 7913cd1 Compare July 7, 2022 11:49
Signed-off-by: Prateek rana <prateekrana1519@gmail.com>
@kingthorin kingthorin force-pushed the version-leak-found branch from 7913cd1 to 91f22e8 Compare July 7, 2022 11:56
@kingthorin
Copy link
Member

⚠️ Please don't make any further changes without resetting your local copy first:

git fetch origin
git reset --hard origin/version-leak-found

@thc202 thc202 merged commit 9fe8c62 into zaproxy:main Jul 7, 2022
@thc202
Copy link
Member

thc202 commented Jul 7, 2022

Thank you both!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants