# CVE-2024-13967: ession-Management Failure

> Attackers can hijack sessions to gain unauthorized access to the EIBPORT KNX web configuration interface.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Jun 2025
- **Updated:** 17 Jun 2025
- **Also known as:** CVE-2022-40285, GHSA-hr6q-624g-cgfg

## What is CVE-2024-13967?

CVE-2024-13967 is a critical authentication bypass vulnerability in ABB EIBPORT V3  KNX GSM, published on 4 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

This vulnerability allows the successful attacker to gain unauthorized access to a 
configuration web page delivered by the integrated web Server of EIBPORT.

This issue affects EIBPORT V3 KNX: through 3.9.8; EIBPORT V3 KNX GSM: through 3.9.8.

Weakness: CWE-384 (Session Fixation)

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


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

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

## Is CVE-2024-13967 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13967 is a critical authentication bypass vulnerability in ABB EIBPORT V3  KNX GSM, published on 4 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-13967 in the wild and no public exploit code.

Affected product: ABB EIBPORT V3  KNX GSM. 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-13967/ (Markdown: https://insights.sbomify.com/CVE-2024-13967/index.md)
```

## Sources

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

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