dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 25 Nov 2024.
Pt30x Sdi FirmwareOperating system · Ptzoptics

CVE-2024-8957

HIGH · 7.2 CVSS v3.1 Published 2024-09-17
Fix available
A fix is available. Upgrade to 6.3.40 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit 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
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.

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

PTZOptics PT30X-SDI/NDI-xx cameras before firmware 6.3.40 contain an OS command injection vulnerability in the ntp_addr configuration parameter. The camera fails to properly validate this value, allowing an attacker to inject arbitrary OS commands that execute when the ntp_client service starts. When chained with CVE-2024-8956 (authentication bypass), a remote unauthenticated attacker can achieve arbitrary command execution.

MitigationUpgrade PTZOptics camera firmware to version 6.3.40 or later. If immediate patching is not possible, isolate affected devices on a restricted network segment and disable the NTP client service if not required.

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
Pt30x Sdi FirmwareOperating system
Affected:< 6.3.40
Pt30x Ndi Xx G2 FirmwareOperating system
Affected:< 6.3.40

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

CVSS:3.1/AV:N/AC:L/PR:H/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 camera model and firmware version
    Access the camera's web interface or use the manufacturer's API to retrieve the device information, specifically noting the model (PT30X-SDI or PT30X-NDI-xx G2) and current firmware version
    Affected if Firmware version is below 6.3.40 for either model
  2. Verify NTP client configuration
    Check if the NTP client feature is enabled on the camera. This is typically found in the camera settings under Network or Time configuration
    Affected if NTP client is enabled and the camera is on vulnerable firmware
  3. Inspect NTP server address setting
    Locate the ntp_addr configuration parameter in the camera's configuration settings or by querying the device configuration
    Affected if The ntp_addr value contains unexpected characters such as semicolons, pipes, backticks, or other shell metacharacters indicating injection
  4. Check NTP client service status
    If you have shell access to the device, verify whether the ntp_client service is running or configured to start
    Affected if The ntp_client service executes with elevated privileges and the ntp_addr contains injected commands

The camera is affected if it is a PT30X-SDI or PT30X-NDI-xx G2 model running firmware prior to 6.3.40 with the NTP client feature enabled and the ntp_addr parameter contains suspicious characters or unexpected values.

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 6.3.40 or later
Fixed in 6.3.40
Interim mitigation

Upgrade PTZOptics camera firmware to version 6.3.40 or later. If immediate patching is not possible, isolate affected devices on a restricted network segment and disable the NTP client service if not required.

Recommended fix High confidence

PTZOptics PT30X-SDI/NDI-xx G2 firmware 6.3.40 or later

  1. Identify the specific model (Pt30x-SDI or Pt30x-NDI-xx G2) of the affected PTZOptics camera
  2. Navigate to the official PTZOptics support page at ptzoptics.com/support or the firmware download section
  3. Locate and download firmware version 6.3.40 or the latest available version for your specific model
  4. Access the camera's web interface using administrative credentials
  5. Navigate to the firmware upgrade or system settings section
  6. Upload and apply the downloaded firmware file
  7. Allow the camera to complete the firmware update process (do not power off during upgrade)
  8. After reboot, verify the firmware version has been updated to 6.3.40 or later

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

Fix this in Pt30x Sdi Firmware Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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