-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Vulnerability created via API is empty #68
Comments
I'll take a look this week. |
Thanks, no rush! In the meantime I am using MongoDB and some scripting to directly update the db. |
Hi @summitt did you by any chance had the time to have a look at that? |
I've been a bit backlogged on other projects at the moment. I hope to get to is early next week. |
@ptrac3 Newest release fixes this issue. Take note that we made updates to our password hashing as part of other updates we have been making, which means you'll need to reset your password in the system after you upgrade. |
I hope this is the right place to ask and, if by any chance, you recognise I have missed something and/or this is not the right place to ask feel free to delete this message.
I was trying to add vulnerabilities the available documentation at https://docs.factionsecurity.com/Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/ by using JSON with the following payload:
curl -X 'POST'
'http://localhost:8080/api/vulnerabilities/default'
-H 'accept: application/json'
-H 'FACTION-API-KEY: API_KEY'
-H 'Content-Type: application/json'
-d '[
{
"Name": "This_is_a_test",
"CategoryName": "Unvalidated Input",
"Description": "Description",
"Recommendation": "Recommendation",
"LikelihoodId": 4,
"ImpactId": 4,
"SeverityId": 4,
"Active": true
}
]'
This request will result in the creation of the vulnerability but, as you can see from the screenshot, it will not include any of the details provided. Did I miss something?
I also tried changing the name of the parameters (in the web UI for example the Likelihood parameters is "Likelyhood") but it did not yield any successful results.
Also, there seems to be something weird happening since the Impact and Likelihood are correct while the overall Severity is not. In addition, no information regarding the issue description or recommendation is added.
The text was updated successfully, but these errors were encountered: