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

[Snyk] Security upgrade org.mongodb:mongodb-driver-reactivestreams from 4.10.0 to 4.10.1 #79

Closed
wants to merge 1 commit into from

Conversation

brambg
Copy link
Collaborator

@brambg brambg commented Oct 2, 2023

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • pom.xml

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
low severity 486/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 3.3
Information Exposure
SNYK-JAVA-ORGJETBRAINSKOTLIN-2393744
org.mongodb:mongodb-driver-reactivestreams:
4.10.0 -> 4.10.1
No Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Check the changes in this PR to ensure they won't cause issues with your project.


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Information Exposure

@brambg brambg closed this Oct 3, 2023
@brambg brambg deleted the snyk-fix-65bba55fbe84ecae3ab535c6dea3fd30 branch November 6, 2023 19:43
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

Successfully merging this pull request may close these issues.

2 participants