Certain Anpviz products contain a hardcoded cryptographic key stored in the firmware of…
Priority HIGH 76CWE-321Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-321.
Summary
Certain Anpviz products contain a hardcoded cryptographic key stored in the firmware of the device. This affects IPC-D250, IPC-D260, IPC-B850, IPC-D850, IPC-D350, IPC-D3150, IPC-D4250, IPC-D380, IPC-D880, IPC-D280, IPC-D3180, MC800N, YM500L, YM800N_N2, YMF50B, YM800SV2, YM500L8, and YM200E10 firmware v3.2.2.2 and lower and possibly more vendors/models of IP camera.
Why it matters now
Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00372 31st percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
CPE names CISA-ADP · 18
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:o:anpviz:ipc-b850_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:ipc-d250_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:ipc-d260_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:ipc-d280_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:ipc-d3150_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:ipc-d3180_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:ipc-d350_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:ipc-d380_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:ipc-d4250_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:ipc-d850_firmware:*:*:*:*:*:*:*:* | — | — | — |
- cpe:2.3:o:anpviz:ipc-b850_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:ipc-d250_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:ipc-d260_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:ipc-d280_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:ipc-d3150_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:ipc-d3180_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:ipc-d350_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:ipc-d380_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:ipc-d4250_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:ipc-d850_firmware:*:*:*:*:*:*:*:* Versions — — ·—
Show 8 more CPE
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:o:anpviz:ipc-d880_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:mc800n_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:ym200e10_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:ym500l8_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:ym500l_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:ym800n_n2_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:ym800sv2_firmware:*:*:*:*:*:*:*:* | — | — | — |
| cpe:2.3:o:anpviz:ymf50b_firmware:*:*:*:*:*:*:*:* | — | — | — |
- cpe:2.3:o:anpviz:ipc-d880_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:mc800n_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:ym200e10_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:ym500l8_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:ym500l_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:ym800n_n2_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:ym800sv2_firmware:*:*:*:*:*:*:*:* Versions — — ·—
- cpe:2.3:o:anpviz:ymf50b_firmware:*:*:*:*:*:*:*:* Versions — — ·—
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2024-35344
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences