CVE-2022-23765
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 · uneditedThis vulnerability occured by sending a malicious POST request to a specific page while logged in random user from some family of IPTIME NAS. Remote attackers can steal root privileges by changing the password of the root through a POST request.
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 confidenceIPTIME NAS devices contain an improper authorization vulnerability where any authenticated user can escalate privileges to root by sending a malicious POST request to a specific page to change the root password. This allows remote attackers with low-privilege access to gain full administrative control of the device.
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.4.86< 1.4.86< 1.4.86CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 the NAS modelAccess the NAS web interface or check the device label to confirm the model is one of: Nas1dual, Nas2dual, or Nas4dualAffected if Device is an IPTIME NAS model listed in the affected products
-
Check firmware versionLog into the NAS administration panel and navigate to System Settings or About page to view the installed firmware versionAffected if Firmware version is below 1.4.86 (for example, 1.4.85 or earlier)
-
Verify network exposure of management interfaceCheck router/firewall configuration to determine if the NAS web management interface (typically ports 80/443) is accessible from external/untrusted networksAffected if Management interface is exposed to the internet or untrusted networks without IP restrictions
-
Review logs for password change attemptsExamine NAS system logs for entries indicating root password modifications or privilege escalation events, particularly from low-privilege user accountsAffected if Logs show password changes initiated by non-administrator accounts or unauthorized root password modifications
The environment is affected if the device is an IPTIME Nas1dual, Nas2dual, or Nas4dual running firmware version below 1.4.86 and the management interface is accessible to untrusted users.
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 · scoped1.4.86
Apply vendor patches when available. Until then, restrict network access to the NAS management interface to trusted IPs only, and monitor for unauthorized password change attempts in logs.
Firmware 1.4.86
- Identify the exact NAS model (Nas1dual, Nas2dual, or Nas4dual) from the IPTIME NAS product line
- Access the NAS administrative web interface
- Navigate to the firmware update or system settings section
- Upgrade the firmware to version 1.4.86 or later
- After upgrading, verify the root password has not been changed unexpectedly and confirm proper system functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23765 — 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-23765 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