CVE-2023-35830
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSTW (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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe STW TCG-4 Connectivity Module contains a critical authentication bypass vulnerability allowing unauthenticated attackers to execute arbitrary code with root privileges via SMS commands sent over LTE/4G networks. This represents a complete compromise of the device with no authentication requirements.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.01r1= 3.02r0= 3.03r0= 3.04r2= 3.04r2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the STW TCG-4 device model and firmware versionAccess the device management interface or use the vendor's diagnostic tool to retrieve the exact firmware version. This is typically found in the system information or device status page of the web-based management console, or via CLI commands specified in the device documentation.Affected if The firmware version matches 3.01r1, 3.02r0, 3.03r0, or 3.04r2 for TCG-4, or 3.04r2 for TCG-4lite.
-
Determine if SMS functionality is enabledExamine the device configuration settings to verify whether the SMS-based command interface is active. Check for SMS reception settings, SMS command processing, or remote command via SMS options in the device management interface.Affected if SMS functionality is turned on and available to receive commands.
-
Verify SMS interface exposure to external networksReview network configuration to confirm whether the device's LTE/4G modem is configured to accept SMS commands from external sources or untrusted networks. Check for any port/service listings related to SMS or remote command reception.Affected if The device accepts SMS commands from external sources without additional network filtering or authentication layers.
-
Check for unexpected or unauthorized SMS command activityReview device logs, command history, or event logs for any SMS-based commands that were processed, particularly those involving system operations, file execution, or configuration changes.Affected if There are logs of SMS commands that were executed, especially those involving root-level operations or arbitrary code execution.
A user is affected if they have an STW TCG-4 or TCG-4lite device running any of the listed firmware versions with SMS functionality enabled and exposed to external networks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately restrict SMS-based command interfaces through network filtering or disable SMS functionality if not required, implement additional authentication layers for remote commands, and apply vendor-provided firmware updates as they become available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35830 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-35830 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data