Thank you <@U02KLCTEW0Y> for the response. When is...
# fluent-bit
y
Thank you @Pat for the response. When is the next release coming up with this krb5 fix. As this vulnerability is rated as High I need to fix this as soon as possible. Is there any workaround I can follow to mitigate this vulnerability?
p
Sure, just build the container image like normal if it's fixed upstream. Is it fixed upstream?
Separately have you analysed the vulnerability and confirmed it is relevant? Does it actually impact fluent bit or you, if not then it's a false positive.
You likely also need to ensure you only pull the updated library and not the old one if you're going this way. You should remove the libpq install from the dependency tree plus anything that pulls it in. The image includes the status files and package info that various scanners use to check what dependencies are installed. So if you just overwrite the raw libraries that won't change the fact the image thinks it has the old ones.
y
Defender issue Id:- CVE-2024-26462 Severity:- High Description:- Kerberos 5 versions, including 1.21.2, contain vulnerabilities related to memory handling. A memory leak in the file /krb5/src/kdc/ndr.c can be exploited by remote attackers to cause a denial of service (DoS). Additionally, certain memory operations in Kerberos were incorrectly handled, potentially leading to excessive memory consumption and DoS. Specific issues were identified in Ubuntu 24.04 LTS (CVE-2024-26462) and the kadmind daemon when handling log files during incremental propagation, which could result in crashes or arbitrary code execution (CVE-2025-24528). [Generated by AI] Impact:- Remediation:- Apply the latest patches and updates provided by the respective vendors. [Generated by AI] patches to fix the vulnerabilities:
@Pat The issue is reported by Microsoft defender. This issue is valid. Currently I am working for Microsoft project
p
Valid is not right here, does that actually apply to the usage is my point. Just because an issue is possible does not mean it is relevant if no code path or data flow uses it. I'm not going to argue though on how to do security 🙂
Once the issue is fixed in upstream dependencies then it'll be brought in automatically on the next build: you can do this yourself or wait as I say for the next release
If you need faster turnaround on it then an OSS project then I'd recommend an enterprise provider: I'd recommend fluent.do 😄
I suspect you're just overwriting the library binaries but not removing the actual package info or status files that the scanner uses. Again, you've not said how it didn't work and whether you confirmed it was updated in the image. Just copying updated library files should not work, you'll have to remove the old dependency and ensure only the new one is used directly and by all transitive libraries (other dependencies may need it and install the old one).