CVE-2024-50339
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 · uneditedGLPI is a free asset and IT management software package. Starting in version 9.5.0 and prior to version 10.0.17, an unauthenticated user can retrieve all the sessions IDs and use them to steal any valid session. Version 10.0.17 contains a patch for this issue.
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 confidenceGLPI versions 9.5.0 through 10.0.16 contain an unauthenticated session enumeration vulnerability allowing remote attackers to retrieve all active session IDs, which can then be used to hijack any valid user session.
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>= 9.5.0, < 10.0.17CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed GLPI versionLocate the version file in your GLPI installation directory (typically version.php or similar) and read the version number, or use the GLPI system information page if accessible to authenticated administratorsAffected if The installed version is 9.5.0 through 10.0.16 (any version >= 9.5.0 and < 10.0.17)
-
Confirm GLPI is network-accessibleDetermine if the GLPI web interface is exposed to untrusted networks or the internet by reviewing network configuration, firewall rules, or reverse proxy settingsAffected if GLPI is reachable from untrusted networks without proper access controls
-
Verify active user sessions existCheck if there are currently active authenticated sessions in the system by reviewing session storage (database or filesystem-based depending on configuration)Affected if There are active user sessions in the system
-
Review session configurationExamine the GLPI session configuration files and php.ini settings to understand how sessions are handled and storedAffected if Session handling is configured with default settings
You are affected if your GLPI version is 9.5.0 through 10.0.16 and the application is accessible to untrusted network actors, as the vulnerability allows unauthenticated retrieval of active session IDs.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.17
Upgrade GLPI to version 10.0.17 or later to patch the session enumeration issue. If immediate upgrade is not possible, review session configuration and consider network-level access controls to limit exposure.
GLPI 10.0.17
- Upgrade GLPI to version 10.0.17 or later to resolve the vulnerability
- Verify the upgrade in a test environment before deploying to production
- After upgrade, consider invalidating existing sessions to force re-authentication for all users as a security precaution
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50339 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-50339 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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