# CVE-2024-51347: Memory corruption in n/a

> A buffer overflow in the LSC Smart Indoor IP Camera allows attackers to execute arbitrary code or cause denial of service via the ONVIF Time Zone parameter.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2026
- **Updated:** 25 Mar 2026
- **Also known as:** GHSA-gmh9-fg82-9pr5

## What is CVE-2024-51347?

CVE-2024-51347 is a high-severity memory corruption vulnerability in n/a, published on 25 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A 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.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2024-51347?


## How do I fix CVE-2024-51347?

No fix has been published for CVE-2024-51347 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-51347 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51347 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-51347 and fix it if it is affected.

What it is: CVE-2024-51347 is a high-severity memory corruption vulnerability in n/a, published on 25 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51347 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-51347/ (Markdown: https://insights.sbomify.com/CVE-2024-51347/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-51347
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-51347
- OSV: https://osv.dev/vulnerability/CVE-2024-51347

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-51347/
Summaries are generated and may contain mistakes; the official description above is the record.