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.

Sign up for GitHub

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

Jump to bottom

nuclei variable seems to parse numbers differently #1497

Closed
No-Github opened this issue Jan 17, 2022 · 1 comment · Fixed by #1516
Closed

nuclei variable seems to parse numbers differently #1497

No-Github opened this issue Jan 17, 2022 · 1 comment · Fixed by #1516
Assignees
@Mzack9999
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Milestone
v2.6.0

Comments

@No-Github
Copy link

No-Github commented Jan 17, 2022 •
edited
Loading

Nuclei version:

2.5.8

Current Behavior:

id: test

info:
  name: test
  author: ffffffff0x
  severity: info
  tags: test

requests:
  - method: GET
    path:
      - "{{BaseURL}}/{{123123}}"
      - "{{BaseURL}}/{{aaabbb}}"
      - "{{BaseURL}}/{{123*123}}"
      - "{{BaseURL}}/{{123!123}}"

    skip-variables-check: true

image

Expected Behavior:

GET /%7B%7B123123%7D%7D HTTP/1.1
Host: 127.0.0.1
User-Agent: Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36
Connection: close
Accept: */*
Accept-Language: en
Accept-Encoding: gzip

GET /%7B%7Baaabbb%7D%7D HTTP/1.1
Host: 127.0.0.1
User-Agent: Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36
Connection: close
Accept: */*
Accept-Language: en
Accept-Encoding: gzip

GET /%7B%7B123*123%7D%7D HTTP/1.1
Host: 127.0.0.1
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.137 Safari/4E423F
Connection: close
Accept: */*
Accept-Language: en
Accept-Encoding: gzip

GET /%7B%7B123%21123%7D%7D HTTP/1.1
Host: 127.0.0.1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36
Connection: close
Accept: */*
Accept-Language: en
Accept-Encoding: gzip

Steps To Reproduce:

Anything else:
@No-Github No-Github added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Jan 17, 2022
@Mzack9999 Mzack9999 self-assigned this Jan 17, 2022
@Mzack9999 Mzack9999 added the Status: In Progress This issue is being worked on, and has someone assigned. label Jan 17, 2022
@Mzack9999 Mzack9999 linked a pull request Jan 19, 2022 that will close this issue
Implementing lexer with runtime expression validation #1516
Merged
4 tasks
@ehsandeep ehsandeep added Status: Review Needed The issue has a PR attached to it which needs to be reviewed Status: Completed Nothing further to be done with this issue. Awaiting to be closed. and removed Status: In Progress This issue is being worked on, and has someone assigned. Status: Review Needed The issue has a PR attached to it which needs to be reviewed labels Jan 25, 2022
@ehsandeep
Copy link
Member

@No-Github this is now fixed in the dev version, thanks for reporting this.

@ehsandeep ehsandeep added this to the v2.6.0 milestone Feb 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Mzack9999 Mzack9999

Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Milestone
v2.6.0
Development

Successfully merging a pull request may close this issue.

Implementing lexer with runtime expression validation projectdiscovery/nuclei
3 participants
@ehsandeep @Mzack9999 @No-Github