Qcp200w FirmwareOperating system · Qcp

CVE-2021-26627

HIGH · 7.5 CVSS v3.1 Published 2022-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Real-time image information exposure is caused by insufficient authentication for activated RTSP port. This vulnerability could allow to remote attackers to send the RTSP requests using ffplay command and lead to leakage a live image.

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

Insufficient authentication on an activated RTSP (Real Time Streaming Protocol) port allows remote unauthenticated attackers to access live video streams by sending RTSP requests via tools like ffplay, leading to exposure of real-time image information.

MitigationEnable and enforce proper authentication mechanisms for the RTSP service to prevent unauthorized access to live video 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
Qcp200w FirmwareOperating system
Affected:all versions

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 RTSP service status
    Access the device admin interface or check running services to determine if the RTSP server is enabled. Common ports for RTSP are 554, 8554, or device-specific ports. Use 'netstat -an | grep -E "554|8554"' or check device documentation for RTSP port information.
    Affected if RTSP service is running and accessible on the network without any access restrictions
  2. Locate RTSP configuration file
    Check the device configuration files for RTSP settings. Common locations include /etc/rtsp.conf, /mnt/mtd/Config/rtsp.ini, or through the device's web admin interface under Network or Streaming settings.
    Affected if RTSP authentication settings are set to disabled, blank, or use default/weak credentials
  3. Test RTSP authentication
    Attempt to connect to the RTSP port using a tool like ffplay (ffplay rtsp://<device_ip>:<port>/) or a browser-based RTSP player without providing credentials. Observe if a stream is accessible without authentication prompt.
    Affected if Live video stream is accessible without being prompted for username/password
  4. Verify authentication enforcement
    If accessing the web admin interface is possible, navigate to RTSP service settings and verify whether 'Authentication' or 'Auth' is explicitly enabled and set to a strong configuration rather than 'None' or 'Disabled'.
    Affected if Authentication is not enforced or is set to 'disabled'/'none' in the RTSP service configuration
  5. Check for default or blank credentials
    Examine the RTSP configuration or device documentation to determine what authentication type is configured. Look for fields like 'Username', 'Password', 'AuthMode' and verify they are not using default manufacturer credentials or blank values.
    Affected if Default manufacturer credentials or no password is configured for RTSP access

The device is affected if the RTSP service is active and accessible without requiring valid authentication credentials.

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 and enforce proper authentication mechanisms for the RTSP service to prevent unauthorized access to live video streams.

Fix this in Qcp200w Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-26627 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-26627 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