dbcve.org
E11 FirmwareOperating system · Akuvox

CVE-2023-0348

HIGH · 7.5 CVSS v3.1 Published 2023-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Akuvox E11 allows direct SIP calls. No access control is enforced by the SIP servers, which could allow an attacker to contact any device within Akuvox to call any other device.

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 confidence

The Akuvox E11 SIP door phone/intercom devices have a missing access control vulnerability in their SIP servers. The SIP implementation does not enforce any authentication or authorization, allowing any device within the Akuvox network to initiate direct SIP calls to any other device without restriction. An attacker could exploit this to make unauthorized calls between devices.

MitigationImplement access control lists (ACLs) and authentication mechanisms on SIP servers to restrict which devices can call which others. Consider network segmentation to limit SIP traffic to trusted segments only.

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
E11 FirmwareOperating system
Affected:all versions

CVSS 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Check the device label, web interface, or administrative console to confirm the exact model is Akuvox E11
    Affected if The device is an Akuvox E11 door phone/intercom and is running any firmware version
  2. Verify SIP service is enabled
    Access the device web interface or administrative panel and look for SIP/VoIP settings. Check if SIP functionality is turned on in the configuration
    Affected if SIP service is enabled on the device (if SIP is disabled, the vulnerability cannot be exploited)
  3. Inspect SIP server authentication configuration
    In the SIP settings menu, look for authentication, authorization, or access control settings. Check if there are any username/password requirements or ACL entries defined for SIP registration or call initiation
    Affected if No authentication is required for SIP calls, or no access control lists are defined restricting which devices can call which
  4. Check SIP port exposure
    Examine network configuration to determine if SIP ports (typically 5060 UDP/TCP) are accessible from untrusted network segments or the internet. Use netstat or port scanning to verify what IP addresses can reach the SIP service
    Affected if The SIP service is reachable from network segments that contain untrusted or unknown devices
  5. Test SIP call initiation from another device
    From a different device on the same network, attempt to initiate a direct SIP call to the Akuvox E11 using a SIP client (such as SIPp, Linphone, or a script) without providing any credentials
    Affected if The call completes without authentication challenge or rejection, confirming the lack of access control

If the device is an Akuvox E11 with SIP enabled and you can make or receive SIP calls without any authentication or access restrictions, your environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement access control lists (ACLs) and authentication mechanisms on SIP servers to restrict which devices can call which others. Consider network segmentation to limit SIP traffic to trusted segments only.

Fix this in E11 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0348 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-0348 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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