# CVE-2024-6235: Sensitive information disclosure

> Attackers can access sensitive information in NetScaler Console due to an authentication bypass vulnerability.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2024
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-g3gr-qpxc-qc6c

## What is CVE-2024-6235?

CVE-2024-6235 is a critical vulnerability in NetScaler Console, published on 10 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sensitive information disclosure in NetScaler Console

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Citrix Netscaler Console.

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

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

## Is CVE-2024-6235 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6235 exists.

Public exploit code:

- NetScaler Console - Sensitive Information Disclosure (nuclei): http/cves/2024/CVE-2024-6235.yaml

## Other vulnerabilities in NetScaler Console

- [CVE-2025-4365](https://insights.sbomify.com/CVE-2025-4365/): NetScaler Console and NetScaler SDX (SVM) - Arbitrary file read (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6235 is a critical vulnerability in NetScaler Console, published on 10 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6235 exists.

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

## Sources

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

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