-
Notifications
You must be signed in to change notification settings - Fork 267
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
Jira Module (Cloud) #201
Comments
Hi @butsh :) I understand that the error appears as in "main", but that is because the function crashed and went backwards with the error that caused the issue to the main function. It doesn't seem to be a part of the jira module code on first sight though, as the only place where the Could you run VulnWhisperer again with the "-d" debug flag to see the rest of the execution trail? Glad you are testing the module! Cheers! Edit: Didn't notice the (Cloud) part, it could bring up some untested issues that I didn't see in local but we'll see once we understand this specific issue. |
Hi @qmontal ~$ vuln_whisperer -c /home/ubuntu/VulnWhisperer/configs/frameworks.ini -s jira -d |
Hi @butsh! The problem is that, I don't know which value is in your config file in the jira:dns_resolv variable, but it should be either "True" or "False", but the content is caught as float for Python, and when trying to operate and parse it to normalize the values, it breaks because a float can't be treated as a string. The issue is in this line of code. You will have to review the value of the variable and change it to whatever fits you; I don't know if it is well documented, but what that variable does is enabling host resolution (from the vulnwhisperer server) of the assets with vulnerabilities comming from the scanners that DON'T have any hostname. Cheers! |
The following error appears during running jira section:
ERROR:root:main:'float' object has no attribute 'replace'
ERROR: 'float' object has no attribute 'replace'
The nessus section ran perfectly
Ubuntu server 18.04.03 LTS
Python 2.7.15
The text was updated successfully, but these errors were encountered: