CVE-2024-47833

Session cookie is without Secure and HTTPOnly flags.

Details

Please take a look at this part of code (PoC screenshot) or check code directly (provided in Occurrences section below)

Occurrences:
https://github.com/Avaiga/taipy/blob/develop/frontend/taipy-gui/src/components/Taipy/Navigate.tsx#L67

Proposed remediation: add Secure and HTTPOnly flags for cookies.

It could be like this:
document.cookie = tprh=${tprh};path=/;Secure;HttpOnly;;

PoC

Screenshot:

Secure: This flag indicates that the cookie should only be sent over secure HTTPS connections. Without this flag, the cookie will be sent over both HTTP and HTTPS connections, which could expose it to interception or tampering if the connection is not secure.
HttpOnly: This flag prevents the cookie from being accessed by client-side JavaScript. It helps mitigate certain types of attacks, such as cross-site scripting (XSS), by preventing malicious scripts from accessing the cookie's value.

References
CWE-614: Sensitive Cookie in HTTPS Session Without 'Secure' Attribute https://cwe.mitre.org/data/definitions/614.html
CWE-1004: Sensitive Cookie Without 'HttpOnly' Flag - https://cwe.mitre.org/data/definitions/1004.html
OWASP - Secure Cookie Attribute - https://owasp.org/www-community/controls/SecureCookieAttribute
Cookie security flags - https://www.invicti.com/learn/cookie-security-flags/
Cookie lack Secure flag - https://support.detectify.com/support/solutions/articles/48001048982-cookie-lack-secure-flag

Other:
Title: Encrypting the Web
URL: https://www.eff.org/encrypt-the-web

Update (Required advisory information) - added severity, resource:
https://portswigger.net/kb/issues/00500200_tls-cookie-without-secure-flag-set

Best regards,

CVE-2024-47833 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.0.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2024-47833? CVE-2024-47833 is a medium-severity security vulnerability in taipy (pip), affecting versions <= 3.1.1. It is fixed in 4.0.0.
2. How severe is CVE-2024-47833? CVE-2024-47833 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of taipy are affected by CVE-2024-47833? taipy (pip) versions <= 3.1.1 is affected.
4. Is there a fix for CVE-2024-47833? Yes. CVE-2024-47833 is fixed in 4.0.0. Upgrade to this version or later.
5. Is CVE-2024-47833 exploitable, and should I be worried? Whether CVE-2024-47833 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-47833 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-47833? Upgrade taipy to 4.0.0 or later.