CVE-2022-2070
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 · uneditedIn Grandstream GSD3710 in its 1.0.11.13 version, it's possible to overflow the stack since it doesn't check the param length before using the sscanf instruction. Because of that, an attacker could create a socket and connect with a remote IP:port by opening a shell and getting full access to the system. The exploit affects daemons dbmng and logsrv that are running on ports 8000 and 8001 by default.
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 confidenceStack-based buffer overflow in Grandstream GSD3710 firmware 1.0.11.13. The dbmng and logsrv daemons on ports 8000 and 8001 fail to validate parameter length before sscanf operations, allowing an attacker to overflow the stack and achieve remote code execution with full system access.
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= 1.0.11.13CVSS 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.
-
Confirm device model is Grandstream GSD3710Access the device web interface or check the device label to verify the model number is GSD3710Affected if Device is not a Grandstream GSD3710, then it is not affected by this specific CVE
-
Check installed firmware versionLog into the device web interface and navigate to System Settings > Firmware Upgrade, or use the device's web API to retrieve the firmware version. Compare the version string to 1.0.11.13Affected if Firmware version is exactly 1.0.11.13, then the device is running the affected version
-
Verify ports 8000 and 8001 are exposedFrom an external network host, run a port scan against the device IP targeting ports 8000 and 8001 (e.g., nmap -p 8000,8001 <device_ip>)Affected if Ports 8000 or 8001 are open and reachable from an untrusted network, then the vulnerable dbmng and logsrv services are exposed
-
Check if dbmng and logsrv daemons are runningIf you have SSH or console access to the device, run 'ps | grep -E "(dbmng|logsrv)"' to confirm these processes are activeAffected if Both dbmng and logsrv daemons are running on the device, the vulnerability is present and exploitable
A device is affected if it is a Grandstream GSD3710 running firmware version 1.0.11.13 with ports 8000 or 8001 accessible and the dbmng/logsrv daemons active.
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 patch if available; otherwise restrict network access to ports 8000/8001 via firewall or VLAN segmentation to prevent unauthenticated remote exploitation.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2070 — 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-2022-2070 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