CVE-2000-0174
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 · uneditedStarOffice StarScheduler web server allows remote attackers to read arbitrary files via a .. (dot dot) attack.
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 · moderate confidenceStarOffice StarScheduler web server contains a path traversal vulnerability (CWE-22) that allows remote attackers to read arbitrary files on the host system by using '../' sequences in HTTP requests to manipulate file paths.
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= 5.1CVSS 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.
-
Check if StarScheduler web server is runningLook for processes named 'starschd' or 'StarScheduler' or services listening on common web ports (8080, 8081) that may correspond to StarOfficeAffected if StarScheduler process is active and exposed on a network port
-
Identify StarOffice installation and versionCheck for StarOffice installation directories (common paths: /opt/StarOffice, C:\Program Files\StarOffice, or /usr/local/StarOffice) and look for version files or executables indicating version 5.1Affected if StarOffice version 5.1 is installed on the system
-
Verify StarScheduler service statusCheck if the StarScheduler web server component is enabled - look for configuration files in the StarOffice installation directory that enable the web server module, or check if the service is bound to a network interfaceAffected if StarScheduler is bound to a network-accessible interface (0.0.0.0) rather than localhost only
-
Confirm vulnerability is exploitableTest if HTTP requests containing '../' sequences are processed - attempt a benign request like GET /../../etc/passwd or equivalent to see if path traversal is not sanitizedAffected if The web server returns content from paths outside the intended document root when using '../' sequences
System is affected if StarOffice version 5.1 is installed with StarScheduler web server component running and exposed to network access, allowing directory traversal via '../' in HTTP requests.
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 dataIdentify if StarScheduler is still in production; if found, patch to latest version or disable the service if no longer needed, as this is a 2000-era vulnerability.
- Consultation2.0 h
- Implementation1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0174 — 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-2000-0174 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