CVE-2022-40987
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 · uneditedSeveral stack-based buffer overflow vulnerabilities exist in the DetranCLI command parsing functionality of Siretta QUARTZ-GOLD G5.0.1.5-210720-141020. A specially-crafted network packet can lead to arbitrary command execution. An attacker can send a sequence of requests to trigger these vulnerabilities.This buffer overflow is in the function that manages the '(ddns1|ddns2) username WORD password CODE' command template.
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 the DetranCLI command parser of Siretta QUARTZ-GOLD G5.0.1.5-210720-141020. The function handling 'ddns1/ddns2 username WORD password CODE' commands does not properly validate input length before copying to a stack buffer, allowing an attacker to overflow the buffer and achieve arbitrary command execution via specially-crafted network packets.
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= g5.0.1.5-210720-141020CVSS 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 device modelAccess the router web interface or CLI and confirm the device is Siretta QUARTZ-GOLD. Check the device label, web UI footer, or system information page.Affected if Device is not a Siretta QUARTZ-GOLD router, then it is not affected by this specific vulnerability.
-
Check firmware versionIn the router web interface, go to Status > System Information or use the CLI command 'ver' or 'show version' to retrieve the firmware build string.Affected if Firmware version is NOT exactly g5.0.1.5-210720-141020, then it is not affected. This vulnerability affects only this exact build.
-
Locate DetranCLI serviceCheck if the DetranCLI service is accessible via telnet, SSH, or serial connection on the router. Look for port 23/telnet or port 22/ssh in the router's port forwarding or service configuration.Affected if DetranCLI is not exposed or accessible remotely, then the attack surface is limited, though the vulnerability still exists in the firmware.
-
Verify ddns command existsAccess DetranCLI (via telnet/SSH/serial) and attempt to access the ddns configuration context. Type 'ddns ?' or 'ddns1 ?' to see if the ddns command is available.Affected if The ddns/ddns1/ddns2 command is not present in DetranCLI, then this specific vulnerability path does not apply.
The environment is affected only if the device is a Siretta QUARTZ-GOLD running firmware exactly version g5.0.1.5-210720-141020 AND the DetranCLI service with ddns commands is accessible.
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 implement network access controls to limit exposure to trusted networks only, as this vulnerability is exploitable via network packets without authentication.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40987 — 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-40987 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