CVE-2004-0379
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 · uneditedMultiple cross-site scripting (XSS) vulnerabilities in Microsoft SharePoint Portal Server 2001 allow remote attackers to process arbitrary web content and steal cookies via certain server scripts.
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 confidenceMultiple cross-site scripting (XSS) vulnerabilities in Microsoft SharePoint Portal Server 2001 allow remote attackers to inject malicious scripts through server scripts, enabling cookie theft and execution of arbitrary web content in user browsers.
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= 2001CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SharePoint Portal Server installationCheck if Microsoft SharePoint Portal Server 2001 is installed on the system by reviewing installed programs in Control Panel > Programs and Features, or by checking the registry key HKLM\SOFTWARE\Microsoft\Office\SharePoint Portal\Setup\ProductVersionAffected if The installed version is SharePoint Portal Server 2001 (any build)
-
Verify server is accessible over HTTP/HTTPSDetermine if the SharePoint Portal Server web interface is exposed to network users by attempting to access the server's URLs (typically port 80/443) from a remote system or reviewing firewall rulesAffected if The SharePoint Portal Server web interface is accessible from network locations where untrusted users could submit input
-
Identify SharePoint Portal Server version numberLocate the exact version by checking the file properties of the main executable (typically in C:\Program Files\Microsoft Office\SharePoint Portal\ or inspecting assembly information), or by accessing the server's About page if availableAffected if The version reported is 2001 (no other versions are listed as affected for this CVE)
-
Check for XSS vulnerability indicatorsReview server logs and HTTP traffic for evidence of malicious script injection attempts, or manually test by submitting script tags in input fields (only in authorized testing)Affected if User-supplied input is reflected in server responses without proper encoding, enabling script execution in browsers
The environment is affected if SharePoint Portal Server 2001 is installed and its web interface is accessible to untrusted users who can submit input that gets rendered without encoding.
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 input validation and output encoding on all user-supplied data, or upgrade from the deprecated SharePoint Portal Server 2001 to a supported SharePoint version as the product is no longer maintained.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-0379 — 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-2004-0379 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