# CVE-2011-1280: XML external entity in n/a

> Remote attackers can read arbitrary files via crafted Web Service Discovery files in Microsoft InfoPath and related tools.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Jun 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6fpg-25vc-vc92

## What is CVE-2011-1280?

CVE-2011-1280 is a medium-severity vulnerability in Microsoft Sql Server, published on 16 Jun 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The XML Editor in Microsoft InfoPath 2007 SP2 and 2010; SQL Server 2005 SP3 and SP4 and 2008 SP1, SP2, and R2; SQL Server Management Studio Express (SSMSE) 2005; and Visual Studio 2005 SP1, 2008 SP1, and 2010 does not properly handle external entities, which allows remote attackers to read arbitrary files via a crafted .disco (Web Service Discovery) file, aka "XML External Entities Resolution Vulnerability."

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2011-1280?

It affects 4 products.


Products: Microsoft Office Infopath, Microsoft Sql Server, Microsoft Sql Server Management Studio Express, Microsoft Visual Studio.

## How do I fix CVE-2011-1280?

No fix has been published for CVE-2011-1280 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-1280 being exploited?

There is no known exploitation of CVE-2011-1280 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1280 and fix it if it is affected.

What it is: CVE-2011-1280 is a medium-severity vulnerability in Microsoft Sql Server, published on 16 Jun 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-1280 in the wild and no public exploit code.

Affected product: Microsoft Sql Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-1280/ (Markdown: https://insights.sbomify.com/CVE-2011-1280/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-1280
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-1280
- OSV: https://osv.dev/vulnerability/CVE-2011-1280

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-1280/
Summaries are generated and may contain mistakes; the official description above is the record.