CVE-2024-35343
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 · uneditedCertain Anpviz products allow unauthenticated users to download arbitrary files from the device's filesystem via a HTTP GET request to the /playback/ URI. 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 (IP Cameras) firmware v3.2.2.2 and lower and possibly more vendors/models of IP camera.
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 · high confidenceThe vulnerability is a path traversal issue in the /playback/ URI of Anpviz IP cameras (multiple models listed) running firmware v3.2.2.2 and lower. An unauthenticated attacker can send a specially crafted HTTP GET request to download arbitrary files from the device's filesystem, potentially exposing sensitive configuration data, credentials, or firmware components.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 the device as an Anpnviz IP cameraCheck the device model via its web interface, SNMP, or network discovery. Look for Anpnviz branding or check the HTTP server banner if available.Affected if The device is an Anpnviz IP camera from any of the affected model families.
-
Determine the installed firmware versionLog into the camera's web interface and navigate to System > Firmware/Version, or query the device's API endpoint that exposes version information. Compare the firmware version to v3.2.2.2.Affected if The firmware version is v3.2.2.2 or lower.
-
Verify the /playback/ endpoint is accessible without authenticationSend an HTTP GET request to http://<device_ip>/playback/ (or a similar path traversal probe such as /playback/..%2F..%2Fetc/passwd) using a tool like curl. Observe if the device responds or returns file content.Affected if The /playback/ endpoint responds without requiring authentication credentials.
-
Assess network exposure of the cameraCheck if the device is directly accessible from untrusted networks (e.g., internet-facing, guest VLANs) by reviewing firewall rules, VLAN assignments, and access control lists.Affected if The camera's HTTP service is reachable from networks where untrusted users could send malicious requests.
A user is affected if they have an Anpnviz IP camera running firmware v3.2.2.2 or lower with the /playback/ endpoint exposed to untrusted network segments.
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 dataRestrict network access to affected IP cameras (e.g., place behind a firewall/VLAN) and apply vendor firmware updates when available. If no update exists, consider network segmentation and monitoring for attempts to exploit this vulnerability.
- Consultation8.0 h
- Implementation16.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,280.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35343 — 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-35343 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