# CVE-2010-3048: Null dereference in Unified Personal Communicator

> Remote attackers can cause a denial of service in Cisco Unified Personal Communicator due to improper memory allocation validation and failure to free memory.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2020
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-rq69-pg5q-r2x8

## What is CVE-2010-3048?

CVE-2010-3048 is a high-severity vulnerability in Cisco Unified Personal Communicator, published on 16 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco Unified Personal Communicator 7.0 (1.13056) does not free allocated memory for received data and does not perform validation if memory allocation is successful, causing a remote denial of service condition.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2010-3048?

It affects 1 product.


Products: Cisco Unified Personal Communicator.

## How do I fix CVE-2010-3048?

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

## Is CVE-2010-3048 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-3048 and fix it if it is affected.

What it is: CVE-2010-3048 is a high-severity vulnerability in Cisco Unified Personal Communicator, published on 16 Jan 2020. 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-2010-3048 in the wild and no public exploit code.

Affected product: Cisco Unified Personal Communicator. 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-2010-3048/ (Markdown: https://insights.sbomify.com/CVE-2010-3048/index.md)
```

## Sources

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

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