CVE-2024-51347
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 buffer overflow vulnerability in the dgiot binary in LSC Smart Indoor IP Camera V7.6.32. The flaw exists in the handling of the Time Zone (TZ) parameter within the ONVIF configuration interface. The time zone (TZ) parameter does not have its length properly validated before being copied into a fixed-size buffer using the insecure strcpy function.
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 confidenceA buffer overflow vulnerability exists in the dgiot binary of LSC Smart Indoor IP Camera V7.6.32. The Time Zone (TZ) parameter received through the ONVIF configuration interface is copied into a fixed-size buffer using the insecure strcpy function without any length validation. An attacker sending a TZ value exceeding the buffer size can trigger overflow, potentially leading to code execution or denial of service.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 modelCheck your device labeling, web interface, or system information to confirm the product is an LSC Smart Indoor IP Camera.Affected if The device is not an LSC Smart Indoor IP Camera.
-
Check firmware versionAccess the camera's web interface or check via ONVIF/SNMP to retrieve the firmware version. Compare against V7.6.32.Affected if Firmware version is V7.6.32.
-
Verify ONVIF service is enabledCheck the camera's network settings or service list to determine if the ONVIF interface is currently active and accessible.Affected if ONVIF service is enabled and reachable on the network.
-
Confirm dgiot binary presenceIf you have shell access or can enumerate the camera's filesystem, locate the dgiot binary which contains the vulnerable strcpy call.Affected if The dgiot binary exists and handles ONVIF configuration.
-
Check TZ parameter acceptanceAttempt to send an ONVIF SetConfiguration request with a TimeZone parameter to determine if the camera accepts and processes this value.Affected if The camera accepts TZ parameters through ONVIF without length validation.
You are affected if you are running an LSC Smart Indoor IP Camera on firmware V7.6.32 with the ONVIF interface enabled and the dgiot binary present, allowing TZ parameter configuration.
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 dataImplement proper input length validation on the TZ parameter before copying and replace strcpy with bounds-safe functions like strncpy or strlcpy. Apply vendor firmware updates when available. Restrict ONVIF interface access to trusted networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51347 — 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-51347 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