CVE-2022-1039
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 · uneditedThe weak password on the web user interface can be exploited via HTTP or HTTPS. Once such access has been obtained, the other passwords can be changed. The weak password on Linux accounts can be accessed via SSH or Telnet, the former of which is by default enabled on trusted interfaces. While the SSH service does not support root login, a user logging in using either of the other Linux accounts may elevate to root access using the su command if they have access to the associated 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 confidenceThis vulnerability involves default/weak passwords on both the web UI (accessible via HTTP/HTTPS) and Linux system accounts (accessible via SSH/Telnet). An attacker who obtains these credentials can change other passwords and, after gaining access to non-root Linux accounts, can escalate to root using the su command if they have the associated password.
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 dataall versionsCVSS 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.
-
Check web UI for default credential accessibilityAccess the device web interface via HTTP or HTTPS and attempt login using common default credentials (such as admin/admin, admin/1234, root/root, or manufacturer-published defaults). Also check if the login page responds differently for valid vs invalid usernames.Affected if Default credentials still work or the device accepts login with factory-default usernames and passwords
-
Verify Telnet service statusCheck if Telnet port (23) is open and responding on the device using 'telnet <device-ip>' or a port scanner. Review device network configuration to confirm Telnet service is enabled.Affected if Telnet is enabled and accessible, as it transmits credentials in plaintext
-
Confirm SSH accessibilityCheck if SSH port (22) is open on the device. Attempt an SSH connection using known or suspected Linux system accounts.Affected if SSH is accessible and accepts connections with default or weak passwords
-
Check for default Linux system accountsIf you have console or SSH access, examine /etc/passwd to list all user accounts. Compare against known default accounts for this device. Attempt to authenticate with default passwords.Affected if Default Linux accounts exist with default or weak passwords that have not been changed
-
Assess su command privilege escalation riskIf you have access to a non-root account, attempt to run 'su -' to switch to root. Check /etc/pam.d/su or group membership (wheel, sudo groups) to see if non-root users can escalate to root.Affected if Non-root users can execute the su command without proper restrictions, allowing password-based privilege escalation
The environment is affected if any default or weak passwords remain active on the web UI or Linux accounts, or if Telnet is enabled, or if non-root users can use su to escalate to root.
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 dataImmediately change all default/weak passwords on the web interface and Linux accounts; disable Telnet and restrict SSH access to trusted sources; implement strong password policies and consider disabling the su command for non-privileged users.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1039 — 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-1039 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