Skip to content
This repository has been archived by the owner on Jan 19, 2023. It is now read-only.

Incorrect vulnerability details for dom4j / CVE-2018-1000632 #112

Closed
kpshek opened this issue Jul 28, 2020 · 4 comments
Closed

Incorrect vulnerability details for dom4j / CVE-2018-1000632 #112

kpshek opened this issue Jul 28, 2020 · 4 comments
Labels
bug Something isn't working

Comments

@kpshek
Copy link

kpshek commented Jul 28, 2020

Vulnerability URL
https://ossindex.sonatype.org/vuln/09883ba9-5094-49df-bd4a-1eaf1d6ba07b

Description
The affected version range for most of the packages are incorrect and showing as (,2.1.1).

The affected version range for pkg:github/dom4j/dom4j is [2.0.0,2.0.3), [2.1.0,2.1.1) and is correct and is what should be set to all of the other packages.

CVE-2018-1000632 was fixed on versions 2.0.3 and 2.1.1 for dom4j. References:

Note that the CPE entries in the NVD are correct.

@kpshek kpshek added the bug Something isn't working label Jul 28, 2020
@kpshek
Copy link
Author

kpshek commented Aug 11, 2020

Hi @ken-duck - any chance you could take a look at this? Thanks in advance!

@ken-duck
Copy link
Contributor

Whoop. Yup, I'll get on this one today. Sorry for the delay.

@ken-duck
Copy link
Contributor

Sorry again for the delay. I have fixed this locally, and it should make it to the public database by sometime tomorrow.

@ken-duck
Copy link
Contributor

Closing old issues. I have validated that all affected packages appear to have the correct ranges.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants