Security readout for executives and security teams
Plain-English summary
ESCAM QD-900 WIFI HD cameras can expose a downloadable configuration backup without requiring login. That backup may contain administrator credentials and sensitive device settings, so an internet- or LAN-reachable camera could leak information that enables further compromise.
Executive priority
Prioritize remediation for any internet-exposed or broadly reachable ESCAM QD-900 cameras. The vulnerability is high severity, remotely reachable, requires no authentication, and may disclose administrator credentials, making it a strong candidate for rapid containment even without confirmed active exploitation.
Technical view
CVE-2020-36871 affects the ESCAM QD-900 WIFI HD Camera according to the provided bundle. The unauthenticated /web/cgi-bin/hi3510/backup.cgi endpoint can allow remote download of a compressed configuration backup without authentication or authorization. The issue is categorized as CWE-306 and has CVSS 4.0 score 8.7 with network attack vector, low complexity, no privileges, and no user interaction required.
Likely exposure
Highest risk applies to ESCAM QD-900 WIFI HD cameras reachable from the internet, guest networks, shared LANs, or any untrusted segment. Exposure is lower if devices are isolated behind strict firewall rules and management interfaces are only reachable through trusted administrative paths. The bundle lists affected version as "0" with default status unknown and no CPEs, so exact fleet matching should be verified by asset inventory and vendor identifiers.
Exploitation context
The source bundle includes public exploit references from Packet Storm and Exploit-DB, indicating public exploitation knowledge or proof-of-concept availability. However, KEV is false and the bundle does not provide evidence of active in-the-wild exploitation, so active exploitation should not be asserted from this data alone.
Researcher notes
Do not claim confirmed active exploitation based on this bundle. Public exploit references are present, but KEV is false. Patch status is not established in the supplied data, so remediation should emphasize exposure reduction, segmentation, credential rotation where appropriate, and checking vendor guidance.
Mitigation direction
- Identify whether any ESCAM QD-900 WIFI HD cameras are deployed, especially at internet edges or on untrusted networks.
- Remove public internet exposure for camera management interfaces and restrict access to trusted administrative networks only.
- Place affected cameras on an isolated network segment with firewall rules limiting inbound access to required management sources.
- Review vendor guidance for firmware updates, replacement guidance, or official remediation because the bundle does not include patch evidence.
- Rotate camera administrative credentials and any reused credentials if configuration backup exposure is suspected.
- Review network and device logs for unexpected access to configuration backup functionality, while avoiding assumptions of compromise without supporting evidence.
Validation and detection
- Confirm asset inventory for ESCAM QD-900 WIFI HD cameras and record firmware or product identifiers where available.
- From an authorized defensive assessment path, verify that unauthenticated users cannot access configuration backup functionality from untrusted networks.
- Check external exposure management, firewall policy, and remote access configuration to ensure camera administrative paths are not publicly reachable.
- Confirm segmentation prevents guest, user, and internet-originated traffic from reaching camera management interfaces.
- Document whether vendor remediation exists after checking official vendor guidance, since the provided bundle does not include a confirmed fixed version.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-36871 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- https://packetstorm.news/files/id/156492/CVE reference · exploit
- https://www.exploit-db.com/exploits/48107CVE reference · exploit
- https://www.vulncheck.com/advisories/escam-qd900-unauthenticated-config-disclosureCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.