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

> A read-only user can escalate privileges to root on Extreme XOS devices via a crafted HTTP POST request to the MMI interface.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-3jmm-qp9w-h326

## What is CVE-2024-27453?

CVE-2024-27453 is a high-severity vulnerability in n/a, published on 3 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Extreme XOS through 22.6.1.4, a read-only user can escalate privileges to root via a crafted HTTP POST request to the python method of the Machine-to-Machine Interface (MMI).

Weakness: CWE-266 (Incorrect Privilege Assignment)

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

It affects 1 product.


Products: Extremenetworks Extremexos.

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

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

## Is CVE-2024-27453 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-14332](https://insights.sbomify.com/CVE-2017-14332/): Information disclosure in n/a (high 8.1)
- [CVE-2020-18305](https://insights.sbomify.com/CVE-2020-18305/): Missing authorization in n/a (high 8.0)
- [CVE-2017-14328](https://insights.sbomify.com/CVE-2017-14328/): Memory corruption in n/a (high 7.5)
- [CVE-2017-14329](https://insights.sbomify.com/CVE-2017-14329/): Privilege escalation in n/a (medium 6.7)
- [CVE-2017-14330](https://insights.sbomify.com/CVE-2017-14330/): Privilege escalation in n/a (medium 6.7)

## Fix prompt for AI coding agents

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

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

## Sources

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

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