Skip to content

Backport: Map unknown or retired vulnerability sources to UNKNOWN in v4-migrator - #7752

Merged
nscuro merged 1 commit into
DependencyTrack:5.2.xfrom
nscuro:backport-pr-7705
Oct 22, 2026
Merged

nscuro merged 1 commit into
DependencyTrack:5.2.xfrom
nscuro:backport-pr-7705

Conversation

@nscuro

@nscuro nscuro commented Oct 22, 2026

Copy link
Copy Markdown
Member

Description

Maps unknown or retired vulnerability sources to UNKNOWN in v4-migrator.

Addressed Issue

Fixes #7667
Backports #7705

Additional Details

N/A

Checklist

  • I have read and understand the contributing guidelines
  • This PR fixes a defect, and I have provided tests to verify that the fix is effective
  • This PR implements an enhancement, and I have provided tests to verify that it works as intended
  • This PR introduces changes to the database model, and I have updated the migration changelog accordingly
  • This PR introduces new or alters existing behavior, and I have updated the documentation accordingly
  • This PR is a substantial change (per the ADR criteria), and I have added an ADR under docs/adr/

In v4, vulnerability sources such as legacy 'NPM' (from the Node Security Working Group) were written to VULNERABILITY.SOURCE and AFFECTEDVERSIONATTRIBUTION.SOURCE.

In v5, Vulnerability.Source is an enum that only recognizes canonical sources (NVD, GITHUB, VULNDB, OSSINDEX, INTERNAL, OSV, SNYK, CX, JVN, UNKNOWN). When rows migrated with unrecognized sources are queried by endpoints such as /v1/finding, JDBI's EnumMapper throws an UnableToProduceResultException, resulting in an HTTP 500 error.

Map unrecognized or retired sources to 'UNKNOWN' and ensure uppercase matching during transformation of VULNERABILITY and AFFECTEDVERSIONATTRIBUTION, and enforce this via CHECK constraints on the staging tables.

Fixes DependencyTrack#7667

Signed-off-by: Pravin Jha <83289698+jha-pravin@users.noreply.github.com>
(cherry picked from commit 9e91313)
Signed-off-by: nscuro <nscuro@protonmail.com>
@nscuro nscuro added this to the 5.2.1 milestone Oct 22, 2026
@nscuro nscuro added the defect Something isn't working label Oct 22, 2026
@codacy-production

codacy-production Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric Results
Complexity 0

View in Codacy

🟢 Coverage ∅ diff coverage · +0.00% coverage variation

Metric Results
Coverage variation ✅ +0.00% coverage variation (-1.00%)
Diff coverage ✅ ∅ diff coverage (70.00%)

View coverage diff in Codacy

Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (74adccb) 45888 40297 87.82%
Head commit (acf6759) 45888 (+0) 40297 (+0) 87.82% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#7752) 0 0 ∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@nscuro
nscuro merged commit 11e5707 into DependencyTrack:5.2.x Oct 22, 2026
21 checks passed
@nscuro
nscuro deleted the backport-pr-7705 branch October 22, 2026 20:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

defect Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants