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

Too old version of Okhttp #5449

Closed
ahmed-abdelmonem opened this issue Sep 14, 2023 · 6 comments
Closed

Too old version of Okhttp #5449

ahmed-abdelmonem opened this issue Sep 14, 2023 · 6 comments

Comments

@ahmed-abdelmonem
Copy link

Is your enhancement related to a problem? Please describe

The current okhttp version has vulnerabilities (CVE-2023-3635) which cause many issues for us. okhttp-3.12.12. It would be great if the latest version of okhttp is used.

Describe the solution you'd like

Upgrade to the latest version of okhttp.

Describe alternatives you've considered

No response

Additional context

No response

@rohanKanojia
Copy link
Member

I think we are sticking to 3.x version because 4.x is based on kotlin. It should still be possible to use okhttp 4 with fabric8 by just excluding okhttp3 and adding okhttp4. See example here

@ahmed-abdelmonem
Copy link
Author

@rohanKanojia Thank you for your comment. That will fix my issue.

@ahmed-abdelmonem ahmed-abdelmonem closed this as not planned Won't fix, can't repro, duplicate, stale Sep 15, 2023
@tomdw
Copy link

tomdw commented Nov 27, 2023

@rohanKanojia why stick with an unsupported version with vulnerabilities? it is Kotlin based but this should not affect its usage. If there is a workaround to exclude okhttp3 and include okhttp4 in your project dependencies, then it means it is a drop in replacement. It will be a non-breaking upgrade then. Can this be reopened and fixed please?

@rohanKanojia
Copy link
Member

@tomdw : I think it would be better if we open a new issue to discuss this.

Just to be clear, you're interested in upgrade from kubernetes mock server perspective, right?

@tomdw
Copy link

tomdw commented Nov 27, 2023

@rohanKanojia that is correct, I'll create another issue

@tomdw
Copy link

tomdw commented Nov 27, 2023

@rohanKanojia this is the new issue: #5613

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

No branches or pull requests

3 participants