Skip to content
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

External mariadb CVE database running into incompatible character encoding issue #5733

Open
ptecihner opened this issue May 25, 2023 · 8 comments
Labels

Comments

@ptecihner
Copy link

Describe the bug
When using external db during the merge operation with cve and cisa the operation fails

Version of dependency-check used
Maven 8.2.1

Log file
Will attach later

To Reproduce
Steps to reproduce the behavior:

  1. Run maven in update only mode

Expected behavior
Db to have been updated IMG_20230525_100415.jpg

@ptecihner ptecihner added the bug label May 25, 2023
@ptecihner
Copy link
Author

@aikebah aikebah changed the title Using external db is creating a SQL exception External mariadb CVE database running into incompatible character encoding issue May 27, 2023
@aikebah
Copy link
Collaborator

aikebah commented May 27, 2023

@ptecihner Did you modify the default characterset of mariadb from the default?

@ptecihner
Copy link
Author

No

@aikebah
Copy link
Collaborator

aikebah commented May 27, 2023

Looks like there were unicode replacement characters (U+FFFD (�) encoded by the reported 0xEF BF DD in utf-8) surrounding IOMobileFrameBuffer in the short description of the Known Exploited Vulnerabilities datafeed of the CISA that have by now been corrected by replacing them with regular spaces. Do you still experience the issue on a fresh update?

@cpfeiffer
Copy link

I still see the same problem. See stefanneuhaus/dependencycheck-central-mysql-docker#18
Even if the data feed would be fixed upstream, one shouldn't rely on that, IMHO.

@aikebah
Copy link
Collaborator

aikebah commented Jun 26, 2023

Fully agree to that cpfeiffer, but would need to get my hands on a problematic file to be able to reproduce and verify the fix.

@cpfeiffer
Copy link

If you download https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
have a look at the shortDescription for CVE-2021-42013 and CVE-2021-41773.

@cpfeiffer
Copy link

(those links to github's advisory data were not made by me, I entered plain CVE-...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants