dbcve.org
CWE-331Weakness · CWE-331

CVE-2020-36925

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
Arteco Web Client DVR/NVR contains a session hijacking vulnerability with insufficient session ID complexity that allows remote attackers to bypass authentication. Attackers can brute force session IDs within a specific numeric range to obtain valid sessions and access live camera streams without authorization.

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

Arteco Web Client DVR/NVR contains a session hijacking vulnerability caused by insufficient session ID complexity. The session IDs follow a predictable numeric range that allows remote attackers to brute force valid session identifiers and bypass authentication, enabling unauthorized access to live camera streams.

MitigationImplement cryptographically random session IDs with sufficient entropy (minimum 128-bit) and add rate limiting or account lockout mechanisms to prevent brute force attacks on session IDs.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Arteco Web Client is installed
    Identify the Arteco Web Client DVR/NVR software running in your environment by checking running services, web server configurations, or installed applications that match this product name
    Affected if The system is running Arteco Web Client DVR/NVR software
  2. Determine installed version
    Check the installed version of Arteco Web Client through the software's about panel, help menu, or system information if accessible, then compare against any known version boundaries
    Affected if The installed version falls within any known vulnerable version range for this CVE
  3. Login and capture session ID
    Authenticate to the Arteco Web Client interface and capture the session identifier (typically found in cookies, URL parameters, or response headers) after successful login
    Affected if A session is established and a session ID is generated
  4. Analyze session ID complexity
    Examine the captured session ID for length, character set (numeric only vs alphanumeric), and entropy. Count the number of unique characters and estimate the possible ID space
    Affected if The session ID uses only numeric characters, is short (under 20 characters), or appears to use a sequential or predictable pattern
  5. Test session ID predictability
    If accessible, generate multiple new sessions by logging in repeatedly and compare session IDs to determine if they follow an incremental or predictable sequence
    Affected if Session IDs follow a sequential, incremental, or otherwise predictable pattern across multiple sessions
  6. Check for rate limiting on authentication
    Attempt multiple failed authentication attempts or observe whether the system implements rate limiting, account lockout, or captcha mechanisms on login attempts
    Affected if No rate limiting or account lockout mechanisms are present, allowing unlimited session ID guessing attempts

Your environment is affected if you are running Arteco Web Client DVR/NVR and the generated session IDs consist only of short numeric sequences or follow a predictable pattern that could be brute forced.

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

Implement cryptographically random session IDs with sufficient entropy (minimum 128-bit) and add rate limiting or account lockout mechanisms to prevent brute force attacks on session IDs.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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