dbcve.org
NfuseApplication · Citrix

CVE-2002-0301

MEDIUM · 5.0 CVSS v2.0 Published 2002-05-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Citrix NFuse 1.6 allows remote attackers to bypass authentication and obtain sensitive information by directly calling launch.asp with invalid NFUSE_USER and NFUSE_PASSWORD parameters.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Citrix NFuse 1.6 contains an authentication bypass vulnerability in launch.asp where invalid NFUSE_USER and NFUSE_PASSWORD parameter values still allow access to sensitive information, enabling unauthenticated attackers to retrieve confidential data.

MitigationUpgrade from the deprecated NFuse 1.6 to a supported Citrix solution, or if legacy systems must remain operational, implement strict network access controls and web application firewall rules to restrict direct access to launch.asp.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NfuseApplication
Affected:= 1.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Citrix NFuse installation and version
    Check for the presence of NFuse installation directories, typically under the web server's root (e.g., /Citrix/NFuse, /nfuse, or similar paths). Look for version files, about pages, or meta-inf/VERSION files within the NFuse application directory. Alternatively, check the HTTP server banner or examine the HTML source of NFuse pages for version strings like '1.6'.
    Affected if The installed version is exactly Citrix NFuse 1.6
  2. Verify launch.asp is accessible
    Confirm that the launch.asp file exists within the NFuse web application directory and is accessible via HTTP (e.g., https://target/Citrix/NFuse/launch.asp or similar path). Use a web crawler or manually request the file to verify its presence.
    Affected if launch.asp is present and reachable over the network
  3. Check if NFUSE_USER and NFUSE_PASSWORD parameters are accepted
    Send an HTTP POST or GET request to launch.asp with deliberately invalid or empty values for NFUSE_USER and NFUSE_PASSWORD parameters. For example: NFUSE_USER=invalid&NFUSE_PASSWORD=invalid. Observe whether the application processes the request without rejecting it due to authentication failure.
    Affected if The application accepts and processes requests with invalid credential parameters without proper authentication rejection
  4. Confirm unauthenticated access to sensitive resources
    After submitting invalid credentials via the NFUSE_USER/NFUSE_PASSWORD parameters, verify whether the response contains sensitive data, session tokens, application state, or redirect URLs that should only be accessible to authenticated users. Compare the response to that of a legitimate authenticated session.
    Affected if Invalid credentials still provide access to sensitive application data or functionality that should require authentication

A system is affected if it runs Citrix NFuse version 1.6 with the launch.asp page accessible and accepting NFUSE_USER/NFUSE_PASSWORD parameters without proper authentication validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade from the deprecated NFuse 1.6 to a supported Citrix solution, or if legacy systems must remain operational, implement strict network access controls and web application firewall rules to restrict direct access to launch.asp.

Fix this in Nfuse Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-0301 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2002-0301 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data