Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessScan internet for open TCP 34567
-
DeliverySend crafted JSON to DebugShell
-
ExploitCommand injection bypasses sanitization
-
ExecutionExecute OS commands as root
-
ImpactFull device compromise and network pivot
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Hidden functionality detection
|
| Exploitation Conditions | Exploitation requires only network reachability to the DebugShell service on TCP port 34567, which is exposed by default on affected firmware; the CVSS vector (AV:N/AC:L/AT:N/PR:N/UI:N) confirms no authentication, no user interaction, and low complexity. The concrete prerequisite is that port 34567 (the binary-protocol DebugShell interface) is reachable from the attacker - directly internet-exposed cameras or attackers already on the same LAN/VLAN qualify. The primary limiting factor is network segmentation: if the port is firewalled, NAT-isolated without port-forwarding, or confined to a management VLAN, remote exploitation is blocked. The affected population is limited to Puwell IP Camera firmware 2.x through 4.x (and OEM rebrands sharing that firmware). |
| Impact | All independent signals point to genuine high priority. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N with VC:H/VI:H/VA:H) describes network-reachable, low-complexity, unauthenticated exploitation with total confidentiality, integrity, and availability impact - consistent with the description. Publicly available exploit code exists (VulnCheck advisory plus a third-party writeup), lowering the barrier to opportunistic and automated attacks against internet-exposed cameras, which are routinely mass-scanned. No EPSS score was provided in the input, so probabilistic exploitation likelihood cannot be quantified here, and the CVE is not listed in CISA KEV, so there is no confirmation of active exploitation - the risk is driven by ease of exploitation and POC availability rather than confirmed campaigns. SSVC/KEV automatable and exploitation-status fields were not supplied; however, the trivial, unauthenticated, network vector strongly implies the attack is automatable. Overall this is a real, actionable priority for any exposed device, not a high-CVSS-but-low-real-risk case. |
| Exploit ScenarioDerived | An attacker scans the internet for devices with TCP port 34567 open, identifies a Puwell-based camera, and sends a single crafted JSON request to the DebugShell service embedding shell metacharacters and OS commands. With no authentication or input filtering, the commands execute as root, giving the attacker a foothold to exfiltrate video, pivot into the internal network, or enroll the device into a botnet - and a public POC makes this repeatable at scale. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 04, 2026
Unauthenticated remote code execution in Puwell IP Camera firmware versions 2.x through 4.x lets remote attackers achieve root-level control by sending a crafted JSON payload to an undocumented DebugShell service listening on TCP port 34567. Because the service performs neither authentication nor input sanitization, any attacker with network reach to the port can pass operating-system commands directly to the device, resulting in full compromise. Reported by VulnCheck with publicly available exploit code exists; no public evidence of active in-the-wild exploitation (not in CISA KEV).
RemediationAI
No vendor-released patched firmware version is identified in the available data (no fix version supplied), so treat this as unpatched pending confirmation from Puwell - monitor https://www.puwell.com/Index/catalog and the VulnCheck advisory (https://www.vulncheck.com/advisories/puwell-ip-camera-2-x-4-x-unauthenticated-command-injection-via-debugshell) for firmware updates and apply the fixed release once published. As immediate compensating controls, block or firewall inbound TCP port 34567 at the network perimeter and place cameras on an isolated VLAN with no direct internet exposure, permitting management only from a trusted jump host or VPN (trade-off: remote mobile/cloud app access to the camera may break if it relies on that port). Disable UPnP/port-forwarding on the gateway to prevent the DebugShell port from being auto-exposed, and if the device offers any option to disable the debug/maintenance service, disable it. Where feasible, retire or replace end-of-support cameras that cannot be updated, since the hidden DebugShell functionality cannot be removed by configuration alone.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is a proprietary binary-protocol network service ("DebugShell") bundled in Puwell IP camera firmware and reachable on TCP/34567 - a port historically associated with Dahua/XMeye-derived DVR and IP-camera stacks used across many OEM/white-label camera products. The root cause maps to CWE-912 (Hidden Functionality), meaning an undocumented debug interface ships enabled in production firmware; combined with a lack of input sanitization, attacker-supplied fields in a JSON request are concatenated into a shell/command context (command injection) and executed by the underlying embedded Linux OS. Cameras typically run their main services as root, so successful injection yields root without privilege escalation. CPE cpe:2.3:a:puwell_technology_inc.:ip_camera:*:*:*:*:*:*:*:* identifies the affected application across all listed versions.
Know when Ip Camera gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Unauthenticated, low-complexity network exploitation of an exposed debug port yields root, so PR:N/UI:N/AC:L with full C/I/A impact; scope unchanged as compromise stays on the device.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Puwell IP Camera firmware versions 2.x through 4.x contains an unauthenticated command injection vulnerability that allows remote attackers to execute arbitrary operating system commands by sending a crafted JSON payload to the DebugShell interface exposed on TCP port 34567. Attackers can exploit the lack of authentication and input sanitization in the binary protocol service to pass arbitrary commands directly to the underlying operating system, achieving root-level code execution and complete device compromise.
Executive ViewAI
Puwell IP Camera firmware versions 2.x through 4.x are vulnerable to unauthenticated remote code execution (CVE-2026-61515, CVSS 9.3), allowing attackers to gain complete root-level control of affected devices. Organizations deploying these cameras in surveillance or network monitoring infrastructure face immediate compromise of physical security systems with no vendor patch currently available. Publicly available exploit code amplifies exploitation risk and reduces time to compromise.
No vendor-released patch identified at time of analysis. Implement network segmentation and access control lists restricting TCP port 34567 connectivity to cameras; deploy network-based intrusion detection signatures to alert on exploitation attempts; contact Puwell vendor support to determine if DebugShell service can be disabled in your firmware version; maintain monitoring of vendor security advisories and CISA for patch release notification.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
EUVD-2026-52689
GHSA-mm4w-x64v-48cj
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB