-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fluentd is not coming up after installing openssl gem on RHEL 8 #4690
Comments
fluent-package and td-agent (Linux version) uses system openssl. |
According to https://access.redhat.com/errata/RHSA-2024:7848, it seems openssl-1.1.1k-14 is available for CVE-2024-5535. |
ok, thanks for the reply, is it required to reinstall fluentd post System openssl upgrade? would strings command to /opt/././x86_64-linux to openssl.so gives the updated result? |
You don't need to reinstall Fluentd. |
Sorry, I don't know it... |
I tried it on AlmaLinux 8 and it is no problem to start Fluentd with the openssl gem new version.
|
Describe the bug
I installed fluentd 5 from below script to see if CVE-2024-5535 is resolved or not.
curl -fsSL https://toolbelt.treasuredata.com/sh/install-redhat-fluent-package5-lts.sh | sh
I can still see the output of /opt/td-agent/lib/ruby/2.7.0/x86_64-linux/strings openssl.so | grep OpenSSL shows OpenSSL 1.1.1k FIPS 25 Mar 2021
I attempted to install openssl gem to see if that points latest openssl and resolve the issue
command:
After that fluentd start is failing with below error
To Reproduce
Install fluentd : curl -fsSL https://toolbelt.treasuredata.com/sh/install-redhat-fluent-package5-lts.sh | sh
install openssl gem
ruby gem install openssl
Fluentd does not start
Expected behavior
Fluend should be start after installing openssl gem
Is the standalone fluentd always use system openssl ? How to mitigate if any openssl vulnerability is reported? CVE-2024-5535 in my case.
Your Environment
Your Configuration
Your Error Log
Additional context
The actual problem statement is to how to mitigate CVE-2024-5535 vulnerability.
The text was updated successfully, but these errors were encountered: