Loading vulnerability…
CVE-2024-51348 is a stack-based buffer overflow in the P2P API service of the BS Producten Petcam running firmware version 33.1.0.0818. An unauthenticated attacker within network range can trigger the flaw by sending a specially crafted HTTP request to the affected service. Successful exploitation allows overwriting the instruction pointer, which can be leveraged to achieve remote code execution on the device.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a small, focused exploit PoC for CVE-2024-51348 affecting BS Petcam firmware. It contains two files: a README with vulnerability research and exploitation notes, and a single Python script implementing the proof of concept. The exploit is not part of a larger framework. The README documents an unauthenticated remote code execution path in the device's custom P2P API service on TCP port 8001. According to the analysis, the service parses the URI path, prepends './html/', and copies the result into a 260-byte stack buffer without proper bounds checking. An oversized resource string in an HTTP GET request causes a stack-based buffer overflow. The write-up also describes environmental context: the device exposes an unauthenticated local-mode Wi-Fi network, and open ports include 80, 554, and 8001. It further notes a practical exploitation constraint: bytes equal to '?' (0x3f) break payload delivery because the parser splits on '?', making ret2libc difficult when library addresses begin with 0x3f. As a workaround, the exploit uses a gadget in the main binary instead of libc. The Python file exploitPoC.py is the operational entry point. It accepts a target IP, target port (default 8001), Telnet port (default 23), and Telnet credentials. The trigger_exploit() function builds a malicious HTTP GET request with 253 'A' bytes, marker padding, and a hardcoded 3-byte return address intended to redirect execution to a gadget that starts telnetd. After sending the request over a raw TCP socket, the script pauses briefly, then verify_access() attempts to connect via Telnet, authenticate, and run 'whoami' to confirm successful code execution. Overall, the repository's purpose is to demonstrate practical exploitation of the BS Petcam buffer overflow and verify post-exploitation access. It is more than a crash PoC because it includes a hardcoded control-flow hijack and a post-exploitation verification step, but it remains a basic, target-specific PoC rather than a generalized exploit framework.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.