CVE-2019-25236
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 · uneditediSeeQ Hybrid DVR WH-H4 1.03R contains an unauthenticated vulnerability in the get_jpeg script that allows unauthorized access to live video streams. Attackers can retrieve video snapshots from specific camera channels by sending requests to the /cgi-bin/get_jpeg endpoint without authentication.
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 confidenceThe iSeeQ Hybrid DVR WH-H4 version 1.03R contains an unauthenticated command injection or path traversal flaw in the /cgi-bin/get_jpeg script. Attackers can exploit this to retrieve live video snapshots from specific camera channels without any authentication credentials by sending crafted HTTP requests to the vulnerable endpoint.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Availability
- High
CVSS:3.1/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 modelAccess the DVR web interface or use network enumeration tools (e.g., nmap, SNMP) to determine if the device is an iSeeQ Hybrid DVR WH-H4. Check the system information or device identification pages.Affected if The device model matches iSeeQ Hybrid DVR WH-H4
-
Verify the firmware versionLocate the firmware version in the DVR system settings, web interface, or via SNMP/sysinfo queries. Compare the installed version against 1.03R.Affected if The firmware version is 1.03R specifically
-
Confirm the vulnerable endpoint existsSend an HTTP GET request to http://[device-ip]/cgi-bin/get_jpeg or attempt to access this URL through a web browser. Check if the endpoint responds.Affected if The /cgi-bin/get_jpeg endpoint is accessible and returns a response
-
Assess network exposureDetermine if the DVR HTTP service is exposed to untrusted networks. Check firewall rules, NAT configurations, or port forwards that allow external access to the device's web interface on ports 80 or 443.Affected if The device HTTP service is reachable from networks outside the trusted local network without VPN or firewall restrictions
The environment is affected if the device is an iSeeQ Hybrid DVR WH-H4 running firmware version 1.03R with the /cgi-bin/get_jpeg endpoint exposed to untrusted networks.
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 update if available; otherwise, isolate the DVR behind a firewall or VPN to restrict unauthorized external access to the /cgi-bin/get_jpeg endpoint.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-25236 — 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-25236 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