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

JARM and ja3 output don't exist in Nuclei Engine #3403

Closed
pussycat0x opened this issue Mar 10, 2023 · 2 comments · Fixed by #3906
Closed

JARM and ja3 output don't exist in Nuclei Engine #3403

pussycat0x opened this issue Mar 10, 2023 · 2 comments · Fixed by #3906
Assignees
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Enhancement Most issues will probably ask for additions or changes.

Comments

@pussycat0x
Copy link

pussycat0x commented Mar 10, 2023

Please describe your feature request:

TLSX has jarm and ja3 output support, but Nuclei engine doesn't have.

"jarm_hash": ""
"ja3_hash": ""

echo "google.com" | tlsx -ja3 -jarm

  _____ _    _____  __
 |_   _| |  / __\ \/ /
   | | | |__\__ \>  < 
   |_| |____|___/_/\_\	v1.0.5

		projectdiscovery.io

google.com:443 [27d40d40d29d40d1dc42d43d00041d4689ee210389f4f6b4b5b1b93f92252d] [a4f7219fbfd4687a8a1bc1e648517be2]

Proposed implementation in ssl templates:

- address: "{{Host}}:{{Port}}"
    probes:
      - ja3
      - jarm
@pussycat0x pussycat0x added the Type: Enhancement Most issues will probably ask for additions or changes. label Mar 10, 2023
@Mzack9999
Copy link
Member

Mzack9999 commented Jul 3, 2023

Notes:

  • ja3 doesn't seem to be very helpful as it's related to the client
  • jarm requires lots of probes. Hence it might be implemented as a helper function like jarm() to minimize the execution time, and the result stored in some internal kv cache to avoid recalculating it multiple times

@Mzack9999 Mzack9999 self-assigned this Jul 5, 2023
@Mzack9999 Mzack9999 linked a pull request Jul 5, 2023 that will close this issue
4 tasks
@Mzack9999 Mzack9999 added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Aug 11, 2023
@Mzack9999
Copy link
Member

Indirectly completed via #3906

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. Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants