dbcve.org
D2gfxApplication · Deerfield

CVE-2002-1684

MEDIUM · 5.0 CVSS v2.0 Published 2002-12-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
Directory traversal vulnerability in (1) Deerfield D2Gfx 1.0.2 or (2) BadBlue Enterprise Edition 1.5.x and BadBlue Personal Edition 1.5.6 allows remote attackers to read arbitrary files via a ../ (dot dot slash) in the script used to read Microsoft Office documents.

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

Directory traversal vulnerability in Deerfield D2Gfx 1.0.2 and BadBlue (Enterprise 1.5.x and Personal 1.5.6) allows remote attackers to read arbitrary files via '../' sequences in requests to the script used to read Microsoft Office documents.

MitigationUpgrade to patched versions of the affected software; if no patch is available, disable the vulnerable script, apply input validation to reject traversal sequences, and restrict file system access permissions on the web server.

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
D2gfxApplication
Affected:= 1.0.2
BadblueApplication
Affected:= enterprise_1.5= personal_1.5.6_beta

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 if Deerfield D2Gfx or BadBlue web server is running
    Check running processes or services on the system for 'D2Gfx', 'D2gfx', or 'BadBlue' processes. Also check HTTP server headers or banner information on commonly targeted ports (typically port 80 or 8080).
    Affected if Either Deerfield D2Gfx or BadBlue web server software is running on the system
  2. Determine the installed version
    For D2Gfx: Check the installed software version in the application or its About dialog. For BadBlue: Check the version reported in the server banner or in the installed program files. Compare against the affected versions: D2Gfx = 1.0.2, BadBlue Enterprise 1.5.x, BadBlue Personal 1.5.6_beta.
    Affected if The installed version exactly matches 1.0.2 for D2Gfx, or falls within the 1.5.x range for BadBlue Enterprise, or matches 1.5.6_beta for BadBlue Personal
  3. Locate the document reading script
    Identify if the script used to read Microsoft Office documents is accessible on the web server. This is typically a CGI or server-side script that handles Office file requests. Check the web server's document root for scripts that handle document conversion or viewing functionality.
    Affected if The document reading script is present and accessible on the web server
  4. Verify if directory traversal is possible
    Send an HTTP request to the document reading script with '../' sequences in the URL parameters (for example: http://server/script?file=../../../../etc/passwd). If the server returns file contents instead of rejecting the request, the vulnerability is present.
    Affected if The server returns file contents from outside the intended document directory when using '../' traversal sequences in requests to the document script

The environment is affected if either Deerfield D2Gfx 1.0.2 or BadBlue (Enterprise 1.5.x or Personal 1.5.6_beta) is running with the document reading script accessible, and directory traversal '../' sequences return arbitrary file contents.

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 to patched versions of the affected software; if no patch is available, disable the vulnerable script, apply input validation to reject traversal sequences, and restrict file system access permissions on the web server.

Fix this in D2gfx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-1684 — 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-1684 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