# CVE-2011-1068: Information disclosure in n/a

> Remote attackers can obtain sensitive information by reading encrypted cookies in Azure SDK ASP.NET applications using Full IIS and Web Roles.

- **Severity:** Low 2.6 (`AV:N/AC:H/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:** Not needed
- **Fix available:** No
- **Published:** 23 Feb 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r55g-qvh3-7x6g

## What is CVE-2011-1068?

CVE-2011-1068 is a low-severity vulnerability in n/a, published on 23 Feb 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Microsoft Windows Azure Software Development Kit (SDK) 1.3.x before 1.3.20121.1237, when Full IIS and a Web Role are used with an ASP.NET application, does not properly support the use of cookies for maintaining state, which allows remote attackers to obtain potentially sensitive information by reading an encrypted cookie and performing unspecified other steps.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Microsoft Windows Azure Sdk.

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

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

## Is CVE-2011-1068 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2011-1068 is a low-severity vulnerability in n/a, published on 23 Feb 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-1068 in the wild and no public exploit code.

Affected product: n/a. 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-1068/ (Markdown: https://insights.sbomify.com/CVE-2011-1068/index.md)
```

## Sources

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

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