# CVE-2023-30350: Privilege escalation in n/a

> Authenticated guest users can escalate privileges and reset the admin password on FS S3900-24T4S switches.

- **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:** 28 May 2023
- **Updated:** 14 Jan 2025
- **Also known as:** GHSA-pxrr-pgq5-m3w3

## What is CVE-2023-30350?

CVE-2023-30350 is a high-severity vulnerability in n/a, published on 28 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FS S3900-24T4S devices allow authenticated attackers with guest access to escalate their privileges and reset the admin password.

## Which versions are affected by CVE-2023-30350?

It affects 1 product.


Products: Fs S3900 24t4s Firmware.

## How do I fix CVE-2023-30350?

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

## Is CVE-2023-30350 being exploited?

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

Public exploit code:

- FS-S3900-24T4S - Privilege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-24033](https://insights.sbomify.com/CVE-2020-24033/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-30350 and fix it if it is affected.

What it is: CVE-2023-30350 is a high-severity vulnerability in n/a, published on 28 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-30350 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-2023-30350/ (Markdown: https://insights.sbomify.com/CVE-2023-30350/index.md)
```

## Sources

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

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