Known vulnerabilities in shared libraries xerces-c which mikecore depends on.Can you help upgrade to patch versions?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 28/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system, security
Research direction
Inspect mikecore's dependency and shared-library build configuration to find where xerces-c 3.1.1 enters the package. Start by tracing the three C-library dependencies shown in the issue, then determine how the package build selects their versions. Done means the packaged dependency uses xerces-c 3.2.3 or newer and the resulting artifacts no longer contain the reported vulnerable library.
Written by the indexing model from the issue text.
Description
Hi, @jsmariegaard , @ecomodeller , I'd like to report a vulnerability issue in mikecore_0.2.0.
Dependency Graph between Python and Shared Libraries
Issue Description
As shown in the above dependency graph, mikecore_0.2.0 directly or transitively depends on 3 C libraries (.so). However, I noticed that one C library is vulnerable, containing the following CVEs:
libxerces-c-3.1.so from C project xerces-c(version:3.1.1) exposed 2 vulnerabilities:
CVE-2018-1311, CVE-2015-0252
Suggested Vulnerability Patch Versions
xerces-c has fixed the vulnerabilities in versions >=3.2.3
Python build tools cannot report vulnerable C libraries, which may induce potential security issues to many downstream Python projects.
As a popular python package (mikecore has 2,265 downloads per month), could you please upgrade the above shared libraries to their patch versions?
Thanks for your help~
Best regards,
Andy
- Dominant language
- Python
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DHI/mikecore-python
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
DHI/mikecore-python#49 ·
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
DHI/mikecore-python#52 ·
-
Remaining TODOs in production code: platform notes, licensing questions, and one likely-stale marker Open
Difficulty 5/5 Over a week Newbie friendliness 30/100
DHI/mikecore-python#51 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
DHI/mikecore-python#50 ·
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
DHI/mikecore-python#48 ·
All issues in DHI/mikecore-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100