dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-1415

MEDIUM · 5.1 CVSS v4.0 Published 2025-05-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
53/100
Remediation priority · Moderate
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 low-privileged user is able to obtain information about tasks executed on devices controlled by Proget MDM (Mobile Device Management), as well as details of the devices like their UUIDs needed for exploitation of CVE-2025-1416. In order to perform the attack, one has to know a task_id, but since it's a low integer and there is no limit of requests an attacker can perform to a vulnerable endpoint, the task_id might be simply brute forced. This issue has been fixed in 2.17.5 version of Konsola Proget (server part of the MDM suite).

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

A low-privileged user can enumerate sensitive task execution data and device UUIDs from the Proget MDM server by brute-forcing low-integer task IDs on an unauthenticated or improperly authorized endpoint lacking rate limiting. This information can be used to exploit follow-on vulnerabilities (CVE-2025-1416).

MitigationUpgrade Konsola Proget to version 2.17.5 or later, and implement rate limiting on the affected endpoint to prevent enumeration attacks.

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
Adjacent
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/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 checks

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

  1. Confirm ProGet MDM server is running
    Identify if the ProGet MDM server software is installed in your environment. Check for processes named 'ProGet' or services listening on common ProGet ports (typically 80/443 for web interface).
    Affected if ProGet MDM server is installed and running in your environment.
  2. Determine ProGet version
    Locate the installed ProGet version by checking the web interface footer, using the administrative console, or querying the API endpoint for version information.
    Affected if The installed version is earlier than 2.17.5 (the fixed version).
  3. Identify task enumeration endpoint availability
    Locate the API endpoint that handles task execution data. Based on the CVE, this is typically an endpoint that accepts integer task IDs (such as /api/tasks/{id} or similar paths). Probe this endpoint without authentication to determine if it responds.
    Affected if The task ID endpoint is accessible without authentication or with low-privileged credentials.
  4. Test for unauthenticated task data enumeration
    Send HTTP GET requests to the task endpoint with sequential low-integer IDs (e.g., 1, 2, 3, 4, 5). Observe if the responses contain sensitive task execution data or device UUIDs without requiring proper authorization.
    Affected if The endpoint returns task execution data or device UUIDs for sequential task IDs without requiring elevated privileges.
  5. Check for rate limiting on task endpoint
    Send multiple rapid requests to the task enumeration endpoint with different task IDs. Determine if the server implements any rate limiting, throttling, or request blocking after a certain number of attempts.
    Affected if No rate limiting is enforced, allowing unlimited enumeration attempts.

Your environment is affected if ProGet MDM version is earlier than 2.17.5 and the task enumeration endpoint is accessible without proper authentication and without rate limiting protection.

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 Konsola Proget to version 2.17.5 or later, and implement rate limiting on the affected endpoint to prevent enumeration attacks.

Recommended fix High confidence

Konsola Proget version 2.17.5 or later

  1. Upgrade Konsola Proget (server part of MDM suite) to version 2.17.5 or later
  2. Verify the upgrade was successful by logging into the Konsola Proget administrative interface
  3. Confirm that low-privileged users can no longer access task information or device UUIDs through the vulnerable endpoint
  4. If applicable, review access logs to ensure no unauthorized access occurred prior to patching
Caveat Review release notes for 2.17.5 for any configuration or behavioral changes before upgrading in production environments

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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