CVE-2023-0354
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 Akuvox E11 web server can be accessed without any user authentication, and this could allow an attacker to access sensitive information, as well as create and download packet captures with known default URLs.
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 Akuvox E11 web server contains an authentication bypass vulnerability where the entire web interface can be accessed without any credentials. This allows unauthenticated attackers to view sensitive system information and abuse built-in packet capture functionality using known default URL paths to create and download network captures.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Confirm device is Akuvox E11Identify the device by checking the product label, DHCP vendor fingerprint, or by accessing the web interface and examining the page header or login page for 'Akuvox' branding. The E11 is a VoIP door phone/intercom device.Affected if The device is an Akuvox E11 unit (all firmware versions are affected)
-
Verify web interface is network-accessibleAttempt to reach the device's web interface via HTTP/HTTPS from a network-connected host. Check if the device responds on common web ports (80, 443, 8080).Affected if The web interface is reachable on the network
-
Test authentication bypass on web pathsAccess common administrative paths WITHOUT providing any credentials: '/', '/cgi-bin/luci', '/cgi-bin/admin', or '/cgi-bin/webmain'. Observe if the interface loads or returns sensitive system information without a login prompt.Affected if The web interface loads or displays system information without requiring any authentication credentials
-
Check for unauthenticated packet capture accessAttempt to access known default URL paths for packet capture functionality (such as '/cgi-bin/pcap.cgi' or similar capture-related endpoints) without any authentication. Verify if network capture files can be created or downloaded.Affected if Packet capture functionality or network capture files are accessible without authentication
If the device is an Akuvox E11 and its web interface or sensitive functions like packet capture are accessible without any credentials, the environment is affected by CVE-2023-0354.
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 restrict network access to the E11 device using firewall rules or network segmentation, and contact Akuvox for a firmware patch that implements proper authentication. If no patch is available, consider replacing the device.
- 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-0354 — 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-0354 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