CVE-2022-40989
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 'bandwidth WORD dlrate <1-9999> dlceil <1-9999> ulrate <1-9999> ulceil <1-9999> priority (highest|high|normal|low|lowest)' 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 · moderate confidenceStack-based buffer overflow in Siretta QUARTZ-GOLD router firmware's DetranCLI command parser, specifically in the bandwidth command handling function. The 'bandwidth WORD dlrate/dlceil/ulrate/ulceil/priority' template lacks proper bounds checking, allowing overflow via specially-crafted network packets to achieve arbitrary command execution.
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 router admin interface or check device label to confirm the model is Siretta QUARTZ-GOLDAffected if Device is not a Siretta QUARTZ-GOLD router, then not affected
-
Check firmware versionNavigate to router admin panel (typically at 192.168.1.1) and look under Status, System Info, or Firmware Upgrade section to find the installed firmware version stringAffected if Firmware version is NOT exactly g5.0.1.5-210720-141020, then not affected (only this specific version is vulnerable)
-
Verify DetranCLI service availabilityCheck if the DetranCLI service is exposed on the router. This is typically accessed via telnet or SSH to the router's CLI interface. Attempt to connect to the CLI and run '?' or 'help' to see available commandsAffected if DetranCLI service is not accessible or not present, then not affected (attack requires CLI access)
-
Confirm bandwidth command existsIn the DetranCLI interface, run the 'bandwidth ?' or 'bandwidth help' command to verify the bandwidth command template existsAffected if The bandwidth command is not available in the CLI, then not affected
User is affected only if running exactly firmware version g5.0.1.5-210720-141020 on a QUARTZ-GOLD router with the DetranCLI service accessible and the bandwidth command available.
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 dataImplement strict input validation and bounds checking on all CLI command parameters, particularly for the bandwidth command template fields. Consider input length limits and type checking for dlrate, dlceil, ulrate, and ulceil parameters.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40989 — 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-40989 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