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

Vault dependency (CVE-2020-15250) issue when using 1.7 #158

Open
LuckyLuckiest opened this issue Jul 8, 2023 · 1 comment
Open

Vault dependency (CVE-2020-15250) issue when using 1.7 #158

LuckyLuckiest opened this issue Jul 8, 2023 · 1 comment

Comments

@LuckyLuckiest
Copy link

LuckyLuckiest commented Jul 8, 2023

<dependency>
<groupId>com.github.MilkBowl</groupId>
<artifactId>VaultAPI</artifactId>
<version>1.7</version>
<scope>provided</scope>
</dependency>

I used this dependency from the README.md given in the github repo. And Intellij gave me the following vulnerability,
'Provides transitive vulnerable dependency maven:junit:junit:4.10
CVE-2020-15250 5.5 Incorrect Permission Assignment for Critical Resource vulnerability pending CVSS allocation
Results powered by Checkmarx(c)'

@Geolykt
Copy link
Contributor

Geolykt commented Jul 8, 2023

While of course referencing CVEs sounds like a super serious issue, this is not a vault bug nor a serious issue in the realm of Vault. Report this to IJ instead - dependencies with the test scope (which is the case for junit, see https://github.com/MilkBowl/VaultAPI/blob/master/pom.xml#L70-L71) are irrelevant to you as an API consumer. (Hell, it's even an optional dependency!)

Technically this issue could be resolved in a future version of vault, but there is little reason to update vault just for this CVE that probably doesn't affect vault in the first place as that dependency is not used at all (at least at first glance).
If anyone wants to fix this issue regardless, the dependency should be dropped.

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

No branches or pull requests

2 participants