# CVE-2020-5281: LDAP connector injection in Perun

> A manager can manipulate LDAP configuration to bypass access controls and retrieve all data from the Perun LDAP directory.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gj88-9q3f-72m3

## What is CVE-2020-5281?

CVE-2020-5281 is a medium-severity vulnerability in CESNET perun, published on 25 Mar 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

In Perun before version 3.9.1, VO or group manager can modify configuration of the LDAP extSource to retrieve all from Perun LDAP. Issue is fixed in version 3.9.1 by sanitisation of the input.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-90 (Improper Neutralization of Special Elements used in an LDAP Query)

## Which versions are affected by CVE-2020-5281?

It affects 1 product.


Products: Cesnet Perun.

## How do I fix CVE-2020-5281?

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

## Is CVE-2020-5281 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-5281 and fix it if it is affected.

What it is: CVE-2020-5281 is a medium-severity vulnerability in CESNET perun, published on 25 Mar 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-5281 in the wild and no public exploit code.

Affected product: CESNET perun. 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-2020-5281/ (Markdown: https://insights.sbomify.com/CVE-2020-5281/index.md)
```

## Sources

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

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