CVE-2005-4734 json
Stack-based buffer overflow in IISWebAgentIF.dll in RSA Authentication Agent for Web (aka SecurID Web Agent) 5.2 and 5.3 for IIS allows rem…
published 2005-12-31 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-4727
- cvss
- 6.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 55.3%
- EPSS 55.3% chance of exploitation in 30 days, percentile 99%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
Stack-based buffer overflow in IISWebAgentIF.dll in RSA Authentication Agent for Web (aka SecurID Web Agent) 5.2 and 5.3 for IIS allows remote attackers to execute arbitrary code via a long url parameter in the Redirect method.
Timeline
- First public exploit (Metasploit exploit/windows/isapi/rsa_webagent_redirect)
- Published
Exploit prediction
55.27% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/windows/isapi/rsa_webagent_redirect Microsoft IIS ISAPI RSA WebAgent Redirect Overflow metasploit exploit, good rank, 2005-10-21
- EDB-16358 Microsoft IIS - ISAPI RSA WebAgent Redirect Overflow (Metasploit) remote, 2010-09-20
- osvdb.org http://www.osvdb.org/20151 referenced PoC, tagged "exploit" by a source, unverified
- metasploit.com http://www.metasploit.com/projects/Framework/exploits.html#rsa_iiswebagent_redirect referenced PoC, tagged "exploit" by a source, unverified
- secunia.com http://secunia.com/advisories/17281 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:N/I:P/A:P |
References
-
osvdb.org
/20151
vdb-entry, exploit
-
metasploit.com
/projects/Framework/exploits.html#rsa_iiswebagent_redirect
exploit
-
secunia.com
/advisories/17281
third-party-advisory, exploit, vendor-advisory
-
securityfocus.com
/bid/26424
vdb-entry
- knowledge.rsasecurity.com /dlcpages/rsa_securid/securid_dlc_aaweb.asp
Sources
- CVE List CVE-2005-4734
- NVD CVE-2005-4734
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.