# CVE-2018-7562: Race condition in n/a

> An authenticated attacker can exploit a race condition during file upload to execute arbitrary code on the GLPI server.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m6v3-mvq4-j684, UBUNTU-CVE-2018-7562

## What is CVE-2018-7562?

CVE-2018-7562 is a high-severity vulnerability in Glpi-Project Glpi, published on 12 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A remote code execution issue was discovered in GLPI through 9.2.1. There is a race condition that allows temporary access to an uploaded executable file that will be disallowed. The application allows an authenticated user to upload a file when he/she creates a new ticket via front/fileupload.php. This feature is protected using different types of security features like the check on the file's extension. However, the application uploads and creates a file, though this file is not allowed, and then deletes the file in the uploadFiles method in inc/glpiuploaderhandler.class.php.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2018-7562?

It affects 1 product.


Products: Glpi-Project Glpi.

## How do I fix CVE-2018-7562?

No fix has been published for CVE-2018-7562 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-7562 being exploited?

There is no known exploitation of CVE-2018-7562 in the wild and no public exploit code.

## Other vulnerabilities in Glpi-Project Glpi

- [CVE-2022-35914](https://insights.sbomify.com/CVE-2022-35914/): Teclib GLPI Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2023-42802](https://insights.sbomify.com/CVE-2023-42802/): GLPI vulnerable to unallowed PHP script execution (critical 10.0)
- [CVE-2023-28849](https://insights.sbomify.com/CVE-2023-28849/): GLPI vulnerable to SQL injection and Stored XSS via inventory agent request (critical 10.0)
- [CVE-2022-35947](https://insights.sbomify.com/CVE-2022-35947/): SQL injection in GLPI (critical 10.0)
- [CVE-2022-31056](https://insights.sbomify.com/CVE-2022-31056/): SQL injection with _actor parameter in GLPI (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7562 and fix it if it is affected.

What it is: CVE-2018-7562 is a high-severity vulnerability in Glpi-Project Glpi, published on 12 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-7562 in the wild and no public exploit code.

Affected product: Glpi-Project Glpi. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-7562/ (Markdown: https://insights.sbomify.com/CVE-2018-7562/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-7562
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-7562
- OSV: https://osv.dev/vulnerability/CVE-2018-7562

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-7562/
Summaries are generated and may contain mistakes; the official description above is the record.