CVE-2019-11560
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 · uneditedA buffer overflow vulnerability in the streaming server provided by hisilicon in HI3516 models allows an unauthenticated attacker to remotely run arbitrary code by sending a special RTSP over HTTP packet. The vulnerability was found in many cameras using hisilicon's hardware and software, as demonstrated by TENVIS cameras 1.3.3.3, 1.2.7.2, 1.2.1.4, 7.1.20.1.2, and 13.1.1.1.7.2; FDT FD7902 11.3.14.1.3 and 10.3.14.1.3; FOSCAM cameras 3.2.1.1.1_0815 and 3.2.2.2.1_0815; and Dericam cameras V11.3.8.1.12.
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 confidenceA buffer overflow in the Hisilicon HI3516 streaming server allows unauthenticated remote code execution via specially crafted RTSP over HTTP packets. This affects multiple IP camera brands including TENVIS, FDT, FOSCAM, and Dericam.
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 dataall versionsCVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device chipsetAccess the camera's web interface or check the device specifications/datasheet to determine if the device uses a Hisilicon HI3516 processor. This information is typically found under 'Device Info', 'System Info', or in the hardware specifications.Affected if The device is confirmed to use a Hisilicon HI3516 chipset
-
Check RTSP over HTTP configurationLog into the camera's web interface and navigate to the RTSP or Network settings. Look for any option enabling 'RTSP over HTTP' or 'RTSP tunnel' functionality. This is often found under Advanced Settings > Network > RTSP or similar paths depending on the vendor interface.Affected if RTSP over HTTP is enabled on the device
-
Verify RTSP service exposureScan the device's accessible network ports using a tool like nmap (e.g., nmap -p 554,8080,8554 <device_ip>) to identify if RTSP ports (typically 554, 8080, or custom HTTP ports) are open and responding.Affected if RTSP service ports are open and accessible on the network
-
Confirm device vendor and modelCheck the camera's label, web interface, or documentation to identify if the device is from TENVIS, FDT, FOSCAM, or Dericam, as these brands are known to use the affected Hisilicon HI3516 chip.Affected if The device is a TENVIS, FDT, FOSCAM, or Dericam IP camera model using the HI3516 chipset
-
Review network accessibilityDetermine whether the device RTSP service is accessible from untrusted networks by checking firewall rules, router configurations, and whether the device is directly exposed to the internet.Affected if The RTSP over HTTP service is accessible from outside the local trusted network
A device is affected if it uses a Hisilicon HI3516 chipset with RTSP over HTTP enabled and that service is network-accessible, regardless of firmware version since all versions are vulnerable.
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 dataApply vendor firmware updates when available; if no patch exists, isolate affected devices on restricted network segments and block RTSP over HTTP traffic at the network boundary.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11560 — 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-2019-11560 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