CVE-2025-31701Public exploitNetwork attack vector

Unauthenticated root code execution via Cseq overflow

Published Jul 23, 2025 · Updated Jul 23, 2025

Buffer overflow in Dahua IPC and SD camera firmware built before April 16, 2025 allows remote attackers to execute code via crafted HTTP requests. The undocumented POST /RPC2_UploadFileWithName/* handler copies the Cseq header with flawed strncpy bounds into a .bss buffer, allowing adjacent session function pointers to be overwritten. No authentication or user interaction is required on the local network; redirected execution reaches system() with root privileges, while ASLR reduces code-execution reliability but not crash risk.

CVSS severity8.1
High
EPSS probability0.82%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Buffer overflow in Dahua IPC and SD camera firmware built before April 16, 2025 allows remote attackers to execute code via crafted HTTP requests. The undocumented POST /RPC2_UploadFileWithName/* handler copies the Cseq header with flawed strncpy bounds into a .bss buffer, allowing adjacent session function pointers to be overwritten. No authentication or user interaction is required on the local network; redirected execution reaches system() with root privileges, while ASLR reduces code-execution reliability but not crash risk.

The record

CVE
CVE-2025-31701
Published
Jul 23, 2025
Updated
Jul 23, 2025
Vendor
Zhejiang Dahua Technology Co., Ltd.
Product
IPC
Classifications
CWE-120, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 23, 2025CVE publishedPublication date reported by the CVE source.
  2. Jul 23, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=Affected products include certain models from the IPC-1XXX, IPC-2XXX, IPC-WX, and IPC-ECXX series, and limited to versions which build time before April 16, 2025.

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Zhejiang Dahua Technology Co., Ltd. · IPCversion=Affected products include certain models from the IPC-1XXX, IPC-2XXX, IPC-WX, and IPC-ECXX series, and limited to versions which build time before April 16, 2025.
Zhejiang Dahua Technology Co., Ltd. · SDversion=Affected products include certain models from the SD3A, SD2A, SD3D, SDT2A, and SD2C series, and limited to versions which build time before April 16, 2025.

Published CVSS scores

8.1Dahua PSIRTCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
7.3Dahua PSIRTCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo