# CVE-2023-50356: Improper Certificate Validation in AREAL Topkapi Vision (Server)

> A remote attacker can intercept SSL connections to gather sensitive information and block user logins due to improper certificate validation.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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:** 31 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-hgqh-qj43-xfmf

## What is CVE-2023-50356?

CVE-2023-50356 is a medium-severity vulnerability in AREAL SAS Topkapi Vision (Server), published on 31 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SSL connections to some LDAP servers are vulnerable to a man-in-the-middle attack due to improper certificate validation in AREAL Topkapi Vision (Server). This allows a remote unauthenticated attacker to gather sensitive information and prevent valid users from login.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2023-50356?

It affects 1 product.


Products: Areal-Topkapi Vision Server.

## How do I fix CVE-2023-50356?

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

## Is CVE-2023-50356 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-50356 and fix it if it is affected.

What it is: CVE-2023-50356 is a medium-severity vulnerability in AREAL SAS Topkapi Vision (Server), published on 31 Jan 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-2023-50356 in the wild and no public exploit code.

Affected product: AREAL SAS Topkapi Vision (Server). 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-2023-50356/ (Markdown: https://insights.sbomify.com/CVE-2023-50356/index.md)
```

## Sources

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

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