Skip to content

Conversation

@jankuehl
Copy link
Contributor

@jankuehl jankuehl commented Dec 3, 2019

Since Xanitizer 4.1 we renamed and split up some problem types so that the parser for Xanitizer's XML findings list report format can not map the new problem types to the corresponding CWE number. To reduce necessary changes/commits in case of renamed or new problem types, the parser reads the CWE number directly from the detected finding output in the XML report instead of using an internal problem type <-> CWE number mapping.

@davewichers
Copy link
Contributor

It appears that this change does not preserve backward compatibility for older results files. i.e., it can only parse the new format, not the old one anymore. Can you add logic to detect if the format is old vs. new so it can score old results and new results too?

@jankuehl
Copy link
Contributor Author

jankuehl commented Dec 3, 2019

Hi @davewichers, thanks for your hint to introduce backward compatibility for the old report format without CWE numbers. Restore old problem type <-> CWE number mapping as fallback with commit dd34136 .

@davewichers davewichers merged commit a53ec0a into OWASP-Benchmark:master Dec 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants