# CVE-2024-25977: Session Fixation

> Attackers can hijack user accounts by fixing session tokens before login due to lack of token regeneration in the HAWKI web application.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2024
- **Updated:** 13 Feb 2025

## What is CVE-2024-25977?

CVE-2024-25977 is a high-severity authentication bypass vulnerability in Interaction Design Team at the University of Applied Sciences and Arts in Hildesheim/Germany HAWKI, published on 29 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The application does not change the session token when using the login or logout functionality. An attacker can set a session token in the victim's browser (e.g. via XSS) and prompt the victim to log in (e.g. via a redirect to the login page). This results in the victim's account being taken over.

Weakness: CWE-384 (Session Fixation)

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


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

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

## Is CVE-2024-25977 being exploited?

There is no known exploitation of CVE-2024-25977 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25977 is a high-severity authentication bypass vulnerability in Interaction Design Team at the University of Applied Sciences and Arts in Hildesheim/Germany HAWKI, published on 29 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-25977 in the wild and no public exploit code.

Affected product: Interaction Design Team at the University of Applied Sciences and Arts in Hildesheim/Germany HAWKI. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-25977/ (Markdown: https://insights.sbomify.com/CVE-2024-25977/index.md)
```

## Sources

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

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