# CVE-2019-9944: Path traversal in n/a

> Attackers can bypass permission restrictions to read arbitrary files via embedded pathnames in imported image filesets.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p97h-4jgc-m3x7

## What is CVE-2019-9944?

CVE-2019-9944 is a high-severity path traversal vulnerability in n/a, published on 17 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Open Microscopy Environment OMERO.server 5.0.0 through 5.6.0, the reading of files from imported image filesets may circumvent OMERO permissions restrictions. This occurs because the Bio-Formats feature allows an image file to have embedded pathnames.

## Which versions are affected by CVE-2019-9944?

It affects 1 product.


Products: Openmicroscopy Omero.server.

## How do I fix CVE-2019-9944?

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

## Is CVE-2019-9944 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16244](https://insights.sbomify.com/CVE-2019-16244/): Missing authorization in n/a (critical 9.8)
- [CVE-2019-9943](https://insights.sbomify.com/CVE-2019-9943/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9944 and fix it if it is affected.

What it is: CVE-2019-9944 is a high-severity path traversal vulnerability in n/a, published on 17 Jun 2020. 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-2019-9944 in the wild and no public exploit code.

Affected product: n/a. 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-2019-9944/ (Markdown: https://insights.sbomify.com/CVE-2019-9944/index.md)
```

## Sources

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

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