# CVE-2020-10194: Missing authorization in n/a

> Authenticated users can access any GAL account regardless of domain, bypassing intended domain restrictions in Zimbra.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 20 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-72wm-wxqm-26cv

## What is CVE-2020-10194?

CVE-2020-10194 is a medium-severity missing authorization vulnerability in n/a, published on 20 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

cs/service/account/AutoCompleteGal.java in Zimbra zm-mailbox before 8.8.15.p8 allows authenticated users to request any GAL account. This differs from the intended behavior in which the domain of the authenticated user must match the domain of the galsync account in the request.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2020-10194?

It affects 1 product.


Products: Zimbra Zm-Mailbox.

## How do I fix CVE-2020-10194?

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

## Is CVE-2020-10194 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10194 and fix it if it is affected.

What it is: CVE-2020-10194 is a medium-severity missing authorization vulnerability in n/a, published on 20 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10194 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-2020-10194/ (Markdown: https://insights.sbomify.com/CVE-2020-10194/index.md)
```

## Sources

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

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