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

> An authenticated guest user can bypass client-side controls to perform unauthorized administrative actions like adding users in the Mavenir SCE Application Provisioning Portal.

- **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:** No
- **Published:** 12 Feb 2025
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-4369-mg8x-jq9f

## What is CVE-2024-34520?

CVE-2024-34520 is a high-severity authentication bypass vulnerability in n/a, published on 12 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An authorization bypass vulnerability exists in the Mavenir SCE Application Provisioning Portal, version PORTAL-LBS-R_1_0_24_0, which allows an authenticated 'guest' user to perform unauthorized administrative actions, such as accessing the 'add user' feature, by bypassing client-side access controls.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2024-34520 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-34520 is a high-severity authentication bypass vulnerability in n/a, published on 12 Feb 2025. 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-34520 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-34520/ (Markdown: https://insights.sbomify.com/CVE-2024-34520/index.md)
```

## Sources

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

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