# CVE-2024-12284: Authenticated privilege escalation

> Authenticated attackers can escalate privileges in NetScaler Console and Agent, requiring immediate patching by administrators.

- **Severity:** High 8.8 (`CVSS:4.0/AV:A/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-4g7p-889h-qvww

## What is CVE-2024-12284?

CVE-2024-12284 is a high-severity vulnerability in NetScaler Agent, published on 19 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Authenticated privilege escalation in NetScaler Console and NetScaler Agent allows.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-12284?

It affects 2 products.


Products: Citrix Netscaler Agent, Citrix Netscaler Console.

## How do I fix CVE-2024-12284?

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

## Is CVE-2024-12284 being exploited?

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

## Other vulnerabilities in NetScaler Agent

- [CVE-2024-6236](https://insights.sbomify.com/CVE-2024-6236/): Denial of Service (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12284 and fix it if it is affected.

What it is: CVE-2024-12284 is a high-severity vulnerability in NetScaler Agent, published on 19 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-12284 in the wild and no public exploit code.

Affected product: NetScaler Agent. 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-2024-12284/ (Markdown: https://insights.sbomify.com/CVE-2024-12284/index.md)
```

## Sources

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

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