CVE-2024-51348
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA stack-based buffer overflow vulnerability in the P2P API service in BS Producten Petcam with firmware 33.1.0.0818 allows unauthenticated attackers within network range to overwrite the instruction pointer and achieve Remote Code Execution (RCE) by sending a specially crafted HTTP request.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA stack-based buffer overflow in the P2P API service of BS Producten Petcam firmware 33.1.0.0818 allows unauthenticated attackers within network range to overwrite the instruction pointer and achieve remote code execution via a specially crafted HTTP request.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify BS Producten Petcam device on the networkUse network scanning tools (nmap, Angry IP Scanner) or check device documentation/manufacturer labeling to confirm the device model is BS Producten PetcamAffected if The device is a BS Producten Petcam camera
-
Check firmware versionAccess the device administration interface (web UI, mobile app, or via SNMP/SSH if available) and navigate to System Settings, About, or Firmware Information to view the installed firmware versionAffected if Firmware version is 33.1.0.0818 or earlier (no fixed version provided, so treat the installed version as affected if it matches or precedes 33.1.0.0818)
-
Confirm P2P API service is enabledAccess the device settings and check for P2P, Cloud, or Remote Access configuration options. Look for settings named 'P2P Cloud', 'P2P Service', or 'Enable P2P' and verify whether they are turned onAffected if The P2P API service is enabled or configured to allow remote/network access
-
Verify P2P API is network-accessibleUse a port scanner (such as nmap) to probe common P2P service ports (typically 32100, 34599, or vendor-specific ports) from an external or untrusted network segment to confirm the service is reachableAffected if The P2P API service port responds to connections from untrusted network segments
The environment is affected if a BS Producten Petcam device is running firmware version 33.1.0.0818 or earlier AND the P2P API service is enabled and accessible to the attacker.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor firmware update when available; until then, restrict network access to the P2P API service using network segmentation or firewall rules to limit exposure to trusted networks only.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51348 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-51348 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data