dbcve.org
Dse855 FirmwareOperating system · Deepseaelectronics

CVE-2024-5947

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
Deep Sea Electronics DSE855 Configuration Backup Missing Authentication Information Disclosure Vulnerability. This vulnerability allows network-adjacent attackers to disclose sensitive information on affected installations of Deep Sea Electronics DSE855 devices. Authentication is not required to exploit this vulnerability. The specific flaw exists within the web-based UI. The issue results from the lack of authentication prior to allowing access to functionality. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-22679.

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

The DSE855 device's web-based configuration backup functionality lacks authentication checks, allowing any network-adjacent attacker to directly access the backup endpoint and retrieve stored credentials. This is a classic broken access control vulnerability where the critical function of exporting device configuration (including credentials) is exposed without verifying user identity.

MitigationRestrict network access to the DSE855 web interface via firewall rules or network segmentation. Implement authentication enforcement on the backup endpoint and apply any available vendor patches. Consider disabling remote access entirely if not required.

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
Dse855 FirmwareOperating system
Affected:= 1.1.0

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Identify device model and firmware version
    Access the DSE855 web interface and navigate to the system information or firmware version page, or check the device label/documentation for the firmware version
    Affected if The device is a Deepseaelectronics DSE855 running firmware version 1.1.0 specifically
  2. Confirm web interface is network-accessible
    Attempt to reach the DSE855 web interface from a host on the network that is not the localhost or a trusted management station
    Affected if The web interface responds to HTTP/HTTPS requests from an unauthorized network-adjacent host
  3. Test backup endpoint without authentication
    Send a direct HTTP GET request to common backup export URLs such as /backup, /cgi-bin/backup, /export, or /config/export without providing any login credentials or session cookies
    Affected if The backup endpoint returns configuration data or a downloadable backup file without requiring authentication
  4. Inspect backup content for credentials
    Open the retrieved backup file and search for stored credentials, passwords, or authentication tokens within the configuration data
    Affected if The backup file contains plaintext or encoded credentials, API keys, or authentication secrets

The environment is affected if you have a DSE855 device running firmware 1.1.0 with its web-based backup endpoint accessible without authentication, exposing stored credentials in the exported configuration data.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to the DSE855 web interface via firewall rules or network segmentation. Implement authentication enforcement on the backup endpoint and apply any available vendor patches. Consider disabling remote access entirely if not required.

Fix this in Dse855 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5947 — 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-2024-5947 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