-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Include analysis.detail from Dependency Track FPF in finding description #14931
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
Open
webdevred
wants to merge
4
commits into
DefectDojo:master
Choose a base branch
from
webdevred:forward-analysis-detail-from-dependency-track
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
9cbff68
Update versions in application files
ae0ea54
Merge pull request #14915 from DefectDojo/master-into-bugfix/2.58.4-2…
rossops f4e0606
Include analysis.detail from Dependency Track FPF in finding description
webdevred c3494e1
Move audit detail to top of finding description
webdevred File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
42 changes: 42 additions & 0 deletions
42
unittests/scans/dependency_track/one_finding_with_analysis_detail.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,42 @@ | ||
| { | ||
| "meta": { | ||
| "application": "Dependency-Track", | ||
| "version": "4.14.0", | ||
| "timestamp": "2026-01-01T00:00:00Z" | ||
| }, | ||
| "findings": [ | ||
| { | ||
| "component": { | ||
| "name": "log4j-core", | ||
| "project": "d38ebf15-96cd-4a01-9bca-7b49b5b0e7c4", | ||
| "purl": "pkg:maven/org.apache.logging.log4j/log4j-core@2.14.1", | ||
| "uuid": "c8a65fcd-dbf4-41eb-b1ec-55e67c91b22b", | ||
| "version": "2.14.1" | ||
| }, | ||
| "attribution": { | ||
| "analyzerIdentity": "INTERNAL_ANALYZER", | ||
| "attributedOn": "2026-01-01 00:00:00.000" | ||
| }, | ||
| "vulnerability": { | ||
| "uuid": "f8469ce4-019a-4482-8510-624dcf65f005", | ||
| "source": "NVD", | ||
| "vulnId": "CVE-2021-44228", | ||
| "severity": "CRITICAL", | ||
| "description": "Apache Log4j2 JNDI features do not protect against attacker-controlled LDAP.", | ||
| "aliases": [] | ||
| }, | ||
| "analysis": { | ||
| "state": "IN_TRIAGE", | ||
| "isSuppressed": false, | ||
| "detail": "Reviewed and confirmed vulnerable. Upgrade scheduled for next sprint." | ||
| }, | ||
| "matrix": "d38ebf15-96cd-4a01-9bca-7b49b5b0e7c4:c8a65fcd-dbf4-41eb-b1ec-55e67c91b22b:f8469ce4-019a-4482-8510-624dcf65f005" | ||
| } | ||
| ], | ||
| "project": { | ||
| "name": "test-app", | ||
| "uuid": "d38ebf15-96cd-4a01-9bca-7b49b5b0e7c4", | ||
| "version": "1.0.0" | ||
| }, | ||
| "version": "1.3" | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't it make more sense to put the audit detail after the description? Or maybe even in the impact field?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, happy to discuss. My reasoning for putting it first: the audit detail is analyst-added context specific to this finding in your environment, whereas the vulnerability description is generic upstream text. When triaging, the analyst note is usually the more immediately relevant piece. Open to changing it if you feel strongly though.
On the impact field: that field has a specific semantic meaning (consequence of exploitation), so putting analyst workflow notes there felt wrong.
Also, I'll rebase against
bugfixas requested.