dbcve.org
Rut200 FirmwareOperating system · Teltonika Networks

CVE-2023-32350

HIGH · 8.8 CVSS v3.1 Published 2023-05-22
Fix available
A fix is available. Upgrade to after 00.07.03 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Versions 00.07.00 through 00.07.03 of Teltonika’s RUT router firmware contain an operating system (OS) command injection vulnerability in a Lua service. An attacker could exploit a parameter in the vulnerable function that calls a user-provided package name by instead providing a package with a malicious name that contains an OS command injection payload.

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 · moderate confidence

OS command injection vulnerability in Teltonika RUT router firmware (versions 00.07.00-00.07.03) within a Lua service. The vulnerable function accepts a user-supplied package name parameter without proper sanitization, allowing an attacker to embed OS command injection payloads within the package name that get executed on the underlying operating system.

MitigationUpdate to a patched firmware version if available; otherwise, implement strict input validation on the package name parameter in the Lua service to reject shell metacharacters and ensure only valid package identifiers are processed.

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
Rut200 FirmwareOperating system
Affected:>= 00.07.00, <= 00.07.03
Rut240 FirmwareOperating system
Affected:>= 00.07.00, <= 00.07.03
Rut241 FirmwareOperating system
Affected:>= 00.07.00, <= 00.07.03
Rut300 FirmwareOperating system
Affected:>= 00.07.00, <= 00.07.03
Rut360 FirmwareOperating system
Affected:>= 00.07.00, <= 00.07.03
Rut901 FirmwareOperating system
Affected:>= 00.07.00, <= 00.07.03
Rut950 FirmwareOperating system
Affected:>= 00.07.00, <= 00.07.03
Rut951 FirmwareOperating system
Affected:>= 00.07.00, <= 00.07.03

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Access the router web interface or use the command line to determine the exact model (Rut200, Rut240, Rut241, Rut300, Rut360, Rut901, Rut950, or Rut951)
    Affected if The model is any of the listed Teltonika Rut series routers
  2. Check the installed firmware version
    Navigate to the router's web interface (typically Status > Device > Firmware) or use the command line to retrieve the firmware version string
    Affected if The firmware version is 00.07.00, 00.07.01, 00.07.02, or 00.07.03
  3. Determine if the Lua package management service is enabled
    Inspect the router's running services or configuration files to see if the Lua-based package management functionality is active and accessible
    Affected if The Lua service that handles package name parameters is exposed and accepting user input

Your environment is affected if you are running any of the listed Teltonika Rut router models (Rut200, Rut240, Rut241, Rut300, Rut360, Rut901, Rut950, Rut951) with firmware version 00.07.00 through 00.07.03 and the vulnerable Lua service is enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 00.07.03
Interim mitigation

Update to a patched firmware version if available; otherwise, implement strict input validation on the package name parameter in the Lua service to reject shell metacharacters and ensure only valid package identifiers are processed.

Recommended fix Moderate confidence

Firmware version 00.07.04 or later

  1. 1. Identify the specific Teltonika RUT router model from the affected list (RUT200, Rut240, Rut241, Rut300, Rut360, Rut901, Rut950, or Rut951)
  2. 2. Access the router's web interface or management console
  3. 3. Navigate to the firmware upgrade section (typically under System > Firmware or similar)
  4. 4. Download the latest firmware version from Teltonika's official support website (www.teltonika-networks.com)
  5. 5. Upload and apply firmware version 00.07.04 or later
  6. 6. Verify the upgrade was successful by checking the firmware version in the router's web interface
  7. 7. After upgrade, validate that the vulnerable Lua service function no longer accepts malicious command injection payloads
Caveat Review Teltonika release notes for version 00.07.04 to check for any configuration or feature changes that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rut200 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32350 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32350 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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