# CVE-2023-33468: Auth bypass in n/a

> Attackers can remotely extract connection codes to bypass authentication and manipulate KramerAV VIA devices without physical access.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 9 Aug 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-jgwh-r9rp-8372

## What is CVE-2023-33468?

CVE-2023-33468 is a critical authentication bypass vulnerability in n/a, published on 9 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

KramerAV VIA Connect (2) and VIA Go (2) devices with a version prior to 4.0.1.1326 exhibit a vulnerability that enables remote manipulation of the device. This vulnerability involves extracting the connection confirmation code remotely, bypassing the need to obtain it directly from the physical screen.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 2 products.


Products: Kramerav via Connect2 Firmware, Kramerav via Go2 Firmware.

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

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

## Is CVE-2023-33468 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-33469](https://insights.sbomify.com/CVE-2023-33469/): Code injection in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-33468 is a critical authentication bypass vulnerability in n/a, published on 9 Aug 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-33468 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-33468/ (Markdown: https://insights.sbomify.com/CVE-2023-33468/index.md)
```

## Sources

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

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