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

Allow custom technology mapping for wappalyzer data #1796

Merged
merged 5 commits into from
Apr 7, 2022

Conversation

Ice3man543
Copy link
Member

@Ice3man543 Ice3man543 commented Apr 1, 2022

Proposed changes

With a wappalyzer-mapping.yml file in nuclei-templates repository, it will be read when using auto-scan feature and will use custom mapping names.

Example file -

> ~/nuclei-templates: cat wappalyzer-mapping.yml
node.js: nodejs
echo https://example.com | ./nuclei -as -v -vv

                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   2.6.5

		projectdiscovery.io

[WRN] Use with caution. You are responsible for your actions.
[WRN] Developers assume no liability and are not responsible for any misuse or damage.
[INF] Using Nuclei Engine 2.6.5 (latest)
[INF] Using Nuclei Templates 8.9.4 (latest)
[INF] Templates added in last update: 20
[INF] Templates loaded for scan: 3120
[VER] Normalized mapping (1): map[node.js:nodejs]
[INF] Executing wappalyzer based tech detection on input URLs

Checklist

  • Pull request is created against the dev branch
  • All checks passed (lint, unit/integration/regression tests etc.) with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

@Ice3man543 Ice3man543 self-assigned this Apr 1, 2022
@Ice3man543 Ice3man543 linked an issue Apr 1, 2022 that may be closed by this pull request
@Ice3man543 Ice3man543 added the Status: Review Needed The issue has a PR attached to it which needs to be reviewed label Apr 1, 2022
@ehsandeep ehsandeep merged commit 5ddc37e into dev Apr 7, 2022
@ehsandeep ehsandeep deleted the technology-mapping branch April 7, 2022 12:25
@ehsandeep ehsandeep added Status: Completed Nothing further to be done with this issue. Awaiting to be closed. and removed Status: Review Needed The issue has a PR attached to it which needs to be reviewed labels Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Configurable tech to tags mapping for automatic scan
2 participants