pysec-2024-168
Vulnerability from pysec
Published
2024-10-09 19:15
Modified
2025-01-18 19:19
Severity ?
Details
Taipy is an open-source Python library for easy, end-to-end application development for data scientists and machine learning engineers. In affected versions session cookies are served without Secure and HTTPOnly flags. This issue has been addressed in release version 4.0.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.
Impacted products
Name | purl |
---|---|
taipy | pkg:pypi/taipy |
Aliases
{ affected: [ { package: { ecosystem: "PyPI", name: "taipy", purl: "pkg:pypi/taipy", }, ranges: [ { events: [ { introduced: "0", }, { fixed: "4.0.0", }, ], type: "ECOSYSTEM", }, ], versions: [ "1.0.0", "1.1.0", "2.0.0", "2.1.0", "2.2.0", "2.3.0", "2.3.1", "2.4.0", "3.0.0", "3.1.0", "3.1.1", ], }, ], aliases: [ "CVE-2024-47833", "GHSA-r3jq-4r5c-j9hp", ], details: "Taipy is an open-source Python library for easy, end-to-end application development for data scientists and machine learning engineers. In affected versions session cookies are served without Secure and HTTPOnly flags. This issue has been addressed in release version 4.0.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.", id: "PYSEC-2024-168", modified: "2025-01-18T19:19:07.718423+00:00", published: "2024-10-09T19:15:14+00:00", references: [ { type: "ADVISORY", url: "https://github.com/Avaiga/taipy/security/advisories/GHSA-r3jq-4r5c-j9hp", }, { type: "EVIDENCE", url: "https://github.com/Avaiga/taipy/security/advisories/GHSA-r3jq-4r5c-j9hp", }, ], severity: [ { score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N", type: "CVSS_V3", }, ], }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.