Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ZAP HUD broken after emptying browser cache #1349

Open
1 task
2m4d2bs4d opened this issue Jan 9, 2024 · 1 comment
Open
1 task

ZAP HUD broken after emptying browser cache #1349

2m4d2bs4d opened this issue Jan 9, 2024 · 1 comment
Labels

Comments

@2m4d2bs4d
Copy link

2m4d2bs4d commented Jan 9, 2024

Describe the bug

Reproducible bug: When using the integrated browser with the HUD, the HUD words fine. However after emtpying the browser cache, the Tools disappear, there are only the green + signs on the left and right. However they don't list tools anymore when clicked on. The underlying software analyzing potential security flaws while browsing still works though.
Workaround is Tools -> Options -> Reset to Factory Defaults, this fixes the HUD, however you lose your config this way so it is no durable solution.
Using kali linux.

Thank you for your help :)

Steps to reproduce the behavior

  1. run integrated firefox browser from zaproxy.
  2. do zaproxy stuff.
  3. clear browser cache.
  4. close integrated browser.
  5. open integrated browser again and surf to any page.
  6. HUD welcome screen appears but disappears quickly by itself. You will see + on the left and right and you will see that all the tools, spider, attack mode, etc. are not visible. Clicking on the + signs will also show empty tool lists. Clicking on the bottom right buttons to reset config etc. will not have positive effect on this issue.

Expected behavior

The ZAP HUD should also work after emptying the browser cache.

Software versions

ZAP
Version: 2.14.0

Installed Add-ons: [[id=accessControl, version=9.0.0],
[id=alertFilters, version=19.0.0], [id=ascanrules,
version=59.0.0], [id=attacksurfacedetector, version=1.1.4],
[id=authhelper, version=0.10.0], [id=automation,
version=0.34.0], [id=bruteforce, version=15.0.0],
[id=callhome, version=0.10.0], [id=commonlib,
version=1.20.0], [id=custompayloads, version=0.13.0],
[id=database, version=0.3.0], [id=diff, version=14.0.0],
[id=directorylistv1, version=7.0.0], [id=directorylistv2_3,
version=4.0.0], [id=directorylistv2_3_lc, version=4.0.0],
[id=domxss, version=18.0.0], [id=encoder, version=1.4.0],
[id=evalvillain, version=0.3.0], [id=exim, version=0.8.0],
[id=fileupload, version=1.2.1], [id=formhandler,
version=6.5.0], [id=fuzz, version=13.12.0], [id=fuzzdb,
version=9.0.0], [id=fuzzdboffensive, version=4.0.0],
[id=gettingStarted, version=16.0.0], [id=graaljs,
version=0.5.0], [id=graphql, version=0.22.0], [id=help,
version=17.0.0], [id=hud, version=0.18.0], [id=invoke,
version=14.0.0], [id=jsonview, version=3.0.0], [id=jwt,
version=1.0.3], [id=network, version=0.13.0], [id=oast,
version=0.17.0], [id=onlineMenu, version=12.0.0],
[id=openapi, version=38.0.0], [id=packpentester,
version=0.1.0], [id=postman, version=0.2.0], [id=pscanrules,
version=53.0.0], [id=quickstart, version=43.0.0],
[id=replacer, version=16.0.0], [id=reports, version=0.27.0],
[id=requester, version=7.4.0], [id=retest, version=0.8.0],
[id=retire, version=0.29.0], [id=reveal, version=7.0.0],
[id=scripts, version=44.0.0], [id=selenium,
version=15.16.0], [id=soap, version=21.0.0], [id=spider,
version=0.8.0], [id=spiderAjax, version=23.18.0],
[id=sqliplugin, version=15.0.0], [id=tips, version=12.0.0],
[id=viewstate, version=3.0.0], [id=wappalyzer,
version=21.29.0], [id=webdriverlinux, version=69.0.0],
[id=websocket, version=30.0.0], [id=zest, version=43.0.0]]

Operating System: Linux
Architecture: amd64
Java Version: Debian 17.0.10-ea
System's Locale: en_US
Display Locale: en_GB
Format Locale: en_US
Default Charset: UTF-8
[...]
Look and Feel: FlatLaf Light (com.formdev.flatlaf.FlatLightLaf)

Screenshots

No response

Errors from the zap.log file

No response

Additional context

No response

Would you like to help fix this issue?

  • Yes
@2m4d2bs4d 2m4d2bs4d added the bug label Jan 9, 2024
@psiinon psiinon transferred this issue from zaproxy/zaproxy Jan 9, 2024
@psiinon
Copy link
Member

psiinon commented Jan 9, 2024

Dont clear the browser cache then? 😛
Actually this is very helpful - I've seen this happen intermittently but its hard to reproduce. If this does allow us to reproduce it consistently then it should help us to diagnose the underlying problem more easily.

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

No branches or pull requests

2 participants