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

Wappalyzer - crawling of resources on a website #4020

Open
stephanie0x00 opened this issue Jan 9, 2025 · 0 comments
Open

Wappalyzer - crawling of resources on a website #4020

stephanie0x00 opened this issue Jan 9, 2025 · 0 comments
Assignees
Labels
bug Something isn't working discussion

Comments

@stephanie0x00
Copy link
Contributor

stephanie0x00 commented Jan 9, 2025

Describe the bug
The very first wappalyzer performed some kind of crawling on websites to find software and it's versions. However this version was outdated and didn't provide any proof of how the data was gathered for reproducibility. The newer versions of our wappalyzer implementation do not crawl all page of a website, thus software instances and it's versions are often missed, as these are often found in external files (e.g. https://example.com/js/core.js contains the string jQuery 1.2.3).

Issue identified with #3800.

The question now is:

  • How are we going to crawl the resources?
  • What depth are we going to crawl?
  • What scopes?
  • Others?

Expected behavior
Some kind of crawling should be performed to identify these files and check for software and software versions.

OpenKAT version
main

@stephanie0x00 stephanie0x00 added bug Something isn't working discussion labels Jan 9, 2025
@github-project-automation github-project-automation bot moved this to Incoming features / Need assessment in KAT Jan 9, 2025
@stephanie0x00 stephanie0x00 moved this from Incoming features / Need assessment to To be discussed in KAT Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working discussion
Projects
Status: To be discussed
Development

No branches or pull requests

2 participants