-
-
Notifications
You must be signed in to change notification settings - Fork 600
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
CycloneDX BOM validation fails when URLs contain %-encoded '[' and ']' characters #3831
Comments
Thanks for identifying and fixing the issue in Marked this as blocked since we'll have to wait for a validator release. |
A release that contains the fix have been released in |
Yup, and I merged an update into There'll likely be a release of that shorty, closely followed by a v4.11.4 release of DT I reckon... |
…acters Fixes DependencyTrack#3831 Signed-off-by: nscuro <nscuro@protonmail.com>
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
…acters Fixes DependencyTrack#3831 Signed-off-by: nscuro <nscuro@protonmail.com>
Current Behavior
When BOM validation is enabled certain CycloneDX BOMs will erroneously fail to validate. This happens (at least) when a component entry contains an external reference with a URL containing %-encoded
[
or]
characters (%5B
and%5D
) in the query string. When this occurs the following (sample) error message is returned from the/api/v1/bom
endpoint:This is due to a bug in the underlying
json-schema-validator
library used by cyclonedx-core-java (which Dependency Track uses for BOM validation). The bug has been fixed in the latest commit but a new release ofjson-schema-validator
hasn't been published yet.Steps to Reproduce
Expected Behavior
This BOM should pass validation and successfully populate the project with components.
Dependency-Track Version
4.12.0-SNAPSHOT
Dependency-Track Distribution
Container Image
Database Server
H2
Database Server Version
No response
Browser
N/A
Checklist
The text was updated successfully, but these errors were encountered: