CVE-2012-1862
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 · uneditedOpen redirect vulnerability in Microsoft Office SharePoint Server 2007 SP2 and SP3 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a crafted URL, aka "SharePoint URL Redirection Vulnerability."
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 confidenceOpen redirect vulnerability in Microsoft Office SharePoint Server 2007 SP2 and SP3 allows remote attackers to redirect users to arbitrary web sites via crafted URLs containing malicious redirect parameters, facilitating phishing attacks.
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= 2007CVSS 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.
-
Identify SharePoint Server versionCheck the installed SharePoint version via PowerShell command: Get-SPFarm | Select-Object BuildVersion, or check Registry: HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\SharePoint versionAffected if The version shown is 2007 (build 12.x) indicating SharePoint Server 2007 is installed
-
Confirm SharePoint Service Pack levelRun: Get-Command *spproduct* or check Add/Remove Programs for 'Microsoft Office SharePoint Server 2007' service pack level (SP2 or SP3)Affected if Service Pack 2 or Service Pack 3 is installed on SharePoint Server 2007
-
Verify SharePoint Web Application is accessibleConfirm the SharePoint web application is running and accessible by accessing the main site URL (e.g., http://servername or the configured web application URL)Affected if SharePoint Server 2007 SP2/SP3 web application is exposed and reachable over HTTP/HTTPS
-
Check for vulnerable redirect parameter usageReview SharePoint site URLs for the presence of redirect parameters (common patterns include 'Source=' or 'RedirectUrl=' in query strings). Use log analysis or URL monitoring to identify if such parameters are being processedAffected if The SharePoint Server accepts and processes redirect parameters in URLs without validating the destination domain
You are affected if Microsoft SharePoint Server 2007 with Service Pack 2 or SP3 is installed and accessible, and the server processes redirect parameters without restricting destinations to trusted domains.
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 Microsoft's security patch for CVE-2012-1862; if patches are unavailable (end-of-life product), implement URL validation or rewrite rules at the web server or WAF level to restrict redirect destinations to trusted domains.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1862 — 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-2012-1862 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