CVE-2022-47036
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 · uneditedSiklu TG Terragraph devices before approximately 2.1.1 have a hardcoded root password that has been revealed via a brute force attack on an MD5 hash. It can be used for "debug login" by an admin. NOTE: the vulnerability is not fixed by the 2.1.1 firmware; instead, it is fixed in newer hardware, which would typically be used with firmware 2.1.1 or later.
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 confidenceSiklu TG Terragraph devices contain a hardcoded root password stored as an MD5 hash that has been cracked via brute force, allowing unauthorized 'debug login' access with administrative privileges. The vulnerability exists in devices before firmware version 2.1.1.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device modelIdentify the specific hardware model by checking the device label, management interface, or CLI output. Verify the device is a Siklu TG Terragraph unit.Affected if The device is not a Siklu TG Terragraph product
-
Check firmware versionAccess the device management interface or CLI and retrieve the current firmware version. Compare it against version 2.1.1.Affected if The installed firmware version is earlier than 2.1.1
-
Inspect for debug access interfacesCheck if the device exposes any debug login, root shell, or administrative console interfaces that could be accessed using hardcoded credentials.Affected if Debug or root access interfaces are accessible on the device
If the device is a Siklu TG Terragraph unit running firmware earlier than version 2.1.1, it contains the hardcoded root password and is vulnerable to unauthenticated administrative access.
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.
dbcve · scopedThis vulnerability cannot be remediated via firmware update; affected devices require replacement with newer hardware that does not contain the hardcoded credentials.
Newer Siklu TG Terragraph hardware (firmware 2.1.1 or later on new hardware)
- This vulnerability requires hardware replacement rather than software remediation
- The hardcoded root password is embedded in the device firmware/hardware and cannot be fixed via firmware update alone
- According to the CVE description, the vulnerability is fixed in newer hardware, not by firmware 2.1.1
- Contact Siklu to obtain newer hardware that addresses this hardcoded credential vulnerability
- If immediate mitigation is needed, ensure the affected devices are not exposed to untrusted networks since the hardcoded credentials are publicly known
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation12.0 h
- Implementation24.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 $13,824.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47036 — 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-47036 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