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

> Attackers can access sensitive data and escalate privileges by obtaining the service account token due to insecure permissions in Meshery.

- **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:** No
- **Published:** 24 Jul 2024
- **Updated:** 13 Aug 2024
- **Also known as:** GHSA-fv8v-82f6-g6f6

## What is CVE-2024-36535?

CVE-2024-36535 is a critical missing authorization vulnerability in n/a, published on 24 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insecure permissions in meshery v0.7.51 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Layer5 Meshery.

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

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

## Is CVE-2024-36535 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36535 exists.

## Other vulnerabilities in n/a

- [CVE-2023-46575](https://insights.sbomify.com/CVE-2023-46575/): SQL injection vulnerability in Meshery (critical 9.8)
- [CVE-2021-31856](https://insights.sbomify.com/CVE-2021-31856/): SQL injection in n/a (critical 9.8)
- [CVE-2024-29031](https://insights.sbomify.com/CVE-2024-29031/): Meshery SQL Injection vulnerability (high 7.5)
- [CVE-2024-35181](https://insights.sbomify.com/CVE-2024-35181/): GHSL-2024-013 Meshery SQL Injection vulnerability (medium 5.9)
- [CVE-2024-35182](https://insights.sbomify.com/CVE-2024-35182/): GHSL-2024-014 Meshery SQL Injection vulnerability (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36535 is a critical missing authorization vulnerability in n/a, published on 24 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36535 exists.

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-36535/ (Markdown: https://insights.sbomify.com/CVE-2024-36535/index.md)
```

## Sources

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

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