Skip to content
This repository was archived by the owner on Mar 9, 2023. It is now read-only.

[Snyk] Upgrade org.bitcoinj:bitcoinj-core from 0.13.1 to 0.15.10#56

Open
snyk-bot wants to merge 1 commit intomasterfrom
snyk-upgrade-f7f2938c773bda4ac48ac0c037095eb0
Open

[Snyk] Upgrade org.bitcoinj:bitcoinj-core from 0.13.1 to 0.15.10#56
snyk-bot wants to merge 1 commit intomasterfrom
snyk-upgrade-f7f2938c773bda4ac48ac0c037095eb0

Conversation

@snyk-bot
Copy link

@snyk-bot snyk-bot commented Dec 8, 2021

Snyk has created this PR to upgrade org.bitcoinj:bitcoinj-core from 0.13.1 to 0.15.10.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 24 versions ahead of your current version.
  • The recommended version was released 10 months ago, on 2021-02-18.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Integer Overflow
SNYK-JAVA-COMGOOGLEPROTOBUF-173761
590/1000
Why? Has a fix available, CVSS 8.8
No Known Exploit

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


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

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@@ -60,7 +60,7 @@
<dependency>
<groupId>org.bitcoinj</groupId>
Copy link

@Kalliingi Kalliingi Apr 13, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Real

Copy link

@Kalliingi Kalliingi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants