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

> Attackers can bypass access controls in Citrix ADM to gain unauthorized access to the management interface.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/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:** 9 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fm4g-2r58-3xc3

## What is CVE-2019-17366?

CVE-2019-17366 is a high-severity missing authorization vulnerability in n/a, published on 9 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Citrix Application Delivery Management (ADM) 12.1 before build 54.13 has Incorrect Access Control.

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

It affects 1 product.


Products: Citrix Application Delivery Management.

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

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

## Is CVE-2019-17366 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-9548](https://insights.sbomify.com/CVE-2019-9548/): Missing authorization in n/a (critical 10.0)
- [CVE-2022-27511](https://insights.sbomify.com/CVE-2022-27511/): Privilege escalation in Citrix Application Delivery Management (Citrix ADM) (high 8.1)
- [CVE-2021-22920](https://insights.sbomify.com/CVE-2021-22920/): Auth bypass in Citrix ADC, Citrix Gateway (medium 6.5)
- [CVE-2022-27512](https://insights.sbomify.com/CVE-2022-27512/): Temporary disruption of the ADM license service (medium 5.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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