GHSA-pp84-v3mw-gg4w json
Taipy 3.1.1 affected by CVEs on flask-core and pymongo
published 2y ago modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### Summary Indirect CVEs affect Taipy 3.1.1
### Details Taipy 3.1.1 is affected by two existing CVEs: CVE-2024-1681 affects flask-core <4.0.1 and taipy 3.1.1 needs <=4.0.0 CVE-2024-5629 affects pymongo <4.6.3 and taipy 3.1.1 needs <=4.6.1
Please see References for further details.
### Patch please upgrade to the following versions:
Fixed on patch versions: >=3.1.2 and on major releases: >=4.0.0
### Impact pre-commit breaks when using dependency Taipy 3.1.1
Patch / fix
- pypi taipy 4.0.0
Is GHSA-pp84-v3mw-gg4w in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | taipy | <4.0.0 |
4.0.0 |
References
-
github.com
/Avaiga/taipy/security/advisories/GHSA-pp84-v3mw-gg4w
web
-
nvd.nist.gov
/vuln/detail/CVE-2024-1681
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2024-5629
advisory
-
github.com
/Avaiga/taipy
package
-
github.com
/advisories/GHSA-84pr-m4jr-85g5
advisory
-
github.com
/advisories/GHSA-m87m-mmvp-v9qm
advisory
Sources
- GitHub Advisory GHSA-pp84-v3mw-gg4w
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.