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

> Attackers on the same network can bypass authentication by reusing the device's NAT-assigned IP address due to weak session management.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-xvj2-rc4p-2jx2

## What is CVE-2023-33684?

CVE-2023-33684 is a medium-severity authentication bypass vulnerability in n/a, published on 6 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Weak session management in DB Elettronica Telecomunicazioni SpA SFT DAB 600/C Firmware: 1.9.3 Bios firmware: 7.1 (Apr 19 2021) Gui: 2.46 FPGA: 169.55 uc: 6.15 allows attackers on the same network to bypass authentication by re-using the IP address assigned to the device by the NAT protocol.

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

It affects 2 products.


Products: Dbbroadcast Sft Dab 600\/C Bios, Dbbroadcast Sft Dab 600\/C Firmware.

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

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

## Is CVE-2023-33684 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-33684 is a medium-severity authentication bypass vulnerability in n/a, published on 6 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-33684 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-33684/ (Markdown: https://insights.sbomify.com/CVE-2023-33684/index.md)
```

## Sources

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

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