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 com.ibm.mq:com.ibm.mq.jakarta.client from 9.3.2.1 to 9.3.3.1 #383

Closed

Conversation

svkcemk
Copy link

@svkcemk svkcemk commented Sep 18, 2024

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

  • pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
medium severity Uncontrolled Resource Consumption ('Resource Exhaustion')
SNYK-JAVA-ORGBOUNCYCASTLE-7986105
  475   com.ibm.mq:com.ibm.mq.jakarta.client:
9.3.2.1 -> 9.3.3.1
No Path Found No Known Exploit

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Uncontrolled Resource Consumption ('Resource Exhaustion')

[//]: # 'snyk:metadata:{"customTemplate":{"variablesUsed":[],"fieldsUsed":[]},"dependencies":[{"name":"com.ibm.mq:com.ibm.mq.jakarta.client","from":"9.3.2.1","to":"9.3.3.1"}],"env":"prod","issuesToFix":[{"exploit_maturity":"No Known Exploit","id":"SNYK-JAVA-ORGBOUNCYCASTLE-7986105","priority_score":475,"priority_score_factors":[{"type":"freshness","label":true,"score":50},{"type":"fixability","label":true,"score":150},{"type":"cvssScore","label":"5.5","score":275},{"type":"scoreVersion","label":"v1","score":1}],"severity":"medium","title":"Uncontrolled Resource Consumption ('Resource Exhaustion')"},{"exploit_maturity":"No Known Exploit","id":"SNYK-JAVA-ORGBOUNCYCASTLE-7986105","priority_score":475,"priority_score_factors":[{"type":"freshness","label":true,"score":50},{"type":"fixability","label":true,"score":150},{"type":"cvssScore","label":"5.5","score":275},{"type":"scoreVersion","label":"v1","score":1}],"severity":"medium","title":"Uncontrolled Resource Consumption ('Resource Exhaustion')"},{"exploit_maturity":"No Known Exploit","id":"SNYK-JAVA-ORGBOUNCYCASTLE-7986105","priority_score":475,"priority_score_factors":[{"type":"freshness","label":true,"score":50},{"type":"fixability","label":true,"score":150},{"type":"cvssScore","label":"5.5","score":275},{"type":"scoreVersion","label":"v1","score":1}],"severity":"medium","title":"Uncontrolled Resource Consumption ('Resource Exhaustion')"}],"prId":"19df611a-092b-41af-97f7-287352504cea","prPublicId":"19df611a-092b-41af-97f7-287352504cea","packageManager":"maven","priorityScoreList":[475],"projectPublicId":"417639a4-7326-4de4-a577-80f97021b563","projectUrl":"https://app.snyk.io/org/application-services-red-hat-camel-for-quarkus/project/417639a4-7326-4de4-a577-80f97021b563?utm_source=github&utm_medium=referral&page=fix-pr","prType":"fix","templateFieldSources":{"branchName":"default","commitMessage":"default","description":"default","title":"default"},"templateVariants":["updated-fix-title","priorityScore"],"type":"auto","upgrade":["SNYK-JAVA-ORGBOUNCYCASTLE-7986105"],"vulns":["SNYK-JAVA-ORGBOUNCYCASTLE-7986105"],"patch":[],"isBreakingChange":false,"remediationStrategy":"vuln"}'

@zhfeng zhfeng closed this Sep 27, 2024
@jamesnetherton jamesnetherton deleted the snyk-fix-077a4534f5d2ce73cd9b675c382f71a8 branch October 15, 2024 14:34
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.

3 participants