# CVE-2024-28144: Broken Access Control

> Attackers can hijack user sessions by spoofing IP and User-Agent, leading to unauthorized account access in Scan2Net.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2024
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-q8r8-h2xj-8948

## What is CVE-2024-28144?

CVE-2024-28144 is a medium-severity authentication bypass vulnerability in Image Access GmbH Scan2Net, published on 12 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An attacker who can spoof the IP address and the User-Agent of a logged-in user can takeover the session because of flaws in the self-developed session management. If two users access the web interface from the same IP they are logged in as the other user.

Weakness: CWE-384 (Session Fixation)

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


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

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

## Is CVE-2024-28144 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28144 is a medium-severity authentication bypass vulnerability in Image Access GmbH Scan2Net, published on 12 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-28144 in the wild and no public exploit code.

Affected product: Image Access GmbH Scan2Net. 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-28144/ (Markdown: https://insights.sbomify.com/CVE-2024-28144/index.md)
```

## Sources

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

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