# CVE-2024-39848: Auth bypass in n/a

> Attackers can bypass authentication in Internet2 Grouper when LDAP is configured in specific ways, gaining unauthorized access.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2024
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-r52c-mh2p-jmpj

## What is CVE-2024-39848?

CVE-2024-39848 is a critical authentication bypass vulnerability in n/a, published on 29 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Internet2 Grouper before 5.6 allows authentication bypass when LDAP authentication is used in certain ways. This is related to internet2.middleware.grouper.ws.security.WsGrouperLdapAuthentication and the use of the UyY29r password for the M3vwHr account. This also affects "Grouper for Web Services" before 4.13.1.

Weakness: CWE-1390 (Weak Authentication)

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


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

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

## Is CVE-2024-39848 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-39848 is a critical authentication bypass vulnerability in n/a, published on 29 Jun 2024. 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-2024-39848 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-39848/ (Markdown: https://insights.sbomify.com/CVE-2024-39848/index.md)
```

## Sources

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

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