dbcve.org
Dcs 935l FirmwareOperating system · Dlink

CVE-2025-10779

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-22
Fix available
A fix is available. Upgrade to after 1.13.01 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was found in D-Link DCS-935L up to 1.13.01. The impacted element is the function sub_402280 of the file /HNAP1/. The manipulation of the argument HNAP_AUTH/SOAPAction results in stack-based buffer overflow. The attack may be launched remotely. The exploit has been made public and could be used. This vulnerability only affects products that are no longer supported by the maintainer.

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 confidence

Stack-based buffer overflow in D-Link DCS-935L IP cameras (firmware up to 1.13.01) in the HNAP1 web interface function sub_402280. The vulnerability is triggered via manipulation of the HNAP_AUTH or SOAPAction HTTP header arguments, potentially allowing remote code execution.

MitigationThis is an end-of-life device receiving no vendor patches. Immediate mitigation requires replacing the affected camera with a supported model. Until replacement, network segmentation and restricting web interface access to trusted IPs only may reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dcs 935l FirmwareOperating system
Affected:<= 1.13.01

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is DCS-935L
    Access the camera web interface or check the device label/metadata. The vulnerability specifically affects the D-Link DCS-935L model.
    Affected if The device is a D-Link DCS-935L IP camera.
  2. Identify firmware version
    Log into the camera web interface and navigate to the firmware/version information page, or use the manufacturer diagnostic page (typically at /ver.ini or /cgi-bin/get_status? miscellaneous). Compare the displayed firmware version to the affected range.
    Affected if Firmware version is 1.13.01 or lower.
  3. Verify HNAP1 web interface is accessible
    Attempt to access the camera's web interface over HTTP/HTTPS on the local network. The vulnerability exists in the HNAP1 function sub_402280 within the web interface.
    Affected if The camera web interface (HNAP1 service) is reachable and responds to requests.
  4. Check if device is exposed to untrusted networks
    Review network firewall rules and NAT configurations to determine if the camera web interface (ports 80/443) is accessible from untrusted networks or the internet.
    Affected if The HNAP1 web interface is exposed to untrusted or internet-facing networks.

A user is affected if they operate a D-Link DCS-935L camera running firmware version 1.13.01 or lower, with the HNAP1 web interface accessible on their network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.13.01
Interim mitigation

This is an end-of-life device receiving no vendor patches. Immediate mitigation requires replacing the affected camera with a supported model. Until replacement, network segmentation and restricting web interface access to trusted IPs only may reduce attack surface.

Recommended fix High confidence
  1. 1. Immediately isolate the affected D-Link DCS-935L device from the network to prevent remote exploitation.
  2. 2. Disable or block access to the HNAP1 service endpoint on the device firewall.
  3. 3. Since D-Link has stated this product is no longer supported, replace the DCS-935L with a currently supported device from D-Link or an alternative vendor.
  4. 4. If continued use is absolutely necessary, implement strict network segmentation to limit exposure to local networks only.
  5. 5. Monitor for any D-Link security advisories or community-provided patches, though official support is discontinued.
Caveat The DCS-935L is end-of-life with no official firmware updates; replacement is the only secure path forward.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dcs 935l Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10779 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10779 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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