Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-34065AVTECH IP camera, DVR, and NVR Devices Authentication Bypass via /nobody URL Path

Description

An authentication bypass vulnerability exists in AVTECH IP camera, DVR, and NVR devices’ streamd web server. The strstr() function allows unauthenticated access to any request containing "/nobody" in the URL, bypassing login controls.

Public exploit

An exploit or proof of concept is public: anyone can try it against an unpatched system. 2 references of the record are tagged as an exploit. CISA's SSVC rates its exploitation: a proof of concept is public.

Show the exploits2

Timeline

  1. ID reserved

    By VulnCheck

  2. · 3 months later

    Published

  3. · 9 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-34065, by who scored it
Scored byCVSSScoreVector
VulnCheckCNA (assigner)4.0Medium6.9CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
NVDNVD · Deferred4.0Medium6.9CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS (exploitation in 30 days)
0.62% · top 50% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: poc · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.9.

Affected products

  • AVTECH · IP camera, DVR, and NVR Devices

    • affected 1000-1000-1000-1000
    • affected 1000C-1000C-1000C-1000C
    • affected 1001-1000-1000-1000
    • affected 1001-1001-1000-1000
    • affected 1002-1000-1000-1000
    • affected 1002-1002-1000-1002
    • affected 1002D-1000D-1000D-1000D
    • affected 1003-1000-1000-1001
    • affected 1003-1001-1001-1000
    • affected 1003-1002-1001-1000
    • affected 1004-1000-1000-1000
    • affected 1004-1001-1001-1001
    • affected 1004-1002-1000-1001
    • affected 1004-1003-1001-1002
    • affected 1004-1003-1002-1001
    • affected 1004A-1001A-1002A-1000A
    • affected 1005-1002-1001-1002
    • affected 1005-1003-1001-1002
    • affected 1005-1004-1002-1001
    • affected 1005A-1001A-1002A-1001A
    • affected 1005D-1001D-1002D-1001D
    • affected 1006-1002-1001-1002
    • affected 1006-1003-1001-1001
    • affected 1006-1004-1003-1001
    • affected 1007-1001-1003-1001
    • affected 1007-1001-1004-1003
    • affected 1007-1002-1001-1000
    • affected 1007-1002-1001-1003
    • affected 1007-1002-1003-1002
    • affected 1007-1004-1003-1001
    • affected 1008-1001-1003-1002
    • affected 1008-1004-1004-1001
    • affected 1008D-1003D-1004D-1002D
    • affected 1008J-1004J-1004J-1001J
    • affected 1009-1001-1004-1001
    • affected 1009-1002-1005-1003
    • affected 1009-1003-1001-1003
    • affected 1009-1003-1005-1002
    • affected 1010-1001-1004-1001
    • affected 1010-1001-1004-1002
    • and 12 more

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-34065 badge
[![CVE-2025-34065](https://cveledger.app/badge/CVE-2025-34065.svg)](https://cveledger.app/cve/CVE-2025-34065)

Record last updated .