CVE-2023-24020
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 could bypass the brute force protection, allowing multiple attempts to force a login.
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 contains an authentication bypass vulnerability where the brute force protection mechanism can be circumvented. This allows attackers to make unlimited login attempts without triggering account lockout, enabling automated credential stuffing or brute force attacks against the device's admin interface.
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
- 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 model is Wattbox WB-300-IP-3Access the device's web interface or check the device label/physics to verify the exact model number is WB-300-IP-3Affected if The device is not a Wattbox WB-300-IP-3 model
-
Check installed firmware versionLog into the Wattbox admin interface and navigate to the firmware or status page to view the current firmware version, or check via SNMP or the device's API if availableAffected if Firmware version is wb10.9a17 or lower (any version <= wb10.9a17)
-
Verify admin interface network exposureCheck network configuration to determine if the device's web admin interface (typically ports 80/443 or custom HTTP/HTTPS ports) is accessible from untrusted networks such as the public internet or less-trusted VLANsAffected if The admin interface is reachable from networks outside the trusted management network
-
Review authentication logs for brute force patternsExamine device logs, syslog exports, or SIEM/monitoring systems for signs of repeated failed login attempts from the same source IP, or successful logins from unexpected locationsAffected if Logs show high-volume authentication attempts from a single source or patterns indicative of automated credential stuffing without account lockout triggering
A user is affected if they have a Wattbox WB-300-IP-3 running firmware version wb10.9a17 or lower, with its admin interface network-accessible and no compensating controls blocking the attack vector.
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 dataApply the vendor firmware update that addresses CVE-2023-24020. If no patch is available, restrict network access to the management interface using firewall rules or VPN, and monitor for suspicious authentication activity.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24020 — 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-24020 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