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

OpenSSL 3.0.8 in latest Nuget release #4786

Open
2 tasks done
davmas30cent opened this issue Jul 18, 2024 · 5 comments
Open
2 tasks done

OpenSSL 3.0.8 in latest Nuget release #4786

davmas30cent opened this issue Jul 18, 2024 · 5 comments

Comments

@davmas30cent
Copy link

davmas30cent commented Jul 18, 2024

Description

The Nuget packet still uses the 3.0.8 version of OpenSSL even though an upgrade to 3.0.12 was done in version 2.4.0 of librdkafka. Vulnerability scanners then report vulnerabilities, such as CVE-2023-5363.

How to reproduce

dotnet new console
dotnet add package librdkafka.redist --version 2.5.0
dotnet build

Vulnerable versions are in the following directories (libcrypto.dll and libssl-3.dll):

  • bin/Debug/net8.0/librdkafka\x64
  • bin/Debug/net8.0/librdkafka\x86
  • bin/Debug/net8.0/runtimes\win-x64\native
  • bin/Debug/net8.0/runtimes\win-x86\native

Checklist

  • librdkafka version (release number or git tag): v2.5.0
  • Operating system: Windows 10
@emasab
Copy link
Collaborator

emasab commented Jul 18, 2024

That's only for Windows because we use the LTS version of OpenSSL 3.0.x and that's not updated in vcpkg
https://vcpkg.io/en/package/openssl
we can think about using the non-LTS version for window packaging.

@davmas30cent
Copy link
Author

Do you have any idea why 3.0.12 was not added to vcpkg? Maybe we should raise that issue with them.

@zhuoyan-khoh
Copy link

Hi, is there a plan to address this security issue? If yes, may I know when will the fix be merged into master?

@milindl
Copy link
Contributor

milindl commented Jul 30, 2024

There is a reason why 3.0.12 is not present in vcpkg, see the upstream issue in vcpkg here: microsoft/vcpkg#39417 . I don't think there's a plan by the maintainers to add 3.0.12 or 3.0.13 to vcpkg.

We'll internally discuss what we can do.

@zhuoyan-khoh
Copy link

Thanks @milindl. I understand the issue better now. Can you help to update once you guys have a plan. Thanks again.

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

4 participants