# CVE-2023-32637: File upload in GBrowse

> Attackers can upload malicious files to GBrowse to execute arbitrary code on the server due to lack of file type validation.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2023
- **Updated:** 23 Oct 2024
- **Also known as:** DEBIAN-CVE-2023-32637, GHSA-jffq-5gqv-qfcx

## What is CVE-2023-32637?

CVE-2023-32637 is a critical vulnerability in Generic Model Organism Database Project GBrowse, published on 25 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GBrowse accepts files with any formats uploaded and places them in the area accessible through unauthenticated web requests. Therefore, anyone who can upload files through the product may execute arbitrary code on the server.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2023-32637?

It affects 1 product.


Products: Gmod Gbrowse.

## How do I fix CVE-2023-32637?

Apply the vendor's patch.

## Is CVE-2023-32637 being exploited?

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

## Other vulnerabilities in Generic Model Organism Database Project GBrowse

- [CVE-2008-3781](https://insights.sbomify.com/CVE-2008-3781/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32637 and fix it if it is affected.

What it is: CVE-2023-32637 is a critical vulnerability in Generic Model Organism Database Project GBrowse, published on 25 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-32637 in the wild and no public exploit code.

Affected product: Generic Model Organism Database Project GBrowse. 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-2023-32637/ (Markdown: https://insights.sbomify.com/CVE-2023-32637/index.md)
```

## Sources

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

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