# CVE-2024-52946: Privilege escalation in n/a

> Authenticated users can escalate privileges by exploiting improper session refresh checks in LemonLDAP::NG when adaptive authentication rules are configured with increments.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Nov 2024
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-52946, GHSA-3r2v-8348-hx3r, UBUNTU-CVE-2024-52946

## What is CVE-2024-52946?

CVE-2024-52946 is a high-severity vulnerability in n/a, published on 18 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in LemonLDAP::NG before 2.20.1. An Improper Check during session refresh allows an authenticated user to raise their authentication level if the admin configured an "Adaptative authentication rule" with an increment instead of an absolute value.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2024-52946?


## How do I fix CVE-2024-52946?

Upgrade to a fixed version.

## Is CVE-2024-52946 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52946 and fix it if it is affected.

What it is: CVE-2024-52946 is a high-severity vulnerability in n/a, published on 18 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-52946 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-2024-52946/ (Markdown: https://insights.sbomify.com/CVE-2024-52946/index.md)
```

## Sources

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

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