CriticalCVE-2024-8957

    PTZOptics NDI and SDI Cameras Command Injection via NTP Address Configuration (CVE-2024-8957)

    Published In CISA KEV since Sources: CVE.org, pwn.watch

    Share

    What is affected, what to do

    PTZOptics PT30X-SDI/NDI-xx before firmware 6.3.40 is vulnerable to an OS command injection issue. The camera does not sufficiently validate the ntp_addr configuration value which may lead to arbitrary command execution when ntp_client is started.

    The vulnerability is being actively exploited; treat it as a priority. Update PTZOptics PT30X-SDI to version 6.3.40, PTZOptics PT30X-NDI to version 6.3.40. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • PTZOptics PT30X-SDI lt *..6.3.40
    • PTZOptics PT30X-NDI lt *..6.3.40
    Fixed in
    • PTZOptics PT30X-SDI 6.3.40
    • PTZOptics PT30X-NDI 6.3.40

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.2

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.2

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org, pwn.watch

    79.8 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.61

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    221.59 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.2 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.2
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    79.8 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.61
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 8 September 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-78

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This CVE is on KEV because, when chained with CVE-2024-8956, it provides unauthenticated remote code execution as root on devices typically deployed in boardrooms, lecture halls, studios, stadiums and control centres — meaning both audio/video access to sensitive meetings and a lateral pivot point into internal networks. Exploitation likelihood is among the highest tracked by EPSS, and mass scanning for /cgi-bin/param.cgi has been publicly observed since late 2024; CISA has not confirmed ransomware use, but botnet recruitment (Mirai variants) is the norm for IoT RCEs of this shape. Treat the patch ticket as P1 for any organisation with internet-exposed PTZOptics cameras — especially KRITIS control rooms, universities and media houses; purely internal, well-segmented deployments can run as P2 with a short SLA (7 days).

    1. Runbook step 1

      Immediate response (0-24 h)

      • Upgrade PTZOptics PT30X-SDI/NDI firmware to 6.3.40 or later — this release fixes both CVE-2024-8957 and the authentication bypass CVE-2024-8956 that chains it into an unauthenticated RCE.
      • Remove PTZOptics cameras from the public internet: block inbound TCP/80 and TCP/443 to camera management interfaces at the perimeter firewall today. Use Shodan/Censys queries for "PTZOptics" and "/cgi-bin/param.cgi" to find exposed assets you may not own in your CMDB.
      • Segment the camera management VLAN from the general corporate network; only dedicated AV control hosts should reach TCP/80, TCP/443, RTSP (TCP/554), NDI (UDP/5353 plus dynamic ports) and VISCA (TCP/5678).
      • Rotate default and weak admin credentials (admin/admin) on every PTZOptics device — the authenticated variant of the flaw remains exploitable even on partially patched estates if default creds persist.
      • Compromise check: inspect the admin UI's NTP configuration (ntp_addr field) for shell metacharacters (;, |, `, $()), and verify firmware integrity plus running processes for unexpected binaries or reverse shells.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: place cameras in an isolated AV/IoT VLAN without a default route to the internet; restrict egress at the firewall to the NTP server (UDP/123) and central syslog only. This neutralises the egress stage of a command injection payload (second-stage download, reverse shell).
      • WAF or reverse proxy in front of the camera: drop requests to /cgi-bin/param.cgi where any parameter value (ntp_addr, and ideally all configuration parameters) contains shell metacharacters ; | & $ \ ( ) < > \n. This is an effective virtual patch.
      • Deploy an IPS/Suricata signature matching POST requests to /cgi-bin/param.cgi with shell metacharacters in the body; enable existing community rules tagged for CVE-2024-8956/8957.
      • IAM hardening: expose the admin interface only via a jump host with MFA; replace shared accounts with per-user credentials stored in a PAM/vault solution.
      • Configuration hardening: disable the camera's NTP client where time sync is not business-critical — the vulnerable ntp_client code path then never triggers.
      • Egress monitoring: treat unexpected DNS queries, connections to TCP/4444, TCP/1337, or paste/raw-hosting services from the camera VLAN as high-severity alerts.

    3. Runbook step 3

      Detection rules

      • Zeek/Suricata HTTP logs: http.uri contains "/cgi-bin/param.cgi" with http.request_body containing ;, |, $(, `, wget, curl, /bin/sh, or nc . Sigma shape: selection: cs-uri-stem|contains: '/cgi-bin/param.cgi' AND cs-method: 'POST' AND cs-uri-query|re: '(ntp_addr=.*[;|$])'`.
      • Reverse-proxy/access logs if available: KQL — WebLogs | where UrlPath has "param.cgi" and (QueryString has_any (";","|","","$(") or PostBody has_any (";","|","","$(")).
      • Firewall/NetFlow telemetry: outbound connections from the camera VLAN to anything other than UDP/123 NTP, DNS, and syslog — especially SYN traffic to TCP/4444, TCP/1337, or TCP/80/443 against unfamiliar ASNs.
      • DNS monitoring: lookups from the camera VLAN for dynamic DNS providers, Pastebin, raw.githubusercontent.com, transfer.sh — typical second-stage hosting.
      • Baseline deviation: cameras suddenly initiating SSH/Telnet outbound or showing new periodic beacons should be flagged as likely compromise. Native camera logging is thin, so network telemetry is the primary detection layer.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    PTZOptics PT30X-SDI/NDI-xx before firmware 6.3.40 is vulnerable to an OS command injection issue. The camera does not sufficiently validate the ntp_addr configuration value which may lead to arbitrary command execution when ntp_client is started. When chained with CVE-2024-8956, a remote and unauthenticated attacker can execute arbitrary OS commands on affected devices.

    Source: cvelistv5, pwn.watch, NVD (NIST), CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    PTZOpticsPT30X-NDI
    • < 6.3.40
    • 6.3.40
    PTZOpticsPT30X-SDI
    • < 6.3.40
    • 6.3.40

    Vendors and products

    Affected operating systems

    Affected operating systems
    Otherptzopticspt30x-ndi-xx-g2_firmware—
    Otherptzopticspt30x-sdi_firmware—

    Weakness classes (CWE)

    • CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

      Base

      The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.

      Entry at MITRE CWE-78

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • ptzoptics.comPTZOptics advisory: CVE-2024-8956Vendor advisory, Release notes, pwn-watch
    • vulncheck.comadvisories/ptzoptics-command-injectionThird-party advisory, Third-party advisory
    • labs.greynoise.iogrimoire/2024-10-31-sift-0-day-rceExploit, Technical description, Third-party advisory, Exploit, Third-party advisory
    • greynoise.ioblog/greynoise-intelligence-discovers-zero-day-vulnerabilities-…Third-party advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2024-8957government-resource, US government resource
    • pwn.watchpwn.watch: PTZOptics PT30X-SDI/NDI Cameras: 2 actively exploited vulnerabilitiespwn-watch
    • NVD (NIST)NVD: CVE-2024-8956pwn-watch
    • NVD (NIST)NVD: CVE-2024-8957pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2024-8957
    <a href="https://intel.neosec.eu/en/cve/CVE-2024-8957"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-8957.svg?lang=en" alt="CVE-2024-8957 – NEOSEC Intel" height="20"></a>