# CVE-2009-2453: Auth bypass in n/a

> Attackers can bypass intended access restrictions in Citrix XenApp when Access Gateway Advanced Edition filters are defined, allowing unauthorized access.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-w4g4-v88p-5wq3

## What is CVE-2009-2453?

CVE-2009-2453 is a high-severity authentication bypass vulnerability in n/a, published on 14 Jul 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Citrix XenApp (formerly Presentation Server) 4.5 Hotfix Rollup Pack 3 does not apply an access policy when it is defined with the Access Gateway Advanced Edition filters, which allows attackers to bypass intended access restrictions via unknown vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2009-2453?

It affects 2 products.


Products: Citrix Presentation Server, Citrix Xenapp.

## How do I fix CVE-2009-2453?

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

## Is CVE-2009-2453 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2453 and fix it if it is affected.

What it is: CVE-2009-2453 is a high-severity authentication bypass vulnerability in n/a, published on 14 Jul 2009. 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-2009-2453 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-2009-2453/ (Markdown: https://insights.sbomify.com/CVE-2009-2453/index.md)
```

## Sources

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

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