# CVE-2013-1161: Denial of service in n/a

> Remote authenticated users can cause a denial of service in Cisco Jabber for Android by sending crafted XMPP presence updates.

- **Severity:** Medium 6.3 (`AV:N/AC:M/Au:S/C:N/I:N/A:C`)
- **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:** 26 Mar 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-75x2-v37c-mx8j

## What is CVE-2013-1161?

CVE-2013-1161 is a medium-severity denial of service vulnerability in n/a, published on 26 Mar 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The XML parser in the Cisco Jabber IM application for Android allows remote authenticated users to cause a denial of service (blocked connection) by leveraging an entry on a Buddy list and sending a crafted XMPP presence update message, aka Bug ID CSCue38383.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2013-1161?

It affects 1 product.


Products: Cisco Jabber Im.

## How do I fix CVE-2013-1161?

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

## Is CVE-2013-1161 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1161 and fix it if it is affected.

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

## Sources

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

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