Vulnerator: Unable to process FORTIFY ".fpr" files using Vulnerator
Prerequisites
Before submitting a new issue, please ensure you have completed the following (replace the space in the box with an “x” to denote that it has been completed)
- I have ensured that I am running the latest release
- The issue is repeatable
- The issue has not already been reported
Category
Please select a category for the item being created
- Bug
- Enhancement
- Assistance Request
Description
Please provide a brief synopsis of the feature request or issue; if the item being created is due to a bug, please complete the “Expected Outcome”, “Actual Outcome”, and “Reproduction Steps” sections as well, otherwise, check the boxes to show that it doesn’t apply
Vulnerator fails to process Fortify “.fpr” files, log information provided here. 2018-04-20 08:15:10,766 INFO 0 Begin processing of 2018-04-20 08:19:43,004 ERROR 0 Unable to read “audit.xml”. 2018-04-20 08:19:43,148 ERROR 0 Unable to read FPR Archive. 2018-04-20 08:19:43,150 ERROR 0 Unable to process FPR file. 2018-04-20 08:19:43,152 ERROR 0 processing failed; Elapsed time: 00:04:32.3881301
Synopsis
Place your description here, please! (Replace this line)
Expected Outcome
- N/A (Non-Bug Issue)
What did you think was going to happen? (Replace this line)
Actual Outcome
- N/A (Non-Bug Issue)
What really happened? (Replace this line)
Reproduction Steps
- N/A (Non-Bug Issue)
How did you get Vulnerator to do that? (Replace this line)
Attachments
Please provide any relevant attachments, as you see fit (e.g. screenshots); if supplying vulnerability data (e.g. CKL/Nessus files or reports), please ensure that they are sanitized of IP addresses and host names and email them to alex.kuchta@navy.mil - DO NOT POST VULNERABILITY FILES HERE
- Vulnerator Log (Required for bugs) - this can be found at
C:\Users\%UserName%\AppData\Roaming\Vulnerator\V6Log.txt, where%UserName%is the user profile used to run the application - Screenshots (Optional)
- Vulnerability Files (SANITIZED AND EMAILED)
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 17
Also having this issue, as of December 2019, any updates?
@razorb62 thank you for the issue report! I believe that this is fixed courtesy of a new processing approach that I took for v6.2.0, but I will double check to make sure!