# CVE-2011-3573: Denial of service in n/a

> Remote authenticated users can disrupt availability of Oracle Communications Unified Calendar Server via unspecified vectors.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r6c5-g6jc-872g

## What is CVE-2011-3573?

CVE-2011-3573 is a medium-severity denial of service vulnerability in n/a, published on 18 Jan 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in Oracle Communications Unified 7.0 allows remote authenticated users to affect availability via unknown vectors related to Calendar Server.

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

It affects 1 product.


Products: Oracle Communications Unified.

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

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

## Is CVE-2011-3573 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-3565](https://insights.sbomify.com/CVE-2011-3565/): Other in n/a (medium 4.6)
- [CVE-2011-3574](https://insights.sbomify.com/CVE-2011-3574/): Other in n/a (low 3.3)
- [CVE-2011-3570](https://insights.sbomify.com/CVE-2011-3570/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-3573 is a medium-severity denial of service vulnerability in n/a, published on 18 Jan 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-3573 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-3573/ (Markdown: https://insights.sbomify.com/CVE-2011-3573/index.md)
```

## Sources

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

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