dbcve.org
Personal Web SharingApplication · Apple

CVE-2001-1575

MEDIUM · 5.0 CVSS v2.0 Published 2001-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
Apple Personal Web Sharing (PWS) 1.1, 1.5, and 1.5.5, when Web Sharing authentication is enabled, allows remote attackers to cause a denial of service via a long password, possibly due to a buffer overflow.

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 confidence

Apple Personal Web Sharing versions 1.1, 1.5, and 1.5.5 contain a denial of service vulnerability when Web Sharing authentication is enabled. The vulnerability is triggered by sending a long password, possibly due to a buffer overflow in the authentication handling routine.

MitigationSince this is legacy software from 2001 that is likely no longer supported, the primary mitigation is to upgrade to a supported web server solution or ensure authentication is disabled if Web Sharing must be used.

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
Personal Web SharingApplication
Affected:= 1.1= 1.5= 1.5.5

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
None
Integrity
None
Availability
Partial

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

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. Determine if Apple Personal Web Sharing is installed
    Look for Personal Web Sharing in System Preferences under Web Sharing or check for the application in the Control Panels folder on the Mac system
    Affected if Personal Web Sharing software is present on the system
  2. Identify the installed version of Personal Web Sharing
    Check the version information in System Preferences Web Sharing panel or view the application information (Get Info) in the Finder
    Affected if The version is exactly 1.1, 1.5, or 1.5.5
  3. Verify if Web Sharing authentication is enabled
    Open System Preferences, navigate to Web Sharing, and check the authentication settings for the web server
    Affected if Authentication is enabled in the Web Sharing configuration

The system is affected only if Personal Web Sharing version 1.1, 1.5, or 1.5.5 is installed AND Web Sharing authentication is enabled, making it vulnerable to denial of service via long password input.

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

Since this is legacy software from 2001 that is likely no longer supported, the primary mitigation is to upgrade to a supported web server solution or ensure authentication is disabled if Web Sharing must be used.

Fix this in Personal Web Sharing Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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