# CVE-2021-3825: Missing Authorization Checks in LiderAhenk

> An unsecured API in LiderAhenk leaks LDAP credentials, allowing attackers to bypass authentication and access sensitive configuration data.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2021
- **Updated:** 18 May 2026
- **Also known as:** GHSA-5g5h-vp5m-chrx

## What is CVE-2021-3825?

CVE-2021-3825 is a critical missing authorization vulnerability in TUBITAK Lider, published on 1 Oct 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On 2.1.15 version and below of Lider module in LiderAhenk software is leaking it's configurations via an unsecured API. An attacker with an access to the configurations API could get valid LDAP credentials.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2021-3825?

It affects 1 product.


Products: Pardus Liderahenk.

## How do I fix CVE-2021-3825?

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

## Is CVE-2021-3825 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3825 and fix it if it is affected.

What it is: CVE-2021-3825 is a critical missing authorization vulnerability in TUBITAK Lider, published on 1 Oct 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-3825 in the wild and no public exploit code.

Affected product: TUBITAK Lider. 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-2021-3825/ (Markdown: https://insights.sbomify.com/CVE-2021-3825/index.md)
```

## Sources

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

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