Skip to content

[Snyk] Security upgrade com.google.crypto.tink:tink from 1.2.2 to 1.3.0#2688

Open
shaundmorris wants to merge 1 commit intomasterfrom
snyk-fix-52b85a1dbcd996d4085d4fd6ac6cb35d
Open

[Snyk] Security upgrade com.google.crypto.tink:tink from 1.2.2 to 1.3.0#2688
shaundmorris wants to merge 1 commit intomasterfrom
snyk-fix-52b85a1dbcd996d4085d4fd6ac6cb35d

Conversation

@shaundmorris
Copy link
Copy Markdown
Owner

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
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-JAVA-COMFASTERXMLJACKSONDATAFORMAT-1047329
com.google.crypto.tink:tink:
1.2.2 -> 1.3.0
No No Known Exploit
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Information Exposure
SNYK-JAVA-COMMONSCODEC-561518
com.google.crypto.tink:tink:
1.2.2 -> 1.3.0
No No Known Exploit

(*) 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:

🦉 Denial of Service (DoS)

@stale
Copy link
Copy Markdown

stale Bot commented Apr 26, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

1 similar comment
@stale
Copy link
Copy Markdown

stale Bot commented Jul 19, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@stale stale Bot added the wontfix label Jul 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants