Broken Access Control in Havelsan's Dialogue
Summary
| CVE | CVE-2024-3375 |
|---|---|
| State | PUBLISHED |
| Assigner | TR-CERT |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2024-04-29 09:15:09 UTC |
| Updated | 2026-06-03 16:16:22 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 9.4 CRITICAL from [email protected]
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H
EPSS: 0.001720000 probability, percentile 0.383480000 (date 2026-06-04)
Problem Types: CWE-732 | CWE-732 CWE-732 Incorrect Permission Assignment for Critical Resource
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 9.4 | CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H |
| 3.1 | CNA | CVSS | 9.4 | CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
LowAvailability
HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Havelsan Inc. | Dialogue | affected v1.83 v1.83.1 or v1.84 custom | Not specified |
| ADP | Havelsan | Dialogue | affected 1.83 1.83.1 custom | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-24-0363 | [email protected] | siberguvenlik.gov.tr | |
| www.usom.gov.tr/bildirim/tr-24-0363 | af854a3a-2127-422b-91ae-364da2661108 | www.usom.gov.tr | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: Ahmet Serkan ARI (en)
There are currently no legacy QID mappings associated with this CVE.