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

cve-annotate is not working #3782

Closed
ehsandeep opened this issue Jun 5, 2023 · 0 comments · Fixed by #3788
Closed

cve-annotate is not working #3782

ehsandeep opened this issue Jun 5, 2023 · 0 comments · Fixed by #3788
Assignees
@RamanaReddy0M
Labels
Priority: High After critical issues are fixed, these should be dealt with before any further issues. 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
nuclei v2.9.7

Comments

@ehsandeep
Copy link
Member

cve-annotate version:

latest

Current Behavior:

cve-annotate failed to annotate cve templates.

Expected Behavior:

Populating cves related information to cve templates.

Steps To Reproduce:

id: CVE-2023-0968

info:
  name: Test HTTP Template
  author: pdteam
  severity: info

http:
  - method: GET
    path:
      - "{{BaseURL}}"
cve-annotate -i test.yaml

Note:

  • Currently, only max-request is being populated.
  • Currently, cve-annotate uses nvd lib to populate cve-related information instead now it can be replaced with templateman's enhance api.
@ehsandeep ehsandeep added Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. Priority: High After critical issues are fixed, these should be dealt with before any further issues. labels Jun 5, 2023
@RamanaReddy0M RamanaReddy0M linked a pull request Jun 6, 2023 that will close this issue
Use templateman enhance api to populate CVE info #3788
Merged
@RamanaReddy0M RamanaReddy0M mentioned this issue Jun 6, 2023
Merged
@ehsandeep ehsandeep added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Jun 21, 2023
@ehsandeep ehsandeep added this to the nuclei v2.9.7 milestone Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RamanaReddy0M RamanaReddy0M

Labels
Priority: High After critical issues are fixed, these should be dealt with before any further issues. 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
nuclei v2.9.7
Development

Successfully merging a pull request may close this issue.

Use templateman enhance api to populate CVE info projectdiscovery/nuclei
2 participants
@ehsandeep @RamanaReddy0M