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

Several vulnerabilities in the shared libraries which omim-pytraffic depends on. Could you help upgrade to patch versions? #14183

Open
andy201709 opened this issue Mar 31, 2022 · 1 comment

Comments

@andy201709
Copy link

Hi, @biodranik , @vng , I'd like to report a vulnerability issue in omim-pytraffic_10.3.0rc2.

Dependency Graph between Python and Shared Libraries

image

Issue Description

As shown in the above dependency graph, omim-pytraffic_10.3.0rc2 directly or transitively depends on 11 C libraries (.so). However, I noticed that some C libraries are vulnerable, containing the following CVEs:
libk5crypto-ab4ddf4c.so.3.1 from C project krb5(version:1.13.2) exposed 4 vulnerabilities:
CVE-2021-37750, CVE-2021-36222, CVE-2015-8629, CVE-2015-8630
libpng12-640ca796.so.0.49.0 from C project libpng(version:<=1.2.54) exposed 10 vulnerabilities:
CVE-2011-3045, CVE-2014-9495, CVE-2013-7354, CVE-2013-7353, CVE-2017-12652, CVE-2015-8472, CVE-2016-10087, CVE-2016-3751, CVE-2015-0973, CVE-2015-8540

Suggested Vulnerability Patch Versions

krb5 has fixed the vulnerabilities in versions >=1.19.3
libpng has fixed the vulnerabilities in versions >=1.6.32

Python build tools cannot report vulnerable C libraries, which may induce potential security issues to many downstream Python projects.
As a popular python package (omim-pytraffic has 1,069 downloads per month), could you please upgrade the above shared libraries to their patch versions?

Thanks for your help~
Best regards,
Andy

@vng
Copy link
Contributor

vng commented Mar 31, 2022

Hm, we don't build/release/maintain this package. It was made by maps.me team several years ago ..
We are focused on mobile app.

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

2 participants