# CVE-2024-34519: Missing authorization in n/a

> Attackers can bypass access controls on shared dashboards with auto-login users to disclose sensitive data in Avantra Server.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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:** 5 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-7vvx-296g-vp4g

## What is CVE-2024-34519?

CVE-2024-34519 is a medium-severity missing authorization vulnerability in n/a, published on 5 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Avantra Server 24.x before 24.0.7 and 24.1.x before 24.1.1 mishandles the security of dashboards, aka XAN-5367. If a user can create a dashboard with an auto-login user, data disclosure may occur. Access control can be bypassed when there is a shared dashboard, and its auto-login user has privileges that a dashboard visitor should not have.

Weakness: CWE-289 (Authentication Bypass by Alternate Name)

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


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

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

## Is CVE-2024-34519 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-34519 is a medium-severity missing authorization vulnerability in n/a, published on 5 May 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-34519 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-34519/ (Markdown: https://insights.sbomify.com/CVE-2024-34519/index.md)
```

## Sources

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

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