dbcve.org
Sharepoint FoundationApplication · Microsoft

CVE-2013-1330

HIGH · 10.0 CVSS v2.0 Published 2013-09-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The default configuration of Microsoft SharePoint Portal Server 2003 SP3, SharePoint Server 2007 SP3 and 2010 SP1 and SP2, and Office Web Apps 2010 does not set the EnableViewStateMac attribute, which allows remote attackers to execute arbitrary code by leveraging an unassigned workflow, aka "MAC Disabled 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 confidence

This vulnerability exists because the default configuration of Microsoft SharePoint Portal Server 2003 SP3, SharePoint Server 2007/2010, and Office Web Apps 2010 does not set the EnableViewStateMac attribute. This ASP.NET ViewState MAC (Message Authentication Code) protection is disabled by default, allowing attackers to tamper with view state data and execute arbitrary code by leveraging unassigned workflows.

MitigationEnable the EnableViewStateMac attribute in the SharePoint web.config file and apply the relevant Microsoft security patches for this vulnerability.

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
Sharepoint FoundationApplication
Affected:= 2010
Sharepoint Portal ServerApplication
Affected:= 2003
Sharepoint ServerApplication
Affected:= 2007= 2010
Sharepoint ServicesApplication
Affected:= 2.0= 3.0
Office Web AppsApplication
Affected:= 2010

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
Complete
Integrity
Complete
Availability
Complete

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

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. Identify installed SharePoint version
    Open Windows Control Panel > Programs and Features, or run 'Get-PSSnapin -Name Microsoft.SharePoint.PowerShell' and execute 'Get-SPFarm | Select-Object BuildVersion' to find the exact version number.
    Affected if The installed version matches SharePoint Foundation 2010, SharePoint Portal Server 2003, SharePoint Server 2007/2010, SharePoint Services 2.0/3.0, or Office Web Apps 2010.
  2. Locate SharePoint web.config file
    Navigate to the SharePoint web application directory. Typical paths: C:\Inetpub\wwwroot\wss\VirtualDirectories\<site_guid>\web.config or %SYSTEMROOT%\Inetpub\wwwroot\wss\VirtualDirectories\<port>\web.config. You can also find it via IIS Manager by right-clicking the SharePoint site > Explore.
    Affected if The web.config file exists in the SharePoint web application root directory.
  3. Check EnableViewStateMac attribute setting
    Open the web.config file in a text editor and search for 'EnableViewStateMac'. Look for the attribute value, for example: <pages enableViewStateMac='false' /> or <pages enableViewStateMac='true' />. Also check for the absence of this attribute entirely.
    Affected if The EnableViewStateMac attribute is set to 'false' OR is completely absent from the <pages> section in web.config, which means the default (disabled) is in effect.
  4. Verify ViewState encryption settings
    In the same web.config file, also check for the 'viewStateEncryptionMode' attribute in the <pages> section: <pages viewStateEncryptionMode='Never' />. If this is set to 'Never', the vulnerability impact is heightened.
    Affected if viewStateEncryptionMode is set to 'Never' or is missing (defaulting to Auto), combined with EnableViewStateMac disabled.

You are affected if your SharePoint version matches the affected products AND the EnableViewStateMac attribute is either missing or set to 'false' in the web.config file.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable the EnableViewStateMac attribute in the SharePoint web.config file and apply the relevant Microsoft security patches for this vulnerability.

Recommended fix Moderate confidence

Microsoft SharePoint Server 2013 or later (as SharePoint 2007/2010 are end of life)

  1. Apply the Microsoft security update for CVE-2013-1330 (MS13-030) to affected SharePoint installations
  2. Alternatively, manually enable ViewState MAC validation by setting EnableViewStateMac="true" in the web.config file for SharePoint web applications
  3. For SharePoint 2010, ensure Service Pack 2 is applied as it includes security enhancements
Caveat SharePoint 2007 and 2010 are beyond extended support; upgrading to newer SharePoint versions may require migration planning and compatibility testing

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sharepoint Foundation Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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