dbcve.org
Rut240 FirmwareOperating system · Teltonika Networks

CVE-2023-31728

HIGH · 7.0 CVSS v3.1 Published 2024-02-17
Fix available
A fix is available. Upgrade to 00.07.04.2 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Teltonika RUT240 devices with firmware before 07.04.2, when bridge mode is used, sometimes make SSH and HTTP services available on the IPv6 WAN interface even though the UI shows that they are only available on the LAN interface.

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 confidence

Teltonika RUT240 routers with firmware prior to 07.04.2 have a configuration flaw in bridge mode where SSH and HTTP services are inadvertently exposed on the IPv6 WAN interface despite the UI indicating they should only be accessible from the LAN interface. This allows remote attackers on the IPv6 WAN to reach these services.

MitigationUpgrade firmware to version 07.04.2 or later to resolve the service exposure. Alternatively, block IPv6 WAN traffic to ports 22 and 80/443 at the network perimeter as a compensating control.

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
Rut240 FirmwareOperating system
Affected:< 00.07.04.2

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

CVSS:3.1/AV:L/AC:H/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. Verify device model is Teltonika RUT240
    Log into the router web UI or check the device label to confirm the model number is RUT240
    Affected if Device is not a Teltonika RUT240 (different models have different affected versions)
  2. Check firmware version against 07.04.2
    Navigate to Router Status or System > Firmware in the web UI to view the installed firmware version. Compare it to 00.07.04.2
    Affected if Firmware version is less than 07.04.2 (versions prior to 00.07.04.2 are affected)
  3. Confirm bridge mode is enabled
    Check the network configuration or WAN settings in the web UI to see if bridge mode is configured
    Affected if Bridge mode is enabled on the device
  4. Verify IPv6 is enabled on WAN interface
    Check the IPv6 settings in the WAN or Network > Interfaces section of the web UI to see if IPv6 is active on the WAN side
    Affected if IPv6 is enabled on the WAN interface
  5. Test SSH and HTTP accessibility from IPv6 WAN
    From an external IPv6-enabled host, attempt to connect to the router's public IPv6 address on ports 22 (SSH) and 80/443 (HTTP/HTTPS)
    Affected if SSH (port 22) or HTTP/HTTPS (ports 80/443) are reachable from the IPv6 WAN address when they should not be

The router is affected if it is a RUT240 with firmware prior to 07.04.2, has bridge mode enabled, and has IPv6 WAN configured such that SSH or HTTP services are exposed to the IPv6 WAN interface.

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 00.07.04.2 or later
Fixed in 00.07.04.2
Interim mitigation

Upgrade firmware to version 07.04.2 or later to resolve the service exposure. Alternatively, block IPv6 WAN traffic to ports 22 and 80/443 at the network perimeter as a compensating control.

Recommended fix High confidence

Firmware 00.07.04.2 or later

  1. 1. Back up the current device configuration through the web UI (System > Backup).
  2. 2. Download the firmware version 00.07.04.2 or later from the official Teltonika website (teltonika-networks.com).
  3. 3. Access the router's web interface and navigate to System > Firmware > Flash new firmware.
  4. 4. Upload the downloaded firmware file and initiate the flashing process.
  5. 5. Wait for the device to reboot and reapply the configuration.
  6. 6. After upgrade, verify that SSH and HTTP services are not accessible on the WAN IPv6 interface by attempting to connect from an external IPv6 address.
Caveat Standard firmware upgrade risks apply - ensure configuration backup before upgrading

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

Fix this in Rut240 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31728 — 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-31728 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