NfuseApplication · Citrix
CVE-2002-0502
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 · uneditedCitrix NFuse 1.6 may allow remote attackers to list applications without authentication by accessing the applist.asp page.
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 confidenceCitrix NFuse 1.6 contains an information disclosure vulnerability where the applist.asp page can be accessed without authentication, allowing remote attackers to enumerate published applications and gather intelligence about the infrastructure.
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
= 1.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Citrix NFuse is installedCheck the system for Citrix NFuse installation directories, services, or IIS web application mappings. Look in standard locations such as C:\Citrix\NFuse or check IIS for NFuse application pools.Affected if Citrix NFuse is found on the system and the version is 1.6
-
Confirm the exact NFuse versionReview installation logs, the NFuse administration console, or check the NFuse.dll or other version information within the NFuse installation directory.Affected if The installed version is exactly 1.6
-
Locate the applist.asp fileSearch for applist.asp in the NFuse web root directory (typically under /NFuse/ or /Citrix/NFuse/ within the web server document root).Affected if The applist.asp file exists in the NFuse web directory
-
Test unauthenticated access to applist.aspUse a web browser or curl command to request the applist.asp page without providing any authentication credentials: http://[target]/NFuse/applist.aspAffected if The page loads and displays a list of published applications without requiring login credentials
-
Verify the applist page returns infrastructure informationExamine the response from the applist.asp request. Look for published application names, server names, or other infrastructure details that should not be publicly exposed.Affected if The page returns application names, server details, or other internal infrastructure information without authentication
A system is affected if it runs Citrix NFuse version 1.6 and the applist.asp page is accessible without authentication, exposing published application names and infrastructure details.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement authentication requirements for the applist.asp page or restrict access via network-level controls; if the page is not business-critical, disable or remove it entirely.
Fix this in Nfuse
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0502 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2002-0502 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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