dbcve.org
Gxv3611ir Hd FirmwareOperating system · Grandstream

CVE-2019-10661

CRITICAL · 9.8 CVSS v3.1 Published 2019-03-30
Fix available
A fix is available. Upgrade to 1.0.3.23 or later.
See remediation →
100/100
Remediation priority · Urgent
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
On Grandstream GXV3611IR_HD before 1.0.3.23 devices, the root account lacks a password.

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 confidence

The Grandstream GXV3611IR_HD IP cameras (versions prior to 1.0.3.23) ship with the root account having no password configured, allowing unauthenticated remote attackers to gain complete administrative control of the device.

MitigationApply firmware version 1.0.3.23 or later to all affected devices. Until patched, restrict network access to camera management interfaces via firewall rules or VLAN isolation.

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
Gxv3611ir Hd FirmwareOperating system
Affected:< 1.0.3.23

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. Identify the device model
    Log into the camera web interface or use network discovery to confirm the device is a Grandstream GXV3611IR_HD IP camera. Check the device label or the system information page in the web UI for the exact model number.
    Affected if The device is a Grandstream GXV3611IR_HD model.
  2. Check the firmware version
    In the camera web interface, navigate to Status or System Info page to view the firmware version. Alternatively, access the device via SSH or Telnet (if enabled) and run 'get system_info' or check the upgrade page in the web UI.
    Affected if The firmware version is lower than 1.0.3.23.
  3. Verify root account accessibility
    Attempt to access the device via SSH or Telnet using the username 'root' with no password or a blank password field. If the device allows login without a password, the vulnerability is present.
    Affected if Root login succeeds without requiring a password.
  4. Check for default credentials
    Try accessing the web interface with common default credentials for Grandstream devices (admin/admin, admin/12345, root/root, or root/(blank password)). If any default credential works, the device may be vulnerable.
    Affected if Default credentials grant access to the administrative interface.

The device is affected if it is a Grandstream GXV3611IR_HD camera running firmware version prior to 1.0.3.23 with an accessible root account that does not require a password.

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.

dbcve · scoped
Upgrade available Upgrade to 1.0.3.23 or later
Fixed in 1.0.3.23
Interim mitigation

Apply firmware version 1.0.3.23 or later to all affected devices. Until patched, restrict network access to camera management interfaces via firewall rules or VLAN isolation.

Recommended fix High confidence

1.0.3.23

  1. Identify all Grandstream GXV3611IR_HD devices on the network that need patching
  2. Access the device web interface or administrative console
  3. Navigate to the firmware version information to confirm the current version is below 1.0.3.23
  4. Download firmware version 1.0.3.23 or later from the official Grandstream support website (www.grandstream.com)
  5. Backup the current device configuration if possible
  6. Access the firmware upgrade section in the device administration interface
  7. Upload and apply the new firmware version 1.0.3.23
  8. Verify the upgrade was successful by checking the new firmware version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gxv3611ir Hd Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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