# CVE-2023-34965: Missing authorization in n/a

> Attackers can access the /link/ interface without authentication to leak user information in SSPanel-Uim.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2023
- **Updated:** 3 Jan 2025
- **Also known as:** GHSA-r2p2-p42x-rj6q

## What is CVE-2023-34965?

CVE-2023-34965 is a medium-severity missing authorization vulnerability in n/a, published on 13 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SSPanel-Uim 2023.3 does not restrict access to the /link/ interface which can lead to a leak of user information.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Sspanel-Uim Project Sspanel-Uim.

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

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

## Is CVE-2023-34965 being exploited?

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

Public exploit code:

- SSPanel UIM is a multi-purpose agency service sales management system specially designed for Shadowsocks / V2Ray / Trojan protocols. SSPanel-Uim version before 2023.3 does not restrict access to the /link/ interface,which can lead to a leak of user subscription information. (github_poc): https://github.com/AgentY0/CVE-2023-34965

## Fix prompt for AI coding agents

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

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

## Sources

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

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