TheHive-Project / TheHive-Project/Cortex-Analyzers
vulnerabilities in wkhtmltopdf [emlparser]
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 490
- Forks
- 405
- Avg merge
- 2d 43m
- Merged PRs (30d)
- 8
Description
Describe the bug
Please remove vulnerable version of wkhtmltopdf (this project is abadoned and there are multiple rce/ssrf vulnerabilities)
ref: A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
- step 1
- step 2
- step 3...
Expected behavior
A clear and concise description of what you expected to happen.
Complementary information
If applicable, add screenshots and any additional information that might help explain your problem.
Work environment
- Client OS:
- Server OS:
- Browse type and version:
- Cortex version:
- Cortex Analyzer/Responder name:
- Cortex Analyzer/Responder version:
Possible solutions
If applicable, indicate possible solutions to the problem.
Additional context
Add any other context about the problem here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the emlparser context and wkhtmltopdf, but no file, test, or entry point is specified. Start by locating the emlparser use of wkhtmltopdf and reviewing the linked upstream report; done means the vulnerable version is removed or replaced without breaking the affected analyzer.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100