# CVE-2023-22897: Information disclosure in n/a

> An authenticated user can retrieve uninitialized memory contents via the /spcgi.cgi endpoint, leading to information disclosure.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 12 Apr 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-6pw8-5p8j-m67x

## What is CVE-2023-22897?

CVE-2023-22897 is a medium-severity vulnerability in n/a, published on 12 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in SecurePoint UTM before 12.2.5.1. The firewall's endpoint at /spcgi.cgi allows information disclosure of memory contents to be achieved by an authenticated user. Essentially, uninitialized data can be retrieved via an approach in which a sessionid is obtained but not used.

Weakness: CWE-908 (Use of Uninitialized Resource)

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

It affects 1 product.


Products: Securepoint Unified Threat Management.

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

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

## Is CVE-2023-22897 being exploited?

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

Public exploit code:

- Securepoint UTM - Leaking Remote Memory Contents (nuclei): http/cves/2023/CVE-2023-22897.yaml

## Other vulnerabilities in n/a

- [CVE-2023-22620](https://insights.sbomify.com/CVE-2023-22620/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-22897 is a medium-severity vulnerability in n/a, published on 12 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22897 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-2023-22897/ (Markdown: https://insights.sbomify.com/CVE-2023-22897/index.md)
```

## Sources

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

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