# CVE-2010-1101: Integer overflow in n/a

> Remote attackers can bypass outbound TCP port restrictions in iCab browser via integer overflow, requiring user interaction to visit a malicious site.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Mar 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-939g-r928-2mmf

## What is CVE-2010-1101?

CVE-2010-1101 is a medium-severity vulnerability in n/a, published on 24 Mar 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Integer overflow in Alexander Clauss iCab allows remote attackers to bypass intended port restrictions on outbound TCP connections via a port number outside the range of the unsigned short data type, as demonstrated by a value of 65561 for TCP port 25.

Weakness: CWE-189

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

It affects 1 product.


Products: Icab Icab.

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

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

## Is CVE-2010-1101 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2010-1101 is a medium-severity vulnerability in n/a, published on 24 Mar 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2010-1101 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-2010-1101/ (Markdown: https://insights.sbomify.com/CVE-2010-1101/index.md)
```

## Sources

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

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