DependencyTrack / DependencyTrack/frontend

National Vulnerability Database (NVD) properties are not persisted (Kubernetes, helm, DependencyTrack v4.5)

Open
#275 0 comments 0 reactions 0 assignees View on GitHub
in triage
Dominant language
Vue
Stars
171
Forks
250
Avg merge
11h 12m
Merged PRs (30d)
82

Description

As in this report: https://github.com/DependencyTrack/frontend/issues/137 the problem still reoccurs, but in different environment.

I recognized that National Vulnerability Database properties are not saved to the API Server - Database fields ("PROPERTYVALUE") are empty.

**Current Behaviour:**
Try to Change the National Vulnerability Database properties has no effect

**Steps to Reproduce:**
- The Mirroring was disabled before
- Go to Administration: National Vulnerability Database
- Enable National Vulnerability Database mirroring
- Insert a value for NVD Feeds URL: e.g. https://nvd.nist.gov/feeds
- Click on update.
- Go to another page and return to National Vulnerability Database -> properties are gone

**Expected Behaviour:**
The changed properties of National Vulnerability Database are saved correctly

**Environment:**
- Orchestration platform for managing: Kubernetes
- Installation way: helm v3.9.3
- Database Management System: PostgreSQL
- Dependency-Track Version: **4.5**
- Client Browser: Firefox / Chrome / Safari
- Client O/S: MacOS 12.6

P.S. For those who are having similar issue, only this workaround helped me to update database (it's not the expected behaviour): https://github.com/DependencyTrack/frontend/issues/137#issuecomment-1100099075

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.