CVE-2023-22389
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 · uneditedSnap One Wattbox WB-300-IP-3 versions WB10.9a17 and prior store passwords in a plaintext file when the device configuration is exported via Save/Restore–>Backup Settings, which could be read by any user accessing the file.
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 confidenceThe Wattbox WB-300-IP-3 firmware (versions WB10.9a17 and prior) exports device configuration including user credentials stored in plaintext. When using the Save/Restore→Backup Settings feature, the resulting backup file contains unprotected passwords that can be extracted by anyone with file access.
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<= wb10.9a17CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 Wattbox WB-300-IP-3 device firmware versionAccess the device web interface or check the device status page for the firmware version string (such as 'WB10.9a17' or similar). This is typically found under System Info, Status, or About sections in the device management interface.Affected if The displayed firmware version is 'WB10.9a17' or any version prior to it (for example, WB10.9a16, WB10.9a15, etc.)
-
Locate any backup files created from the deviceSearch local systems, network shares, or the device itself for files that may have been created using the Save/Restore Backup Settings feature. These may have extensions like .xml, .cfg, .dat, or no extension, and may contain 'backup', 'config', 'wattbox', or similar terms in the filename.Affected if Any backup files from the Wattbox device exist on any connected systems or storage locations
-
Inspect backup file contents for plaintext passwordsOpen the backup file using a text editor or parser and search for user credential fields. Look for patterns such as password=, user=, or recognizable plaintext passwords in sections related to user accounts, admin settings, or authentication.Affected if The backup file contains any plaintext password strings, username/password pairs, or credential fields without encryption or obfuscation
You are affected if you have a Wattbox WB-300-IP-3 device running firmware version WB10.9a17 or earlier AND you have used the Backup Settings feature, resulting in backup files that contain plaintext credentials.
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 dataUsers should avoid exporting configurations containing credentials until a firmware patch is available, and should protect any existing backup files from unauthorized access. The vendor should implement encryption for sensitive data stored in backup configurations.
- 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-2023-22389 — 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-2023-22389 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