CVE-2020-25747
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 · uneditedThe Telnet service of Rubetek RV-3406, RV-3409, and RV-3411 cameras (firmware versions v342, v339) can allow a remote attacker to gain access to RTSP and ONFIV services without authentication. Thus, the attacker can watch live streams from the camera, rotate the camera, change some settings (brightness, clarity, time), restart the camera, or reset it to factory settings.
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 Telnet service on Rubetek RV-3406, RV-3409, and RV-3411 IP cameras (firmware v342, v339) exposes RTSP and ONVIF services without authentication, allowing remote attackers to access video streams and manipulate camera settings including rotation, brightness, clarity, time configuration, restart, and factory reset functions.
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= 339= 342= 339= 342= 339= 342CVSS 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
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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 device model and firmware versionAccess the device web interface, check the system information page, or query the device via ONVIF GetDeviceInformation API. Look for model number (RV-3406, RV-3409, or RV-3411) and firmware version (339 or 342).Affected if The device is a Rubetek RV-3406, RV-3409, and RV-3411 with firmware version 339 or 342.
-
Verify Telnet service is exposedUse a network scanner (nmap -p 23 <target_ip>) or netcat (nc -zv <target_ip> 23) to check if port 23 (Telnet) is open and accepting connections on the device.Affected if Port 23 is open and a Telnet banner or login prompt is returned.
-
Confirm RTSP service accessibility without authenticationAttempt to connect to the RTSP port (default 554) using an RTSP client (e.g., ffmpeg -i rtsp://<target_ip>:554/stream) without providing any credentials. Observe if video streams are accessible.Affected if RTSP connection succeeds and video stream is accessible without authentication.
-
Confirm ONVIF service accessibility without authenticationSend an ONVIF GetCapabilities request to the device (typically port 8080 or 80) using a SOAP envelope without including any authentication tokens. Observe if the device responds with service capabilities.Affected if ONVIF GetCapabilities request returns a valid response without requiring authentication credentials.
The device is affected if it is a Rubetek RV-3406, RV-3409, or RV-3411 running firmware version 339 or 342, and either Telnet port 23 is exposed or RTSP/ONVIF services are accessible without authentication.
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 disable the Telnet service on affected devices if not required for legitimate management; if Telnet is needed, restrict network access via firewall or ACLs to trusted IPs only. Check vendor for firmware updates and apply them when 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-2020-25747 — 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-2020-25747 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