CVE-2023-0346
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 · uneditedAkuvox E11 cloud login is performed through an unencrypted HTTP connection. An attacker could gain access to the Akuvox cloud and device if the MAC address of a device if known.
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 device performs cloud login authentication over an unencrypted HTTP connection. An attacker with knowledge of a device's MAC address can intercept credentials or session tokens transmitted in cleartext, potentially gaining unauthorized access to both the Akuvox cloud platform and the physical 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 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm Akuvox E11 device presenceIdentify Akuvox E11 devices on your network by checking device labels, DHCP lease tables, or network discovery scans for MAC address prefixes associated with Akuvox (vendor OUI lookup).Affected if The organization has any Akuvox E11 physical door intercom devices deployed on the network.
-
Identify cloud login traffic destinationCapture network traffic or inspect proxy/logging configurations on the network segment where the E11 device communicates. Determine if the device contacts cloud servers over HTTP (port 80) or HTTPS (port 443).Affected if The device is configured to communicate with Akuvox cloud services over plain HTTP rather than encrypted HTTPS.
-
Inspect credential transmission in transitUse a network packet capture (tcpdump, Wireshark) on the segment monitoring the E11 device's outbound traffic during a cloud login authentication event. Look for POST requests containing username/password parameters or session tokens in cleartext.Affected if Login credentials or session tokens are transmitted in cleartext within HTTP traffic rather than being encrypted within HTTPS.
-
Verify MAC address exposureReview captured traffic or device configuration to confirm the device MAC address is discoverable on the network (through ARP tables, DHCP logs, or device management interfaces).Affected if The device MAC address is exposed on the network, enabling an attacker to target this specific device for man-in-the-middle interception.
The environment is affected if Akuvox E11 devices perform cloud authentication over unencrypted HTTP, exposing credentials and session tokens in cleartext to anyone able to capture network traffic targeting that device's MAC address.
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 dataEnforce TLS/HTTPS encryption for all cloud login communications. If HTTPS is not supported natively, consider network segmentation or VPN tunneling to protect credentials in transit.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0346 — 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-0346 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