# CVE-2019-16244: Missing authorization in n/a

> Attackers can bypass security filters to access hidden objects in OMERO.server via crafted queries, requiring an upgrade to secure data.

- **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:** No
- **Published:** 22 Jul 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9g7m-mw8w-mqc5

## What is CVE-2019-16244?

CVE-2019-16244 is a critical missing authorization vulnerability in n/a, published on 22 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OMERO.server before 5.6.1 allows attackers to bypass the security filters and access hidden objects via a crafted query.

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

It affects 1 product.


Products: Openmicroscopy Omero.server.

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

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

## Is CVE-2019-16244 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-9943](https://insights.sbomify.com/CVE-2019-9943/): Missing authorization in n/a (high 7.5)
- [CVE-2019-9944](https://insights.sbomify.com/CVE-2019-9944/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16244 is a critical missing authorization vulnerability in n/a, published on 22 Jul 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-16244 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-16244/ (Markdown: https://insights.sbomify.com/CVE-2019-16244/index.md)
```

## Sources

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

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