dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-14341

HIGH · 8.3 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Improperly controlled modification of Dynamically-Determined object attributes, Allocation of resources without limits or throttling vulnerability in DivvyDrive Information Technologies Inc. DivvyDrive allows Excessive Allocation, Flooding. This issue affects DivvyDrive: from 4.8.2.19 before 4.8.3.2.

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 confidence

DivvyDrive versions 4.8.2.19 through before 4.8.3.2 contain an improperly controlled modification vulnerability where attackers can manipulate dynamically-determined object attributes without proper validation, combined with a resource allocation flaw allowing excessive allocation/flooding. This can lead to resource exhaustion or denial of service through unbounded attribute manipulation.

MitigationUpgrade DivvyDrive to version 4.8.3.2 or later. If immediate patching is not possible, implement rate limiting and resource quotas at the infrastructure level to mitigate excessive allocation attempts.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/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. Identify installed DivvyDrive version
    Check the DivvyDrive application version through its built-in about dialog, startup logs, or by querying the installed package. Common locations include the application settings menu, a 'divvydrive --version' command if CLI is available, or the software inventory on the system.
    Affected if The installed version is 4.8.2.19, 4.8.2.20, 4.8.2.21, 4.8.2.22, 4.8.2.23, 4.8.2.24, 4.8.2.25, 4.8.2.26, 4.8.2.27, 4.8.2.28, 4.8.2.29, 4.8.3.0, or 4.8.3.1 (any version from 4.8.2.19 up to but not including 4.8.3.2).
  2. Confirm attribute manipulation feature is in use
    Review DivvyDrive configuration files or audit logs for usage of dynamic attribute manipulation features, particularly any feature that allows users to define or modify object attributes at runtime. Check if the application exposes APIs or interfaces that accept attribute parameters from user input.
    Affected if Dynamic object attribute modification features are enabled and accessible to users or unauthenticated attackers.
  3. Inspect for excessive resource allocation indicators
    Monitor DivvyDrive process resource usage and review application logs for patterns of repeated attribute creation, memory growth, or allocation errors. Look for log entries indicating unbounded object creation or memory pressure events.
    Affected if Logs or monitoring show repeated attribute manipulation requests, escalating memory consumption, or resource exhaustion events without proper throttling.
  4. Check for rate limiting configuration
    Examine DivvyDrive configuration files or infrastructure-level settings for rate limiting, throttling, or resource quota enforcement on attribute manipulation operations.
    Affected if No rate limiting or resource quotas are configured on attribute manipulation endpoints or operations.

You are affected if DivvyDrive is installed at any version from 4.8.2.19 through 4.8.3.1 AND the dynamic attribute manipulation feature is accessible and unprotected by rate limiting or resource quotas.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade DivvyDrive to version 4.8.3.2 or later. If immediate patching is not possible, implement rate limiting and resource quotas at the infrastructure level to mitigate excessive allocation attempts.

Recommended fix Moderate confidence

4.8.3.2 or later

  1. 1. Identify the current DivvyDrive version by checking the application settings or system information panel
  2. 2. If the installed version is 4.8.2.19 or any version before 4.8.3.2, this instance is vulnerable
  3. 3. Obtain the updated DivvyDrive version 4.8.3.2 or later from the official vendor
  4. 4. Back up the current DivvyDrive configuration and data according to backup procedures
  5. 5. Apply the upgrade to DivvyDrive version 4.8.3.2 or latest stable release
  6. 6. Verify the upgrade was successful by checking the new version number
  7. 7. Test critical functionality to ensure the application operates normally after the update

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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