CVE-2000-0346
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 · uneditedAppleShare IP 6.1 and later allows a remote attacker to read potentially sensitive information via an invalid range request to the web server.
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 confidenceAppleShare IP 6.1 and later contains a web server vulnerability where invalid HTTP range requests allow remote attackers to read potentially sensitive files from the server. This is an information disclosure issue stemming from improper handling of HTTP Range headers.
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= 6.1= 6.2= 6.3CVSS 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 AppleShare IP installationCheck if AppleShare IP is installed on the system. On Mac OS X Server, this may be visible in System Preferences under Services, or via the command line using 'sw_vers' or checking for the AppleShare IP application bundle.Affected if AppleShare IP is not installed on the system.
-
Determine the installed AppleShare IP versionLocate the AppleShare IP version information. On Mac OS X Server, this may be found in the application bundle info, or via the command line 'serveradmin' command. Compare the version to the affected ranges: 6.1, 6.2, or 6.3.Affected if The installed version is exactly 6.1, 6.2, or 6.3.
-
Verify the web server component is enabledConfirm that the AppleShare IP web server service is running or enabled. This can be checked via the Server Admin tool, or by attempting to connect to port 80 or 443 on the server.Affected if The AppleShare IP web server is not enabled or not running.
-
Test for HTTP Range header vulnerabilitySend a crafted HTTP request with an invalid Range header to the web server. For example, use a tool like netcat or curl to send a request with 'Range: bytes=-500' or a malformed range header and observe if the server returns file contents outside the intended scope.Affected if The server returns partial or full file contents when an invalid Range header is submitted, indicating the vulnerability is present.
The system is affected if AppleShare IP versions 6.1, 6.2, or 6.3 are installed with the web server component enabled and the server responds to invalid HTTP Range header requests with unauthorized file contents.
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 dataApply the vendor patch or update AppleShare IP to a version that properly validates and restricts HTTP range requests, or configure the web server to deny invalid range requests.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0346 — 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-0346 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