dbcve.org
Nc250 FirmwareOperating system · Tp Link

CVE-2017-10796

MEDIUM · 6.5 CVSS v3.1 Published 2017-07-02
Fix available
A fix is available. Upgrade to after 1.2.1 or later.
See remediation →
70/100
Remediation priority · Elevated
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
On TP-Link NC250 devices with firmware through 1.2.1 build 170515, anyone can view video and audio without authentication via an rtsp://admin@yourip:554/h264_hd.sdp URL.

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

The TP-Link NC250 camera's RTSP service allows unauthenticated access to video and audio streams via a specially crafted RTSP URL (rtsp://admin@yourip:554/h264_hd.sdp), bypassing the admin authentication requirement.

MitigationApply the latest firmware update from TP-Link for the NC250 device; if no patched firmware is available, restrict network access to the RTSP service via firewall rules or place the device behind a VPN.

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
Nc250 FirmwareOperating system
Affected:<= 1.2.1

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

CVSS:3.1/AV:A/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 the device model
    Check the device label or access the web interface to confirm it is a TP-Link NC250 camera
    Affected if The device is not a TP-Link NC250 model
  2. Check the firmware version
    Access the camera's web administration panel (typically via HTTP on port 80) and navigate to the System or Settings section to view the firmware version
    Affected if The firmware version is 1.2.1 or lower
  3. Verify RTSP service accessibility
    Check if port 554 (RTSP) is open and reachable on the camera's IP address using a port scanner or netstat command
    Affected if Port 554 is exposed to the network
  4. Test unauthenticated RTSP access
    Attempt to connect to rtsp://[camera_ip]:554/h264_hd.sdp or rtsp://admin@[camera_ip]:554/h264_hd.sdp without providing valid credentials
    Affected if The RTSP stream connects and displays video without requiring authentication

You are affected if you have a TP-Link NC250 camera running firmware version 1.2.1 or lower with the RTSP service (port 554) accessible on your network, and unauthenticated RTSP URL access succeeds.

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
Upgrade available Upgrade to a release after 1.2.1
Interim mitigation

Apply the latest firmware update from TP-Link for the NC250 device; if no patched firmware is available, restrict network access to the RTSP service via firewall rules or place the device behind a VPN.

Fix this in Nc250 Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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