# CVE-2019-19791: Missing authorization in n/a

> Attackers can bypass access controls on SOAP/REST endpoints by manipulating URLs, potentially exposing sensitive management functions.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 May 2023
- **Updated:** 14 Jan 2025
- **Also known as:** DEBIAN-CVE-2019-19791, GHSA-c639-6g37-r8wm, UBUNTU-CVE-2019-19791

## What is CVE-2019-19791?

CVE-2019-19791 is a critical missing authorization vulnerability in n/a, published on 29 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In LemonLDAP::NG (aka lemonldap-ng) before 2.0.7, the default Apache HTTP Server configuration does not properly restrict access to SOAP/REST endpoints (when some LemonLDAP::NG setup options are used). For example, an attacker can insert index.fcgi/index.fcgi into a URL to bypass a Require directive.

## Which versions are affected by CVE-2019-19791?

It affects 1 product.


Products: Lemonldap-Ng Lemonldap\.

## How do I fix CVE-2019-19791?

Upgrade to a fixed version.

## Is CVE-2019-19791 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-28862](https://insights.sbomify.com/CVE-2023-28862/): Auth bypass in n/a (critical 9.8)
- [CVE-2012-6426](https://insights.sbomify.com/CVE-2012-6426/): Auth bypass in n/a (high 7.5)
- [CVE-2024-48933](https://insights.sbomify.com/CVE-2024-48933/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2022-37186](https://insights.sbomify.com/CVE-2022-37186/): Missing authorization in n/a (medium 5.9)
- [CVE-2023-44469](https://insights.sbomify.com/CVE-2023-44469/): Server-side request forgery in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19791 and fix it if it is affected.

What it is: CVE-2019-19791 is a critical missing authorization vulnerability in n/a, published on 29 May 2023. 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-2019-19791 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-2019-19791/ (Markdown: https://insights.sbomify.com/CVE-2019-19791/index.md)
```

## Sources

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

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