dbcve.org
AutokitApplication · Carlinkit

CVE-2025-2764

HIGH · 8.0 CVSS v3.0 Published 2025-04-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
CarlinKit CPC200-CCPA update.cgi Improper Verification of Cryptographic Signature Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of CarlinKit CPC200-CCPA devices. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the handling of update packages provided to update.cgi. The issue results from the lack of proper verification of a cryptographic signature. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-24355.

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

The CarlinKit CPC200-CCPA device has a vulnerability in its update.cgi script where update packages are not properly verified for cryptographic signature before execution. While authentication is required to access the update function, this requirement can be bypassed, allowing a network-adjacent attacker to supply a malicious firmware update that executes with root privileges due to the lack of signature validation.

MitigationApply any vendor-supplied firmware patches when available; otherwise, restrict network access to the device's management interface and monitor for unauthorized update attempts.

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
AutokitApplication
Affected:= 2024.01.19.1541

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

CVSS:3.0/AV:A/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 device model
    Locate the device label or access the device's web management interface to confirm the model is CarlinKit CPC200-CCPA or Carlinkit Autokit
    Affected if The device is a CarlinKit CPC200-CCPA or Carlinkit Autokit unit
  2. Check the installed firmware version
    Access the device's web management interface (typically via HTTP/HTTPS to the device IP) and navigate to the system information or firmware settings page to view the current firmware version
    Affected if The firmware version is 2024.01.19.1541
  3. Verify update.cgi network accessibility
    From a network-adjacent system, attempt to access the update.cgi endpoint (commonly at /cgi-bin/update.cgi or /update.cgi on the device's web interface) using curl or a browser
    Affected if The update.cgi endpoint is reachable from the network without proper authentication controls
  4. Confirm authentication bypass potential
    Test whether the update function can be accessed without valid authentication credentials, or verify if known authentication bypass methods work for this device
    Affected if The update function can be accessed without proper authentication

A user is affected if they have a CarlinKit CPC200-CCPA or Carlinkit Autokit device running firmware version 2024.01.19.1541 with the update.cgi endpoint exposed on the network and accessible without proper authentication.

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

Apply any vendor-supplied firmware patches when available; otherwise, restrict network access to the device's management interface and monitor for unauthorized update attempts.

Fix this in Autokit Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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