# CVE-2021-3027: Other in n/a

> Attackers can perform LDAP injection via unsanitized user input in LibrIT PaSSHport, leading to information disclosure.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-32jf-8hmq-3gv8

## What is CVE-2021-3027?

CVE-2021-3027 is a medium-severity vulnerability in n/a, published on 26 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

app/views_mod/user/user.py in LibrIT PaSSHport through 2.5 is affected by LDAP Injection. There is an information leak through the crafting of special queries, escaping the provided search filter because user input gets no sanitization.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Librit Passhport.

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

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

## Is CVE-2021-3027 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-3027 is a medium-severity vulnerability in n/a, published on 26 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-3027 in the wild and no public exploit code.

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

## Sources

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

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