CVE-2025-41017
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 · uneditedInadequate access control vulnerability in Davantis DDFUSION v6.177.7, which allows unauthorised actors to retrieve perspective parameters from security camera settings by accessing “/cameras/<CAMERA_ID>/perspective”.
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 · moderate confidenceThis is an Insecure Direct Object Reference (IDOR) vulnerability in Davantis DDFUSION video management software v6.177.7. The application fails to enforce proper authorization on the /cameras/<CAMERA_ID>/perspective endpoint, allowing any unauthenticated or unauthorized user to retrieve camera perspective configuration parameters by simply knowing or guessing valid camera IDs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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
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 checksWork through these to decide whether this CVE applies to you.
-
Identify DDFUSION software versionLocate the installed version by checking the web interface footer, admin panel about page, system information section, or application startup logs for version 6.177.7.Affected if Running DDFUSION version 6.177.7 specifically
-
Confirm /cameras/*/perspective endpoint existsSend an HTTP GET request to /cameras/1/perspective (or any numeric camera ID) on the DDFUSION web server and observe if the endpoint responds.Affected if The endpoint responds with any HTTP status other than 404 (not found)
-
Test unauthenticated access to camera perspectiveSend a request to /cameras/<CAMERA_ID>/perspective without providing any authentication credentials (no session cookie, no API token).Affected if The endpoint returns camera perspective configuration data (JSON/XML with perspective parameters) without requiring authentication
-
Test unauthorized access across different camera IDsRequest /cameras/<CAMERA_ID>/perspective using multiple camera ID values (e.g., 1, 2, 3, 100, 1000) without proper authorization for those specific cameras.Affected if Any camera ID returns perspective configuration without verifying the user has permission to view that specific camera
The environment is affected if running DDFUSION v6.177.7 and the /cameras/<CAMERA_ID>/perspective endpoint returns camera perspective data without requiring valid authentication or checking user permissions for the requested camera.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement proper authentication and authorization checks on the /cameras/*/perspective endpoint to ensure users can only access camera settings for cameras they are explicitly permitted to view. Consider implementing role-based access control (RBAC) for all camera-related endpoints.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-41017 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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