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

> An attacker can disclose session IDs via invalid authentication attempts to bypass authentication and access the administrative interface of SecurePoint UTM firewalls.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Apr 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-84pv-v7vg-7784

## What is CVE-2023-22620?

CVE-2023-22620 is a high-severity vulnerability in n/a, published on 12 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in SecurePoint UTM before 12.2.5.1. The firewall's endpoint at /spcgi.cgi allows sessionid information disclosure via an invalid authentication attempt. This can afterwards be used to bypass the device's authentication and get access to the administrative interface.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Securepoint Unified Threat Management.

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

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

## Is CVE-2023-22620 being exploited?

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

Public exploit code:

- SecurePoint UTM 12.x Session ID Leak (nuclei): http/cves/2023/CVE-2023-22620.yaml

## Other vulnerabilities in n/a

- [CVE-2023-22897](https://insights.sbomify.com/CVE-2023-22897/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-22620 is a high-severity vulnerability in n/a, published on 12 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22620 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-22620/ (Markdown: https://insights.sbomify.com/CVE-2023-22620/index.md)
```

## Sources

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

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