CVE-2005-3653 in the critical feed json
Heap-based buffer overflow in the iGateway service for various Computer Associates (CA) iTechnology products, in iTechnology iGateway befor…
published 2005-12-31 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-3650
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 18.6%
- EPSS 18.6% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Exploit prediction
18.60% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
securitytracker.com
/id?1015526
vdb-entry, patch
-
osvdb.org
/22688
vdb-entry, patch
-
secunia.com
/advisories/18591
third-party-advisory, patch, vendor-advisory
-
securityfocus.com
/bid/16354
vdb-entry, patch
-
idefense.com
/intelligence/vulnerabilities/display.php?id=376
third-party-advisory, patch, vendor-advisory
-
supportconnectw.ca.com
/public/ca_common_docs/igatewaysecurity_notice.asp
patch, vendor-advisory
-
vupen.com
/english/advisories/2006/0311
vdb-entry, vendor-advisory
-
marc.info
/?l=full-disclosure&m=113803349715927&w=2
mailing-list
- www3.ca.com /securityadvisor/vulninfo/vuln.aspx?id=33778
-
securityreason.com
/securityalert/380
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/24269
vdb-entry
-
securityfocus.com
/archive/1/423288/100/0/threaded
mailing-list
-
securityfocus.com
/archive/1/423403/100/0/threaded
mailing-list
Sources
- CVE List CVE-2005-3653
- NVD CVE-2005-3653
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.