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

> Attackers can bypass authentication and access sensitive data by replaying admin tokens exposed in browser history or logs during OpenVPN config downloads.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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:** 9 Jul 2026
- **Also known as:** GHSA-cg99-p6r9-c75p

## What is CVE-2023-33621?

CVE-2023-33621 is a medium-severity 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

GL.iNET GL-AR750S-Ext firmware v3.215 inserts the admin authentication token into a GET request when the OpenVPN Server config file is downloaded. The token is then left in the browser history or access logs, potentially allowing attackers to bypass authentication via session replay.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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

It affects 1 product.


Products: Gl-Inet Gl-Ar750s Firmware.

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

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

## Is CVE-2023-33621 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-33620](https://insights.sbomify.com/CVE-2023-33620/): Weak cryptography in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-33621 is a medium-severity 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-33621 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-33621/ (Markdown: https://insights.sbomify.com/CVE-2023-33621/index.md)
```

## Sources

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

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