# CVE-2024-4680: Insufficient Session Expiration in zenml-io/zenml

> Attackers can maintain unauthorized access to compromised accounts because sessions do not expire after password changes in ZenML deployments.

- **Severity:** Low 3.9 (`CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-99hm-86h7-gr3g, PYSEC-2026-2069

## What is CVE-2024-4680?

CVE-2024-4680 is a low-severity vulnerability in zenml-io/zenml, published on 8 Jun 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A vulnerability in zenml-io/zenml version 0.56.3 allows attackers to reuse old session credentials or session IDs due to insufficient session expiration. Specifically, the session does not expire after a password change, enabling an attacker to maintain access to a compromised account without the victim's ability to revoke this access. This issue was observed in a self-hosted ZenML deployment via Docker, where after changing the password from one browser, the session remained active and usable in another browser without requiring re-authentication.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2024-4680?

3 open source packages ship an affected version, including zenml. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zenml` | PyPI | All versions to 0.56.3 | None |
| `zenml` | PyPI | All versions to 0.56.3 | None |
| `zenml` | PyPI | All versions to 0.56.3 | None |

Products: Zenml Zenml.

## How do I fix CVE-2024-4680?

No fix has been published for CVE-2024-4680 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-4680 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4680 exists.

## Other vulnerabilities in zenml-io/zenml

- [CVE-2024-2083](https://insights.sbomify.com/CVE-2024-2083/): Directory Traversal in zenml-io/zenml (critical 9.9)
- [CVE-2024-28424](https://insights.sbomify.com/CVE-2024-28424/): Code injection in n/a (high 8.8)
- [CVE-2024-25723](https://insights.sbomify.com/CVE-2024-25723/): ZenML Server Remote Privilege Escalation Vulnerability (high 8.8)
- [CVE-2024-9340](https://insights.sbomify.com/CVE-2024-9340/): Denial of Service (DoS) via Multipart Boundary in zenml-io/zenml (high 7.5)
- [CVE-2024-2035](https://insights.sbomify.com/CVE-2024-2035/): Improper Authorization in zenml-io/zenml (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4680 and fix it if it is affected.

What it is: CVE-2024-4680 is a low-severity vulnerability in zenml-io/zenml, published on 8 Jun 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4680 exists.

Affected packages and fixed versions:
- zenml (PyPI): affected all versions up to 0.56.3; no fix listed
- zenml (PyPI): affected all versions up to 0.56.3; no fix listed
- zenml (PyPI): affected all versions up to 0.56.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-4680/ (Markdown: https://insights.sbomify.com/CVE-2024-4680/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-4680
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-4680
- OSV: https://osv.dev/vulnerability/CVE-2024-4680

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-4680/
Summaries are generated and may contain mistakes; the official description above is the record.