# CVE-2025-34066: AVTECH IP camera, DVR, and NVR Devices Unauthenticated Information Disclosure

> Attackers can intercept HTTPS traffic via MITM due to disabled certificate validation in AVTECH devices, exposing sensitive data.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-4cx5-3q2w-5wr7

## What is CVE-2025-34066?

CVE-2025-34066 is a high-severity vulnerability in AVTECH DVR devices, published on 1 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An improper certificate validation vulnerability exists in AVTECH IP cameras, DVRs, and NVRs due to the use of wget with --no-check-certificate in scripts like SyncCloudAccount.sh and SyncPermit.sh. This exposes HTTPS communications to man-in-the-middle (MITM) attacks.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2025-34066?


## How do I fix CVE-2025-34066?

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

## Is CVE-2025-34066 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34066 and fix it if it is affected.

What it is: CVE-2025-34066 is a high-severity vulnerability in AVTECH DVR devices, published on 1 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34066 exists.

Affected product: AVTECH DVR devices. 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-2025-34066/ (Markdown: https://insights.sbomify.com/CVE-2025-34066/index.md)
```

## Sources

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

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