dbcve.org
FortivoiceApplication · Fortinet

CVE-2023-40720

HIGH · 7.1 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to after 6.4.8 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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
An authorization bypass through user-controlled key vulnerability [CWE-639] in FortiVoiceEntreprise version 7.0.0 through 7.0.1 and before 6.4.8 allows an authenticated attacker to read the SIP configuration of other users via crafted HTTP or HTTPS requests.

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 confidence

FortiVoice Enterprise versions 7.0.0-7.0.1 and before 6.4.8 contains an authorization bypass vulnerability (CWE-639) where an authenticated attacker can read SIP configuration of other users by manipulating user-controlled keys in crafted HTTP or HTTPS requests.

MitigationUpdate FortiVoice Enterprise to version 7.0.2, 6.4.8, or later. Implement proper authorization checks to ensure users can only access their own SIP configuration data.

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
FortivoiceApplication
Affected:>= 6.0.0, <= 6.0.12>= 6.4.0, <= 6.4.8= 7.0.0= 7.0.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L

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 FortiVoice Enterprise version
    Log into the FortiVoice admin console or use CLI command 'get system status' to retrieve the firmware version
    Affected if The installed version matches 6.0.0-6.0.12, 6.4.0-6.4.8, 7.0.0, or 7.0.1
  2. Verify web interface is accessible
    Confirm that the FortiVoice management web interface (HTTP/HTTPS) is reachable on the network
    Affected if Web interface is exposed, which is required for the HTTP/HTTPS-based exploitation path
  3. Review admin logs for unauthorized SIP configuration access
    Examine FortiVoice admin or audit logs for SIP configuration API requests where the target user ID differs from the authenticated user
    Affected if Logs show SIP configuration reads for user accounts other than the one authenticated

Environment is affected if FortiVoice Enterprise version is 6.0.0 through 6.0.12, 6.4.0 through 6.4.8, 7.0.0, or 7.0.1 and the web management interface is accessible.

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
Upgrade available Upgrade to a release after 6.4.8
Interim mitigation

Update FortiVoice Enterprise to version 7.0.2, 6.4.8, or later. Implement proper authorization checks to ensure users can only access their own SIP configuration data.

Fix this in Fortivoice Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-40720 — 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-40720 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