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

Upgrade Thrift dependency in broker to solve CVE-2019-0210, CVE-2019-0205 and CVE-2020-13949 #9248

Closed
fmiguelez opened this issue Jan 20, 2021 · 5 comments
Labels
lifecycle/stale type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages

Comments

@fmiguelez
Copy link
Contributor

fmiguelez commented Jan 20, 2021

Library from Apache Thrift (libthrift-0.12.jar) used by Apache Pulsar Broker is affected by two high risk vulnerabilities:
CVE-2019-0210 and CVE-2019-0205

These vulnerabilities are solved by version 0.13.

Update 2021/02/19

New vulnerability CVE-2020-13949 has been published affecting libthrift up to (including) version 0.13. Version 0.14 seems to solve the issue.

@fmiguelez fmiguelez added the type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages label Jan 20, 2021
@hpvd
Copy link

hpvd commented Jan 21, 2021

Since these update-needs regularly occurs,
one should think of implementing a procedure to address this:

Automated security and update routine before every release #8815

@fmiguelez fmiguelez changed the title Upgrade Thrift dependency in broker to solve CVE-2019-0210 and CVE-2019-0205 Upgrade Thrift dependency in broker to solve CVE-2019-0210, CVE-2019-0205 and CVE-2020-13949 Feb 19, 2021
@lhotari
Copy link
Member

lhotari commented Jun 7, 2021

Fixing this issue depends on Bookkeeper issue apache/bookkeeper#2695 . libthrift 0.14.1 is broken and a new version is needed before the upgrade can be completed. More details in apache/bookkeeper#2695 (review) .

@codelipenghui
Copy link
Contributor

The issue had no activity for 30 days, mark with Stale label.

@tisonkun
Copy link
Member

tisonkun commented Dec 7, 2022

Closed as stale. Please open a new issue if it's still relevant to the maintained versions.

IIRC we have a OWASP checker to prevent high risk vulnerabilities

@tisonkun tisonkun closed this as completed Dec 7, 2022
@compuguy
Copy link

@tisonkun CVE-2019-0205 and CVE-2019-0210 are still showing up as vulnerabilities as of September 2023 with Pulsar 3.1.0's connectors. I don't think the OWASP checker you have setup is working, or these types of security vulnerabilities are being prioritized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages
Projects
None yet
Development

No branches or pull requests

6 participants