# CVE-2022-2265: Path traversal in Identity and Directory Management System

> An unauthenticated attacker can exploit a path traversal vulnerability to read arbitrary files from the Identity and Directory Management System.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2022
- **Updated:** 20 May 2026
- **Also known as:** GHSA-6jg8-m9ff-fv96

## What is CVE-2022-2265?

CVE-2022-2265 is a high-severity path traversal vulnerability in Çekino Bilgi Teknolojileri, published on 21 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Identity and Directory Management System developed by Çekino Bilgi Teknolojileri before version 2.1.25 has an unauthenticated Path traversal vulnerability. This has been fixed in the version 2.1.25

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-35 (Path Traversal: '.../...//')

## Which versions are affected by CVE-2022-2265?

It affects 1 product.


Products: Identity and Directory Management System Project Identity and Directory Management System.

## How do I fix CVE-2022-2265?

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

## Is CVE-2022-2265 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2265 and fix it if it is affected.

What it is: CVE-2022-2265 is a high-severity path traversal vulnerability in Çekino Bilgi Teknolojileri, published on 21 Sep 2022. 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-2022-2265 in the wild and no public exploit code.

Affected product: Çekino Bilgi Teknolojileri. 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-2022-2265/ (Markdown: https://insights.sbomify.com/CVE-2022-2265/index.md)
```

## Sources

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

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