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

> Attackers can gain root access and execute arbitrary code remotely via SMS without authentication on STW TCG-4 connectivity modules.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2023
- **Updated:** 27 Nov 2024
- **Also known as:** GHSA-xcf7-g637-p7f5

## What is CVE-2023-35830?

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

### Official description

STW (aka Sensor-Technik Wiedemann) TCG-4 Connectivity Module DeploymentPackage_v3.03r0-Impala and DeploymentPackage_v3.04r2-Jellyfish and TCG-4lite Connectivity Module DeploymentPackage_v3.04r2-Jellyfish allow an attacker to gain full remote access with root privileges without the need for authentication, giving an attacker arbitrary remote code execution over LTE / 4G network via SMS.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 2 products.


Products: Stw-Mobile-Machines Tcg-4 Firmware, Stw-Mobile-Machines Tcg-4lite Firmware.

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

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

## Is CVE-2023-35830 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-35830 is a critical authentication bypass vulnerability in n/a, published on 29 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-35830 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-35830/ (Markdown: https://insights.sbomify.com/CVE-2023-35830/index.md)
```

## Sources

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

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