dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2024-39025

HIGH · 7.5 CVSS v3.1 Published 2024-12-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
Incorrect access control in the /users endpoint of Cpacker MemGPT v0.3.17 allows attackers to access sensitive data.

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

In Cpacker MemGPT v0.3.17, the /users endpoint lacks proper access control checks, allowing unauthenticated or unauthorized attackers to retrieve sensitive user data by directly accessing this API endpoint.

MitigationImplement proper authentication and role-based authorization checks on the /users endpoint to ensure only authorized users can access user data; update to a patched version if available.

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

CVSS:3.1/AV:N/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 MemGPT version
    Run 'pip show memgpt' or check the installed package version using your package manager to determine if version 0.3.17 is in use
    Affected if The installed version is 0.3.17 or falls within the range that includes 0.3.17 as vulnerable
  2. Confirm /users endpoint exists
    Locate the API route definitions in the MemGPT application codebase or deployment configuration and verify the /users endpoint is defined
    Affected if The /users endpoint exists in the application routing configuration
  3. Check if /users endpoint is network-accessible
    Identify whether the MemGPT service is exposed to the network (check bind address configuration, firewall rules, or reverse proxy settings) and determine if the /users endpoint can be reached from untrusted networks
    Affected if The /users endpoint is externally accessible or accessible to untrusted users
  4. Test endpoint authentication requirement
    Send an HTTP request to the /users endpoint without providing authentication credentials or with invalid/empty credentials and observe the response
    Affected if The endpoint returns sensitive user data (such as user lists, emails, or personal information) without requiring valid authentication or authorization tokens

If running MemGPT version 0.3.17 (or a vulnerable version range including it) and the /users endpoint is accessible without authentication while returning user data, the environment is affected by this CVE.

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

Implement proper authentication and role-based authorization checks on the /users endpoint to ensure only authorized users can access user data; update to a patched version if available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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