# CVE-2005-3653: Memory corruption in n/a

> Remote attackers can execute arbitrary code on CA iTechnology products via a heap-based buffer overflow in the iGateway service triggered by a malicious HTTP request.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pqwm-v5fq-x4gm

## What is CVE-2005-3653?

CVE-2005-3653 is a critical memory corruption vulnerability in n/a, published on 23 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Heap-based buffer overflow in the iGateway service for various Computer Associates (CA) iTechnology products, in iTechnology iGateway before 4.0.051230, allows remote attackers to execute arbitrary code via an HTTP request with a negative Content-Length field.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2005-3653?

It affects 34 products.


Products: Broadcom Brightstor Arcserve Backup, Broadcom Brightstor Arcserve Backup Laptops Desktops, Broadcom Brightstor Portal, Broadcom Brightstor Process Automation Manager, Broadcom Brightstor San Manager, Broadcom Brightstor Storage Resource Manager, Broadcom Etrust Admin, Broadcom Etrust Audit Aries, Broadcom Etrust Audit Irecorder, Broadcom Etrust Identity Minder, Broadcom Etrust Integrated Threat Management, Broadcom Itechnology Igateway, Broadcom Unicenter Asset Portfolio Management, Broadcom Unicenter Autosys Jm, Broadcom Unicenter Service Delivery, Broadcom Unicenter Service Desk, Broadcom Unicenter Service Desk Knowledge Tools, Broadcom Unicenter Service Fulfillment, Broadcom Unicenter Service Metric Analysis, Ca Brightstor Arcserve Backup and 14 more.

## How do I fix CVE-2005-3653?

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

## Is CVE-2005-3653 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-3175](https://insights.sbomify.com/CVE-2008-3175/): Integer overflow in n/a (critical 10.0)
- [CVE-2008-2241](https://insights.sbomify.com/CVE-2008-2241/): Path traversal in n/a (critical 10.0)
- [CVE-2007-5325](https://insights.sbomify.com/CVE-2007-5325/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5326](https://insights.sbomify.com/CVE-2007-5326/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5327](https://insights.sbomify.com/CVE-2007-5327/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3653 and fix it if it is affected.

What it is: CVE-2005-3653 is a critical memory corruption vulnerability in n/a, published on 23 Jan 2006. 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-2005-3653 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-2005-3653/ (Markdown: https://insights.sbomify.com/CVE-2005-3653/index.md)
```

## Sources

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

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