CVE-2024-8957
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.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. OS command injection puts shell syntax into the request. WAF rules catch common shell commands but miss encoded or unusual payloads.
Also consider: shlex/execve-style APIs
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-8957 being exploited?
Yes. CVE-2024-8957 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-8957?
CVE-2024-8957 is rated High with a CVSS score of 7.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-8957?
Yes. A fix has been recorded for CVE-2024-8957. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-8957 affect?
CVE-2024-8957 affects ptzoptics:pt30x-sdi_firmware, ptzoptics:pt30x-ndi-xx-g2_firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected< 6.3.40
- affected< 6.3.40
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 8 Sept 2025 (SSVC 2.0.3).
timeline
- 17 Sept 2024Published
- 4 Nov 2024Added to CISA KEV (exploited in the wild) · 47 days later
- 25 Nov 2024CISA remediation due date (US federal agencies) · 21 days later
- 8 Sept 2025CISA SSVC assessment: exploitation active · 288 days (about 10 months) later
- 27 Dec 2025CVE record last updated · 110 days (about 4 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 310 days (about 10 months) later
- Advisoryptzoptics.com /firmware-changelog/
- Advisoryvulncheck.com /advisories/ptzoptics-command-injection
- Exploitlabs.greynoise.io /grimoire/2024-10-31-sift-0-day-rce/
- Linkgreynoise.io /blog/greynoise-intelligence-discovers-zero-day-vulnerabilities-in-live-streamin
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-8957
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.