Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2025-57440

HIGH · 7.5 CVSS v3.1 Published 2025-09-22
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
The Blackmagic ATEM Mini Pro 2.7 exposes an undocumented Telnet service on TCP port 9993, which accepts unauthenticated plaintext commands for controlling streaming, recording, formatting storage devices, and system reboot. This interface, referred to as the "ATEM Ethernet Protocol 1.0", provides complete device control without requiring credentials or encryption. An attacker on the same network (or with remote access to the exposed port) can exploit this interface to execute arbitrary streaming commands, erase disks, or shut down the device - effectively gaining full remote control.

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 Blackmagic ATEM Mini Pro exposes an undocumented Telnet service on TCP port 9993 implementing the 'ATEM Ethernet Protocol 1.0'. This service accepts unauthenticated plaintext commands for streaming control, recording, storage formatting, and system reboot operations without any credentials or encryption, providing complete unauthenticated device control to any network attacker with port access.

MitigationNetwork-level controls (firewall rules, VLAN segmentation, ACLs) should be deployed to restrict access to port 9993 to only trusted management hosts; if the Telnet service cannot be disabled, consider network isolation or replacing the device with a patched alternative.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 ATEM Mini Pro devices on the network
    Scan your network for devices with a manufacturer OUI matching Blackmagic Design (00:1D:50 or similar) or use network discovery tools to locate ATEM Mini Pro hardware by MAC address or hostname patterns.
    Affected if The device is a Blackmagic ATEM Mini Pro on the network.
  2. Check if TCP port 9993 is open
    Run a port scan against the suspected device using 'nmap -p 9993 <target_ip>' or equivalent network scanner to determine if port 9993 is listening.
    Affected if Port 9993 returns as open or filtered on the ATEM device.
  3. Verify the service accepts unauthenticated commands
    Connect to port 9993 using a Telnet client ('telnet <target_ip> 9993') or netcat ('nc <target_ip> 9993') and attempt to send a basic protocol command such as 'CPw:' (connection password query) or any ATEM protocol command without providing credentials.
    Affected if The connection succeeds and returns protocol responses without requiring any authentication or password.
  4. Confirm streaming and recording control is exposed
    After connecting to port 9993, issue ATEM protocol commands such as 'STR;' (stream status query) or 'REC;' (record control) and observe whether the device accepts and processes these commands without credentials.
    Affected if The device accepts and executes streaming, recording, or formatting commands without authentication.

If you have an ATEM Mini Pro with port 9993 open that accepts ATEM protocol commands without requiring any password or authentication, your environment is affected by CVE-2025-57440.

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

Network-level controls (firewall rules, VLAN segmentation, ACLs) should be deployed to restrict access to port 9993 to only trusted management hosts; if the Telnet service cannot be disabled, consider network isolation or replacing the device with a patched alternative.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-57440 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