dbcve.org
M3024 Lve FirmwareOperating system · Axis

CVE-2023-5677

HIGH · 8.8 CVSS v3.1 Published 2024-02-05
Fix available
A fix is available. Upgrade to 5.51.7.7 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Brandon Rothel from QED Secure Solutions and Sam Hanson of Dragos have found that the VAPIX API tcptest.cgi did not have a sufficient input validation allowing for a possible remote code execution. This flaw can only be exploited after authenticating with an operator- or administrator-privileged service account. The impact of exploiting this vulnerability is lower with operator-privileges compared to administrator-privileges service accounts. Please refer to the Axis security advisory for more information and solution.

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

A remote code execution vulnerability exists in the VAPIX API tcptest.cgi endpoint on Axis devices due to insufficient input validation. An attacker with valid operator- or administrator-level credentials can exploit this flaw to execute arbitrary code, with higher impact when using administrator privileges.

MitigationApply the vendor patch from the Axis security advisory immediately, and restrict VAPIX API access to only trusted, privileged accounts to reduce attack surface.

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
M3024 Lve FirmwareOperating system
Affected:< 5.51.7.7
M3025 Ve FirmwareOperating system
Affected:< 5.51.7.7
M7014 FirmwareOperating system
Affected:< 5.51.7.7
M7016 FirmwareOperating system
Affected:< 5.51.7.7
P1214 E FirmwareOperating system
Affected:< 5.51.7.7
P7214 FirmwareOperating system
Affected:< 5.51.7.7
P7216 FirmwareOperating system
Affected:< 5.51.7.7
Q7401 FirmwareOperating system
Affected:< 5.51.7.7

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
High
Availability
High

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

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

  1. Identify the Axis device model
    Access the device web interface or query the VAPIX API at /axis-cgi/basicdeviceinfo.cgi to retrieve the model name and serial number.
    Affected if The device model is one of: M3024-LVE, M3025-VE, M7014, M7016, P1214-E, P7214, P7216, or Q7401.
  2. Check the installed firmware version
    Query /axis-cgi/basicdeviceinfo.cgi or check the System > About page in the web interface to retrieve the firmware version.
    Affected if The firmware version is lower than 5.51.7.7.
  3. Confirm VAPIX API is accessible
    Attempt to access the VAPIX API base URL (e.g., http://<device-ip>/axis-cgi/) using valid credentials. A successful response indicates the API is enabled.
    Affected if The VAPIX API responds to authenticated requests.
  4. Verify operator or administrator accounts exist
    Query the VAPIX user/rights API endpoint or check Users in the device administration interface.
    Affected if Any operator-level or administrator-level user accounts are configured on the device.
  5. Check if tcptest.cgi endpoint is reachable
    Send an authenticated GET request to /axis-cgi/networktest.cgi?tcptest or similar tcptest endpoint. The exact path can be confirmed in Axis documentation.
    Affected if The tcptest.cgi endpoint responds to authenticated requests, indicating the vulnerable feature is accessible.

The device is affected if it is one of the listed models, runs firmware below 5.51.7.7, has the VAPIX API accessible, and has operator or administrator accounts configured.

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.

dbcve · scoped
Upgrade available Upgrade to 5.51.7.7 or later
Fixed in 5.51.7.7
Interim mitigation

Apply the vendor patch from the Axis security advisory immediately, and restrict VAPIX API access to only trusted, privileged accounts to reduce attack surface.

Recommended fix High confidence

Firmware version 5.51.7.7 or later for M3024, M3025, M7014, M7016, P1214, P7214, P7216, Q7401

  1. 1. Obtain the fixed firmware version (5.51.7.7 or later) from the official Axis download portal at www.axis.com/support
  2. 2. Log in to the affected Axis device web interface with administrator credentials
  3. 3. Navigate to Settings > System > Upgrade
  4. 4. Click 'Choose File' and select the downloaded firmware file
  5. 5. Click 'Upgrade' to apply the firmware update
  6. 6. Wait for the device to reboot and verify the firmware version shows 5.51.7.7 or later
Caveat Review Axis release notes for any configuration or feature changes between your current version and 5.51.7.7; backup device configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in M3024 Lve Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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