🎉 implement n0s1 scanner #13564#13580
Conversation
valentijnscholten
left a comment
There was a problem hiding this comment.
This is a parser that can return different type of scans. Can you look at implementing the dynamic test_type feature similar to rusty hog?
django-DefectDojo/dojo/tools/rusty_hog/parser.py
Lines 33 to 70 in 1ba1122
Hi @valentijnscholten , before I implement this, I would need multiple different output files. I was just doing the PR, not using it to test different scenarios (for this I don't have time right now). |
|
It's only about adding logic to set the test_type name / parser name. Bot about having all scanners supported. |
|
This pull request introduces an information disclosure issue: the n0s1 Scanner parser copies the raw "secret" field from scanner JSON into the Finding description (dojo/tools/n0s1/parser.py), which exposes sensitive data (keys, passwords, private keys) in the DefectDojo UI. This should be remediated by redacting or omitting secrets before storing/displaying them.
Information Disclosure in Finding Description in
|
| Vulnerability | Information Disclosure in Finding Description |
|---|---|
| Description | The n0s1 Scanner parser explicitly includes the secret field from its JSON output into the description field of a Finding object. This secret field, as confirmed by the test data, contains sensitive information (e.g., AWS access keys, private keys, passwords in URLs). Since the Finding description is displayed in the DefectDojo UI without redaction, this leads to an information disclosure vulnerability where secrets discovered by the scanner are exposed to users viewing the finding details. |
django-DefectDojo/dojo/tools/n0s1/parser.py
Lines 64 to 67 in 6c993e0
All finding details can be found in the DryRun Security Dashboard.
* implement n0s1 scanner DefectDojo#13564 * update * ruff * update * update * update * underline the correctness through comparison with rustyhog
#13564