dbcve.org
GlpiApplication · Glpi Project

CVE-2024-38370

HIGH · 7.5 CVSS v3.1 Published 2024-11-15
Fix available
A fix is available. Upgrade to 10.0.16 or later.
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
GLPI is a free asset and IT management software package. Starting in 9.2.0 and prior to 11.0.0, it is possible to download a document from the API without appropriate rights. Upgrade to 10.0.16.

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

GLPI versions 9.2.0 through 10.0.15 (before 11.0.0) contain an broken access control vulnerability in the API that allows authenticated or unauthenticated users to download documents without proper authorization checks. The API endpoint fails to validate user permissions before serving document content, enabling unauthorized access to sensitive files.

MitigationUpgrade GLPI to version 10.0.16 or later which contains the fix for this authorization bypass. Organizations unable to upgrade immediately should restrict API access through network segmentation or web application firewall rules.

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
GlpiApplication
Affected:>= 9.2.0, < 10.0.16

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 installed GLPI version
    Check the version.php file in the GLPI root directory or log into the GLPI administration interface and navigate to Setup > General > System to view the version information
    Affected if The installed version is 9.2.0 through 10.0.15 (any version before 10.0.16)
  2. Verify API module is enabled
    Log into GLPI as an administrator, navigate to Setup > API, or check the api.disabled configuration file/setting. The API is typically enabled by default for integrations.
    Affected if The API is enabled and accessible (this is the default configuration in affected versions)
  3. Confirm document management is in use
    Check if documents have been uploaded to GLPI by browsing to the Documents section or checking the glpi_documents database table for stored files
    Affected if Documents have been uploaded to the GLPI system (the vulnerability allows unauthorized download of any stored document)
  4. Test API document endpoint access
    Use a web request tool to send a GET request to the API document endpoint (such as /api/document.php?documents_id=1 or similar) without authentication or with a low-privilege user account
    Affected if The API returns document content without requiring proper authorization or returns an unexpected success response indicating the authorization check is bypassed

You are affected if GLPI version is between 9.2.0 and 10.0.15, the API is enabled, and documents exist in the system where an unauthorized user could access them via the API endpoint.

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
Upgrade available Upgrade to 10.0.16 or later
Fixed in 10.0.16
Interim mitigation

Upgrade GLPI to version 10.0.16 or later which contains the fix for this authorization bypass. Organizations unable to upgrade immediately should restrict API access through network segmentation or web application firewall rules.

Recommended fix High confidence

10.0.16

  1. Back up the current GLPI database and files
  2. Back up the configuration file (config_db.php)
  3. Put the site in maintenance mode
  4. Download GLPI version 10.0.16 from the official source (github.com/glpi-project/glpi)
  5. Extract the new files to the web server document root
  6. Run the GLPI update script via browser or command line (php bin/console glpi:database:update)
  7. Verify the upgrade was successful by logging in
  8. Disable maintenance mode
Caveat Review GLPI 10.0.16 release notes for any migration or breaking changes before upgrading

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

Fix this in Glpi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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