dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2024-45841

MEDIUM · 6.5 CVSS v3.0 Published 2024-12-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Incorrect permission assignment for critical resource issue exists in UD-LT1 firmware Ver.2.1.9 and earlier and UD-LT1/EX firmware Ver.2.1.9 and earlier. If an attacker with the guest account of the affected products accesses a specific file, the information containing credentials may be obtained.

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

Incorrect permission assignment in UD-LT1 and UD-LT1/EX firmware allows guest account users to access a specific file containing credentials, enabling unauthorized credential disclosure.

MitigationUpdate firmware to a version beyond Ver.2.1.9 that contains the security fix, or restrict guest account access to sensitive files pending the update.

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

CVSS:3.0/AV:N/AC:L/PR:L/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. Confirm device model
    Identify if the device is a UD-LT1 or UD-LT1/EX unit. Check the device label, web interface, or system information page for the exact model number.
    Affected if Device is a UD-LT1 or UD-LT1/EX unit with firmware prior to Ver.2.1.9
  2. Check firmware version
    Access the device's admin interface or use the appropriate command (such as 'show version' or system status page) to retrieve the current firmware version.
    Affected if Firmware version is earlier than Ver.2.1.9 (the fixed version)
  3. Verify guest account is active
    Check the user account settings in the device admin panel to determine if the guest account is enabled or has been used.
    Affected if Guest account is enabled or accessible on the device
  4. Test for credential file access
    Using the guest account credentials, attempt to locate and access any configuration or credential file that may contain stored credentials. The specific file location varies by implementation.
    Affected if Guest-level access allows reading files that should be restricted to admin users, exposing credentials

A user is affected if the device is a UD-LT1 or UD-LT1/EX with firmware before Ver.2.1.9 and guest account access is enabled, allowing unauthorized retrieval of credential 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

Update firmware to a version beyond Ver.2.1.9 that contains the security fix, or restrict guest account access to sensitive files pending the update.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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