# CVE-2024-3375: Broken Access Control in Havelsan's Dialogue

> Attackers can access restricted functionality due to incorrect permission assignments in Havelsan Dialogue, potentially reading or modifying data.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2024
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-4wch-q26f-448q

## What is CVE-2024-3375?

CVE-2024-3375 is a critical missing authorization vulnerability in Havelsan Inc. Dialogue, published on 29 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect Permission Assignment for Critical Resource vulnerability in Havelsan Inc. Dialogue allows Accessing Functionality Not Properly Constrained by ACLs.

This issue affects Dialogue: from v1.83 before v1.83.1 or v1.84.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2024-3375 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3375 is a critical missing authorization vulnerability in Havelsan Inc. Dialogue, published on 29 Apr 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-3375 in the wild and no public exploit code.

Affected product: Havelsan Inc. Dialogue. 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-3375/ (Markdown: https://insights.sbomify.com/CVE-2024-3375/index.md)
```

## Sources

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

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