dbcve.org
Rv 3406 FirmwareOperating system · Rubetek

CVE-2020-25748

HIGH · 8.1 CVSS v3.1 Published 2020-09-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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
A Cleartext Transmission issue was discovered on Rubetek RV-3406, RV-3409, and RV-3411 cameras (firmware versions v342, v339). Someone in the middle can intercept and modify the video data from the camera, which is transmitted in an unencrypted form. One can also modify responses from NTP and RTSP servers and force the camera to use the changed values.

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

Rubetek RV-3406, RV-3409, and RV-3411 IP cameras transmit video streams in cleartext without encryption, allowing a network-adjacent attacker to intercept and modify video data via MITM. Additionally, NTP and RTSP server responses are also transmitted unencrypted, enabling attackers to manipulate camera time settings and alter RTSP configuration responses.

MitigationEnable encrypted video streaming (RTSP over TLS/HTTPS), implement NTS for secure NTP, and ensure all camera network communications use TLS. If the camera firmware lacks encryption support, consider network segmentation or replacing with hardware supporting encrypted streams.

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
Rv 3406 FirmwareOperating system
Affected:= 339= 342
Rv 3409 FirmwareOperating system
Affected:= 339= 342
Rv 3411 FirmwareOperating system
Affected:= 339= 342

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

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

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

  1. Identify camera model and firmware version
    Access the camera's web interface or use SNMP/SSH to query the device. Look for the exact model number (RV-3406, RV-3409, or RV-3411) and note the firmware version displayed in the system information or status page.
    Affected if The camera is a Rubetek RV-3406, RV-3409, or RV-3411 running firmware version 339 or 342.
  2. Check RTSP stream encryption status
    Capture network traffic on the camera's VLAN while the camera streams video. Inspect the RTSP traffic (port 554 typically) using Wireshark or similar. Look for plain RTSP packets without TLS wrapping.
    Affected if RTSP video streams are transmitted over plain TCP without TLS encryption (not rtsps:// or RTSP over TLS).
  3. Verify video stream protocol in use
    Attempt to access the camera video stream via the web interface. Check if the video player loads streams over HTTP (port 80) or HTTPS (port 443). Inspect the video URL in the browser developer tools or proxy traffic.
    Affected if Video streams are accessible over unencrypted HTTP rather than HTTPS.
  4. Check NTP configuration and transport
    Monitor network traffic from the camera to the NTP server (typically UDP port 123). Use Wireshark to capture and inspect whether NTP packets are plain (vulnerable) or using NTS (Network Time Security).
    Affected if The camera synchronizes time using unencrypted NTP without NTS authentication.
  5. Inspect RTSP configuration response encryption
    Capture RTSP DESCRIBE or SETUP responses from the camera. Examine whether the RTSP server responses (SDP descriptions, transport headers) are sent over plain TCP or TLS-encrypted connections.
    Affected if RTSP server responses are transmitted in cleartext without TLS protection.

You are affected if you own a Rubetek RV-3406, RV-3409, or RV-3411 camera running firmware 339 or 342 AND any of your video streams, NTP traffic, or RTSP configuration responses are transmitted over unencrypted protocols (plain HTTP, RTSP, or NTP instead of HTTPS, RTSP over TLS, or NTS).

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable encrypted video streaming (RTSP over TLS/HTTPS), implement NTS for secure NTP, and ensure all camera network communications use TLS. If the camera firmware lacks encryption support, consider network segmentation or replacing with hardware supporting encrypted streams.

Fix this in Rv 3406 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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