# CVE-2003-1110: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service in Columbia SIP User Agent via crafted INVITE messages.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-qpm3-phwq-qgg4

## What is CVE-2003-1110?

CVE-2003-1110 is a high-severity memory corruption vulnerability in n/a, published on 11 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Session Initiation Protocol (SIP) implementation in Columbia SIP User Agent (sipc) 1.74 and other versions before sipc 2.0 build 2003-02-21 allows remote attackers to cause a denial of service or execute arbitrary code via crafted INVITE messages, as demonstrated by the OUSPG PROTOS c07-sip test suite.

## Which versions are affected by CVE-2003-1110?

It affects 1 product.


Products: Columbia University Sipc.

## How do I fix CVE-2003-1110?

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

## Is CVE-2003-1110 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1110 and fix it if it is affected.

What it is: CVE-2003-1110 is a high-severity memory corruption vulnerability in n/a, published on 11 Mar 2005. 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-2003-1110 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-2003-1110/ (Markdown: https://insights.sbomify.com/CVE-2003-1110/index.md)
```

## Sources

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

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