CVE-2024-8956
PTZOptics PT30X-SDI/NDI-xx before firmware 6.3.40 is vulnerable to an insufficient authentication issue. The camera does not properly enforce authentication to /cgi-bin/param.cgi when requests are sent without an HTTP Authorization header. The result is a remote and unauthenticated attacker can leak sensitive data such as usernames, password hashes, and configurations details. Additionally, the attacker can update individual configuration values or overwrite the whole file.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. A function is missing its authentication check. The attack requests look like normal traffic, so a WAF has nothing to match on.
Also consider: patch · add auth middleware
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-8956 being exploited?
Yes. CVE-2024-8956 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-8956?
CVE-2024-8956 is rated Critical with a CVSS score of 9.1. 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-8956?
Yes. A fix has been recorded for CVE-2024-8956. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-8956 affect?
CVE-2024-8956 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
- yes
- technical impact
- total
Assessed by CISA 8 Oct 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 Oct 2025CISA SSVC assessment: exploitation active · 318 days (about 11 months) later
- 22 Nov 2025CVE record last updated · 45 days later
- 2 Nov 2026Analysed by vulneraibility.com · 345 days (about 12 months) later
- Advisoryptzoptics.com /firmware-changelog/
- Advisoryvulncheck.com /advisories/ptzoptics-insufficient-auth
- Advisorygreynoise.io /blog/greynoise-intelligence-discovers-zero-day-vulnerabilities-in-live-streamin
- Exploitlabs.greynoise.io /grimoire/2024-10-31-sift-0-day-rce/
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-8956
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.