Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

[Snyk] Security upgrade com.slack.api:slack-api-client from 1.34.0 to 1.35.0 #350

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

webstepstianstorrvik
Copy link

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
medium severity 616/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.9
Denial of Service (DoS)
SNYK-JAVA-COMSQUAREUPOKIO-5773320
com.slack.api:slack-api-client:
1.34.0 -> 1.35.0
No Proof of Concept
medium severity 616/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.9
Denial of Service (DoS)
SNYK-JAVA-COMSQUAREUPOKIO-5820002
com.slack.api:slack-api-client:
1.34.0 -> 1.35.0
No Proof of Concept
low severity 486/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 3.3
Information Exposure
SNYK-JAVA-ORGJETBRAINSKOTLIN-2393744
com.slack.api:slack-api-client:
1.34.0 -> 1.35.0
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:

🦉 Denial of Service (DoS)
🦉 Information Exposure

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